GobuntuHardy

Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2007-10-23 15:39:01
Size: 2474
Editor: ool-44c0d208
Comment:
Revision 6 as of 2007-11-20 12:16:54
Size: 4467
Editor: 82-69-40-219
Comment: minor tweaks
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''Packages affected''':  * '''Packages affected''': ubiquity, gobuntu-desktop, gobuntu-artwork
Line 10: Line 10:
Discuss what needs to be done for Gobuntu and what can be achieved in the Hardy time frame. Gobuntu 8.04 will be released alongside Ubuntu 8.04. We will define the Gobuntu brand by creating an independent website for it and by creating additional artwork for the Gobuntu desktop. We will continue to work towards a free software distribution by removing additional software from Gobuntu. We will clearly define the Gobuntu mission and structure by sending a policy document to the Community Council for approval.
Line 14: Line 14:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.
Gobuntu 8.04 brings together the best free software with a distinctive look and vibrant community.
Line 20: Line 18:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. There exists a significant community of individuals wishing to run only free software. Ubuntu will continue to try to meet the needs of these individuals by furthering the development of Gobuntu.
Line 24: Line 22:
== Assumptions ==

== Design ==

You can have subsections that better describe specific parts of the issue.
 * Joe wants an operating system composed with only free software.
 * Carol has seen the Gobuntu name mentioned in other Ubuntu press material and would like to learn more about it.
Line 32: Line 27:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:  * Launchpad integration will remain part of Gobuntu as it is an external resource that the user can choose to use or not, much like Google is in the browser.
 * Support for Gobuntu will be added to Ubiquity and a live CD version of Gobuntu will be added to the CD build system.
Line 34: Line 30:
=== UI Changes === '''Removing non-free software from Gobuntu'''
 * The choice of web browser has been discussed at length and it was agreed that using Epiphany as the default is the right approach. This change has already been made in the seeds, but marketing this choice at release time could be a worthwhile exercise as it should give a boost to the Epiphany community.
 * The main pocket will be further scanned for software that is non-free and such software will be moved into restricted. ffmpeg and libavcodec were cited as examples.
Line 36: Line 34:
Should cover changes required to the UI, or specific UI that is required to implement this '''Website'''
 * Canonical Ltd. owns the Gobuntu domain, which currently points to ubuntu.com. A RT request will be filed for a separate Gobuntu site, which will host a Gobuntu themed version of wiki.ubuntu.com, in the same manner as kubuntu.org, that starts at wiki.ubuntu.com/Gobuntu. The existing links on the main Ubuntu website will need to be updated.
 * It was suggested that the Gobuntu community take control of the free software laptop specification on the wiki. This will not be considered a blocker for this specification being considered complete, however.
Line 38: Line 38:
=== Code Changes === '''Branding'''
 * Gobuntu 7.10 included its own usplash and isolinux bootloader themes. 8.04 will expand on this by including more desktop artwork, such as its own wallpaper. As Kurt has already started this work, further progress will be coordinated between him and the Ubuntu Artwork Team. A list of branding points in Ubuntu already exists.
 * The Gobuntu website will need to be similarly themed.
Line 40: Line 42:
Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
'''Communication'''
 * Matthew East's Gobuntu policy document will be sent to the Community Council for ratification.
 * Areas where Gobuntu can better work with Gnewsense and better define its relationship with that project will be explored.
Line 51: Line 48:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

== Outstanding Issues ==

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
Gobuntu installs will be tested in the QA team's ISO testing tracker alongside Ubuntu and its other derivatives.
Line 61: Line 52:
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.  * keep launchpad integration
 * clarify that this isn't an attempt to kill gnewsense
 * ffmpeg, libavcodec -> restricted
 * further prodding of the kernel team on removing firmware
 * gobuntu community driven list of free hardware
 * talk to scott and ken about gobuntu artwork and branding (there's a list of ubuntu branding items). Kurt is already working on gobuntu-artwork.
 * ubiquity support
 * RT request for separate gobuntu website, in the same vein as kubuntu

Are there any principled reasons for using Launchpad in Gobuntu development apart from the practical one mentioned above?
 * technical, but we should investigate ways in which we can encourage individuals who are concerned about this to join the gnewsense community yet still work with us where they are able, and better define our relationship with gnewsense
Line 64: Line 65:
CategorySpec CategorySpec CategorySpec

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad Entry: gobuntu-hardy

  • Packages affected: ubiquity, gobuntu-desktop, gobuntu-artwork

Summary

Gobuntu 8.04 will be released alongside Ubuntu 8.04. We will define the Gobuntu brand by creating an independent website for it and by creating additional artwork for the Gobuntu desktop. We will continue to work towards a free software distribution by removing additional software from Gobuntu. We will clearly define the Gobuntu mission and structure by sending a policy document to the Community Council for approval.

Release Note

Gobuntu 8.04 brings together the best free software with a distinctive look and vibrant community.

Rationale

There exists a significant community of individuals wishing to run only free software. Ubuntu will continue to try to meet the needs of these individuals by furthering the development of Gobuntu.

Use Cases

  • Joe wants an operating system composed with only free software.
  • Carol has seen the Gobuntu name mentioned in other Ubuntu press material and would like to learn more about it.

Implementation

  • Launchpad integration will remain part of Gobuntu as it is an external resource that the user can choose to use or not, much like Google is in the browser.
  • Support for Gobuntu will be added to Ubiquity and a live CD version of Gobuntu will be added to the CD build system.

Removing non-free software from Gobuntu

  • The choice of web browser has been discussed at length and it was agreed that using Epiphany as the default is the right approach. This change has already been made in the seeds, but marketing this choice at release time could be a worthwhile exercise as it should give a boost to the Epiphany community.
  • The main pocket will be further scanned for software that is non-free and such software will be moved into restricted. ffmpeg and libavcodec were cited as examples.

Website

  • Canonical Ltd. owns the Gobuntu domain, which currently points to ubuntu.com. A RT request will be filed for a separate Gobuntu site, which will host a Gobuntu themed version of wiki.ubuntu.com, in the same manner as kubuntu.org, that starts at wiki.ubuntu.com/Gobuntu. The existing links on the main Ubuntu website will need to be updated.
  • It was suggested that the Gobuntu community take control of the free software laptop specification on the wiki. This will not be considered a blocker for this specification being considered complete, however.

Branding

  • Gobuntu 7.10 included its own usplash and isolinux bootloader themes. 8.04 will expand on this by including more desktop artwork, such as its own wallpaper. As Kurt has already started this work, further progress will be coordinated between him and the Ubuntu Artwork Team. A list of branding points in Ubuntu already exists.
  • The Gobuntu website will need to be similarly themed.

Communication

  • Matthew East's Gobuntu policy document will be sent to the Community Council for ratification.
  • Areas where Gobuntu can better work with Gnewsense and better define its relationship with that project will be explored.

Test/Demo Plan

Gobuntu installs will be tested in the QA team's ISO testing tracker alongside Ubuntu and its other derivatives.

BoF agenda and discussion

  • keep launchpad integration
  • clarify that this isn't an attempt to kill gnewsense
  • ffmpeg, libavcodec -> restricted

  • further prodding of the kernel team on removing firmware
  • gobuntu community driven list of free hardware
  • talk to scott and ken about gobuntu artwork and branding (there's a list of ubuntu branding items). Kurt is already working on gobuntu-artwork.
  • ubiquity support
  • RT request for separate gobuntu website, in the same vein as kubuntu

Are there any principled reasons for using Launchpad in Gobuntu development apart from the practical one mentioned above?

  • technical, but we should investigate ways in which we can encourage individuals who are concerned about this to join the gnewsense community yet still work with us where they are able, and better define our relationship with gnewsense


CategorySpec CategorySpec

GobuntuHardy (last edited 2008-08-06 16:28:38 by localhost)