Re: [OMPI devel] Conversion to GitHub: POSTPONED
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 the 2 repos, like we're currently planning to do at Github (i.e., "ompi" and "ompi-release"). We need a little time to investigate this, and it seems prudent to postpone the transition tomorrow. We'll tentatively aim for *next* Wednesday, October 1, 2014. On Sep 23, 2014, at 11:53 AM, Jeff Squyres (jsquyres) wrote: > REMINDER: The conversion of Open MPI's Subversion repository and Trac tickets > will be happening tomorrow, Wednesday, September 24, 2014. > > SVN and Trac will be going read-only at 8am US Eastern tomorrow, and the > conversion process will begin. I anticipate it taking all day. > > I'll send an "all clear" email when I'm all finished, along with additional > details. > > You should probably go read up on how we're going to use GitHub: > >https://github.com/open-mpi/ompi/wiki > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] Conversion to GitHub: POSTPONED
"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, like we're currently planning to do at > Github (i.e., "ompi" and "ompi-release"). I don't have experience with GerritHub, but Bitbucket supports this feature (permissions on branch names/globs) and we use it in PETSc. pgpGdCnibB071.pgp Description: PGP signature
Re: [OMPI devel] Conversion to GitHub: POSTPONED
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. I'll check it out. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] Conversion to GitHub: POSTPONED
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 ompi-tests repository requires a fee - with bitbucket, the ompi repository requires a fee (there are 119 users in https://github.com/open-mpi/authors/blob/master/authors.txt, in bitbucket pricing model, that means unlimited users and this is 200US$ per month) per branch ACL is a feature that was requested lng time ago on bitbucket, and now they implemented it, i would not expect it takes too much time before github implements it too. from the documentation, gerrithub has also interesting features : - force the use of a workflow (assuming the workflow is a good match with how we want to work ...) - prevent developers from commiting a huge mess to github Gilles On 2014/09/24 10:36, Jeff Squyres (jsquyres) wrote: > 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. > > I'll check it out. >
Re: [OMPI devel] Conversion to GitHub: POSTPONED
The pricing question might not be as simple as it first sounds. At BitBucket Academic accounts are free and allow unlimited users. So, if somebody with an .EDU email address (IU and UTK come to mind) are the owners of the repo then I believe the cost is zero. Somebody should verify that rather than take my word for it. More points for comparison between BitBucket and GitHub are presented in http://www.infoworld.com/article/2611771/application-development/bitbucket-vs--github--which-project-host-has-the-most-.html -Paul On Tue, Sep 23, 2014 at 8:39 PM, Gilles Gouaillardet < gilles.gouaillar...@iferc.org> wrote: > 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 ompi-tests repository requires a fee > - with bitbucket, the ompi repository requires a fee (there are 119 > users in https://github.com/open-mpi/authors/blob/master/authors.txt, in > bitbucket pricing model, that means unlimited users and this is 200US$ > per month) > > per branch ACL is a feature that was requested lng time ago on > bitbucket, and now they implemented it, i would not expect it takes > too much time before github implements it too. > > from the documentation, gerrithub has also interesting features : > - force the use of a workflow (assuming the workflow is a good match > with how we want to work ...) > - prevent developers from commiting a huge mess to github > > Gilles > > On 2014/09/24 10:36, Jeff Squyres (jsquyres) wrote: > > 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. > > > > I'll check it out. > > > > ___ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/09/15909.php > -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies Group Computer and Data Sciences Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
Re: [OMPI devel] Conversion to GitHub: POSTPONED
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 prospect; I'm not sure it's within the intent of a free account. Paying a reasonable amount for a private account isn't out of the question. Indeed, Cisco has already paid $300 for the first year of a Github account so that OMPI can have a private repo. :-\ That can be written off, if necessary, but it would be nice not to. However, paying per developer may become prohibitive -- infrequent bulk payments (e.g., $300/year) are do-able from those of us at corporations. Managing a monthly fee that is dependent upon the number of active committers (and that number changes over time) could get a bit... complex, in terms of corporate payments / reimbursements. That being said, there's quite a bit of OMPI infrastructure that is actively in use at GitHub. It would be a bit of a pain to migrate all of that *again* (from SVN/Trac -> Git/Github -> Git/Bitbucket). Remember, it's not just moving the repos (which, since most repos are now Git, is easy to move to another hosting provider); it's also moving the wiki and the tickets, too. That will take more effort. All the above being said: 1. I'll still have a look at Bitbucket today. It may be a workable model that the main OMPI repo (and wiki and tickets) is at Bitbucket, and most other repos (and wikis and tickets) are at Github. 2. I just sent a mail to Github support asking them if they plan to support per-branch push ACLs. I don't know if they'll be able to give a direct answer, but it's worth asking. It would be a little weird to span Github and Bitbucket, but the individual OMPI sub-projects are suitably independent of each other such that it could work. Indeed, we've effectively been doing that for a while (e.g., hwloc has been at Github for quite a few months now), but that was never intended to be the desired end state. On Sep 23, 2014, at 11:57 PM, Paul Hargrove wrote: > The pricing question might not be as simple as it first sounds. At BitBucket > Academic accounts are free and allow unlimited users. So, if somebody with > an .EDU email address (IU and UTK come to mind) are the owners of the repo > then I believe the cost is zero. Somebody should verify that rather than > take my word for it. > > More points for comparison between BitBucket and GitHub are presented in > > http://www.infoworld.com/article/2611771/application-development/bitbucket-vs--github--which-project-host-has-the-most-.html > > -Paul > > On Tue, Sep 23, 2014 at 8:39 PM, Gilles Gouaillardet > wrote: > 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 ompi-tests repository requires a fee > - with bitbucket, the ompi repository requires a fee (there are 119 > users in https://github.com/open-mpi/authors/blob/master/authors.txt, in > bitbucket pricing model, that means unlimited users and this is 200US$ > per month) > > per branch ACL is a feature that was requested lng time ago on > bitbucket, and now they implemented it, i would not expect it takes > too much time before github implements it too. > > from the documentation, gerrithub has also interesting features : > - force the use of a workflow (assuming the workflow is a good match > with how we want to work ...) > - prevent developers from commiting a huge mess to github > > Gilles > > On 2014/09/24 10:36, Jeff Squyres (jsquyres) wrote: > > 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. > > > > I'll check it out. > > > > ___ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/09/15909.php > > > > -- > Paul H. Hargrove phhargr...@lbl.gov > Future Technologies Group > Computer and Data Sciences Department Tel: +1-510-495-2352 > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > ___ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/09/15910.php -- Jeff Squyres jsquy...@cisco.com For corporate legal
