Hi Martin,

On 25 May 2009, at 20:24, Marten Vijn wrote:

> Following http://wiki.sugarlabs.org/go/Activity_Team/Getting_Involved
> 1. User:Marten refers to me
> 2. my public_key is in User:Marten
> 3. I am on Activity Team/Contacts (I was not sure to me add meself)

Welcome aboard!

> 4. For the people that don't know me yet

(I had the benefit of dragging myself over to SugarCamp :-)

> Hi I am Marten, I live in Leiden, The Netherland. I have a girlfiend,
> two kids (2,5 and 4,7 years). I was a physiotherapist and occupational
> therapist before became a unix and net sysadmin. I run a XO-repaering
> service and organize a camp. I may have noticed my English brake every
> comple of lines. I have dyslexia, pls try to read want I mean. (In a  
> way
> you lucky my Dutch is worse.)
> pls read more http://martenvijn.nl
> http://wiki.sugarlabs.org/go/Activity_Team/TODO
>> From here as a non-developer I seem to really get lost.
> To not scare non-tech people I would:
> - move Community Task more up

+1 thanks, a very good idea (I'll go ahead and move it to the top, I  
need to update some of those items now anyway).

> - create 5 simple tasks than can do done repetitive:
> - download,burn,boot,give feedback
> - hardware reports
> - documentation for BIOS in cd-rom and usbdrive

I think these items are perhaps more in line with the Bug Squad team,  
perhaps they would be better there? Hmmmm, perhaps there are some  
other simple tasks we can come-up with for the Activity Team?

> - reviewing Activities

Yes I like this! It's a good way to get to know what's out there  
already. There are a couple of places I feel reviews should be going:

1) For reviews aiming at other users, at http:// 
activities.sugarlabs.org each Activity supports a 1-5 star rating, a  
comment field, and if you want, there is also a 'detailed review'  
submission form. This should be the place to go if you want to provide  
feedback for other Sugar users (kids/teachers/parents/the rest of us)  
to see. These input forms are not used that much yet, so if you do  
find any bugs or incorrect Mozilla text, please open a ticket on  
dev.sugarlabs.org and use the component "activities.sugarlabs.org" so  
we can get it fixed.

2) For general reviews of a more technical nature (more aimed at other  
developers than users), most currently supported Activities have an 
<activity_name> wiki page. A "Reviews" section could be added at the  
bottom of an Activities page; I think it would also be good to email  
such feedback directly to this list so that other developers can  
easily make use of it.

3) For specific Activity developer bugs/feature-requests/suggestions,  
the very best place is to open a trac ticket (dev.sugarlabs.org), or  
if that looks too scary, email to this list (sugar-devel@lists.sugarlabs.org 
) and someone will file it for you.

>  - writing instruction-sets/PR-materials ?

You might also want to look at http://en.flossmanuals.net/Sugar if the  
goal is more 'book like' releases of static information. Alternatively  
more general/dynamic instructions could probably go to the 
<activity_name> wiki page for each Activity (and could easily be  
picked up again at a later time if static 'book like' snapshots need  
to be pulled together for some formal release set of activities).

> - Roadmaps for LocalSugarLabs (creating UserBase)

Is this aimed at finding other interested local developers, you know  
for beer and high bandwidth hacking time?

> Can I shuffle a bit on the TODO list to make more easy for new coming
> people?

Yes please do!

Thanks for all the feedback.


> cheers,
> Marten
> -- 
> http://martenvijn.nl                 Marten Vijn
> http://martenvijn.nl/trac/wiki/soas  Sugar on a Stick
> http://bsd.wifisoft.org/nek/         The Network Event Kit
> http://har2009.org                   13th-16th August
> http://opencommunitycamp.org         26th Jul - 2nd August
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

Sugar-devel mailing list

Reply via email to