Help yourself with the documentation.
Find an opened issue on this website, or write you own bugfix or feature. Then, once it is necessary, commit with:
$ git commit -a
Do not forget to write a helpful commit message.
You can run these scripts to be sure your patch doesn’t break anything:
$ tools/pyflakes.sh $ tools/run_tests.sh yourmodulename # or without yourmodulename to test everything
Perhaps you should also write or fix tests.
$ git format-patch -n -s origin
Then, send them with this command:
$ git send-email --email@example.com *.patch
You can also send the files by yourself if you haven’t any configured MTA on your system.
To be sure weboob works fine on lot of architectures, OS and configurations, but also that websites haven’t changed and backends still support them, it’s important to have enough buildbot slaves.
If you are interested by hosting a buildbot slave, follow these instructions:
Firstly, you have to install pyflakes, nose and buildbot.
$ buildslave create-slave <dirname> buildbot.weboob.org:9080 <name> <password>
if you use an old version of buildbot, run buildbot instead of buildslave.
$ buildslave create-slave /home/me/buildbot buildbot.weboob.org:9080 me secret123
Then, edit files in /home/me/buildbot/info/ and run the slave:
$ buildslave start /home/me/buildbot
To connect your slave to our master, you can send us an email on firstname.lastname@example.org with the following information:
When your slave will be accepted, you will see it on http://buildbot.weboob.org/waterfall.
When a build is requested by master, your slave updates its local git repository, and run tools/run_tests.sh.
To work correctly, we suggest you to add as many as possible backends with the user of the slave. No private information will be sent to master, and it’s better to have tests on backends which need authentication, because not every developers have accounts on them.