The Okopipi Project

Alright here is a bit of an update, not much has been done. I have been busy with stuff and havnt really had time for this project. I have talked to several developers whom are very intrested in the project. I think right now we just need to start coding. If you need any information please contact me. All coders feel free to start working on a proof of concept program. If you need any tools let me know and Ill hook you up. It would be nice if you either wrote a theory of operation paper or edited mine and posted it so others know what you are doing. Basicly this project is up for grabs to who ever wants to do it.

We are holding an official project meeting, anyone interested may
attend it will be focusing on the development of okopipi, so developers/programmers are encouraged to attend. The meeting will be Aug 19th at 1900 (7:00 PM) GMT on our IRC channel #okopipi on undernet. for questions please contact Journeyman

Many of the steering-committee has been inactive for some time, so after discussing with the remaining committee I was given permission to take charge and start working on production of the Okopipi project. After some research and working with Kwinter we have come up with what we feel will be the best structure for the Okopipi network. This paper explains how everything will work. However we are just 2 people, so please if you find any holes in the paper, or have any suggestions/comments please let us know.

http://svn.okopipi.org/docs/okopipi.pdf

Some of you may be contacted in the next few weeks to inquire about your skills as posted on the wiki, no one will request you give out any personal info, just a rough experience history and availability. This list will be used to build teams for the project and as a way of determining skill levels.

Please do not exaggerate your skills, if you only have a C+ 101 class say so. If you can only devote one hour on the third Friday of every month say so. This is not the project to "figure something out" for the first time. At first the tasks will be low priority/security items so that we can build an understanding of everyone's skill and participation level.

If anyone doupts the authenticity of the request you are free to contact me with the Name/E-mail of the person who contacted you.

Also this is a reminder to update and detail your skills as listed on the Okopipi Wiki and insure there is the correct contact E-mail address listed for you.

I would like to propose all this talk of what the client could do in addition to the Opt-Out be stopped. We have a really bad case of feature creep starting that would delay the original client for months or more.

Lets get the original working client out first as it was first proposed. After that since the client is open we could create addons for the client, maybe listing "Approved" addons that the code has been reviewed by us. This would allow third parties to write add-ons that maybe we would never have imagined, tieing the client to other anti-spam technologies by other groups.

As long as our client is open and we publish any APIs needed this would be an easy way for us to put our effort into the client first and the extras second. This would give users the option of choosing what extra features they want without delaying the time to market of the client.

Right now, we're looking for developers and anyone with experience in P2P systems. Design, development, protocol development, etc.

If you're interested, please join the Okopipi-dev mailing list and introduce yourself.

All skill levels are welcome.