Jean-Baptiste:

    1) last time you accepted my pull request
        https://github.com/apache/karaf/pull/5
    you had to re-process it by hand, and it is still not in svn; this
    is just needless pain!

    2) in comparison, after Achim gave me a blessing on my pax-url pull
        https://github.com/ops4j/org.ops4j.pax.url/pull/4

    I got my commit back as a snapshot the next day :-)

    3) so, the essence of my proposal is this
    "you are still following  apache guidelines, but you use github as
    primary commit source"

    Thank you,

    Andrei 

-------- Original Message --------
Subject: Re: switch to github
From: Jean-Baptiste Onofré <[email protected]>
To: [email protected]
Date: Fri 17 Aug 2012 05:07:22 PM CDT
> Hi Andrei,
>
> We are several (it's my case), to already use git (with git-svn).
>
> For github, we already use it as source, as soon as they contain the
> correct grant, compliant with the Apache standard.
>
> There are already lot of developer that use Karaf github mirror. If
> you take a look on:
> https://github.com/apache/karaf
>
> you can see that we have 28 forks, pull requests, etc.
>
> As you said, we are an Apache project, and so some guidelines. There
> are still discussions in the ASF to provide a git service.
>
> So, be sure that we are following all discussions related to git, and
> we already know (and use since long time now ;)) that git is much
> appreciated ;)
>
> Regards
> JB
>
> On 08/17/2012 11:49 PM, Andrei Pozolotin wrote:
>>     *Jean-Baptiste, and ALL:
>>     *
>>     I am sure you had chance to convince yourself that
>>     git + fork/pull is better then svn + patch.txt
>>
>>     I understand that you have apache guidelines,
>>     but the switch should be easy:
>>
>>     1) treat github as the primary commit source,
>>     require every git pull to contain an apache one liner
>>     " Grant license to ASF for inclusion in ASF works (as per the Apache
>>     License <http://www.apache.org/licenses/LICENSE-2.0>§5)"
>>
>>     2) replicate git to svn on schedule via hudson/jenkins job,
>>     if github goes bust - just fall back to svn;
>>
>>     3) continue to produce snapshots and releases from svn
>>
>>     above all else, get an easy access to 500K github java developers
>>     who are just eager to start committing to the karaf! :-)
>>
>>     what do you think?
>>
>>     Thank you,
>>
>>     Andrei
>>
>

Reply via email to