[Gossip-dev] (no subject)
Martyn Russell
martyn at imendio.com
Sun Mar 25 22:45:02 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Charly Caulet wrote:
> Hello,
>
> I have never participated to any project. So I don't know the steps to
> follow to fix a bug.
>
> By example :
> 1. Get the lastest svn sources
> 2. fix the bug
> 3. commit the new sources.
>
>
> I assume there are some rules to follow. Maybe exists a document that
> explains it?
Hi!
If you are fixing bugs, the best thing to do is to create a new bug in
bugzilla (http://bugzilla.gnome.org) so you can keep track of bugs and
patches together.
If you have commit access, and have gained trust with the project, you
will eventually be able to commit patches yourself, but initially, we
will do that for you.
It is great that you want to help out. If you want to fix already
outstanding issues, you can view the "gnome-love" bugs, "gnome-love"
being the keyword in Bugzilla. I would recommend having a look at some
of these if you are interested, just to get you started and to
understand the code base:
http://bugzilla.gnome.org/reports/keyword-search.cgi?product=gossip&keyword=gnome-love
- --
Regards,
Martyn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBt9OwpLEnE7M298RAgotAKCgsv3Z33XiAoIvGwbx6bZ0PW45TwCgk1MF
a5xp0SI7fMFqQVJ92yk2FsM=
=5HdA
-----END PGP SIGNATURE-----
More information about the Gossip-dev
mailing list