Re: Gnome Development

[<bordoley msu edu>]

The general procedure is to check out a copy of anonymous cvs. Hack that and
than provide a patch according to how the maintainer has specified in the
HACKING file. Typically patches should be submitted either by attaching them
to bugzilla bugs, or in some cases (such as nautilus) emailing them to the
project specific mailing list. This information is typically included in the
HACKING file as well.

dave


James Drabb <JDrabb darden com> said:

> Hello group,
> 
> I wanted to see if I can get any tips on contributing to GNOME
> development.
> I have been a programmer for the dark side for 5 years and I have been
> using
> Linux for 3-4 years.  I have done some Linux/Solaris C/C++ development
> here
> at work, however for the time being most development is on Windoze.  Are
> there any docs that tells one how to start helping out with GNOME?  Does
> one check GNOME out of CVS and just make changes and check it in?  Or
> should I send patches?  What is the preferred diff command for GNOME?
> What
> are some good development tips for GNOME (i.e. check out cvs, make
> changes,
> compile, change the path, start new gnome, etc.).
> 
> As you can see, I have tons of question and I would really like to
> contribute and use my talents to help gnome get better.
> 
> Thanks,
> 
> Jim Drabb
> --
> -------------------------------------------------------------
> Never ask a geek why, just nod your head and slowly back away
> -------------------------------------------------------------
> James Drabb JR
> Programmer Analyst
> Darden Restaurants
> Business Systems
> JDrabb Darden com
> _______________________________________________
> gnome-list mailing list
> gnome-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-list
>