Changes

* Let any casual user request a feature using convenient and friendly tool<br>existed model still works but either not so friendly to non-technical users(like track) or too common(like wiki and mailing lists)

* Let any casual user request a feature using convenient and friendly tool<br>existed model still works but either not so friendly to non-technical users(like track) or too common(like wiki and mailing lists)

* Mix in groupware component to sugar development model keeping in mind its casual and decentralized nature<br>e.g. for now, even core team is not well coordinated and we need at least know what particular developer is doing right now

* Mix in groupware component to sugar development model keeping in mind its casual and decentralized nature

** sugar still has lack of critical mass of participants who contribute on regular bases thus coordination of development efforts is a critical point and we need to track and schedule such efforts in more formal(then posting emails to sugar-devel@ for example) manner<br>e.g. every core team member will all time know what other members are working on and what the progress of current tasks

** groupware brings benefits for other developers as well<br>if some developer doesn't have enough time to implement request he was working on, he can just expose it via UI(in comparing with sending email to sugar-delvel@ which could not be fair every time) and coordinator/requester/other-developers can track such events

* Place like collab.sugarlabs.org could be the first point where interested in contributing/requesting people can go. It could the right place to have database of all sugar contributors and having sustainability features like donate buttons per contributor.

* Place like collab.sugarlabs.org could be the first point where interested in contributing/requesting people can go. It could the right place to have database of all sugar contributors and having sustainability features like donate buttons per contributor.