sm-grimoire AT lists.ibiblio.org
Subject: Discussion of Spells and Grimoire items
List archive
- From: Jon Svendsen <jon-sven AT frisurf.no>
- To: Eric Sandall <sandalle AT hellhound.homeip.net>
- Cc: sm-grimoire AT lists.ibiblio.org
- Subject: Re: [SM-Grimoire]CVS or Perforce
- Date: 06 Aug 2002 04:29:39 +0200
On Tue, 2002-08-06 at 00:50, Eric Sandall wrote:
> > So, I'd like to suggest:
> > a) make modifications unrestricted to section maintainer;
> I think we should do this ASAP so that those "active developers" can help
> the bogged down gurus. And as you said, quite a few are just "this works
> with gcc3" or "this has a new version". I was looking at it yesterday
> thinking of applying patches, but saw quite a few of these, which don't
> need patches. :)
As a reference to this, I thought I'd describe the solution used by the
GNOME project to address the who-can-commit-where problem. In GNOME CVS,
the root directory of each module contains a file called HACKING. Into
this file, the module maintainers can write "rules" for how other
hackers should behave when dealing with that module. These files
typically contain things like (paraphrased):
"Translators may commit translations."
"Release-critical patches may be commited without prior consent."
"Keep your fingers off my code, you slimey piece of filth."
This way, by letting maintainers decide commit rules themselves, noone
is forced into anything, and the job of making maintainers choose sane
rules are left to the wonders of peer pressure. (This sounds bad but
isn't, in this kind of situation. You really want maintainers to
influence other maintainers on how the job should be done).
I'd like to see us adopt a similar solution, where the guru him/herself
decides what is and is not OK for other people to commit. Examples of
our rules would typically include:
"Simple version bumps and otherwise trivial changes are OK, but let me
know what you did."
"I am on vacation, please keep my section up to date."
"I don't give a damn. Delete all the spells if you want."
"Keep your fingers off my code, you slimey piece of filth."
My point is that it's reasonable for gurus to expect to be in control of
the section that they maintain, and it is therefore also sane that they
are able to excercise control over what other people are allowed to do
to it, rather than just adapting to some centrally decided policy. We
should obviously have recommendations, (and maintainers should obviously
follow them or take the heat for their decision not to) but I doubt that
it is necessary or desirable to force anyone into anything.
Jon
-
Re: [SM-Grimoire]CVS or Perforce
, (continued)
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Julian v. Bock, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Dufflebunk, 08/06/2002
- Re: [SM-Grimoire]CVS or Perforce, Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Dufflebunk, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
- Re: [SM-Grimoire]CVS or Perforce, Eric Sandall, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Julian v. Bock, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Sergey A. Lipnevich, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Jon Svendsen, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Julian v. Bock, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Sergey A. Lipnevich, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Ryan Abrams, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Sergey A. Lipnevich, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Jason Flatt, 08/06/2002
- Re: [SM-Grimoire]CVS or Perforce, Eric Sandall, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Jon Svendsen, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Laurent Wandrebeck, 08/07/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Sergey A. Lipnevich, 08/06/2002
- RE: [SM-Grimoire]CVS or Perforce, Derber, Geoffrey, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
Archive powered by MHonArc 2.6.24.