BugSquad/Meetings/Agendas/2008-12-10: Difference between revisions

Line 1:

* SL Community Bugsquad: what is it now, and what do we want it to become?

==SL Community Bugsquad==

* what is it now, and what do we want it to become?

* Testing: upstream/downstream

== Testing: upstream/downstream ==

** Who tests activities?

* Who tests activities?

*** I was almost convinced that it is a downstream task but... OLPC does not support activities (it's an odd case, I know of no downstream project in the same situation). I've seen [[User:Mchua|Mchua's]] post about moving it to Sugar Labs, let's make a good plan on it Wed. [[User:Marcopg]]

** I was almost convinced that it is a downstream task but... OLPC does not support activities (it's an odd case, I know of no downstream project in the same situation). I've seen [[User:Mchua|Mchua's]] post about moving it to Sugar Labs, let's make a good plan on it Wed. [[User:Marcopg]]

*** I think that Activities should be tested by individual Activity project groups, since Activities are independent subprojects. I don't think that the core Sugar Labs bugsquad should be testing Activities. I also don't think that internal OLPC QA should be testing Activities, other than making sure the ones we ship are ship-quality on XOs (by coordinating with the individual Activity projects, ideally).

** I think that Activities should be tested by individual Activity project groups, since Activities are independent subprojects. I don't think that the core Sugar Labs bugsquad should be testing Activities. I also don't think that internal OLPC QA should be testing Activities, other than making sure the ones we ship are ship-quality on XOs (by coordinating with the individual Activity projects, ideally).

** Making Activities platform-independent

* Making Activities platform-independent

*** The question of "who tests Activities?" is somewhat related to the issue of making activities platform independent, similarly to firefox plugins (I will elaborate on it in the meeting). [[User:Marcopg]]

** The question of "who tests Activities?" is somewhat related to the issue of making activities platform independent, similarly to firefox plugins (I will elaborate on it in the meeting). [[User:Marcopg]]

** If we move activities testing upstream, how do we move tickets? If we don't move them, where should user oriented information be hosted?

@@ Line 1: / Line 1: @@
-* SL Community Bugsquad: what is it now, and what do we want it to become?
+==SL Community Bugsquad==
+* what is it now, and what do we want it to become?
-* Testing: upstream/downstream
+== Testing: upstream/downstream ==
-** Who tests activities?
+* Who tests activities?
-*** I was almost convinced that it is a downstream task but... OLPC does not support activities (it's an odd case, I know of no downstream project in the same situation). I've seen [[User:Mchua|Mchua's]] post about moving it to Sugar Labs, let's make a good plan on it Wed. [[User:Marcopg]]
+** I was almost convinced that it is a downstream task but... OLPC does not support activities (it's an odd case, I know of no downstream project in the same situation). I've seen [[User:Mchua|Mchua's]] post about moving it to Sugar Labs, let's make a good plan on it Wed. [[User:Marcopg]]
-*** I think that Activities should be tested by individual Activity project groups, since Activities are independent subprojects. I don't think that the core Sugar Labs bugsquad should be testing Activities. I also don't think that internal OLPC QA should be testing Activities, other than making sure the ones we ship are ship-quality on XOs (by coordinating with the individual Activity projects, ideally).
+** I think that Activities should be tested by individual Activity project groups, since Activities are independent subprojects. I don't think that the core Sugar Labs bugsquad should be testing Activities. I also don't think that internal OLPC QA should be testing Activities, other than making sure the ones we ship are ship-quality on XOs (by coordinating with the individual Activity projects, ideally).
-** Making Activities platform-independent
+* Making Activities platform-independent
-*** The question of "who tests Activities?" is somewhat related to the issue of making activities platform independent, similarly to firefox plugins (I will elaborate on it in the meeting). [[User:Marcopg]]
+** The question of "who tests Activities?" is somewhat related to the issue of making activities platform independent, similarly to firefox plugins (I will elaborate on it in the meeting). [[User:Marcopg]]
 ** If we move activities testing upstream, how do we move tickets? If we don't move them, where should user oriented information be hosted?