Features/SoaS Creation Station: Difference between revisions

Line 83:

The "blog" link for each of these remixes would go to a description - written either by or in conjunction with the teacher - on why the remix was designed that way, and what their plans for classroom usage are. ("Ms. Smith created this remix for her middle-school Spanish-language classes with the following localization and activities so she could do the following things with Sugar in her syllabus...")

=== Image-~~building service~~ ===

=== Image-Database===

Provide and advertise an experimental remix image-~~building service available for the first 2 months after the Mangolassi release~~. ~~For this time period, the~~ feature owner takes responsibility for accepting emails with .ks files attached, ~~building~~ the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.

Provide and advertise an experimental remix image-database. The feature owner takes responsibility for accepting emails with .ks files attached, uploading the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.

The mechanism of this back-and-forth is up to the feature owner to determine, so long as the mechanism (and the unsupported nature of the remixes generated by it) are clear. The current proposal is as follows:

@@ Line 83: / Line 83: @@
 The "blog" link for each of these remixes would go to a description - written either by or in conjunction with the teacher - on why the remix was designed that way, and what their plans for classroom usage are. ("Ms. Smith created this remix for her middle-school Spanish-language classes with the following localization and activities so she could do the following things with Sugar in her syllabus...")
-=== Image-building service ===
+=== Image-Database===
-Provide and advertise an experimental remix image-building service available for the first 2 months after the Mangolassi release. For this time period, the feature owner takes responsibility for accepting emails with .ks files attached, building the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.
+Provide and advertise an experimental remix image-database.  The feature owner takes responsibility for accepting emails with .ks files attached, uploading the resulting images, and responding to those emails with a link to a built .iso of the remix generated by that .ks.
 The mechanism of this back-and-forth is up to the feature owner to determine, so long as the mechanism (and the unsupported nature of the remixes generated by it) are clear. The current proposal is as follows: