14:05 <@jrandom> 0) hi
14:05 <@jrandom> 1) Net status
14:05 <@jrandom> 2) SSU status
14:05 <@jrandom> 3) Roadmap update
14:05 <@jrandom> 4) Q status
14:05 <@jrandom> 5) ???
14:05 <@jrandom> 0) hi
14:05 * jrandom waves
14:05 <@jrandom> weekly status notes (posted a sec ago) up @ http://dev.i2p.net/pipermail/i2p/2005-April/000708.html
14:06 * maestro^ beatboxes
14:06 <+cervantes> evening
14:06 <+protokol> susi23: you there?
14:06 <@jrandom> while y'all read those exciting notes, lets jump on in to 1) net status
14:06 <+protokol> oops, meeting
14:07 <@jrandom> i dont really have much to add beyond what it says though. new release tomorrow, most likely, with the fixes incorporated so far, as well as some neat new contributions
14:08 <@jrandom> anyone have any comments or concerns w/ the net status &&/|| the upcoming 0.5.0.7?
14:10 <@jrandom> if not, moving on to 2) SSU status
14:10 <+maestro^> i've been getting some of these errors: Wanted to build 2 tunnels, but throttled down to 0, due to concurrent requests (cpu overload?)
14:10 <@jrandom> ah, yeah, thats the tunnel throttling issue
14:10 <+protokol> will it support ftp?
14:10 <@jrandom> its a bit... overzealous
14:10 <+protokol> jk jk
14:10 <@jrandom> !thwap protokol
14:10 <+maestro^> heh, ok
14:12 <@jrandom> ok, as for SSU, there's been a bunch of updates in the last week, and still further changes locally not yet committed
14:13 <@jrandom> i havent been making any history.txt entries for the updates though, since its not used by anyone yet, so only people on the i2p-cvs list get to read the exciting details ;)
14:14 <@jrandom> otoh, in the last few days after things have been pretty much working, while streamlining its operation i've found some choke points in the SDK
14:14 <@jrandom> (and in the jobQueue). i've pulled those out now, locally, and testing continues.
14:15 <@jrandom> we may have some alphas for the SSU transport this week, more likely this weekend though
14:15 <@jrandom> not much more i have to say on that - anyone have any questions?
14:16 <+Ragnarok> how much impact did the choke points have?
14:17 <@jrandom> well, it varies - i'm measuring the impact upon the live net now, but on my local ssu network, two minor tweaks gave more than an order of magnitude improvement
14:17 <@jrandom> but i don't expect that to occur on the live net
14:17 <+Ragnarok> yikes
14:18 <+Ragnarok> heh, ok
14:18 <@jrandom> (at least, not until we move to 0.6 ;)
14:20 <@jrandom> ok, following that lead, lets move to 3) Roadmap update
14:21 <@jrandom> as mentioned in the notes, the dates and revs on the roadmap have been moved around. 0.5.1 dropped, with the further tunnel modifications pushed to 0.6.1
14:21 <+cervantes> 3) Roadmap Skew
14:21 <@jrandom> heh
14:22 <@jrandom> yeah, when you run a fast CPU, it skews the clock more frequently. similary... ;)
14:22 <@jrandom> ^ry^rly
14:23 <+cervantes> ooh is that a hint of an ego? I never would have thought! :)
14:23 <@jrandom> but yeah, unfortunately, a 0.6 rev in april just isnt going to happen
14:23 <@jrandom> hehe
14:23 <@jrandom> cervantes: dont worry, its tempered by the fact that its taken 2 years to get this far ;)
14:25 <@jrandom> we will probably have some -X builds for people to brea^Wtest SSU on the live net while i'm offline, but there won't be a 0.6 rev until i'm back
14:25 <@jrandom> (and, like last year, i have no idea how long it'll take to get hooked up again, but hopefully less than a month)
14:25 <+cervantes> heh, if anyone here is a little deserving of self-appreciation then I guess it would be you ;-)
14:26 <+polecat> Where you going, jrandom ?
14:27 <+cervantes> $somewhere
14:27 <@jrandom> dunno
14:27 <@jrandom> (thankfully, $somewhere is a runtime expression ;)
14:27 <+cervantes> jrandom: do you envisage a months downtime?
14:27 <+maestro^> jr: walk around the neighborhood and setup a wireless relay network from someone else's link ;]
14:27 <@jrandom> depends on the internet situation where i end up cervantes.
14:28 <@jrandom> i'm quite likely to hop online occationally of course, though
14:28 <+protokol> polecat: lol
14:28 <+cervantes> I would have though you would have got the relocation class method pretty slick by now
14:28 < Teal`c> lets move to .6 now and work the bugs out as we go along
14:28 <+cervantes> *thought
14:28 <+cervantes> cool, Teal'c you can do Q&A
14:29 <@jrandom> Teal`c: "work the bugs out" == fix the code == (have a coder who knows the code to fix it)
14:29 < Teal`c> ya, I'd like that.
14:29 < Teal`c> I know some perl
14:29 * cervantes sets bugzilla > tealc@mail.i2p
14:29 <@jrandom> word Teal`c, we can always use some help testing
14:30 <@jrandom> especially in automation of tests
14:31 <@jrandom> ok, anything else on 3) or shall we move to 4) Q status
14:31 <+polecat> I see. Good luck getting stable Internet back.
14:31 <+ant> <jrandom> hrm, aum seems to be sleeping still
14:31 <@jrandom> thanks. i'm sure i'll find a way ;)
14:32 <@jrandom> ok, I don't really have much more to add beyond whats in the status notes
14:32 <@jrandom> aum's code is in cvs now though, so the hardcore can grab it and start hacking
14:32 <+maestro^> shweet
14:33 <@jrandom> yeah, definitely. currently things are all GPL (since one component links against I2PTunnel), but I hear aum is working on some refactoring so it'll end up LGPL
14:34 <@jrandom> (but dont ask me what the implications of licensing is when it comes to xmlrpc ;)
14:34 <@jrandom> ok, anyone have anything on 4) to bring up?
14:36 <@jrandom> ok, if not, moving on to 5) ???
14:36 <@jrandom> anyone have anything else to bring up for the meeting?
14:36 <+polecat> I would like to say a few words for this occasion.
14:37 <+polecat> Hinkle finkle dinkle doo.
14:37 <@jrandom> mmmhmm.
14:37 <@jrandom> ok, anyone have anything to bring up in a human language? :)
14:38 < defnax> what moving on 5?
14:39 <+maestro^> long live spacerace! long live i2p!
14:39 <@jrandom> hmm defnax?
14:41 < defnax> on 5 o'clock in the morning?
14:41 < defnax> in 5 hours?
14:41 <+cervantes> wrt xmlrpc, copyright is retained on the specification, but no restrictions placed upon implementation
14:42 <@jrandom> defnax: agenda item 5: "???", where we discuss other issues
14:43 <+maestro^> jr: have you committed those optimization changes?
14:43 <@jrandom> cervantes: my jab related to the question of whether using a GPL'ed app's xmlrpc API is viral (but merely a rhetorical question)
14:43 <@jrandom> maestro^: nope
14:43 * jrandom tests before committing
14:43 <+maestro^> excellent! whats your eta on that?
14:44 <@jrandom> later tonight, maybe, else tomorrow for the release
14:45 <@jrandom> ok, if there's nothing else
14:45 * jrandom winds up
14:45 * jrandom *baf*s the meeting closed