commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: [DISCUSS] Moving to Git...
Date Tue, 08 Oct 2013 12:41:58 GMT
I think the problem we have right now is perception.  We look like
dinosaurs.  A lot of the current contributions we receive come in as
pull requests from Github.  If we want to attract new contributions,
we need to make it easier for folks to contribute.

On Tue, Oct 8, 2013 at 8:24 AM, Romain Manni-Bucau
<rmannibucau@gmail.com> wrote:
> i still think the scm is not an issue. the %age of committers is negligible
> compared to the number of users whatever you use. So you need a nice
> product first. Tools follow or not...you speak about scm but we can speak
> abou tbuild tool too, "gradle is far better than maven"...it doesn't help
> the topic at all
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/10/8 Christian Grobmeier <grobmeier@gmail.com>
>
>> On 8 Oct 2013, at 11:42, Romain Manni-Bucau wrote:
>>
>>  just an habit. svn diff && attach diff to a jira is as easy/hard as git
>>> push + PR.
>>>
>>
>> Tools like GitHub succeed because not everybody agrees with you. svn/diff
>> is stoneage to some. git/pr is the future for them. Maybe you are right
>> about the habit thing, but it doesn't change the fact everybody seems to
>> enjoy with git these days. SVN is on the same road as CVS. It's not that I
>> don't like SVN. It has served me well and I still use it. I know teams
>> which are doing better with SVN. But esp in open source using SVN looks
>> like the code is maintained by dinosaurs who don't want to work with "new
>> things".
>>
>> Please note, I am not saying we should move on to Git right now.
>>
>> Moving to Git will be a lot of work and we'll have a lot of questions to
>> answer.
>> For example: how would we deal with pull requests? There are no partial
>> checkouts in git. We would have most likely one repos per component. Would
>> we need to create a "super parent component" including all proper
>> components as submodule, like we have the svn view? And so on.
>>
>> If we have enough willing folks to push this forward, I am happy to see it
>> happen (unfort i am tight of time at the moment)
>>
>> Cheers
>>
>>
>>
>>> If you want to push back your changes you'll do whatever the techno is.
>>>
>>> *Romain Manni-Bucau*
>>> *Twitter: @rmannibucau <https://twitter.com/**rmannibucau<https://twitter.com/rmannibucau>
>>> >*
>>> *Blog: **http://rmannibucau.**wordpress.com/*<http://rmannibucau.wordpress.com/*>
>>> <http://**rmannibucau.wordpress.com/ <http://rmannibucau.wordpress.com/>>
>>> *LinkedIn: **http://fr.linkedin.com/in/**rmannibucau*<http://fr.linkedin.com/in/rmannibucau*>
>>> *Github: https://github.com/**rmannibucau*<https://github.com/rmannibucau*>
>>>
>>>
>>>
>>> 2013/10/8 Xavier Detant <xavier.detant@gmail.com>
>>>
>>>  2013/10/8 Emmanuel Bourg <ebourg@apache.org>
>>>>
>>>>
>>>>> I don't think using SVN is a barrier to private modifications like this.
>>>>> People just fork the mirror on Github, or import the code with git-svn.
>>>>>
>>>>>
>>>>>  I didn't said it was. Of course you'll do your private change, but you
>>>> won't share it easily (not as easily as with git IMO).
>>>>
>>>> --
>>>> Xavier DETANT
>>>>
>>>>
>>
>> ---
>> http://www.grobmeier.de
>> @grobmeier
>> GPG: 0xA5CC90DB
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<dev-unsubscribe@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message