I quote the FAQ: I have this great idea.... Good! First step: read the mailing list archives. Odds are good that someone else had the same idea and discussed it with the group. Either a flaw was found in the idea, or perhaps it was decided to postpone implementing the idea until later. Some examples of ideas already discussed are storing information by content hash, key redirection, signed keys/data, use of UDP, server discovery, URLs, document versioning, and others. If you don't see the idea discussed in the archives, by all means bring it up in the appropriate mailing list.
This approach has some drawbacks: - you can't be sure it hasn't be discussed in the mailing list because searching isn't 100% reliable - it is a big step, and can freak some potential contributors Maybe, we could, from now one, when a idea is discussed, and accepted or rejected, put it in the wiki, under the right category, with the reasons. This way, a potential contributor is sure his idea has been discussed (or not), and it is really easy to find that out. I know this method has a major drawback : a lot of ideas has already been discussed, and if we don't ask the user to read the archives, some may present an already discussed idea. But I don't think that's a problem, since now, I don't think the user bother to search at all, or very quickly. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20100213/62f08507/attachment.html>
