Changes

There are several (competing?) issues at stake here in regard to use of the Sugar/Sugar Labs name:

There are several (competing?) issues at stake here in regard to use of the Sugar/Sugar Labs name:

* we want clarity in regard to what is directly supported by the Sugar community vs what is supported by third parties who are catering to the specific needs of a deployment (which may, for example require a proprietary driver to support a school's hardware or some proprietary software or content to support a school's existing curricula goals; [[Features/Feature_SoaS_customization|Carlo proposed a technical approach]] to such 'remixing" that may help frame the discussion); and

* we want clarity in regard to what is directly supported by the Sugar community vs what is supported by third parties who are catering to the specific needs of a deployment (which may, for example require a proprietary driver to support a school's hardware or some proprietary software or content to support a school's existing curricula goals; [[Features/SoaS_customization|Carlo proposed a technical approach]] to such 'remixing" that may help frame the discussion); and

* we want clarity in regard to the language we use to make this distinction (our primary audience is not the FOSS community; terms such as "remix" are not going to be very meaningful); it may be that we ''always'' need to direct teachers and parents to third-party solution providers who can manage the deployment.

* we want clarity in regard to the language we use to make this distinction (our primary audience is not the FOSS community; terms such as "remix" are not going to be very meaningful); it may be that we ''always'' need to direct teachers and parents to third-party solution providers who can manage the deployment.