X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Re: [Geda-developers] git.geda-project.org permissions change
From: al davis <ad252 AT freeelectron DOT net>
Date: Tue, 10 Sep 2013 23:18:46 -0400
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201309102318.46300.ad252@freeelectron.net>
Reply-To: geda-user AT delorie DOT com

On Sunday 08 September 2013, Markus Hitter wrote:
> Am 08.09.2013 um 20:07 schrieb Peter TB Brett:
> > I've now changed the default git push policy for all repos
> > on geda-project.org:
> > 
> > - @admins have the ability to git push and git push --force
> > 
> > - Other developers have the ability to git push only.

I had to look that up...
================
       -f, --force
           Usually, the command refuses to update a remote ref 
that is not an ancestor of the local ref used to overwrite it. 
This flag disables the check. This can cause the remote 
repository to lose commits; use it with care.
================

It looks to me like this is something to use only in extreme 
situations.  I think the restriction is appropriate.  I would 
not want to work on a project where just anyone could --force 
and mess things up.  I would be bothered if even the admin used 
it unnecessarily.

For a project to thrive long term, somebody needs to be in 
charge.  To let a minor developer "--force" big changes and 
break tracking will most likely lead to a big mess eventually, 
maybe even a hostile takeover of the project, completely 
changing its course.

All contributors need to learn the style of the project and work 
as a team.  I think "we don't use --force" is quite reasonable.