Re: [Condor-devel] github revisited.

[Ziliang Guo <ziliang@xxxxxxxxxxx>]

Alan De Smet brought one up last time this came up that was never
addressed (or I don't remember it being addressed), how to handle
security embargoes.

On Fri, Sep 14, 2012 at 3:47 PM, Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx> wrote:
> On Friday, 14 September, 2012 at 4:31 PM, Matthew Farrellee wrote:
>
> So far, no one has listed any negatives. Either there are none of people
> who know of some have not spoken up.
>
> Do you know of any?
>
>
> I'm pro github but there are some downsides to it:
>
> You have to have a strategy for managing the pull requests. They'll be a new
> burden on your wrangler(s). And, AFAIK, you can't make the comment streams
> on them private so you've got to keep a level head on them. People can get
> touchy when you tell them no. It's also something that's not part of the
> regular git workflow.
>
> You have to have an outage strategy. Github was done this week for at least
> a whole morning -- what'd you do when that happens?
>
> Don't not backup. Maybe more important now that you're not keeping the bare
> repo on your own disk.
>
> Have a long term strategy for managing the "company" on github -- presumably
> you'll put this in a "company" account and not tie it to one person's
> personal github account so you need to have company account managers, a
> strategy for dealing with attrition, that sort of stuff.
>
> That's the stuff that comes to quickly to mind.
>
> Also, it may be worth considering:
>
> https://bitbucket.org/ -- supports git now, not just mercurial
> http://code.google.com/ -- has the long-term stability of Google behind it
> which is perhaps comforting
>
> - Ian
>
> --
> Ian Chesal
>
> Cycle Computing, LLC
> Leader in Open Compute Solutions for Clouds, Servers, and Desktops
> Enterprise Condor Support and Management Tools
> 888.292.5320
>
> http://www.cyclecomputing.com
> http://www.cyclecloud.com
> http://twitter.com/cyclecomputing
>
> _______________________________________________
> Condor-devel mailing list
> Condor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel