We can't live, work, or learn in freedom unless the software we use is free.
Become an associate member and join the free software movement in defending your freedoms before August 7th! Read more >

200 members

Tips for new GNU maintainers

If you are new to maintaining a GNU package, whether one that you have offered to GNU or an existing one that you have adopted, it can be overwhelming to know where to start. The official email notice you received when you became a GNU maintainer has lots of details; this document is not a replacement for that email, but rather a complement, aiming to provide some tips on getting started.

Of course, what's listed here just skims the surface of GNU maintainership. Please be sure to read the GNU Maintainers Guide and the GNU Coding Standards. Indeed, you should have read them already, but they are densely enough written that careful re-readings are useful. In addition, a few experienced GNU contributors have volunteered to answer questions about GNU maintenance via <[email protected]> as well as <[email protected]>.

First steps for new maintainers

These tasks are listed in order of priority. The labels ([All], [New], and [Adopted]) indicate the category of packages each task mostly applies to.

  1. [All] Update project information on Savannah. Go to your project page (https://sv.gnu.org/projects/PKG, where PKG is the name of your package), log in with your Savannah ID, and check under “Update public info” in the “Main” menu. Here, you should set the project's full name and, if needed, write both a short and a long description for it (please also send those descriptions to <[email protected]> for use in the lists of all GNU packages). You should also set its development status to reflect the maturity of the code. It is essential to do this if you have adopted a package, since it will be marked as “Orphan”.
  2. [All] Turn to the mailing lists. If you have a new GNU package, you should set up at least one mailing list for the package (“Select features” in the Main menu). It is strongly recommended to have one called <[email protected]>; others can wait until traffic warrants. If you have adopted an existing package, send an email introducing yourself. Finally, whether lists are newly created or already existing, don't forget to subscribe yourself, as this is not automatically done. (About dealing with mail.)
  3. [New] Set up a repository for your source code (“Select features” in the Main menu), and import whatever is available (look up the procedures under “Source Code Manager” in the Development Tools section). Experience has shown that self-hosting is unreliable. (About back-up files.)
  4. [New] Upload your package to the GNU FTP site if it is ready for public release. (About the upload procedure.)
  5. [New] Create a GNU home page, to replace the PKG.html file that webmasters have placed in your web repo (keep the same name). If you want to make this quick and easy, use our standard template. Comment out the irrelevant parts, such as Downloading and Documentation if the project has barely started; you'll complete them later on. Also put any documentation you already have in a subdirectory called “manual”. (About web pages.)
  6. [Adopted] Check for existing bug reports if you have adopted an existing package. These may be on any or all of a Savannah bug tracker, a mailing list (mbox archives can be downloaded by HTTPS), or the GNU debbugs server. (About replying to bug reports.)
  7. [Adopted] Contact distro packagers. If you have adopted an existing package and it is available in downstream distros, get in contact with the packagers. It is likely that they have unresolved bug reports to be addressed, and perhaps even patches that should be applied. You may also like to get involved with the GNU Guix package manager. (About distros.)
  8. [Adopted] Use the software. It should go without saying that if you have adopted a GNU package, you should use it to get a feel for its current status and to discover what might need to be fixed.
  9. [All] Pick some tasks and start hacking! There's no substitute for spending time doing the actual work.

General tips on maintaining GNU software

To conclude this list with one final reiteration: the information and links above are just a sampling. Please refer to and (re)read the full GNU Maintainer Information and GNU Coding Standards documents for plenty more.

GNU Philosophy

This also seems like an appropriate page on which to give some links to the basic ideas of GNU and free software:

Available for this page:

[en] English   [fr] fran?ais   [pt-br] português  

 [FSF logo]  “The Free Software Foundation (FSF) is a nonprofit with a worldwide mission to promote computer user freedom. We defend the rights of all software users.”

意甲教母 青海11选5前3直 股权投资基金配资 彩票极速赛车计划软件下载 甘肃十一选五开奖结果今天开奖结果查询结果 天津时时彩开奖号码图 今天广西快乐十分开奖结果 赣州期货配资公司怎么样 pc蛋蛋幸运28赌博 江苏快三计划精准版 明天股票行情大盘走势 排列三直选绝密技巧 快三内蒙古快三走势图今天开始 2007年上证指数 双色球真有人中500万吗 福利彩票3d专家杀号 场外配资的监管