Despite my original snark, I think it's important to note that motivation for 
the original thread was "How can we lower the barrier to entry for those in the 
community to get involved"  

So there is little urgency, but I think the long term importance is worth the 
re:pinging this thread every so often. 

inline comments below. 

----- Original Message -----
> From: "Brian Bockelman" <[email protected]>
> To: "Todd Tannenbaum" <[email protected]>
> Cc: [email protected]
> Sent: Monday, September 17, 2012 7:26:42 AM
> Subject: Re: [Condor-devel] github revisited.
> 
> Hi,
> 
> As I stated the first time around (I think), I think we cover lots of
> the use cases with a read-only mirror of Condor on github, plus
> training committers how to commit pull requests to the main repo (as
> opposed to committing them to the mirror).  Having a read-only
> mirror on github helps the project's visibility, but still allows a
> private UW branch for the "security embargo" model.

Agreed, and I think a mirror is up too. 

> 
> I'd say that pull requests are quite compelling, but not compelling
> enough to do an overnight switch.
> 

Agreed.  I think somehow the idea of changing the world flop'd into the mix 
(perhaps because of snarkyness). 

> I agree the CVSTrac interface has a retro 1998 feel, but modulo a
> volunteer to port things over to another system, it's what we have
> for now.  While broken, it's not broken enough to burn it down ...
> yet.
> 

Agreed.

> Brian
> 
> On Sep 14, 2012, at 4:48 PM, Todd Tannenbaum <[email protected]>
> wrote:
> 
> >> 
> >> It takes time to make the switch,
> > 
> > Yes!
> > 
> >> especially with figuring out how to migrate
> >> all of your CVSTrac items to GitHub. There's not a compelling
> >> reason to switch
> >> to GitHub - Github's version of pull requests, while nice, aren't
> >> especially
> >> compelling.
> >> 
> > 
> > Yes again!
> > 
> >> I think CVSTrac is clunky and feels like it hasn't been updated
> >> since 1998,
> >> Condor should have gone to GitHub in the first place, and that
> >> Condor just
> >> in generally does not use git/distributed source code management
> >> at all as
> >> effectively as it could. But whatever, it's not terrible today,
> >> and switching
> >> now isn't going to fix the things in Condor that should be higher
> >> priority to
> >> fix.
> >> 
> > 
> > Yes a third time!
> > 
> > -Todd
> > _______________________________________________
> > Condor-devel mailing list
> > [email protected]
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
> 
> 
> _______________________________________________
> Condor-devel mailing list
> [email protected]
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
_______________________________________________
Condor-devel mailing list
[email protected]
https://lists.cs.wisc.edu/mailman/listinfo/condor-devel

Reply via email to