Re: [OMPI devel] Conversion to GitHub: POSTPONED

2014-09-24 Thread Jeff Squyres (jsquyres)
If someone with a .edu account gets us a free Bitbucket for Open MPI, and then we use it for both research and industry stuff... at best, I think that falls into a grey area as to whether this is within Bitbucket's TOS (disclaimer: I haven't read their TOS). It still sounds like a murky

Re: [OMPI devel] Conversion to GitHub: POSTPONED

2014-09-24 Thread Gilles Gouaillardet
my 0.02 US$ ... Bitbucket pricing model is per user (but with free public/private repository up to 5 users) whereas github pricing is per *private* repository (and free public repository and with unlimited users) from an OpenMPI point of view, this means : - with github, only the private

Re: [OMPI devel] Conversion to GitHub: POSTPONED

2014-09-23 Thread Jeff Squyres (jsquyres)
On Sep 23, 2014, at 7:52 PM, Jed Brown wrote: > I don't have experience with GerritHub, but Bitbucket supports this > feature (permissions on branch names/globs) and we use it in PETSc. Thanks for the info. Paul Hargrove said pretty much the same thing to me, off-list.

Re: [OMPI devel] Conversion to GitHub: POSTPONED

2014-09-23 Thread Jed Brown
"Jeff Squyres (jsquyres)" writes: > GerritHub claims to allow us to effectively have ACLs on branches. > I.e., everyone could commit on master, but only release managers can > commit on release branches. This would be nice, and would allow us to > avoid having the 2 repos,

Re: [OMPI devel] Conversion to GitHub: POSTPONED

2014-09-23 Thread Jeff Squyres (jsquyres)
At just about at the last minute, a new contender showed up: GerritHub.io. GerritHub claims to allow us to effectively have ACLs on branches. I.e., everyone could commit on master, but only release managers can commit on release branches. This would be nice, and would allow us to avoid having