Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: softfail (nike.apache.org: transitioning domain of
 clint@traveljury.com does not designate 74.125.82.177 as permitted sender)
Subject: Re: mod_perl on github
From: Clinton Gormley <clint@traveljury.com>
To: Vick Khera <khera@kcilink.com>
Cc: mod_perl Dev <dev@perl.apache.org>
In-Reply-To: <B4443961-206B-4E0F-AA33-1F777380DA9A@kcilink.com>
References: <1283158249.21951.20.camel@balrog.traveljury.com>
	 <B4443961-206B-4E0F-AA33-1F777380DA9A@kcilink.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 30 Aug 2010 16:16:40 +0200
Message-ID: <1283177800.21951.74.camel@balrog.traveljury.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


> It makes perfect sense to me :-)

You must have special powers :)
> 
> > I thought, "this would be so much easier, and faster, in git"
> 
> I think that would make it much harder for me :-(
> 
I realise that this is a bit of a vim vs emacs topic.  My own experience
has been that it took me a while to make the change to git, but having
done so, I have never looked back.

A number of mod_perl devs are already on github, so I'd assume that they
are comfortable with using it, but clearly there are others (such as
yourself) who are not.

As I said before, I'm not a mod_perl dev, and am in no way trying to
hijack the source code, or force anybody into anything. My thinking was
more along the lines of, perhaps nobody has done this because of a lack
of time, rather than a lack of desire, so I thought I'd do the work and
then see if others want it too.


> We use the apache resources, and that implies svn.  I think having a
> copy on github will cause confusion to newcomers and people searching
> for mod_perl source who do not know the official location, especially
> if it is not kept up-to-date.


I agree that there shouldn't be an out of date copy on github, so there
are a few possibilities:

1) use svn as the main repo, and push changes to github
2) use github as the main repo, and push changes to svn
3) allow commits to both svn and github, and sync changes
4) abandon svn
5) abandon github

My personal preference would be (2) or (4), but my opinion doesn't
count. I'm just a user. That said, github makes contributing so easy
that it could attract more developers, without the hassle of giving out
commit bits, which is why I prefer (2) or (4) over (1).

Point (3) tries to please everybody, but I'm not sure how easy that
would be to automate. It'd probably require somebody to be responsible.

As I said, I'm suggesting this because I'd like to see the mod_perl code
on github, but if you guys don't want to do it, then I'll happily get
back in my box :)

clint


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org