Files
i2p.www/www.i2p2/pages/meeting34.html
2009-03-01 05:05:18 +00:00

137 lines
9.0 KiB
HTML

{% extends "_layout.html" %}
{% block title %}I2P Development Meeting 34{% endblock %}
{% block content %}
<h3>I2P (invisiblenet) Development Meeting 34</h3>
<div class="irclog">
Courtesy of <a href="http://www.archive.org/">the wayback machine</a>.
<p>
<p>--- Log opened Tue Mar 18 20:14:29 2003
<p>20:15 -!- Topic for #iip-dev: IIP Meeting - logfiles: http://mids.student.utwente.nl/~mids/iip/
<p>20:15 [Users #iip-dev]
<p>20:15 [ jeremiah] [ logger] [ mids] [ UserX]
<p>20:15 -!- Irssi: #iip-dev: Total of 4 nicks [0 ops, 0 halfops, 0 voices, 4 normal]
<p>20:15 -!- Irssi: Join to #iip-dev was synced in 5 secs
<p>20:17 -!- mode/#iip-dev [+o mids] by Trent
<p>22:00 &lt; nop&gt; hi
<p>22:00 &lt;@mids&gt; Tue Mar 18 21:00:10 UTC 2003
<p>22:00 &lt; hezekiah&gt; Hi. :)
<p>22:00 &lt;@mids&gt; HEllo
<p>22:00 &lt;@mids&gt; so
<p>22:01 &lt;@mids&gt; whats on the agenda?
<p>22:01 &lt; hezekiah&gt; I have no clue.
<p>22:01 &lt; armpit&gt; howdy
<p>22:01 &lt; hezekiah&gt; Hi
<p>22:01 &lt;@mids&gt; ok
<p>22:01 &lt; armpit&gt; mind if i lurk around? :)
<p>22:01 &lt;@mids&gt; then lets just keep a question round
<p>22:01 &lt;@mids&gt; btw, Freenet 0.5.1 is out
<p>22:01 &lt; hezekiah&gt; Cool. :)
<p>22:02 &lt; hezekiah&gt; Maybe one of these days I'll try using it. :)
<p>22:02 &lt;@mids&gt; so, any IIP questions?
<p>22:02 &lt; Hitman&gt; quick run down of current status would be nice nop
<p>22:02 &lt; Hitman&gt; so we can get up to speed on what's happening with it all
<p>22:03 &lt;@mids&gt; good point
<p>22:03 &lt; nop&gt; hold
<p>22:03 * hezekiah turns on beautiful classical music those tech-support hotlines play while we wait for them ...
<p>22:04 * Hitman shudders as teh memories flood back
<p>22:05 * mids runs out of breath
<p>22:06 * mids dies
<p>22:06 &lt; hezekiah&gt; Well, meanwhile I think it should be noted that some people don't appear to have remembered the meeting starts 2 hours earlier now.
<p>22:06 &lt;@mids&gt; or they just dont care :)
<p>22:07 &lt; nop&gt; ok
<p>22:07 &lt; nop&gt; back
<p>22:07 &lt; hezekiah&gt; Yay! :)
<p>22:07 &lt; nop&gt; 1.1.0 is out, 1.2 meeting needs to be set
<p>22:07 &lt; nop&gt; so that hez, Userx and I can discuss furthur major development
<p>22:08 &lt;@mids&gt; maybe the development cycle should be more open?
<p>22:08 &lt;@mids&gt; so others can hear what the plans are too?
<p>22:08 &lt; nop&gt; we will log and place in research directory
<p>22:08 &lt; nop&gt; on invisiblenet
<p>22:08 &lt;@mids&gt; ok
<p>22:08 &lt; Aprogas&gt; that would counter allegations that IIP is vapourware
<p>22:09 &lt; hezekiah&gt; mids: I think openess is great, but it can get pretty annoying when you are trying to discuss coding and the listeners are continueally getting off the subject into theory. :(
<p>22:09 &lt; nop&gt; that's why we log
<p>22:09 &lt; nop&gt; ;)
<p>22:09 &lt; hezekiah&gt; I think the logging is a good idra.
<p>22:09 &lt; nop&gt; and publish
<p>22:09 &lt;@mids&gt; hezekiah: channels can be moderated
<p>22:09 &lt; hezekiah&gt; Maybe we could post the log to the iip-dev mailing list too? That would give people a good idea of what's going on behind the scenes.
<p>22:09 &lt; Hitman&gt; open discussion of ideas and brainstorming would rock, but end product changes will have to be discussed seperately by the actual coding team otherwise thing's won't get implemented correctly
<p>22:09 &lt;@mids&gt; k
<p>22:09 &lt; hezekiah&gt; They could pipe up with all kinds of suggestions then. :)
<p>22:10 &lt; hezekiah&gt; UserX? Are you currently present?
<p>22:10 &lt; UserX&gt; i'm present
<p>22:10 &lt; hezekiah&gt; OK. :)
<p>22:10 &lt; hezekiah&gt; (To both UserX and nop): Do either of you have any times for that meeting that would be good for you?
<p>22:11 &lt; hezekiah&gt; I mentioned the times that won't work for me, in my email. I hope it's a small enough subset not to be a problem. :)
<p>22:12 &lt;@mids&gt; anyway, you can settle that in private
<p>22:12 &lt; Hitman&gt; in my personal opinion I think that decentralisation of the network is the number one priority. To make IIP completely p2p would take away any ability whatsoever the goverment and other nasty forces have to shut it down. While a central server exists tehy can still end it....ie napster
<p>22:12 &lt; hezekiah&gt; OK.
<p>22:12 &lt;@mids&gt; we can read the logs afterwards.
<p>22:13 &lt; hezekiah&gt; Hitman: decentralization is the main theme of 1.2
<p>22:13 &lt; Hitman&gt; sweet
<p>22:14 &lt; hezekiah&gt; So where were we?
<p>22:15 &lt; hezekiah&gt; Oh, yeah. Nop was listing the current status of 1.2.
<p>22:15 &lt; nop&gt; yeah
<p>22:15 &lt; hezekiah&gt; Did you have anything else to add, nop?
<p>22:15 &lt; nop&gt; so 1.2 we need a dev meeting to start
<p>22:15 &lt; nop&gt; and from that point is our start
<p>22:16 &lt; Aprogas&gt; did you create a branch in CVS so bugs in 1.1 can be fixed without requiring users to update to a alpha or beta state 1.2 ?
<p>22:17 &lt; UserX&gt; The development is already in a seperate branch from 1.1
<p>22:18 &lt; hezekiah&gt; And the 1.1 release was tagged v1-1-0.
<p>22:18 &lt; Aprogas&gt; so there is a tag on the release, but not a branch tag ?
<p>22:18 &lt; Aprogas&gt; i assume the development is on the `MAIN' branch ?
<p>22:19 &lt; hezekiah&gt; Uh, I currently don't know what CVS commands I should be running to tell the difference. :)
<p>22:19 &lt; UserX&gt; 1.1 is on the MAIN branch
<p>22:19 &lt; Aprogas&gt; something like cvsweb gives more overview of such things than cvs commands anyway; branchs in cvs are quite confusing
<p>22:20 &lt; Aprogas&gt; anyway, having a release on the main branch and the development in a seperate branch is quite an uncommon setup; and that might have reasons
<p>22:20 &lt; Aprogas&gt; maybe it is worth investigating if it would not be more useful to do it the other way around ?
<p>22:25 &lt; hezekiah&gt; Well, I don't know much about CVS so my input wouldn't be much worth here. :)
<p>22:26 &lt; Aprogas&gt; CVS is a scary beast
<p>22:27 &lt; hezekiah&gt; Yeah. I wonder if it ate the other people in the room. It seems deathly quiet in here.
<p>22:27 &lt; Aprogas&gt; i ended up re-importing sources numerous times because i messed up after trying to put my branches right
<p>22:27 &lt; hezekiah&gt; ;-)
<p>22:28 &lt; Aprogas&gt; so be careful with it
<p>22:28 &lt; hezekiah&gt; *lol*
<p>22:29 &lt; hezekiah&gt; Mids? Do we have another item on the agenda? It seems like we're done with this one (or else someone got eaten by the CVS beast.)
<p>22:31 &lt; Aprogas&gt; well.. i didnt really see anyone reacting to my `suggestions'
<p>22:31 &lt; Aprogas&gt; im wondering why the IIP development team uses this different way of using branches
<p>22:31 &lt; hezekiah&gt; I have no clue.
<p>22:31 &lt; Aprogas&gt; i guess 99% of the CVS-using project develop on the MAIN branch and keep releases on seperate branches
<p>22:32 &lt; hezekiah&gt; I do know that it works fine.
<p>22:32 &lt; Aprogas&gt; that will become obvious when you get 1.2
<p>22:32 &lt; Aprogas&gt; what will happen with 1.1 which s currently on the main branch ?
<p>22:32 &lt; hezekiah&gt; So I say that "If it isn't broken, then don't fix it."
<p>22:32 &lt; hezekiah&gt; It's sources are tagged.
<p>22:33 &lt; Aprogas&gt; a bug in it might be found
<p>22:33 &lt; Aprogas&gt; and you might want to create 1.1.1
<p>22:33 &lt; hezekiah&gt; I guess that if we need to do a bug fix, then someone checks out v1-1-0, fixes the bug, and commits under the tag v1-1-1.
<p>22:33 &lt;@mids&gt; hezekiah: no, none
<p>22:33 &lt; Aprogas&gt; hezekiah: that is possible too
<p>22:33 &lt; hezekiah&gt; mids: As I said, I don't know much about CVS. :)
<p>22:33 &lt; Aprogas&gt; but using release branches is more common
<p>22:33 &lt; UserX&gt; the developement will probably be merged back on to the main branch. and if we need to do bug fixes/upgrades to 1.1 we just create a branch from it
<p>22:33 &lt; Aprogas&gt; userx: ok
<p>22:33 &lt; hezekiah&gt; Oh, well. I'll leave the CVS playing to the developers that understand it. :)
<p>22:34 &lt; Aprogas&gt; noone understands CVS
<p>22:34 &lt; hezekiah&gt; lol
<p>22:34 &lt; Aprogas&gt; thats the problem
<p>22:34 &lt; Aprogas&gt; its a beast that cannot really be tamed
<p>22:34 &lt; hezekiah&gt; So, mids. What's next on the agenda? Question round?
<p>22:34 &lt;@mids&gt; ok, I am out. cya
<p>22:35 -!- mode/#iip-dev [+o hezekiah] by Trent
<p>22:35 &lt;@hezekiah&gt; OK. The question round has officially begun, I guess. :)
<p>22:35 &lt; Aprogas&gt; oh
<p>22:35 &lt;@hezekiah&gt; Questions?
<p>22:35 &lt;@hezekiah&gt; (Not that I can promise an answer, but you can ask.)
<p>22:37 &lt;@hezekiah&gt; Going once ...
<p>22:37 &lt;@hezekiah&gt; Going twice ..
<p>22:37 &lt;@hezekiah&gt; Gone!
<p>22:38 &lt;@hezekiah&gt; Sold to the eternal silence of the ever questioning public (until the next iip-dev meeting that is.) ;-)
<p>22:38 &lt;@hezekiah&gt; Well, it was nice talking to you all (and nice to be able to have UserX around and talking in an iip-dev meeting. I'm glad the time change has improved things for him.)
<p>22:38 &lt;@hezekiah&gt; Bye, all! :)
<p>22:38 &lt; nop&gt; bye
<p>--- Log closed Tue Mar 18 22:43:48 2003
</div>
{% endblock %}