66 lines
5.2 KiB
HTML
66 lines
5.2 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}I2P Development Meeting 155{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, November 8, 2005</h3>
|
|
<div class="irclog">
|
|
<p>15:21 < jrandom> 0) hi</p>
|
|
<p>15:21 < jrandom> 1) Net status / short term roadmap</p>
|
|
<p>15:21 < jrandom> 2) I2Phex</p>
|
|
<p>15:21 < jrandom> 3) I2P-Rufus</p>
|
|
<p>15:21 < jrandom> 4) I2PSnarkGUI</p>
|
|
<p>15:21 < jrandom> 5) Syndie</p>
|
|
<p>15:22 < jrandom> 6) ???</p>
|
|
<p>15:22 < jrandom> 0) hi</p>
|
|
<p>15:22 * jrandom waves</p>
|
|
<p>15:22 < jrandom> weekly status notes up at http://dev.i2p.net/pipermail/i2p/2005-November/001206.html</p>
|
|
<p>15:22 * bar mumbles greetings from behind his/her false(?) beard</p>
|
|
<p>15:23 < jrandom> ok, jumping into 1) Net status / short term roadmap</p>
|
|
<p>15:23 < jrandom> Not much to say beyond whats in the mail - hopefully a new release later this week, or this weekend</p>
|
|
<p>15:24 < jrandom> there are some new optimizations in cvs which should help improve reliability, and its worked pretty well in the tests i've done, but it probably won't have much of an impact until it gets widespread deployment</p>
|
|
<p>15:25 < jrandom> I also haven't picked an arbitrary throughput level I want to reach before continuing on to 0.6.2, though my gut instinct tells me that optimizations should continue until I can justify the choke points by per-router hop delays</p>
|
|
<p>15:26 < jrandom> right now, however, that isn't our choke point, so there's still work to be done.</p>
|
|
<p>15:26 < jrandom> I don't have much more to add on that front - anyone have any questions/comments/concerns?</p>
|
|
<p>15:28 < jrandom> ok, if not, moving on to 2) I2Phex</p>
|
|
<p>15:28 < jrandom> I don't have much more to add here beyond whats been said in the email. There have been a bunch of discussions on the forum too, though, so swing by there for more news and ranting </p>
|
|
<p>15:31 < jrandom> ok, if not, jumping on over to 3) I2P-Rufus</p>
|
|
<p>15:31 < jrandom> this bullet point was really just me repeating a rumor, but we'll see how things go</p>
|
|
<p>15:32 < jrandom> Rawn / defnax: do you have anything to add?</p>
|
|
<p>15:35 < tealc_> whats i2p-rufus ?</p>
|
|
<p>15:35 < jrandom> a port of the rufus bittorrent client for I2P (http://rufus.sourceforge.net/)</p>
|
|
<p>15:36 < jrandom> ok, if there's nothing else, we can jump to another quick rumor reportage - 4) I2PSnarkGUI</p>
|
|
<p>15:37 < jrandom> I don't have much to add to this beyond saying "hey, cool" :)</p>
|
|
<p>15:38 <+bar> yeah, looks nice</p>
|
|
<p>15:38 <@frosk> snark is Y.A. BT client?</p>
|
|
<p>15:38 < jrandom> yeah, but snark is a bittorrent client bundled with I2P :)</p>
|
|
<p>15:38 <@frosk> oh yeah, right :)</p>
|
|
<p>15:38 < jrandom> (currently a command line tool, but multitorrent and web interface is on the way, though not imminent)</p>
|
|
<p>15:39 <+fox> <ZipTie> who was doing the work for the rarest-first fetching strategy for snark? did that ever get done?</p>
|
|
<p>15:39 < jrandom> yeah, Ragnarok implemented that</p>
|
|
<p>15:39 < jrandom> its in the current I2PSnark</p>
|
|
<p>15:39 <+fox> <ZipTie> cool</p>
|
|
<p>15:40 < jrandom> aye, quite</p>
|
|
<p>15:41 <+fox> <ZipTie> is i2p-bt going to be decomissioned then in favor of either rufus or snark?</p>
|
|
<p>15:41 < jrandom> thats for users to decide</p>
|
|
<p>15:42 <+fox> <ZipTie> or maintainability :)</p>
|
|
<p>15:42 < jrandom> personally, I think if snark gets a web interface, integrated with the router console, multitorrent capabilities, and offers equivilant performance as the others, it'll be in good shape</p>
|
|
<p>15:43 < jrandom> but really, what you mention is the key - who does the maintenance and development is the driving force</p>
|
|
<p>15:43 * jrandom does not maintain python apps</p>
|
|
<p>15:44 < jrandom> ok, if there's nothing else on 4, lets move on to 5) Syndie</p>
|
|
<p>15:45 < jrandom> I've been doing some usability research into how best to proceed, and I think we've got a pretty viable UI on the way, but if you've got an opinion, post it up on syndie or the forum and we can hopefully take it into consideration</p>
|
|
<p>15:46 < tealc_> ahh, i thought i2phex was java.. the stuff on the forums offers .exe installers and .exe's in zips</p>
|
|
<p>15:47 < jrandom> i2phex is java</p>
|
|
<p>15:47 < jrandom> and the .exe works with any platform that java works on</p>
|
|
<p>15:47 < jrandom> java -jar i2phex.exe</p>
|
|
<p>15:47 < jrandom> (yes, really)</p>
|
|
<p>15:49 < jrandom> (cough)</p>
|
|
<p>15:49 < jrandom> dust: anything to add re: syndie stuff?</p>
|
|
<p>15:50 < dust> nope</p>
|
|
<p>15:50 < jrandom> ok cool. unless anyone else has anything on it, lets jump to ol' faithful: 6) ???</p>
|
|
<p>15:50 < jrandom> anyone have anything else they want to bring up for the meeting?</p>
|
|
<p>15:53 <+fox> <reliver> is the paella ready ? ;-)</p>
|
|
<p>15:53 * jrandom grabs a spork</p>
|
|
<p>15:54 < jrandom> (on that note...)</p>
|
|
<p>15:54 <+fox> <reliver> and the cat still smells like cats ;?)</p>
|
|
<p>15:54 * jrandom windos up</p>
|
|
<p>15:54 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |