AddingPackagesToDesktopCommon

Differences between revisions 1 and 2
Revision 1 as of 2018-05-25 02:54:51
Size: 846
Editor: tsimonq2
Comment:
Revision 2 as of 2018-06-20 02:15:25
Size: 2241
Editor: tsimonq2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Why? =

The
desktop-common seed in the platform seed is what '''all''' Ubuntu flavors and Ubuntu Desktop pulls in. We need to ensure that all parties are aware of the contents of this seed. Additionally, we should also aim to:
desktop-common in the platform seed is what '''all''' Ubuntu flavors and Ubuntu Desktop pull in to their images. We need to ensure that all parties are aware of the contents of this seed. Additionally, we should also aim to:
Line 8: Line 6:
= How? = = The Process =
Line 13: Line 11:
 1.

/!\ NOT DONE YET /!\
 1. What is the purpose of this package? What does it do and why is it important to include this by default? Is there a user-facing impact of including this package by default?
 1. How long has this package been in Main? Are there any open CVEs or high (or greater) priority bugs, or any other known issues with it?
 1. Who takes responsibility for this package and what is the best way to contact them?
 
 At this point, unless there is a reason to add the package immediately (in which case this should be stated), an aging period of one week should be allowed for objections from anyone who includes this seed in their images (including flavors), which should be emailed to ubuntu-release.
 
 Should an objection be stated during '''or after''' this aging period, an attempt should be made by the team responsible for the package to address or provide an explanation for the issues presented by the opposing party, and both parties should come up with a plan (formally or informally) to resolve the issues. If the issues cannot be resolved, the package needs to be removed from the seed. In the case that the party opposing a package's inclusion is dissolved (through a flavor becoming active or some other means), the proposal should be restated to the mailing list.
 
 If no objections are stated, the package should be added to the seed, with a link to the proposal on the mailing list in the commit message.

desktop-common in the platform seed is what all Ubuntu flavors and Ubuntu Desktop pull in to their images. We need to ensure that all parties are aware of the contents of this seed. Additionally, we should also aim to:

  • allow affected parties to voice concerns or questions prior to inclusion.
  • ensure that the rationale for inclusion is clear and agreed upon.
  • clearly define a process which a party can appeal to the inclusion of a package in this seed.

The Process

The package you wish to propose inclusion of should already be in Main. If it is not in Main, you need to follow the MainInclusionRequest procedure.

To proceed, send an email to the ubuntu-release mailing list which answers the following questions:

  1. What is the purpose of this package? What does it do and why is it important to include this by default? Is there a user-facing impact of including this package by default?
  2. How long has this package been in Main? Are there any open CVEs or high (or greater) priority bugs, or any other known issues with it?
  3. Who takes responsibility for this package and what is the best way to contact them? At this point, unless there is a reason to add the package immediately (in which case this should be stated), an aging period of one week should be allowed for objections from anyone who includes this seed in their images (including flavors), which should be emailed to ubuntu-release.

    Should an objection be stated during or after this aging period, an attempt should be made by the team responsible for the package to address or provide an explanation for the issues presented by the opposing party, and both parties should come up with a plan (formally or informally) to resolve the issues. If the issues cannot be resolved, the package needs to be removed from the seed. In the case that the party opposing a package's inclusion is dissolved (through a flavor becoming active or some other means), the proposal should be restated to the mailing list. If no objections are stated, the package should be added to the seed, with a link to the proposal on the mailing list in the commit message.

SeedManagement/AddingPackagesToDesktopCommon (last edited 2018-09-18 07:33:30 by vorlon)