Quote:
Originally Posted by tamarian
That would kill the project, or delay it for a looong time
How do you see a vbulletin board, even a heavily hacked one like vb.org supporting multiple developemnt teams? I mean providing the needed tools such as CSV, authentication of team permissions for each project?
Otherwise, you'd be stuck with the a single thread, single author with the sole responsibility for uploading and updating. To commit changes from others, you'd have to sort emails and PM's to incorporate such contributions. And if you're on vacation or elsewhere, the project is stuck, and you can't deligate anything even if you want to....
|
I honestly dont think it would be so difficult.
Whoever starts the project (by clicking the handy undeveloped 'new project' button) could add devlopers, add releases (along with the developers), and all it would need is three exta tables (in theory).
1- Project
Project id
start date
Last update
title
synopsis
text
latest version
threadid
2. Developers
userid
projectid
versionid
role
3. Roles
id
title
4. Project versions
projectid
versionid
isstable
developers
5 projectpackages
id
projectid
versionid
stateid
text
allrightallright. Its not exactly 3 tables AND there would be more I am sure (with refined and additional fields)... however I am sure you get the point.
I think it would take as long to get the project going here as it would anywhere else and be of stonger benefit here.
Hell, why not open auditions for a dev team to create it? There is enough talent floating around these parts to entice something that wouldnt take too long to bring to fruition AND end up being the beta team for the project.
(as you can see - the hotel room is getting to me)