[ESS] public git mirror?
spinuvit at gmail.com
Thu Feb 9 14:09:53 CET 2012
>>>> Yihui Xie <xie at yihui.name>
>>>> on Wed, 8 Feb 2012 17:41:19 -0600 wrote:
YX> I think it almost completely depends on whether the developers want
YX> this project to be decentralized or not. If a small group of rigid
YX> developers is preferred, it will be hard for us to convince ESS
YX> developers to move over, no matter how many goodies there are on
YX> GitHub. That being said, I still want to second Vitalie.
Organizations on GitHub are actually a convex-combination of the
styles. The main team is working on a common repo. Everyone else is forking
the usual way. At least this is what I got from the description.
And it's not about switching yet, but rather about creating an official
mirror on GitHub. People can freely work the old svn ways if they wish
YX> Yihui Xie <xieyihui at gmail.com>
YX> Phone: 515-294-2465 Web: http://yihui.nameDepartment of Statistics, Iowa State University
YX> 2215 Snedecor Hall, Ames, IA
YX> On Wed, Feb 8, 2012 at 4:33 PM, Ken Williams
YX> <Ken.Williams at windlogics.com> wrote:
>>> -----Original Message-----
>>> From: ess-help-bounces at r-project.org [mailto:ess-help-bounces at r-
>>> project.org] On Behalf Of Vitalie Spinu
>>> Sent: Wednesday, February 08, 2012 12:31 PM
>>> To: Martin Maechler
>>> Cc: ess-help at r-project.org; Rodney Sparapani
>>> Subject: Re: [ESS] public git mirror?
>>> It's actually a two-way path, we also don't have enough developers because
>>> of the rigid development system. Git encourages and is all about branching.
>>> On GitHub forking and pull requests are one click away. Very decent bug
>>> tracking system, network graphs , statistics and all their pro-social-and-
>>> collaboration tools are making contribution painless and as frictionless as it
>>> can possibly be.
>>> GitHub is full of one-file.el projects with more people on it than ESS has
>>> developers. Such a big project as ESS will end up with many more.
>> Just to add my perspective: whenever I want to get involved with an open-source project these days, I basically (slightly subconsciously) *expect* it to be hosted on Git, preferably on GitHub. If it's not, the barriers to entry are a lot higher, so I might just not bother getting involved at all. It does make a big difference.
>> I've noticed the same thing on the flip side, when people want to contribute to a project of mine (typically some Perl module, pretty similar in size to ESS), the first question they ask is whether I'd support moving to Git. I always say yes, the process takes about 5 minutes, most of which is just filling out a form on GitHub describing the project.
>> I appreciate the learning curve that the core folks would have to overcome, but there are some pretty big benefits to making the leap.
>>> As an alternative, we can just try it out and fork ESS-SVN as an user account.
>>> If successful in an year or two we can think of migrating ESS to git completely.
>> It might not take that long to make a pretty convincing case. The Git train is moving *really* fast these days.
>> CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.
>> ESS-help at r-project.org mailing list
More information about the ESS-help