My first and foremost goals of this project are to get all the basic features of Pligg into it. After the basics I/we can start with some of the more advanced things like "modules", templates, and how to handle different languages. I don't want to base this project solely off of Pligg but I think it's necessary to get many of it's features into PliggDotNet. I've already started on some features that aren't in Pligg. One of my first priorities is to get a the back end management done (obviously).
I think I am going to use the strategy that we use here at Pligg if you want to become a developer for PliggDotNet. Basically, how it works is that I would like to see either 1) Bug fixes to show me that you are able to understand the code and fix bugs or 2) Code that adds new functionality or would benefit the project. If I feel that you could really benefit the project and make it better than I would give you access to commit files. You probably understand that I can't just give anyone access to the repository right off the bat.
The code will be available as soon as I find the best way to structure the files.
If you would like to communicate through the forum on the SF project page feel free do to so. Once the code is available and you would like to report bugs, request new features through the sourceforge tracker that would be great. If this starts to take off I'll probably put a forum up or something at
Pligg.NET - Published News but I like the idea of having everyone gather at the source forge project page for now.