Difference between revisions of "CommunicationLibrePackages/En"
From TuxFamilyFAQ
Jump to navigationJump to searchm |
|||
Line 29: | Line 29: | ||
* Why don't you work upstream with existing package maintainers ? Don't you think you would learn much more than simply on you own to be integrated in an existing team ? | * Why don't you work upstream with existing package maintainers ? Don't you think you would learn much more than simply on you own to be integrated in an existing team ? | ||
− | == Mandriva == | + | == Debian GNU/Linux == |
+ | * See http://www.debian.org/distrib/packages | ||
+ | ** documentation http://www.debian.org/doc/debian-policy/ | ||
+ | |||
+ | == Mandriva Linux == | ||
* See http://cookerspot.tuxfamily.org/wikka.php?wakka=PackagingMadeSimple | * See http://cookerspot.tuxfamily.org/wikka.php?wakka=PackagingMadeSimple | ||
** Get known on [http://wiki.mandriva.com/en/Development/Howto/Participate cooker mailing-list] | ** Get known on [http://wiki.mandriva.com/en/Development/Howto/Participate cooker mailing-list] |
Revision as of 13:12, 26 January 2008
Communication Libre > Packages
Contents
Indexing
Indexing is important to let know about the software(s) you've developed
- http://www.ohloh.net/ provides informations about the activity of your subversion repository
- http://cia.vc/ see documentation to show your developers' activities
- http://demoll.tuxfamily.org (prototype) assurez-vous que les bons tags ont été choisis
Co - mmu - ni - cate
Your better communication is your documentation and your code.
For packages (deb or rpm or any other),
- Provide instructions to use your repository
- Get acquainted with your distribution : we promote upstream work, see below
- Integrate and collaborate with the maintainers of packages in the same domain as yours
Upstream contributions
- Before opening yet another new repository, try to join an existing project upstream
- Be involved in development mailing-lists (this will permit to recruit testers for your packages)
- Join the contributers of your distribution, they will show you good practices
- Ask yourself one second "why would I open yet another repository rather than join existing teams?"
- Have a look at http://demoll.tuxfamily.org/tags/index.php?tag=distrib and contact the projects to join their team
- It's infuriating to observe the number of repositories opened for no rational, unmaintained afterwards, only addressing a ponctual need et visibly unsufficiently tested (giving your help to integrate your packages upstream ensures that packages orphans won't stay without maintainers too long)
Have a look at it from a user point of view :
- Who would use your packages ? (which ones BTW)
- Why would they add yet another repository to their source list ? how would they know the level of maintenance you will be providing ? (will it still exist when there are security advisories, in 3 years from now on when 6 versions went out ?)
- Why don't you work upstream with existing package maintainers ? Don't you think you would learn much more than simply on you own to be integrated in an existing team ?
Debian GNU/Linux
Mandriva Linux
- See http://cookerspot.tuxfamily.org/wikka.php?wakka=PackagingMadeSimple
- Get known on cooker mailing-list
- You can come on chans irc://irc.freenode.net/#mandriva-cooker ou irc://irc.freenode.net/#mandrivafr
Ubuntu
- See https://wiki.ubuntu.com/MOTU , more precisely https://wiki.ubuntu.com/UbuntuDevelopment#NewPackages
- For any question, come by the chans irc://irc.freenode.net#ubuntu-fr-classroom (in French) or #ubuntu-motu (in English)
The community is always happy to integrate new contributers, do not hesitate to ask for help to see your work incorporated to the official distribution !