widget development enviornment

[Gota]

I'd like to know if widget developers would like to have a system to ease collaboration.

ATM:
widgets are made mostly by individuals and there is no system to ease work of groups of people on widgets that are similar in nature.
For example a UI project.
ATM an OTA based UI is developed mostly by individuals working on small parts like a player list or a buildmenu modification on their own.
what this results in are small parts that don't really add up to one solid UI because they are made by different people with different visual themes colors and styles.

what could be:
an environment under which projects can be started and joined by others to work on a one solid big widget instead of many small unconnected widgets
That the player needs to assemble later just to find out that all these small widgets don't fit well together.

Under this system a coder can start a project which will be exclusive to people whom the project founder thinks are good enough to join his project or a project that is open to everyone.
Each project can have an inner poll or voting system,or be completely free to be changed by the project members without any limitations.
If the project uses polls and votes than When one member wants to make a change in some area of a project(a widget),he raises it along side the benefits of his change,gives a short explanation and awaits the other members to vote yes or no and give their constructive criticism or approval of the change.

The question is would you like such a system if it was available?would you use it or anything similar?

[MidKnight]

*points at svn*
*points at Trac*
*points at ChiliGUI*


The problem isnt with the software, but with the coders, not that we have bad lua coders, we have awesome lua coders! They just havent decided to collab yet...

[Ashnal]

You forgot IceUI MidKnight, IceUI is meant to be the framework for exactly what you're talking about Gota, a windowing system that the user can color and theme himself. All it needs is lua coders interested in developing for it aside from meltrax.

And yeah, the collaboration can be handled with svn, the problem isn't the method, but rather that those who need to collaborate, already have the means to do so. See the CA svn, and the S44 svn.