Marketing Team/Events/FOSDEM 2009/Notes: Difference between revisions
ChristophD (talk | contribs) No edit summary |
ChristophD (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== Pre-conference community meetup == | == Pre-conference community meetup == | ||
* Bernie gives an overview of the current state of Sugar Labs | * Bernie gives an overview of the current state of Sugar Labs: | ||
* infrastructure (servers, services, etc.) in in place | ** infrastructure (servers, services, etc.) in in place | ||
* mode of governance has been established | ** mode of governance has been established | ||
* getting away from the ''old mindset'' (thinking like a company, asking for permission before doing something) | ** getting away from the ''old mindset'' (thinking like a company, asking for permission before doing something) | ||
* ''show me the code'', we will support you but you should do things yourself | ** ''show me the code'', we will support you but you should do things yourself | ||
* SugarLabs is a community '''not''' a company | ** SugarLabs is a community '''not''' a company | ||
* more developers are needed | ** more developers are needed | ||
* people should be pointed to join.sugarlabs.org | ** people should be pointed to join.sugarlabs.org | ||
* a few thousand dollars have been collected via individual donations | ** a few thousand dollars have been collected via individual donations | ||
* no success in getting grants so far | ** no success in getting grants so far | ||
* Sugar Labs has no employees, should work like the Gnome foundation, people getting paid by companies who want Sugar to suceed | ** Sugar Labs has no employees, should work like the Gnome foundation, people getting paid by companies who want Sugar to suceed | ||
* in the larger context SugarLabs should be responsible for high-levels decisions and setting the framework for activities | * in the larger context SugarLabs should be responsible for high-levels decisions and setting the framework for activities | ||
* focus on setting up Local Sugar Labs, direct contact to educators and other relevant parties in their respective communities | * focus on setting up Local Sugar Labs, direct contact to educators and other relevant parties in their respective communities | ||
* [http://sugarlabs.org/go/ActivityTeam/Remora_port Remora] | * [http://sugarlabs.org/go/ActivityTeam/Remora_port Remora] as a central hub for activities (downloads, reviews, etc.); should be available in a couple of weeks | ||
* Collaboration: | |||
** (as previously also discussed on the mailing-list) it would be good to have a minimum-level of collaboration in all activities in the form of a view-only mode | |||
** activities should also declare a max. number of collaborators, any additional users who join are automatically connected in a view-only mode | |||
== FOSDEM'09 == | == FOSDEM'09 == | ||
== Other Notes == | == Other Notes == | ||
Revision as of 07:11, 8 February 2009
Pre-conference community meetup
- Bernie gives an overview of the current state of Sugar Labs:
- infrastructure (servers, services, etc.) in in place
- mode of governance has been established
- getting away from the old mindset (thinking like a company, asking for permission before doing something)
- show me the code, we will support you but you should do things yourself
- SugarLabs is a community not a company
- more developers are needed
- people should be pointed to join.sugarlabs.org
- a few thousand dollars have been collected via individual donations
- no success in getting grants so far
- Sugar Labs has no employees, should work like the Gnome foundation, people getting paid by companies who want Sugar to suceed
- in the larger context SugarLabs should be responsible for high-levels decisions and setting the framework for activities
- focus on setting up Local Sugar Labs, direct contact to educators and other relevant parties in their respective communities
- Remora as a central hub for activities (downloads, reviews, etc.); should be available in a couple of weeks
- Collaboration:
- (as previously also discussed on the mailing-list) it would be good to have a minimum-level of collaboration in all activities in the form of a view-only mode
- activities should also declare a max. number of collaborators, any additional users who join are automatically connected in a view-only mode