[IAEP] [sugar] list of complaints from sugarcamp community building talk

[Simon Schampijer]

[...]
>>> So I argue, to please use sugar-devel for those discussions.
>> +1 unless the Sugar Newbies tell us otherwise. We also have other
>> lists appropriate for content and the rest.
> 
> Ok, we had this now several times, I propose the following tags for 
> sugar-devel:
> 
> [RELEASE] when developers of a sucrose component make a release (this is 
> in use already) ---> a packager should have all the information he needs 
> when filtering for those messages
> 
> [ANNOUNCE] announcements like: a new sucrose release, feature freeze, 
> 0.86 feature process, services outage, upcoming trac activities after a 
> release (to move tickets and clean everything), API changes ---> an 
> activity developer should have all the information he needs when only 
> filtering for those information
> 
> [BEET] (comes from sugar-beet) This is a tag that should be used by 
> beginners questions ---> To avoid having an extra list, and to produce a 
> culture of critique
> 
> Anything I have missed? If there are no objections I will take care to 
> add this to the list info, announce it and note it in appropriate places 
> on the wiki.


I reflected the above on the subscribe page of the sugar-devel list 
http://lists.sugarlabs.org/listinfo/sugar-devel

On request I left the [BEET] part out.

Thanks for the feedback,
    Simon