Files
i2p.www/www.i2p2/pages/meeting195.html
2008-02-04 18:22:36 +00:00

78 lines
7.0 KiB
HTML

{% extends "_layout.html" %}
{% block title %}I2P Development Meeting 195{% endblock %}
{% block content %}<h3>I2P dev meeting, January 2, 2007</h3>
<div class="irclog">
<p>15:02 &lt; jrandom&gt; 0) hi</p>
<p>15:02 &lt; jrandom&gt; 1) Net status and plans</p>
<p>15:02 &lt; jrandom&gt; 2) Syndie 1.001a</p>
<p>15:02 &lt; jrandom&gt; 3) ???</p>
<p>15:02 &lt; jrandom&gt; 0) hi</p>
<p>15:02 * jrandom waves</p>
<p>15:02 &lt; jrandom&gt; weekly status notes posted up on http://dev.i2p.net/pipermail/i2p/2007-January/001325.html</p>
<p>15:03 * mrflibble waves to jrandom</p>
<p>15:03 * jrandom expects most are still nursing their hangovers, so we'll do this quietly</p>
<p>15:04 &lt; jrandom&gt; lets jump on in to 1) Net status and plans</p>
<p>15:05 &lt; jrandom&gt; as mentioned in the notes, there's been a lot covered, but we've got our work cut out for us this year</p>
<p>15:05 &lt; jrandom&gt; we'll want to discuss the various tradeoffs though and make sure the most appropriate ones are taken to support the specific functionality we're driving towards</p>
<p>15:06 &lt; jrandom&gt; but, we'll see how it goes as things progress</p>
<p>15:06 &lt; jrandom&gt; for the time being though, the net seems fairly steady-state, which is Good</p>
<p>15:07 &lt; jrandom&gt; anyone have anything they'd like to bring up re: net status and plans?</p>
<p>15:09 &lt; jrandom&gt; if not, lets hop on over to 2) Syndie 1.001a</p>
<p>15:09 &lt; z^z&gt; anything I can work on on the net - netdb or tunnels?</p>
<p>15:09 * jrandom hops back</p>
<p>15:10 &lt; z^z&gt; I know we have questions on netdb propagation and on cpu usage but I would need a good pointer to get started</p>
<p>15:11 &lt; z^z&gt; think about it anyway</p>
<p>15:11 &lt; jrandom&gt; z^z: netDb search when the # of known/reachable floodfill peers reaches 0 needs to, most likely, do a random iterated walk across known peers</p>
<p>15:12 &lt; z^z&gt; ok thx will poke around and ask questions later</p>
<p>15:12 &lt; jrandom&gt; perhaps a new flag on the netDb lookup message asking for "give me some floodfill peers"</p>
<p>15:12 &lt; jrandom&gt; kickass z^z! that'd likely have a substantial impact for new users - let me know if you run into any trouble</p>
<p>15:13 &lt; z^z&gt; ha that will take me into new territory sounds like fun for the new year</p>
<p>15:13 &lt; jrandom&gt; :)</p>
<p>15:14 &lt; bar&gt; "do not delete floodfill peer router infos from netdb if there are too few of them" &lt;-- does anyone remember if this one got into cvs or not?</p>
<p>15:15 &lt; jrandom&gt; nope</p>
<p>15:15 &lt; jrandom&gt; or, not that i recall...</p>
<p>15:16 &lt; bar&gt; okie</p>
<p>15:17 &lt; jrandom&gt; (a great spot for that would be KademliaFloodfillNetworkFacade::dropAfterLookupFailed)</p>
<p>15:18 &lt; jrandom&gt; er, KademliaNetworkDatabaseFacade, that is (floodfill extends it)</p>
<p>15:20 &lt; jrandom&gt; (there's also a few bits in the DatabaseLookupMessage that could be used to flag 'send me floodfill peers' - the 'tunnelSpecified' is a boolean, but transferred in a full byte)</p>
<p>15:21 &lt; jrandom&gt; ok, anything else on 1) Net status and plans?</p>
<p>15:23 * jrandom resumes the hopping to 2) Syndie 1.001a </p>
<p>15:24 &lt; jrandom&gt; she's coming soon, maybe in a day or two. lots of bugfixes and cleanup (thanks to everyone helping!), with more details in the announcement when its released</p>
<p>15:25 &lt; jrandom&gt; thats about it to mention on that, though (but if you're using the new syndie, you can follow up on the latest discussions there ;)</p>
<p>15:27 &lt; jrandom&gt; anyone have anything to bring up on syndie 1.001a, or shall we skip on over to 3) ???</p>
<p>15:27 &lt; jrandom&gt; anyone have anything else they'd like to discuss in the meeting?</p>
<p>15:28 &lt;+fox&gt; &lt;covracer&gt; are you still not in favor of an ebuild?</p>
<p>15:29 &lt; jrandom&gt; for syndie, or i2p? </p>
<p>15:29 &lt;+fox&gt; &lt;covracer&gt; i2p</p>
<p>15:29 &lt; jrandom&gt; correct, i am still not in favor of an ebuild</p>
<p>15:29 &lt; jrandom&gt; (thank you for the offer/suggestion though!)</p>
<p>15:30 &lt; jrandom&gt; i2p's problems are not related to the size of the network, so increasing the size will not address them</p>
<p>15:30 &lt; jrandom&gt; instead, it will just force more people to deal with the problems and the upgrade path to address them</p>
<p>15:30 &lt;+fox&gt; &lt;covracer&gt; yeah</p>
<p>15:31 &lt;+fox&gt; &lt;covracer&gt; alex has done some good work though on an ebuild</p>
<p>15:31 &lt;+fox&gt; &lt;covracer&gt; it's in the java-experimental-migration overlay iirc</p>
<p>15:31 &lt;+fox&gt; * godmode0 is back (gone 01:57:51)</p>
<p>15:32 &lt;+fox&gt; &lt;covracer&gt; well at any rate it depends on lots improvements in gentoo's handling of java and jetty</p>
<p>15:32 &lt;+fox&gt; &lt;covracer&gt; and won't get into the main tree any time soon</p>
<p>15:33 &lt; jrandom&gt; cool (that alex's work is going well), and hopefully we'll get i2p to the point where pushing it to main will be a great thing :)</p>
<p>15:34 &lt;+fox&gt; &lt;covracer&gt; would a ebuild for syndie be welcomed or should it also be postponed?</p>
<p>15:34 * jrandom wonders how much shakeup there is going to be in java handling once the sun jvm & libs go gpl</p>
<p>15:35 &lt; jrandom&gt; syndie will hopefully be ready for full production use in a matter of months, with beta in maybe a month, so looking at an ebuild there would be great</p>
<p>15:36 &lt; jrandom&gt; when syndie goes production i'd like to make it as easy as possible for people to use - apt-get, emerge, rpm, etc</p>
<p>15:36 &lt;+fox&gt; &lt;covracer&gt; okay, I'll see if I can hack an ebuild together this week of vacation--I've got nothing better to do</p>
<p>15:36 &lt; jrandom&gt; kickass, thanks covracer!</p>
<p>15:37 &lt;+fox&gt; &lt;covracer&gt; easy installation is very important for wide adoption</p>
<p>15:37 &lt; jrandom&gt; (and let me know if you run into any bits that could be simplified 'upstream' - i'd like to make packaging as transparent as possible)</p>
<p>15:37 &lt; jrandom&gt; aye, definitely</p>
<p>15:38 &lt;+fox&gt; &lt;covracer&gt; alright, although I'm only vaguely aware of the best practices of ebuild writing, not being a dev myself or really all that active on the coding front</p>
<p>15:40 &lt; jrandom&gt; cool, you likely know more about ebuild writing than I though :) good luck, and thanks</p>
<p>15:40 &lt; jrandom&gt; ok, anyone have anything else they'd like to bring up for the meeting?</p>
<p>15:40 &lt; bar&gt; well, i think an official post in cervantes' syndie forum and the old syndie wouldn't hurt, if/when you're looking for more testers for the new syndie</p>
<p>15:40 &lt; bar&gt; except for the last meeting log, i don't think there has been much mentioning of the alpha release, many i2p users simply haven't heard the news, methinks</p>
<p>15:41 &lt; jrandom&gt; good idea - i'll spam 'em when 1.001a is out</p>
<p>15:42 &lt; bar&gt; alritey :)</p>
<p>15:47 &lt; jrandom&gt; ok, if there isn't anything else for the meeting...</p>
<p>15:47 * jrandom winds up</p>
<p>15:47 * jrandom *baf*s the meeting closed</p>
</div>
{% endblock %}