(→New package checklist) |
Uhofemeier (Talk | contribs) |
||
| (8 intermediate revisions not shown) | |||
| Line 5: | Line 5: | ||
Following this checklist will ensure smooth submission and acceptance of NEW package. | Following this checklist will ensure smooth submission and acceptance of NEW package. | ||
| - | + | === Step 1: Have your Program Manager provide you with an SBOM (Software Bill of Materials.) === | |
| + | An SBOM is required to be completed by the P.M and submitted to the Release Engineering team when packages for specific verticals/products are going to be introduced into MeeGo. | ||
| + | |||
| + | === Step 2: Agreed upon by copyright owner === | ||
Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful. | Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful. | ||
| - | * For package owned by Intel, please make sure it passes open source PDT | + | * For package owned by Intel, please make sure it passes open source PDT. |
* If this package is from community | * If this package is from community | ||
** Talks to maintainer via project mailing list to ask for permission | ** Talks to maintainer via project mailing list to ask for permission | ||
** If first approach is unavailable, please make sure it is in at least two other linux distributions | ** If first approach is unavailable, please make sure it is in at least two other linux distributions | ||
| - | + | === Step 3: Appropriate license === | |
| + | |||
| + | Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't allow a package of GPLV3 into default build of non-netbook image. So make sure it doesn't need to be installed by default if it's GPLV3. Otherwise, if this new package is GPLV3 and/or has dependency of another GPLV3 package, you either stop here or you could do following to move further | ||
| + | * Remove GPLv3 parts or parts requires another GPLV3 package OR | ||
| + | * Rewrite GPLv3 parts by yourself so that this package doens't need to be GPLV3 OR | ||
| + | * Revert back to a non-GPLV3 version | ||
| + | |||
| + | === Step 4: It must be with a FEA# === | ||
| + | |||
| + | Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager | ||
| + | |||
| + | === Step 5: Submit to correct target project === | ||
| - | + | Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project | |
| - | + | * Trunk:Testing which is staging project for Trunk for all of open sourced packages | |
| + | * Trunk:non-oss:Testing which staging project for Trunk:non-oss for all those packages MeeGo could redistribute but copyright owner(s) don't want to get them open-sourced like some 3D gfx packages and phone call specific packages. | ||
| - | + | === Step 6: Claim ownership === | |
| + | Once your package are accepted, please claim ownership for this package use "osc reqms --role bugowner". For detail, please reference of [[Packaging/Guidelines#Maintaining_a_Package|Maintain a package]] | ||
| - | + | [[Category:Release engineering]] | |
Contents |
This a checklist which developers have to follow to submit a new package to MeeGo OBS of http://build.meego.com. This checklist talks about only specical parts for new package, for other commen practise required to submit code to MeeGo, please follow Submission Checklist
Following this checklist will ensure smooth submission and acceptance of NEW package.
An SBOM is required to be completed by the P.M and submitted to the Release Engineering team when packages for specific verticals/products are going to be introduced into MeeGo.
Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful.
Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't allow a package of GPLV3 into default build of non-netbook image. So make sure it doesn't need to be installed by default if it's GPLV3. Otherwise, if this new package is GPLV3 and/or has dependency of another GPLV3 package, you either stop here or you could do following to move further
Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager
Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project
Once your package are accepted, please claim ownership for this package use "osc reqms --role bugowner". For detail, please reference of Maintain a package