The Okopipi Project

We are currently working on revamping the project bear with us. Like I said before I am in talks with a member of the apache group and he has agreed to join our team and will become our lead developer. We have discussed the latest paper and will be making improvements to it soon. We are still in need of developers to help us create a Proof of Concept program.

We are looking at renaming the project during this revamp due to the fact we need control to moderate the group and manage the website and most of the people who had control are long gone. Please let us know what you think and any ideas. developers please email me at c130commnav (at) gmail.com

Here is a bit of an update on what is going on with the okopipi project.

[RANT]
First off I want to say, you people complain way to much. You act like it is your God given right to have this project developed for you. Stop posting things that are not productive, stop posting things you don't have a clue about. READ ALL the forums instead of posting about somthing that is already covered. If you don't want to help develope then stop complaing that code isn't being written, if you don't wanna volunteer to be a leader in the project, stop whining about the leadership. The fact that this project is completely distributed makes it insainly complicated, WE ARE WORKING ON IT. STOP COMPLAINING!

Recently I got a couple emails concerning Okopipi, I am rather surpised, after I posted about not being able to work on the project anymore I monitored the forums and such, and nothing...I thought the project would die and that was that. Now I see it has started to become active in the last couple months which is good to hear. I have a bit more time these days, but with a baby and deployment on the way that time will soon be cut short. If anyone can get nathan off his ass I have a server we can use for free so he can stop paying this hosting company. Maybe there is hope after all.

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.

On Saturday June 10th at 10pm GMT the Okopipi Steering Committee will be holding a public meeting to answer your questions. The topic will be Project Management and Structure.

The meeting will be held on the Undernet IRC Network in the #Okopipi room. If you do not have an IRC client you can follow the link to the Java Client here. This will be a moderated meeting and you will have to submit your questions by Private Message to one of the moderators to ask it. Please be patient as a lot of people are expected to attend and it may take some time before your question is asked.

This is to announce the intent of the Steering Committee to conduct a community-wide public meeting to discuss the project, how it should be structured, and the best way to proceed in attempting to create a productive environment.

This meeting will be a chance for all interested to be heard regarding matters specifically related to project management. Issues related to architecture, the DNIR, ideological concerns, security, or any other topic shall be saved for a later date.

The meeting will be held via IRC on undernet, in the #okopipi channel. Undernet does not reject Torified IRC clients, so if you would like to retain anonymity, you can install Tor and Privoxy and set up your IRC client to connect using a SOCKS5 proxy at 127.0.0.1:9050. You may experience some lag, however.

We currently have our channel on Undernet and for the most part it is working fine. We will be registering it soon (have to wait 3 more days), however there have been alot of complaints about spambots, and the lack of nickserv, so I have made a test IRC server that seems to be working well. We have moved once already from freenode, and I know it is a bit of a pain, so I am asking the community, would you prefer to stay on undernet or how our own IRC network. If we do our own network, it of course won't be restricted to the Okopipi project, you would be free to create your own channels for your personal use, and hopefully we could host other open source projects there.

We just wanted to clarify a few naming issues with regards to the Okopipi project.

Pronunciation
It's pronounced Oko-pip-e (as in Pippi Longstockings).

Other names
There are no other names for this project.

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.