BugFixingInitiative
Getting Started |
Bug fixing initiatives
We plan to have regular bug fixing initiatives, which should be particularly interesting for new contributors.
Instructions
If you are interested in helping out, you might want to
- read these articles first:
Our development guide has much more interesting information as well.
join us in #ubuntu-motu on IRC
Please: If you decide to work on fixing the issues pointed out below, please make sure you add your Launchpad ID next to them, ie:
- fix bug 12345
turns into
- fix bug 12345 (dholbach)
Have a great time and be sure to ask questions if you have any.
New contributors
Spelling errors
Here are a few packages which have spelling errors in their package description. An easy way to fix them is:
run bzr branch ubuntu:<packagename>
edit the debian/control file
- fix the spelling mistake
run dch -i to document the change you did
- For the ones specifically mentioned below:
run debcommit
run bzr push lp:~<your LP ID>/ubuntu/quantal/<source package>/typo-fix
run bzr lp-propose
This time around we will try to fix the following issues:
revu-tools (informations information) (scarneiro)
qlix, qlix-dbg (intuative intuitive) (scarneiro)
swac-play (allows to allows one to) (contato-brunoribeiro)
encadre-image (automaticaly automatically) (contato-brunoribeiro)
semantik (targetted targeted) (contato-brunoribeiro)
- installation-report-generator (informations information)
- linux-tools-3.4.0-3 (dependant dependent)
python-zope.size (allows to allows one to)
- happycoders-libdbg-dev (This packages These packages)
- qgfe (allows to allows one to)
- kdevelop-custom-buildsystem (arbitary arbitrary, allows to allows one to)
- gambas2-gb-crypt (allows to allows one to)
vdr-genindex (Usefull Useful)
There are obviously more packages to be fixed, but as they are also in Debian, we'd prefer to get them fixed in Debian, so you might want to take these steps as well:
run bzr bd -- -S
run submittodebian to submit your changes to Debian
Experienced contributors
GCC 4.7
If you have a bit more experience, you might want to help out with the transition to gcc-4.7.
Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html
- To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from quantal.
Here's the list in the Debian bug tracker:
Outstanding bugs -- Serious (policy violations or makes package unfit for release); Unclassified
Forwarded bugs -- Serious (policy violations or makes package unfit for release)
Make sure you
Java 7
If you are a bit more experienced and have worked with Java before this might be just the right thing for you.
Have a look at JavaTeam/Java7Default and familiarise yourself with the general task of porting packages to Java 7
Pick any of the bug list and propose a fix
Make sure you
submit your changes to Debian with the usertag 'openjdk-7-transition'
More bugs
MOTU/TODO lists lots and lots of other tasks you might want to start working on.
Organisation
If you want to help out organising these events, check out our Organisation page and join us at MOTU/Meetings or generally in #ubuntu-motu on irc.freenode.net