70 lines
5.3 KiB
HTML
70 lines
5.3 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}Pages/meeting117.html{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, November 23, 2004</h3>
|
|
<div class="irclog">
|
|
<p>13:03 < jrandom> 0) hi</p>
|
|
<p>13:03 < jrandom> 1) Net status</p>
|
|
<p>13:03 < jrandom> 2) Streaming lib</p>
|
|
<p>13:04 < jrandom> 3) 0.4.2</p>
|
|
<p>13:04 < jrandom> 4) Addressbook.py 0.3.1</p>
|
|
<p>13:04 < jrandom> 5) ??? </p>
|
|
<p>13:04 < jrandom> 0) hi</p>
|
|
<p>13:04 * jrandom waves</p>
|
|
<p>13:04 <+postman> hi :)</p>
|
|
<p>13:04 < jrandom> weekly status notes posted up to http://dev.i2p.net/pipermail/i2p/2004-November/000490.html</p>
|
|
<p>13:05 < jrandom> well, might as well jump on in to 1) net status</p>
|
|
<p>13:05 < jrandom> i dont have much to add to this that wasn't in the email</p>
|
|
<p>13:05 < jrandom> anyone have anything they want to bring up wrt the network status over the last week?</p>
|
|
<p>13:06 < jrandom> if not, we can jump on down to 2) streaming lib</p>
|
|
<p>13:06 < jrandom> there's lots of info in the mail about this, so i'll let y'all digest a bit</p>
|
|
<p>13:07 < jrandom> while the new lib will improve lots of things, the most important (imho) is its resiliance and handling of congestion</p>
|
|
<p>13:08 < jrandom> especially the latter, as we've seen how things get funky with the old lib under heavy congestion</p>
|
|
<p>13:08 < jrandom> there's also a lot of things left out of the lib though, places for people to experiment and optimize further</p>
|
|
<p>13:09 < jrandom> anyone have any questions wrt this, or have we been beating a dead horse by discussing it each week for the last month? ;)</p>
|
|
<p>13:10 <+Ragnarok> we'll call that a yes</p>
|
|
<p>13:10 < jrandom> heh</p>
|
|
<p>13:10 < jrandom> ok, moving on to 3) 0.4.2</p>
|
|
<p>13:10 < jrandom> out real soon, just doing some minor updates to the install process at the moment</p>
|
|
<p>13:11 <+postman> yesss</p>
|
|
<p>13:11 <+postman> :)</p>
|
|
<p>13:11 < jrandom> the updated install proc will be a bit nicer for people, addressing the most common user errors</p>
|
|
<p>13:12 < jrandom> (since no one ever reads the text on the router console ;)</p>
|
|
<p>13:12 < jrandom> but that should be ready in the next day or two, so with some testing we should have a release out by friday</p>
|
|
<p>13:12 < jrandom> (if not sooner)</p>
|
|
<p>13:13 < jrandom> as i mentioned in the mail though, its both backwards compatbile and /not/ backwards compatible</p>
|
|
<p>13:13 <+Ragnarok> awesome</p>
|
|
<p>13:13 < jrandom> does anyone have any strong preferences as to how we should do that tap dance?</p>
|
|
<p>13:13 < jrandom> should we just push out 0.4.2 and let people upgrade when they notice they cant reach any eepsites?</p>
|
|
<p>13:14 < jrandom> (or will they uninstall it and say "dood i2p sux0rz")</p>
|
|
<p>13:14 * jrandom neither</p>
|
|
<p>13:15 <+Ragnarok> I'd say mark it as not compatible. It's always better to be explicit.</p>
|
|
<p>13:15 < jrandom> well, the docs and announcement will say not compatible, mandatory upgrade in big bold letters</p>
|
|
<p>13:16 <+Ragnarok> no reason to send mixed messages, then</p>
|
|
<p>13:16 < jrandom> aye</p>
|
|
<p>13:16 < jrandom> though we would be able to tunnel route through those old peers</p>
|
|
<p>13:16 < jrandom> i dunno, we've got a few days to finalize the decision anyway</p>
|
|
<p>13:17 < jrandom> just something to think about, and a WARNING to people that they'll NEED TO UPGRADE TO 0.4.2 </p>
|
|
<p>13:17 < jrandom> :)</p>
|
|
<p>13:18 < jrandom> ok, anyone have any questions/comments/concerns wrt 0.4.2, or shall we move on to 4) addressbook.py?</p>
|
|
<p>13:18 < jrandom> consider us moved</p>
|
|
<p>13:18 < jrandom> Ragnarok: wanna give us an update?</p>
|
|
<p>13:20 <+Ragnarok> sure. Minor update released yesterday. Fixes some bugs on windows, and doesn't violently die if the proxy isn't there. Only really notable thing is that this will probably be the last release for this version, barring a giant bug.</p>
|
|
<p>13:20 < jrandom> ok cool</p>
|
|
<p>13:21 < jrandom> avoiding violent death is always a nice feature to have</p>
|
|
<p>13:21 < lba> hi folks</p>
|
|
<p>13:21 <+Ragnarok> I'm planning on redesigning (just designing, really) it from the ground up based on jrandom's thoughts from the mailing list. Possibly in java too, if I can figure out the xml parsing and http stuff I'll have to do.</p>
|
|
<p>13:21 < jrandom> wikked :)</p>
|
|
<p>13:21 < jrandom> 'lo lba</p>
|
|
<p>13:22 <+Ragnarok> well, that's all. Carry on.</p>
|
|
<p>13:22 < jrandom> cool, thanks for the update</p>
|
|
<p>13:22 < jrandom> ok if there's nothing else on that, we can move on at a blazing pace to 5) ???</p>
|
|
<p>13:22 < jrandom> anyone else have something they want to bring up?</p>
|
|
<p>13:23 <+Ragnarok> anyone else here?</p>
|
|
<p>13:23 < jrandom> heh, yeah, we dont have our usual malcontents ;)</p>
|
|
<p>13:24 < jrandom> then again, they'll show up to read the logs on the site later [yeah, i mean *YOU*]</p>
|
|
<p>13:24 < jrandom> ok, i think thats probably the shortest meeting we've had in over a year</p>
|
|
<p>13:25 < jrandom> might as well wraper 'er up</p>
|
|
<p>13:25 * jrandom winds up</p>
|
|
<p>13:25 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |