[ruby-core:89348] Re: Studying the evolution of the Ruby project

Hello Gustavo,

Unfortunately, your mail had been in status "moderator wanted" since 2016.
Today, the admin (@hsbt) checked the mail pool, released, and then we've
just got your mail.

So.  At first, it seems you may misunderstand that Ruby was migrated to
GitHub.  It has not been migrated yet, even in 2018.  We are still using
Subversion, and https://github.com/ruby/ruby is just a mirror to the
original subversion repository.  The migration to git.ruby-lang.org (not
GitHub) is planned, but not done yet.

> 1. What motivated the project to migrate to Github? How do you evaluate
the benefits of this migration?

We will migrate to git because some contributors want to keep their author
information in the repository.  Subversion itself does not keep the
information, so the committer must manually write the contributor's name in
the commit log.  But, the committer sometimes forgets to write the name,
and the contribution log disappears from the repository itself,
unfortunately.  If we migrate to git, the problem will be fixed.  This is
what I heard from matz, the project leader of Ruby.

> 2. Does this snapshot make sense? Did you find any inconsistency on the
data?

As I said, we've not migrated yet.

> 3. Do you have any internal policy to promote/attract/retain newcomers?
If so, do them succeed?
> 4. Why did this project attract so few contributors over its life cycle?

I'm unsure if the number is few or not because I don't know the number of
other projects.
The subversion repository and the GitHub mirror do not keep author
information as a machine-readable form.  I guess you checked only committer
information.
Ruby uses "enrollment by recommendation" for committers: those who wrote
some good patches that were merged to the repository, will be recommended
to be a committer.  So, a short-time contributor normally does not have a
commit bit.  The number of contributors might look smaller than actual.

Thank you,


2018年10月10日(水) 8:25 Gustavo Henrique Lima Pinto <
[e-mail]>:

> Hi there,
>
> I'm a researcher studying software evolution. As part of my current
> research, I'm studying the implications of migrating an open-source
> software project to GitHub, for instance, if the project succeed in
> attracting newcomers. Ruby was in my list.
>
> To further analyze the impacts of Ruby’s migration, we analyzed the git
> log commit history of your project in terms of number of contributions,
> number of newcomers and number of contributors per month. The following
> figure presents a temporal perspective regarding these three measures.
>
> [image: Inline image 1]
>
> Given the numbers presented in the graphic, we would like to ask Ruby
> developers the following questions:
>
> 1. What motivated the project to migrate to Github? How do you evaluate
> the benefits of this migration?
> 2. Does this snapshot make sense? Did you find any inconsistency on the
> data?
> 3. Do you have any internal policy to promote/attract/retain newcomers? If
> so, do them succeed?
> 4. Why did this project attract so few contributors over its life cycle?
>
> Thanks in advance for your collaboration,
>
> Gustavo Pinto, PhD
> www.gustavopinto.org
>
> Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>