Hi all,
By the end of 2003 we want to have the Projects area fully online and functional. In order to achieve this I'm polling you all now as to what functionality you'd like to see present. The way I see this working so far is as follows:
You enter the Projects Manager from your Control Panel where you can create a new Project, Maintain an existing one, Search through your Projects or Delete a Project entirely.
When creating a Project you specify some attributes for it:
Project Title
Type of Project (game, app, demo, DLL, etc)
Intended final status (freeware, shareware, commercial)
Access Level (public, registered members, Buddies, DBDN)
Description of the Project (short summary, 4KB max)
Estimated Release Date (optional.. heh)
Once you've done this the Project itself is created and you can now start adding information to it.
I will allow the attachment of screen shots showing the progress of development. This will be limited in some way, although I'm not yet sure how. I think I will allow a maximum number of shots per Project and any extra can be linked to your own web site.
You can keep an online work log. Basically a development diary, you post what work you've done on your Project and it's date stamped so people can see what has been updated easily.
People can comment on your work log (post questions, mini forum style) which you self-moderate.
When you hit what you consider to be a milestone release you can lock the Project. This will increment the version number ready for the next release but also sign-off (at its current stage) the Project allowing you to upload code for people to access.
Users can then provide feedback on the code itself.
I see the process working something like this.. you create the Project, you update your work log daily (or however often you want to) and when you have the code in a state you're happy with you zip it and upload it, signing off that version. People can then download, test and provide feedback. You continue to work on the code, updating your work log until you're happy with the next release which you again sign-off (uploading the latest version). Doing this purges the old version from our system.
This process continues until you flag the Project as complete. For small Projects this whole process might take a matter of a weekend or it might take months.
The Projects Manager will let you export your Change List so you can include the file with your final release. Each Project will also have a unique URL so that you can give it to people or place it in your documentation so they know where to go for updates or to post a bug report.
Members will be able to "Watch" a Project and receive notification of new work log entries and / or milestones.
As usual Registered Members will have a file size limit on the uploads and DBDNers will get a significant amount more.
Projects will be browsable via the Developers Network site, so you can see "what's new", etc.
In the future I will consider adding support for multi-person Projects (i.e. Team creation with each member submitting assets to the final Project) but that will not happen this year (so don't suggest it please!).
I would like to know what other kind of things you'd like to see this system do / provide.
Cheers,
Rich
"Gentlemen, we have short-circuited the Universe!"