Announcement: Moving to github

Announcement: Moving to github

[Bryan Hundven]

Hello list,

I'm sure you're probably still catching up on all the updates and call
to arms on the list of patches in patchwork, but I have one more
announcement to make.

I was able to get our code hosted on Github:
https://github.com/crosstool-ng/crosstool-ng

Over the next month, as we clear out patchwork, I'd like contributors
to start "forking" crosstool-ng and opening "pull requests" to get
code into mainline for crosstool-ng.

# Why Github
For one, it's widely used in other open-source projects and keeps me
away from being an "BDFL" (Benevolent dictator for life). Top
contributors can now be added as "Project contributors" that can
commit code themselves.

Secondly, there is an issue tracker!!!
https://github.com/crosstool-ng/crosstool-ng/issues
I'm no good at tracking issues on the mailing list. If I forget about
the issue, it will hide on the mailing list until someone (the issue
reporter) gets angry at me. Tracking the issue from the time it is
reported until it is resolved will help crosstool-ng become a better
tool!

There are many other reasons this better then what we currently have,
but for now this is a good start.

# Why not X (bitbucket, gitorious, etc..)
I've used them all. I prefer github, and so do most other people.

# How is this transition going to work?
I personally have two remotes in my local git clone of crosstool-ng.
My origin is currently the new github repository, and I have another
remote for the crosstool-ng.org repository.

As we clear out patchworks, I will be applying those changes to
crosstool-ng.org and then pushing those to github. As new pull
requests come in from github, I will help work the pull requests into
the github repository and push those changes to the crosstool-ng.org
repository.

When patchwork is empty and there are no more patches to be worked
there, I will turn off patchwork and the crosstool-ng.org git
repository.

There might still be need for the server crosstool-ng.org is currently
on, so that might stick around for a while.

Let me know if you have any questions or comments.

Cheers,

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Announcement: Moving to github

[Andreas Bießmann]

resent due to spam message (ml + ml-owner)

Dear Bryan,

On 2014-12-06 04:10, Bryan Hundven wrote:
> Hello list,

> # How is this transition going to work?
> I personally have two remotes in my local git clone of crosstool-ng.
> My origin is currently the new github repository, and I have another
> remote for the crosstool-ng.org repository.
> 
> As we clear out patchworks, I will be applying those changes to
> crosstool-ng.org and then pushing those to github. As new pull
> requests come in from github, I will help work the pull requests into
> the github repository and push those changes to the crosstool-ng.org
> repository.
> 
> When patchwork is empty and there are no more patches to be worked
> there, I will turn off patchwork and the crosstool-ng.org git
> repository.
> 
> There might still be need for the server crosstool-ng.org is currently
> on, so that might stick around for a while.

I'd appreciate the crosstool-ng.org repository could stay there, at 
least as a mirror for the one at github. Wouldn't it be possible to sync 
the github repo to the crosstool-ng.org one? Once patches are only 
integrated at github this will be a simple fast-forward for the 
crosstool-ng.org repo, a single oneliner could do that.

regards

Andreas Bießmann

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Announcement: Moving to github

[Bryan Hundven]

On Tue, Dec 9, 2014 at 1:34 AM, Andreas Bießmann <andreas@biessmann.de> wrote:
> Dear Bryan,
>
> On 2014-12-06 04:10, Bryan Hundven wrote:
>>
>> Hello list,
>
>
>> # How is this transition going to work?
>> I personally have two remotes in my local git clone of crosstool-ng.
>> My origin is currently the new github repository, and I have another
>> remote for the crosstool-ng.org repository.
>>
>> As we clear out patchworks, I will be applying those changes to
>> crosstool-ng.org and then pushing those to github. As new pull
>> requests come in from github, I will help work the pull requests into
>> the github repository and push those changes to the crosstool-ng.org
>> repository.
>>
>> When patchwork is empty and there are no more patches to be worked
>> there, I will turn off patchwork and the crosstool-ng.org git
>> repository.
>>
>> There might still be need for the server crosstool-ng.org is currently
>> on, so that might stick around for a while.
>
>
> I'd appreciate the crosstool-ng.org repository could stay there, at least as
> a mirror for the one at github. Wouldn't it be possible to sync the github
> repo to the crosstool-ng.org one? Once patches are only integrated at github
> this will be a simple fast-forward for the crosstool-ng.org repo, a single
> oneliner could do that.

Look at http://crosstool-ng.org/git/crosstool-ng and compare it with
https://github.com/crosstool-ng/crosstool-ng and tell me if anything
is out of sync. I've been keeping them in sync, even after starting
the github account.

-Bryan

> regards
>
> Andreas Bießmann

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Announcement: Moving to github

[Andreas Bießmann]

Dear Bryan,

On 2014-12-09 11:37, Bryan Hundven wrote:
> On Tue, Dec 9, 2014 at 1:34 AM, Andreas Bießmann <andreas@biessmann.de> 
> wrote:
>> On 2014-12-06 04:10, Bryan Hundven wrote:
>>> # How is this transition going to work?
>>> I personally have two remotes in my local git clone of crosstool-ng.
>>> My origin is currently the new github repository, and I have another
>>> remote for the crosstool-ng.org repository.
>>> 
>>> As we clear out patchworks, I will be applying those changes to
>>> crosstool-ng.org and then pushing those to github. As new pull
>>> requests come in from github, I will help work the pull requests into
>>> the github repository and push those changes to the crosstool-ng.org
>>> repository.
>>> 
>>> When patchwork is empty and there are no more patches to be worked
>>> there, I will turn off patchwork and the crosstool-ng.org git
>>> repository.
>>> 
>>> There might still be need for the server crosstool-ng.org is 
>>> currently
>>> on, so that might stick around for a while.
>> 
>> 
>> I'd appreciate the crosstool-ng.org repository could stay there, at 
>> least as
>> a mirror for the one at github. Wouldn't it be possible to sync the 
>> github
>> repo to the crosstool-ng.org one? Once patches are only integrated at 
>> github
>> this will be a simple fast-forward for the crosstool-ng.org repo, a 
>> single
>> oneliner could do that.
> 
> Look at http://crosstool-ng.org/git/crosstool-ng and compare it with
> https://github.com/crosstool-ng/crosstool-ng and tell me if anything
> is out of sync.

I havn't sayed it is currently out-of-sync (and havn't checked it).

You say the crosstool-ng.org repository 'might stick around for a 
while'. All I
say is: please let it there forever and keep it synced. If the github 
repo is the master keeping the crosstool-ng.org repo in sync should be a 
noop.

> I've been keeping them in sync, even after starting
> the github account.

No problem, please consider to not switch of the crosstool-ng.org repo 
ever.

regards

Andreas

--
For unsubscribe information see http://sourceware.org/lists.html#faq