The ideas I would like to do/see.
Une petite liste d'idées que je voudrais faire/voir.
The good point of spending 2 weeks without touching a keyboard is that it gives you ideas on what you want to do or see done.
There is what I have been thinking of:
- R2spec is a tool to create spec file, and now rpm, for R packages. It has quite evolve since I first write it and my python knowledge for sure has changed. I therefore would like to clean it and rewrite it to a more logical and hopefully cleaner code.
- cran2rpm, this is a tool to generate the order in which the R packages should be built for a given repo. This would be used with R2spec to generate RPMs for the whole CRAN or Bioconductor. There has been some thoughts about it on the Fedora-R-devel mailing-list and it is something I would like to help as I don't think I'd have time to do it myself.
- Revelation is a password management tool. If I had time I would like to remove its warnings and even implement a pgp encryption for the database. At some point I started to rewrite it but it would be simpler to just work on revelation rather than rewrite everything.
- pkgdb-cli would be a tool to query the package database of Fedora. It would give you the version of the package in the different repo, the owner of the package on the different branches and if possible maybe it could also handle ACL request. So basically a CLI version of pkgdb.
- Make yum-utils a python library. At the moment most of yum-utils' code are simple python file, I was thinking that making it a python library would be nice as it would allow people to import yumutils and use the code easily.
- ABRT report upstream. This is something I have been thinking about but I never shared it nor did I check if the discussion already happened, but I was thinking that there cases were one would like ABRT to report its bug to the bug tracker of the project rather than Fedora's bugzilla. I was thinking that there could be a plugin system on ABRT with a plugin for each bug tracker system (trac, bugzilla, google code...) and a small database containing for each packages concerned the url of the bug tracker, its system and username and password. When a bug would be detected, ABRT would check if the package is present in the database, if it is, then the bug is opened against this bug tracker otherwise it is opened in Fedora's bugzilla.
So there are my few ideas. I don't know whether they are good nor if I will have time to work on them. But what do you think about them?
If there are people interested about them, maybe I could make some time ;-)