Ticket #702 (closed provenpackager request: fixed)
provenpackager request - denisarnaud
|Reported by:||denisarnaud||Owned by:|
- I have been packaging for Fedora for almost three years by now, mainly to submit packages for which I am part of the upstream teams. And, down that way, since those upstream projects use Fedora-packaged components, such as Boost and Soci, I have been led to maintain and/or co-maintain those important Fedora components.
- Apart from Boost (see below the Rationale section for details on my contribution to the packaging of Boost), I intend to maintain around 15-20 packages, which have not been all submitted: https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&emailreporter1=1&emailtype1=exact&email1=denis.arnaud_fedora%40m4x.org
- As I spend most of my spare time maintaining my own open source projects, and packaging them into Fedora, I did not have that much time to review a lot of packages myself. However, whenever I can, I strive to help in a few reviews, especially the ones related to C++ or Python languages, as well as related to the scientific (in particular, operations research, mathematics and physics), GIS or image handling arenas. For instance, I helped dis-embedding and packaging TCLAP from Hugin: https://bugzilla.redhat.com/show_bug.cgi?id=683591
- The full list of review/merge review bugs, I was involved in, including my own review requests and reviews, is as following: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&emaillongdesc1=1&email1=denis.arnaud_fedora%40m4x.org&component=Package%20Review&emailtype1=substring
- I have been practicing the guidelines for a while and, as an upstream developer, I now have a pretty good knowledge and practice of:
- the build frameworks (e.g., GNU Autotools and CMake, but also some SCons, Ant, Maven, Ivy and Rake);
- documentation processes (Doxygen, JavaDoc, Latex);
- testing frameworks (CruiseControl, Hudson/Jenkins?, Boost Unit Test framework);
- project management frameworks (Trac and Redmine);
- delivery and deployment infrastructures (Heroku, Google App. Engine, Eucalyptus, Amazon);
- "alien" packaging processes (Debian).
- For every new Fedora release, I upgrade Boost to the newest available version. For instance, Boost-1.48.0 is being slipped into Fedora Rawhide to be generally available with Fedora 17.
- And, every time Boost is upgraded, numerous Fedora packages have to be rebuilt, and some have even to be patched, in order to follow the new Boost API. Some older APIs are constantly deprecated, as for instance with Boost.Filesystem v2.
- As both my co-maintainers (Petr Machata, a.k.a pmachata, and Deji Akingunola, a.k.a. deji) are not proven-packagers themselves, we have to file bug reports/rel-eng tickets every time for all the packages which are depending on Boost. An example of such procedure is explained by Petr in that message. Being a proven-packager myself would allow me to participate more actively to the Boost upgrade process, and to make it smoother for all the maintainers of those packages.
- By the way, Adam Williamson himself recommended that (some of) the Boost co-maintainers apply for a proven-packager status.
- I would not use my proven packager privileges (in other words, I do not intend) to update packages out of the above-detailed scope. I am already kept very busy with all that activity, without having to interfere with technologies with which I am less at ease.
- I copy Petr, so as to suggest that he also applies to become a proven packager :)
Note: See TracTickets for help on using tickets.