Might as well add version control while you're at it I don't think this place will ever become that though. Its hard enough getting any change implemented here as it is
Might as well add version control while you're at it I don't think this place will ever become that though. Its hard enough getting any change implemented here as it is
And then everyone will have a massive debate over which system we should implement...
Might as well add version control while you're at it I don't think this place will ever become that though. Its hard enough getting any change implemented here as it is
The solution would be to post in a more postive way then dean. I won't pretend and like this idea because this would give the original author no rights on his/her work if things turn out sour. Sure, on paper it sounds like a great idea but this to me only benefits vbulletin.org and would restrict the author to remove his/her work if he/she allows a third party to join/takeover a project, script that they where brought in to get involved in. If coders want to recruit other people I guess they could realistically do this on their own site retaining full rights to their work.
How would that exactly work out? If the original author (let's say) had an argument with the staff and/or person they brought in and wished for the work to be removed but the person who was brought in rejected this and wanted it kept on the site?
These are the questions that really need to be asked before such an implementation is enforced.
Quite simply if you don't like the idea than don't participate. The suggestion was meant to augment the current offerings not replace them. If you don't want someone taking over the project than don't invite anyone to be on your team.
However if you're interested in a more open development environment and willing to create an open project the capabilities should be available here instead of elsewhere.
I like the idea... doesn't seem too realistic here though. I don't see why people don't just use sourceforge or github for collaboration and then put the final release here. Surely only supporting authors would need to do is edit the release itself -- the primary author can simply update the package.