Collab mockup - Revision history

Alsroot: /* Possible implementations */

2012-02-08T03:16:28Z

Possible implementations

← Older revision		Revision as of 23:16, 7 February 2012
Line 95:		Line 95:
	== Possible implementations ==		== Possible implementations ==

			* [[Sugar Network]]
	* http://brainstorm.ubuntu.com/		* http://brainstorm.ubuntu.com/
	* adapt ASLO		* adapt ASLO

FGrose: Project interaction visualization

2010-04-30T14:20:07Z

Project interaction visualization

← Older revision		Revision as of 10:20, 30 April 2010
Line 110:		Line 110:
	* http://wiki.laptop.org/go/Feature_requests		* http://wiki.laptop.org/go/Feature_requests
	* http://wiki.laptop.org/go/Feature_roadmap		* http://wiki.laptop.org/go/Feature_roadmap
			* [[Marketing Team/Project Visualization]]

FGrose: tune English

2010-04-30T14:14:46Z

tune English

Show changes

Alsroot: /* Possible implementations */

2010-04-30T12:29:53Z

Possible implementations

← Older revision		Revision as of 08:29, 30 April 2010
Line 100:		Line 100:
	* special activity		* special activity
	* ...		* ...

			=== Implementations in progress ===

			* [[Activities/Activity_Library]]

	== Related resources ==		== Related resources ==

Alsroot: /* Related resources */

2010-04-06T16:32:49Z

Related resources

← Older revision		Revision as of 12:32, 6 April 2010
Line 103:		Line 103:
	== Related resources ==		== Related resources ==

	* [http://~~www~~.~~mail-archive~~.~~com~~/~~iaep@lists~~.~~sugarlabs~~.~~org~~/~~msg08145.html~~ POLL collab.sugarlabs.org]		* [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/20180 POLL collab.sugarlabs.org]
	* [http://www.mail-archive.com/grassroots@lists.laptop.org/msg00455.html Is this the "Idea Funnel?"]		* [http://www.mail-archive.com/grassroots@lists.laptop.org/msg00455.html Is this the "Idea Funnel?"]
	* http://wiki.laptop.org/go/Feature_requests		* http://wiki.laptop.org/go/Feature_requests
	* http://wiki.laptop.org/go/Feature_roadmap		* http://wiki.laptop.org/go/Feature_roadmap

Alsroot: /* Possible implementations */

2010-01-08T09:23:05Z

Possible implementations

← Older revision		Revision as of 05:23, 8 January 2010
Line 98:		Line 98:
	* http://brainstorm.ubuntu.com/		* http://brainstorm.ubuntu.com/
	* adapt ASLO		* adapt ASLO
			* special activity
	* ...		* ...

Alsroot: /* Possible implementations */

2010-01-07T16:56:16Z

Possible implementations

← Older revision		Revision as of 12:56, 7 January 2010
Line 97:		Line 97:

	* http://brainstorm.ubuntu.com/		* http://brainstorm.ubuntu.com/
			* adapt ASLO
	* ...		* ...

Alsroot: /* Purposes */

2010-01-07T13:41:11Z

Purposes

← Older revision		Revision as of 09:41, 7 January 2010
Line 17:		Line 17:
	** 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		** 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		** 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
			** from requesters mode, people who initiated request can track development status
	** tracking what contributors do has also social aspect - any sugar user can see how much particular contributor does for sugar community thus encourage people do more(of course this information is accessible via git repositories or bugs tracker but in case of collab.sl.o it will be given by several clicks for any casual user) e.g. we can have Hall of Fame on main page		** tracking what contributors do has also social aspect - any sugar user can see how much particular contributor does for sugar community thus encourage people do more(of course this information is accessible via git repositories or bugs tracker but in case of collab.sl.o it will be given by several clicks for any casual user) e.g. we can have Hall of Fame on main page

Alsroot: /* Purposes */

2010-01-06T15:59:47Z

Purposes

← Older revision		Revision as of 11:59, 6 January 2010
Line 12:		Line 12:
	=== Purposes ===		=== Purposes ===

	* 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) e.g. collab.sl.o will provide simple method to track progress of request implementation, let other users vote for this request thus stimulate contributors to participate

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

Alsroot: /* Implementation ideas */

2010-01-06T15:33:05Z

Implementation ideas

← Older revision		Revision as of 11:33, 6 January 2010
Line 27:		Line 27:
	=== Implementation ideas ===		=== Implementation ideas ===

	The major idea of this proposal is having several modes. Every mode will provide only useful components for particular audience. For example requesters mode should be friendly as much as possible for newcomers and especially for non-technical newcomers and full featured groupware for experienced contributors.		* The major idea of this proposal is having several modes. Every mode will provide only useful components for particular audience. For example requesters mode should be friendly as much as possible for newcomers and especially for non-technical newcomers and full featured groupware for experienced contributors.

			* Idea of having only collab.sugarlabs.org site could not be useful for Sugar Labs, in that case we should use enterprise level products that could be overkill. Instead, we can have callab.sl.o as lightweight component and reuse existed infrastructure like wiki and bugs trackers as much as possible.

	== Workflows ==		== Workflows ==