Difference between revisions of "CommunicationLibrePackages/En"

From TuxFamilyFAQ
Jump to navigationJump to search
m
Line 12: Line 12:
  
 
For packages (deb or rpm or any other),  
 
For packages (deb or rpm or any other),  
* provide instructions to use your repository
+
* Provide instructions to use your repository
* get acquainted with your distribution : we promote upstream work, see below
+
* 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
+
* Integrate and collaborate with the maintainers of packages in the same domain as yours
  
 
= Upstream contributions  =
 
= Upstream contributions  =
* before opening yet another new repository, try to join an existing project upstream
+
* 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)
+
** 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
+
** 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?"
+
* 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
+
** 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 unsuficiently tested (giving your help to integrate your packages upstream ensures that packages orphans won't stay without maintainers too long)
+
** 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 :
 
Have a look at it from a user point of view :
* who would use your packages ? (which ones BTW)
+
* 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 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 ?
+
* 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 ==
 
== Mandriva ==
* 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]
**you can come on chans irc://irc.freenode.net/#mandriva-cooker ou irc://irc.freenode.net/#mandrivafr
+
** You can come on chans irc://irc.freenode.net/#mandriva-cooker ou irc://irc.freenode.net/#mandrivafr
  
 
==Ubuntu==
 
==Ubuntu==
* see https://wiki.ubuntu.com/MOTU , more precisely https://wiki.ubuntu.com/UbuntuDevelopment#NewPackages
+
* 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)
+
** 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 helpto see your work incorporated to the official distribution !
+
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 !

Revision as of 13:31, 17 January 2008


Communication Libre > Packages

Indexing

Indexing is important to let know about the software(s) you've developed

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 ?

Mandriva

Ubuntu

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 !