Upstream
|
Size: 1270
Comment:
|
Size: 3076
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| = Knowledge Base = * '''[[Upstream/Adopt|Adopt an Upstream]] - if you are highly interested in some Upstream project and want work with them to improve it in Ubuntu''' * [[Upstream/AdoptingTemplate|document links to an upstream project]] * [[UpstreamGuide|How you as an Upstream project can make your Ubuntu packager's life easier]] = General Links = * [[UbuntuDevelopment|Overview over Ubuntu Development]] * [[ReleaseSchedule|Our release schedule]], including freezes and milestones |
== How Ubuntu Works == * [[UbuntuDevelopment|Overview]] of Ubuntu Development * Our relationship with [[Debian|Debian]]. * [[ReleaseSchedule|Our release schedule]], including freezes and milestones. * Our [[StableReleaseUpdates|Stable Release Policy]] - this is information handy if you have a fix that you would like to see shipped in a current stable release. * Our [[SecurityTeam/Policies|security policies]] - Security Team [[SecurityTeam/Contacts|contact information]] |
| Line 23: | Line 21: |
| === "How to Get In Ubuntu" === If your existing software is not available in Ubuntu then here are some steps to get your package in there: * [[PackagingGuide|Packaging Guide]] - Your software needs to be packaged up in .deb format. * [[MOTU/GettingStarted|Getting Started]] - After you have packages you should get ahold of a MOTU to peer review your work. Remember that this is done on a volunteer basis, so please have realistic expectations on how quickly your package will be reviewed. It helps '''tremendously''' if someone from your existing upstream community can help out with packaging, do bug workflow, and do general [[/Upstream/Adopt|upstream contact]] work. If you are serious about maintaining your software in Ubuntu, then we recommend you just become and Ubuntu Developer by following [[/UbuntuDevelopment|Ubuntu development]]. * Most software lives in the universe component of Ubuntu, which is synced from Debian on a regular basis. Getting your software packaged in Debian has many benefits. * Ease of maintenance - it's easier to find a volunteer that can work on one set of packaging instead of nuances between distros. * Your software will be in both distros at once. * ... * Please note that if your software packaging has licensing issues or glaring flaws that skipping the Debian requirements will likely mean that it won't meet Ubuntu requirements. = Knowledge Base = * '''[[Upstream/Adopt|Adopt an Upstream]] - if you are highly interested in some Upstream project and want work with them to improve it in Ubuntu''' - this is a good starting point if you want to start going through bugs. * [[Upstream/AdoptingTemplate|Template]] to adopt a project. * [[UpstreamGuide|How you as an Upstream project can make your Ubuntu packager's life easier]] |
In Ubuntu it's important to us to have a good relationship with our Upstream projects and an efficient workflow we both benefit from.
The Upstream namespace on the wiki is all about:
- best practices for collaboration between Ubuntu and Upstream
- giving Upstreams better visibility into what's happening in Ubuntu
- recommendations for engaging and working with an Upstream project
How Ubuntu Works
Overview of Ubuntu Development
Our relationship with Debian.
Our release schedule, including freezes and milestones.
Our Stable Release Policy - this is information handy if you have a fix that you would like to see shipped in a current stable release.
Our security policies - Security Team contact information
Ubuntu Upstream Report - Low hanging fruit for bugs you might have fixed that we haven't applied yet.
"How to Get In Ubuntu"
If your existing software is not available in Ubuntu then here are some steps to get your package in there:
Packaging Guide - Your software needs to be packaged up in .deb format.
Getting Started - After you have packages you should get ahold of a MOTU to peer review your work. Remember that this is done on a volunteer basis, so please have realistic expectations on how quickly your package will be reviewed. It helps tremendously if someone from your existing upstream community can help out with packaging, do bug workflow, and do general upstream contact work. If you are serious about maintaining your software in Ubuntu, then we recommend you just become and Ubuntu Developer by following Ubuntu development.
- Most software lives in the universe component of Ubuntu, which is synced from Debian on a regular basis. Getting your software packaged in Debian has many benefits.
- Ease of maintenance - it's easier to find a volunteer that can work on one set of packaging instead of nuances between distros.
- Your software will be in both distros at once.
- ...
- Please note that if your software packaging has licensing issues or glaring flaws that skipping the Debian requirements will likely mean that it won't meet Ubuntu requirements.
Knowledge Base
Adopt an Upstream - if you are highly interested in some Upstream project and want work with them to improve it in Ubuntu - this is a good starting point if you want to start going through bugs.
Template to adopt a project.
How you as an Upstream project can make your Ubuntu packager's life easier
Upstream (last edited 2017-11-27 15:47:17 by bryanquigley)