----- Original Message ----
> From: Brad Nicholes <BNICHOLES@...>
> To: Jesse Becker <hawson@...>; ganglia-developers <ganglia-developers@...>
> Sent: Thursday, July 10, 2008 9:48:20 PM
> Subject: Re: [Ganglia-developers] [Ganglia-svn] SF.net SVN: ganglia:trunk/monitor-core/Makefile.am
> >>> On 7/10/2008 at 12:52 PM, in message
> , "Jesse Becker"
> > On Thu, Jul 10, 2008 at 13:15, Brad Nicholes wrote:
> >> I'm OK with it either way. If we add contrib/ to the package, then we
> > should still have someplace where we put stuff that we like and think is
> > valuable, but haven't approved yet. Does that make sense? However a
> > download page on the wiki or some other kind of web directory listing might
> > make it easier to reference for the user.
> > This is exactly what "contrib" directories are for: things that are
> > useful and worth distributing as a courtesy, but are *not* directly
> > supported by the main development team. If something is ever
> > promoted/taken over by main developers, then it gets removed from
> > contrib/, and added into the "proper" location elsewhere in the
> > project.
> So what does that mean? Should contrib/ be part of the tarballs, snapshots,
> releases or just an SVN repository location for misc. stuff?
I personally would put them into any archive that gets into the hand of developers: tarballs, src-RPMs, ... They don't neccessarily have to be part of the binary packages. On the other hand, would it hurt? What about "/usr/share/ganglia/contrib/" ?