Sugar Labs - User contributions [en]

Math4Team/Meetings

2009-05-18T18:55:40Z

Quaid: fixing spacing

<noinclude>{{GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Math4Team|home=Project Home|xbgColor=ffe792}}
{{TOCright}}
= Meetings =

== Meeting Time ==

* [http://timeanddate.com/worldclock/fixedtime.html?month=5&day=18&year=2009&hour=14&min=45&sec=0&p1=179 Monday, May 18 2:45-4:30 EDT] (1845 to 2030 UTC)
* '''#fedora-OLPC''' on freenode

== Participants ==

This Meeting will be lead by [[User:KRobinson | Karlie Robinson]].

* The participants will be posted after the meeting.



== Agenda ==

Update this agenda with your latest items before the meeting has started.

* First hour of this meeting will be dedicated to the RIT Student presentations, and feedback of the development process.
* Second hour will start with Roll Call
* Announcements
* Project updates
* Recruitment
* Open floor

== Transcript ==

Transcript can be found here:

== Summary ==

Summary is available here:

== Next Meeting ==
Will be posted after this meeting is completed

Math4Team/Meetings

2009-05-18T18:54:35Z

Quaid: adding time in UTC, which is honestly more useful than a link to a conversion tool; everyone in a global project needs to know how to convert UTC to localtime in their heads.

<noinclude>{{GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Math4Team|home=Project Home|xbgColor=ffe792}}
{{TOCright}}
= Meetings =

== Meeting Time ==

* [http://timeanddate.com/worldclock/fixedtime.html?month=5&day=18&year=2009&hour=14&min=45&sec=0&p1=179 Monday, May 18 2:45-4:30 EDT ] (1845 to 2030 UTC)
* '''#fedora-OLPC''' on freenode

== Participants ==

This Meeting will be lead by [[User:KRobinson | Karlie Robinson]].

* The participants will be posted after the meeting.



== Agenda ==

Update this agenda with your latest items before the meeting has started.

* First hour of this meeting will be dedicated to the RIT Student presentations, and feedback of the development process.
* Second hour will start with Roll Call
* Announcements
* Project updates
* Recruitment
* Open floor

== Transcript ==

Transcript can be found here:

== Summary ==

Summary is available here:

== Next Meeting ==
Will be posted after this meeting is completed

Sugar Kids QA Team

2009-05-04T18:31:47Z

Quaid: /* QA Process */

All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop. Lots of QA work happpening in there. But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?

[[Sugar Kids QA Team]] is the solution. The Sugar Kids QA Team goals are:

* Test Sugar activities early and often
* Provide feedback directly to the Sugar development team, usually through a parent or teacher coordinator
* Create a repeatable process for kids QA'ing Sugar
* Document and publicize the process.

== QA Process ==

We use this template and fill it out during testing:

* [[Image:Sugar Kids QA Team-Activity check sheet.odt]] template page
* Download [http://wiki.sugarlabs.org/images/1/1a/Sugar_Kids_QA_Team-Activity_check_sheet.odt ODT file] directly

In essence, it contains this form:

<hr/>
<hr/>

'''Project:''' Quality Assurance for Math4 activities on the XO/Sugar platform

'''Team:''' XO Kids QA Team (''Names'')

'''Task:''' Basic task description

'''Activity resolves:''' 4.N.## Curriculum description.

'''Date:''' ''YYYY-MM-DD''

'''Method:''' Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.

'''Results of method:''' Team ...

'''DATA'''

'''A. How fun was the activity?'''
# Very un-fun
# Not fun
# A little fun
# Fun
# Very fun!

'''Comments:'''

'''B. How hard was it to figure out what you were supposed to do?'''
# Very hard
# Hard
# Not hard nor easy
# Easy
# Very easy

'''Comments:'''

'''C. What didn't work right about the activity?'''

'''Comments:'''

'''D. TBD'''

'''E. TBD'''

<hr/>
<hr/>

== Teams ==

=== Team Santa Cruz ===

''Parent coordinator(s):'' [[User:Quaid|Karsten Wade]], Larry Cafiero

''Team:'' Malakai, Saskia, and Mirano are steady members. We are inviting Sigi, Sophia, and Victoria.

''Team page:''

[[Category:BugSquad]]
[[Category:Sugar Kids QA Team]]
[[Category:Activity Team]]

Sugar Kids QA Team

2009-05-04T18:31:16Z

Quaid: /* QA Process */

All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop. Lots of QA work happpening in there. But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?

[[Sugar Kids QA Team]] is the solution. The Sugar Kids QA Team goals are:

* Test Sugar activities early and often
* Provide feedback directly to the Sugar development team, usually through a parent or teacher coordinator
* Create a repeatable process for kids QA'ing Sugar
* Document and publicize the process.

== QA Process ==

We use this template and fill it out during testing:

* ([[Image:Sugar Kids QA Team-Activity check sheet.odt]] template page
* Download [http://wiki.sugarlabs.org/images/1/1a/Sugar_Kids_QA_Team-Activity_check_sheet.odt ODT file] directly

In essence, it contains this form:

<hr/>
<hr/>

'''Project:''' Quality Assurance for Math4 activities on the XO/Sugar platform

'''Team:''' XO Kids QA Team (''Names'')

'''Task:''' Basic task description

'''Activity resolves:''' 4.N.## Curriculum description.

'''Date:''' ''YYYY-MM-DD''

'''Method:''' Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.

'''Results of method:''' Team ...

'''DATA'''

'''A. How fun was the activity?'''
# Very un-fun
# Not fun
# A little fun
# Fun
# Very fun!

'''Comments:'''

'''B. How hard was it to figure out what you were supposed to do?'''
# Very hard
# Hard
# Not hard nor easy
# Easy
# Very easy

'''Comments:'''

'''C. What didn't work right about the activity?'''

'''Comments:'''

'''D. TBD'''

'''E. TBD'''

<hr/>
<hr/>

== Teams ==

=== Team Santa Cruz ===

''Parent coordinator(s):'' [[User:Quaid|Karsten Wade]], Larry Cafiero

''Team:'' Malakai, Saskia, and Mirano are steady members. We are inviting Sigi, Sophia, and Victoria.

''Team page:''

[[Category:BugSquad]]
[[Category:Sugar Kids QA Team]]
[[Category:Activity Team]]

Sugar Kids QA Team

2009-05-04T18:27:53Z

Quaid: updating link to ODT template

All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop. Lots of QA work happpening in there. But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?

[[Sugar Kids QA Team]] is the solution. The Sugar Kids QA Team goals are:

* Test Sugar activities early and often
* Provide feedback directly to the Sugar development team, usually through a parent or teacher coordinator
* Create a repeatable process for kids QA'ing Sugar
* Document and publicize the process.

== QA Process ==

We can use the template ([[Image:Sugar Kids QA Team-Activity check sheet.odt|ODT]] format template) to fill out during testing. In essence, it contains this form:

'''Project:''' Quality Assurance for Math4 activities on the XO/Sugar platform

'''Team:''' XO Kids QA Team (''Names'')

'''Task:''' Basic task description

'''Activity resolves:''' 4.N.## Curriculum description.

'''Date:''' ''YYYY-MM-DD''

'''Method:''' Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.

'''Results of method:''' Team ...

'''DATA'''

'''A. How fun was the activity?'''
# Very un-fun
# Not fun
# A little fun
# Fun
# Very fun!

'''Comments:'''

'''B. How hard was it to figure out what you were supposed to do?'''
# Very hard
# Hard
# Not hard nor easy
# Easy
# Very easy

'''Comments:'''

'''C. What didn't work right about the activity?'''

'''Comments:'''

'''D. TBD'''

'''E. TBD'''

== Teams ==

=== Team Santa Cruz ===

''Parent coordinator(s):'' [[User:Quaid|Karsten Wade]], Larry Cafiero

''Team:'' Malakai, Saskia, and Mirano are steady members. We are inviting Sigi, Sophia, and Victoria.

''Team page:''

[[Category:BugSquad]]
[[Category:Sugar Kids QA Team]]
[[Category:Activity Team]]

File:Sugar Kids QA Team-Activity check sheet.odt

2009-05-04T18:26:58Z

Quaid: This is a template to fill out when kids QA teams are working with Math4 Sugar activities. The final two questions are undecided still; we'll talk with the developer teams to find out what they want to hear back from us.

This is a template to fill out when kids QA teams are working with Math4 Sugar activities. The final two questions are undecided still; we'll talk with the developer teams to find out what they want to hear back from us.

Sugar Kids QA Team

2009-05-04T18:20:20Z

Quaid: addiing in the QA form we worked out -- both the OpenOffice.org template link, and the actual bits right here for reference.

All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop. Lots of QA work happpening in there. But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?

[[Sugar Kids QA Team]] is the solution. The Sugar Kids QA Team goals are:

* Test Sugar activities early and often
* Provide feedback directly to the Sugar development team, usually through a parent or teacher coordinator
* Create a repeatable process for kids QA'ing Sugar
* Document and publicize the process.

== QA Process ==

We can use the template ([[:Image:Sugar Kids QA Team Report Template|ODT]] format) to fill out during testing. In essence, it contains this form:

'''Project:''' Quality Assurance for Math4 activities on the XO/Sugar platform

'''Team:''' XO Kids QA Team (''Names'')

'''Task:''' Basic task description

'''Activity resolves:''' 4.N.## Curriculum description.

'''Date:''' ''YYYY-MM-DD''

'''Method:''' Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.

'''Results of method:''' Team ...

'''DATA'''

'''A. How fun was the activity?'''
# Very un-fun
# Not fun
# A little fun
# Fun
# Very fun!

'''Comments:'''

'''B. How hard was it to figure out what you were supposed to do?'''
# Very hard
# Hard
# Not hard nor easy
# Easy
# Very easy

'''Comments:'''

'''C. What didn't work right about the activity?'''

'''Comments:'''

'''D. TBD'''

'''E. TBD'''

== Teams ==

=== Team Santa Cruz ===

''Parent coordinator(s):'' [[User:Quaid|Karsten Wade]], Larry Cafiero

''Team:'' Malakai, Saskia, and Mirano are steady members. We are inviting Sigi, Sophia, and Victoria.

''Team page:''

[[Category:BugSquad]]
[[Category:Sugar Kids QA Team]]
[[Category:Activity Team]]

Category:Sugar Kids QA Team

2009-03-11T17:53:43Z

Quaid: adding new category with descrition

This category is for team pages, processes, and anything related to the [[Sugar Kids QA Team]] activities.

Sugar Kids QA Team

2009-03-11T17:51:38Z

Quaid: adding in the basics for the Sugar Kids QA Team