[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    Re: James to Git?
From:       gzsombor () gmail ! com
Date:       2012-10-11 7:51:08
Message-ID: 1202632934.8.1349941864267.JavaMail.c8706513581643b397cba28b633bf465 () ex-std-node50 ! prod ! rhcloud ! com
[Download RAW message or body]


I would favor git, it's much simpler to develop and maintain patches with git(hub) until it's merged.


Regards,
 Zsombor

On Thu Sep 27 10:34:25 GMT+200 2012, Eric Charles <eric@apache.org>. wrote:

Sounds like a reasonable plan. 
 
In the meantime, if there are any barrier to contribute with the current 
SVN, just tell us so we can help. 
 
Thx, Eric 
 
On 27/09/2012 03:12, Saibabu Vallurupalli wrote: 
> Add me as well +1 
> 
> 
> 
> On Wed, Sep 26, 2012 at 4:22 PM, Ioan Eugen Stan <stan.ieugen@gmail.com>wrote: 
> 
>> Hello, 
>> 
>> I've noticed the possibility to switch to Git for Apache projects. I 
>> believe working with git is faster at accepting external 
>> contributions, especially that Github is so popular, and a lot of 
>> people fork and work on local projects. 
>> 
>> I also know that we probably don't have the resources yet, but how do 
>> you feel about moving James to git as primary development? I think it 
>> will speed up development and adoption as it's easier to play with. 
>> 
>> Some talks about the process: 
>> http://lucene.472066.n3.nabble.com/lucy-dev-Moving-to-Git-td4006735.html 
>> 
>> Cheers, 
>> 
>> -- 
>> Ioan Eugen Stan / CTO / http://axemblr.com 
>> 
>> --------------------------------------------------------------------- 
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org 
>> For additional commands, e-mail: server-dev-help@james.apache.org 
>> 
>> 
> 
 
--------------------------------------------------------------------- 
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org 
For additional commands, e-mail: server-dev-help@james.apache.org 
 


[prev in list] [next in list] [prev in thread] [next in thread]