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. I'd say that pull requests are quite compelling, but not compelling enough to do an overnight switch. 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. Brian On Sep 14, 2012, at 4:48 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx> 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 > Condor-devel@xxxxxxxxxxx > https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
Attachment:
smime.p7s
Description: S/MIME cryptographic signature