Difference between revisions of "Decision panels/SOAS"
(..) |
|||
Line 48: | Line 48: | ||
==Further ideas== | ==Further ideas== | ||
− | + | * discussion of potential naming conventions. | |
− | + | * discussion of ''how'' to support products such as SOAS, and what that means | |
− | * | + | * exploration of what it means to "produce a distribution", which some active contributors felt was a huge effort and others felt was already being done, with most effort happening upstream. Better agreement within the community about what is being done may help avoid distracting meta-debates about direction. |
− | |||
− | * | ||
− | |||
[[category:decision panels]] | [[category:decision panels]] |
Revision as of 18:30, 29 October 2009
NOTICE: This page is a draft in active flux... Please contribute to these contents and discuss issues on the discussion page. |
Origin
A 12-person Sugar-on-a-Stick (SoaS) decision panel was appointed by a September 25, 2009 Oversight Board decision.
Mandate
Members
- Sebastian Dziallas
- Luke Faraone
- Martin Dengler
- Bill Bogstad
- Faisal Khan
- Benjamin M. Schwartz
- Samuel Klein
- Sean Daly
- Tabitha Roder
- Caryl Bigenho
- Daniel Drake
- Abhishek Indoria
Procedures
The Decision Panel procedures were adopted.
Discussion took place on the SoaS mailing list with subject lines beginning with the text "[DP]".
Report
Introduction
This constitutes the report of the SoaS decision panel (DP), convened by SLOB.
The structure of this report is:
- Introduction (this section)
- Executive Summary
- Mandate
- Members
- Report on Questions 1-3
- Conclusion
- Appendices
Executive Summary
The Decision Panel was mandated to answer three questions. The Decision Panel's answers are below:
- Question 1
- "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
- Answer
- Consensus trending towards yes. There has been some discussion about what is involved in 'being a GNU/Linux distributor' and what the risks and benefits would be; specifics have been suggested but not clearly enumerated, making consensus building harder. TBD - see below for opinions
- Question 2
- "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
- Answer
- Consensus is yes. There are requests for clarification of how SL can promote effective ways of distributing Sugar, and endorse all good distributions. TBD - see below for opinions
- Question 3
- "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
- Answer
- A plurality of people with definite opinions say yes, SL should ask its community to avoid using 'Sugar on a Stick' in a confusing way. There is consensus that whatever name is used for common distributions should not be used in a confusing way, but disagreement over whether SOAS should refer to a specific distribution or a broad class of them. TBD - see below for opinions
In addition, the mandate allows the Decision Panel to raise and answer any other question the DP deems required to provide an answer to the original question: "Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?" (Question 0).
The Decision Panel has not raised any additional questions, outside of requesting clarification of terms in questions 2 and 3.
Mandate
- "Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:
- "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
- "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
- "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
- Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"
Members
- Sebastian Dziallas
- Luke Faraone
- Martin Dengler
- Bill Bogstad
- Faisal Khan
- Benjamin M. Schwartz
- Samuel Klein
- Sean Daly
- Tabitha Roder
- Caryl Bigenho
- Daniel Drake
- Abhishek Indoria
Report on Questions 1-3
Q1: OS distributor v. upstream
Question 1: "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"
Proposed answers:
Yes | No | Invalid | Undecided |
---|---|---|---|
|
|
|
|
Q2: distro endorsement v. neutrality
Question 2: "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"
Proposed answers:
Yes | No | Invalid | Undecided |
---|---|---|---|
|
|
|
|
Q3: SoaS name
Question 3: "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"
Proposed answers:
Yes | No | Invalid | Undecided |
---|---|---|---|
|
|
|
|
DP Conclusion
to come
Appendices
Recorded opinions
Question 1"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?" | ||||
Yes | No | Invalid | Defer | |
---|---|---|---|---|
|
|
Samuel Klein |
Faisal Khan, Daniel Drake | |
Question 2"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?" | ||||
Yes | No | Invalid | Defer | Undecided |
|
Samuel Klein - SL should support effective distros; this can be done neutrally. |
Bill Bogstad, Faisal Khan, Daniel Drake | ||
Question 3"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?" | ||||
Yes | No | Invalid | Defer | Undecided |
|
|
Samuel Klein - The question is too specific. I agree with both Ben and Sean, who feel they fall on 'Yes' and 'No' sides of the fence. |
Bill Bogstad, Faisal Khan, Daniel Drake |
Further ideas
- discussion of potential naming conventions.
- discussion of how to support products such as SOAS, and what that means
- exploration of what it means to "produce a distribution", which some active contributors felt was a huge effort and others felt was already being done, with most effort happening upstream. Better agreement within the community about what is being done may help avoid distracting meta-debates about direction.