ideosphere-discuss — Public discussion about the Ideosphere

[George K. <mrd...@ya...>]

Welcome to the mailing list, this is the first message.
The source code of LimeWire is uploaded in four RAR segments.The next task is to group the coding tasks so people can choose.Here's my suggestion how the project could be divided into task groups:
1.) Adding an online store-like GUI2.) Adding user identity routines (signup, handle verification, etc.)3.) Adding general currency handling routines; send, receive, transfer, balance4.) Adding author & host ID-handling routines (embedding into & payment from file)5.) Adding messaging support between users6.) Adding a public message board with vote support and invitation via button7.) Adding security features 1 (transaction watch, etc.)8.) Adding security features 2 (account login protection)9.) Adding security features 3 (amount verification for ideo sales)10.) Adding security features 4 (banning and IP block of the "outvoted")11.) Adding security features 5 (ID tampering protection)12.) Adding user rating and ranking features13.) Adding a vote pattern detection feature (the "learning" ability)14.) Adding the Ideo Store feature
It's just a suggestion, I'm open to changes.
To save time I suggest two things:
A.) Developers should use branches for the task groups whenever possible. The LimeWire project also lists code entry points at http://wiki.limewire.org/index.php?title=Code_Entry_Points  A combination of these two techniques should help in coordinating the development.B.) Before writing code for any of the tasks above, the person should check and decide if another GPL project's code (if it's good) couldn't be adapted easier
For those new to working with LimeWire code, there is an excellent "Getting Started" resource at http://wiki.limewire.org/index.php?title=Getting_Started
Thank you in advance, I'm looking ahead to your responses, suggestions, and task choices.
George