I2P dev meeting, April 26, 2005

Quick recap

  • Present:

bla, duck, jrandom, jrandom2p, laberhorst, Lorie, smeghead,

完全な IRC ログ

14:10 <@jrandom> 0) hi
14:10 <@jrandom> 1) Net status
14:10 <@jrandom> 2) SSU status
14:10 <@jrandom> 3) Unit test bounty
14:10 <@jrandom> 4) ???
14:10 <@jrandom> 0) hi
14:10  * jrandom waves
14:10 <@jrandom> (late) weekly status notes are up @ http://dev.i2p.net/pipermail/i2p/2005-April/000723.html
14:10 < bla> hi
14:11 <@jrandom> while y'all read that tome, lets jump on into 1) Net status
14:12 <@jrandom> the previous set of problems we saw with some eepsites going offline in seems to be resolved, though there are a few people who have been running into other problems with their sites
14:13 <@jrandom> i've seen some increased torrent activity at some trackers as well, though it hasn't caused any problems on irc from what i can tell
14:13 < laberhorst> net status: fairly well beside the not reachable prob :-)
14:13 <@jrandom> heh
14:13 <@jrandom> yeah, i'm stil not sure whats going on with your site. we can debug further after the meeting
14:14 <@jrandom> other than that, anyone else have any questions/comments/concerns wrt the net status /
14:16 <@jrandom> ok, if not, moving on to 2) SSU status
14:16 <@jrandom> [insert hand waving here]
14:17 < Lorie> Good morning.
14:17 <@jrandom> i know, i'm dragging my heels a bit by not pushing it out faster, and it does perform really well as is.  still, there are some issues i'm not comfortable with yet, so y'all will have to bear with me a bit during this testing
14:18 <@smeghead> i commend you for not foisting crapware on us :)
14:18 <@jrandom> i'm hoping this week we'll have some further live net tests though (fingers crossed)
14:19 <@jrandom> well, i've foisted enough bugs on y'all so far
14:19 < Lorie> you're dragging your heels, are you ?
14:19  * Lorie eyes smeghead
14:19 < bla> jrandom: Just to make things clear: We could even have an intermediate period in which clients can be both UDP and TCP?
14:20 <@jrandom> bla: yes.  i've got a test network now with some TCP-only and some both TCP and UDP.  its kind of neat running the tunnels through both :)
14:20 <@jrandom> the live net will actually handle that as well, ignoring any UDP addresses (for people who don't yet support it)
14:20 <@smeghead> and that's given us lots of protein, but we don't want to over-indulge
14:21 < bla> jrandom: Nice! That's good for the transition
14:23 <@jrandom> aye, thats the hope.  still, there's lots of work to do[/obligatory]
14:23 <@jrandom> while our transport is SSU - "SEMIreliable Secure UDP" - we still need to try to be kind of reliable
14:24 <@jrandom> i've followed a bunch of research out there on the net, watching whats worked best, and while we could just be lazy and fire & forget, there's a lot to be gained by doing some simple tcp-esque reliability, which is what i'm hacking on now
14:25 <@jrandom> otoh, since its just semireliable, if it doesn't get ACKed quickly we can just drop the message, rather than drop the connection
14:26 < Lorie> yes
14:26 < Lorie> do be reliable; time is a luxury one has
14:27 <@jrandom> thats about all i have to bring up for 2) SSU status.  anyone have any questions/comments/concerns, or shall we move on to 3) Unit test bounty?
14:28 < jrandom2p> consider us moved
14:29 < jrandom2p> ok, duck posted up a good summary about whats up and the importance of the unit test bounty the other day, and there's a lot of detail referenced from the site.
14:30 < jrandom2p> this is a good chance for someone to dig into i2p a bit and get a little cash back in the process ;)
14:30 < jrandom2p> but anyway, y'all can read all that stuff.  does anyone have any questions on it?
14:31 < jrandom2p> ok, if not, moving on to 4) ???
14:32 <@smeghead> anyone tried that emma code coverage suite?
14:32 < jrandom2p> there's been a lot of various things going on in the last week, though i'm not sure whats ready for discussion yet.  anyone have anything they want to bring up?
14:33 < jrandom2p> not i
14:33 <@duck> *hick*
14:34 <@smeghead> either duck is inebriated, or he has spotted a redneck
14:34 <@duck> !former
14:35 < jrandom2p> (to evaluate as a shell command or c/java... ;)
14:36 < jrandom2p> anyone else have anything to bring up for the meeting?
14:36  * jrandom2p likes short meetings, leaves more time for coding
14:36 <@smeghead> and drinking apparently :)
14:36 <@duck> & drinking
14:37 <@smeghead> bah lag
14:37 < jrandom2p> heh
14:38 < jrandom2p> ok, time to get back to dri^Wworking
14:38  * jrandom2p winds up
14:38  * jrandom2p *baf*s the meeting closed