Talk:Sugar on a Stick: Difference between revisions

Line 21:

== Proposed next steps ==

=== Formalize a SoaS ~~development team~~ ===

=== Formalize what SL project status means for SoaS spins ===

~~This means acknowledging that~~ SoaS development and Sugar platform development are ~~not the same thing, and that they are~~ done by ~~two~~ different groups ~~(which may have many overlapping members)~~. ~~The creation of~~ a ~~mailing list is seen as part of this separation~~ of project ~~identities~~.

SoaS development and Sugar platform development are two separate projects done by different groups; one for Sugar platform development and one for each SoaS spin. There is currently only one active SoaS spin, and it is the Fedora-based project being driven by Sebastian Dziallas, for a current grand total of 2 project groups; however, there may be other SoaS spins in the future.

Exactly ~~how~~ these ~~groups will operate, what~~ the ~~relationship between them will be~~, ~~how they will be governed~~, what ~~tools they will use where~~, etc. ~~are still open questions with varying opinions on each topic; however, it~~ does ~~not seem~~ that ~~anyone has objected to~~ the ~~notion that SoaS~~ and the ~~Sugar Platform are two (highly related) projects, not one.~~

Exactly what it means to be a SL project is still an open question.

# What are the criteria a SL project must meet (including requirements for ongoing engagement/contribution)?

# How does something become a SL project?

## Who determines whether a project meets these criteria?

## How do they make that determination?

## Is there a schedule and/or timeline for this determination?

## How does someone initiate the process for requesting SL project status, and who can do so?

## What happens if it is determined that a project does not meet these criteria?

# How does a SL project become not a SL project, and for what reasons might this happen?

# What benefits (mailing list, etc.) does a SL project get?

# How can all of the above answers be amended if needed in the future?

# What is the list of current projects that we are considering including in the initial "this is a SL project" approval round, and what do these projects have to do in order to be approved for the criteria?

Who decides:

~~As a~~ SL project, SoaS ~~can~~ formalize ~~its development team however it likes~~.

These decisions need to ultimately be ratified by SLOBs. It's been suggested that Sebastian's Fedora-based SoaS spin be the test case for the first "SL project," so it makes sense to start out on the SoaS mailing list to come up with a set of proposed answers to these questions that will work for the projects themselves, then ask SLOBs to formalize them (with more discussion/modification if need be).

=== Determine what "Sugar on a Stick" refers to ===

@@ Line 21: / Line 21: @@
 == Proposed next steps ==
-=== Formalize a SoaS development team ===
+=== Formalize what SL project status means for SoaS spins ===
-This means acknowledging that SoaS development and Sugar platform development are not the same thing, and that they are done by two different groups (which may have many overlapping members). The creation of a mailing list is seen as part of this separation of project identities.
+SoaS development and Sugar platform development are two separate projects done by different groups; one for Sugar platform development and one for each SoaS spin. There is currently only one active SoaS spin, and it is the Fedora-based project being driven by Sebastian Dziallas, for a current grand total of 2 project groups; however, there may be other SoaS spins in the future.
-Exactly how these groups will operate, what the relationship between them will be, how they will be governed, what tools they will use where, etc. are still open questions with varying opinions on each topic; however, it does not seem that anyone has objected to the notion that SoaS and the Sugar Platform are two (highly related) projects, not one.
+Exactly what it means to be a SL project is still an open question.
+# What are the criteria a SL project must meet (including requirements for ongoing engagement/contribution)?
+# How does something become a SL project?
+## Who determines whether a project meets these criteria?
+## How do they make that determination?
+## Is there a schedule and/or timeline for this determination?
+## How does someone initiate the process for requesting SL project status, and who can do so?
+## What happens if it is determined that a project does not meet these criteria?
+# How does a SL project become not a SL project, and for what reasons might this happen?
+# What benefits (mailing list, etc.) does a SL project get?
+# How can all of the above answers be amended if needed in the future?
+# What is the list of current projects that we are considering including in the initial "this is a SL project" approval round, and what do these projects have to do in order to be approved for the criteria?
 Who decides:
-As a SL project, SoaS can formalize its development team however it likes.
+These decisions need to ultimately be ratified by SLOBs. It's been suggested that Sebastian's Fedora-based SoaS spin be the test case for the first "SL project," so it makes sense to start out on the SoaS mailing list to come up with a set of proposed answers to these questions that will work for the projects themselves, then ask SLOBs to formalize them (with more discussion/modification if need be).
 === Determine what "Sugar on a Stick" refers to ===