Re: Compiling Anjuta2 on RH8.0

[Dave Camp <dave ximian com>]

On Tue, 2002-10-22 at 17:53, Andy Piper wrote:
> 
> > > OK to commit that Dave?
> > 
> > That's fine with me, but I'm Not The Maintainer ;)
> 
> Can you just remind us who is? 

JP Rosevear and Naba Kumar.  I tend to feel comfortable approving
patches to the pieces I wrote (which includes the shell and document
manager), and they haven't yelled at me yet.

> What is the policy for modifying the
> anjuta2 modules or submitting patches? 

JP and Naba maintain the anjuta2 module.  Additionally, Dirk Vangestel
and I have unrestricted commit access.

To quote anjuta2/HACKING:

"Minor changes (build fixes, typos, documentation and small bug fixes)
can be committed at will, but please send a note to the maintainer(s)
alerting them to what you have done and be sure to include a ChangeLog
entry.

"Major changes should be submitted for approval to the maintainer(s).

"Please read docs/style.txt for information on the coding style used."

> ... it makes it easier for newcomers if this kind of stuff is readily
> accessible. If I have time - which is *unlikely* - I'll pull together my
> build script, with a link to the Hacking Anjuta2 paper and other useful
> information (such as RPMs I needed to install on RH8 in order to get
> anywhere)

It is easily accessible in the anjuta2/HACKING file.  I firmly believe
that we can expect would-be hackers to read the HACKING and README files
in a module they want to commit to.  These files are the canonical
location for this sort information, and adding any more information is
just another point of failure.  If somebody wants to duplicate this
information on a web page that's fine, but it will be up to them to keep
it up to date with the HACKING and README files, not the other way
around.
 
-- 
Dave Camp <dave ximian com>