I am slightly concerned that development seems to have ground to a halt on many interdependent features which are rather important, in fact, essential. My fear is that this is because whenever proposals are suggested people are too quick to find fault (rather than to point out and correct weaknesses), or worse: thrust forward their own proposal without regard to what has been suggested previously. I am not pointing fingers, in fact, I am sure that, at times, I am guilty of this too.
It is, of course, essential to get a consensus wherever possible, but we must be wary of allowing this to paralyse development as everyone competes to either have their proposal accepted, or to knock others. Here are what I feel to be the significant issues: * Searching I have a reasonably solid proposal for this which tackles the issue of routing searches, frequently glossed over in other proposals. I don't claim it is perfect, but it is a start * Unrequests I think [hope] that everyone is happy with this now, it should be reasonably straight-forward to implement * Simulation Oskar has done some good work on this * Updates This proved to be a thorny one, and we will probably need the simulation to decide on the best way to do it * Protocol issues There is much discussion on the dev list about the protocol - this seems to be coming up with sensible ideas, so I think that is progressing ok already. I am minded to create separate mailing lists for each of these, and to invite people to join them as teams. Segregating people like this should help avoid the "too many cooks..." problem which I think has been causing problems recently. Thoughts? Have I left anything out? Ian. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
