On Tue, 17 Mar 2009, Fabio M. Di Nitto wrote:
On Tue, 2009-03-17 at 08:37 -0500, Mike McGrath wrote:
> On Tue, 17 Mar 2009, Fabio M. Di Nitto wrote:
> > On Tue, 2009-03-17 at 08:23 -0500, Mike McGrath wrote:
> > > On Tue, 17 Mar 2009, Fabio M. Di Nitto wrote:
> > >
> > > > On Tue, 2009-03-17 at 11:25 +0100, Jim Meyering wrote:
> > > > > I've been lurking here for some time, and have seen
> > > > > some recent opportunities to help make a difference,
> > > > > so have just applied for membership to the sysadmin group.
> > > > > For example, Fabio Di Nitto and I would like to set up
> > > > > an svn-to-git mirror for a project on fedorahosted.
> > > > >
> > > > > While I set up and maintain git.et.redhat.com
, it's not open
> > > > > access to people outside of Red Hat, so it's rather
> > > >
> > > > I am planning to help Jim to get this project going and maintain the
> > > > tress I already own. Since they are all "special" cases
> > > > fedorahosted, this will lift some work from the usual suspects.
> > > >
> > >
> > > I'm confused as to what this actually means. The subject and bodies
> > > these emails don't match eachother :)
> > >
> > > What is it exactly you two are proposing?
> > >
> > Right.. 2 things.. I shouldn't have mixed them up.
> > 1) Jim and I need to setup an svn-to-git mirroring within fedorahosted.
> > This will allow a one direction way to export svn projects into git
> > and sync via svn hooks. For eg. svn.fh.o/corosync/trunk to
> > git.fh.o/corosync.git/master branch.
> > We have plenty of use cases for this setup.
> > 2) Personally, I often ask guys around to do this or that on the git
> > trees I own on fedora hosted. For me, being able to access hosted* to do
> > the job myself, will lift work from the other admins and speed up things
> > around.
> So are you two working on a svn mirroring solution for Fedora Hosted svn
> projects? Or just a couple of one offs for your own hosted repos?
I don't like "one off" solutions at all.
We will start clearly with one project to drive the tests.
If the test drive results in some good, then we will make it generally
available. There is no point to keep a secret either.
I just don't like the precident of "I want to do X with my project and you
don't support it, let me log in and do it myself." I'm also trying to
make sure the pros of this outweigh the cons.