Moving the Gitx project into its own Gitx organization

[nanoant]

@rowanj I would like hereby ask to move project to its own organization which may (in future) let other developers to join the GitX effort. Also we would have nice gitx.github.io page and so on and so on. Probably we could ask also @pieter and other forks developers to join.

WDYT?

[xpe]

@nanoant Can you find Rowan and other maintainers of other forks and contact them directly to see what they think? This sounds like a good idea to me, but they are doing the hard work, so I'd defer to them.

[xpe]

See also #259, Project Status, which goes into some detail about getting more hands on deck.

[pieter]

Let me know if there's something I can do

Sent from my iPad

On 11 mei 2014, at 23:06, David James notifications@github.com wrote:

See also #259, Project Status, which goes into some detail about getting more hands on deck.

—
Reply to this email directly or view it on GitHub.

[nanoant]

I am pasting below mail which I have sent to you February.

Hello Pieter, Rowan, German and Eric,

I want to propose you all moving the project into GitX github organisation so it is possible to:
(1) have sevaral maintainers (commiters) for organization
(2) have github pages gitx.github.io
(3) have central dmg downloads
(4) reduce userbase fragmentation
(5) fullfill dream of Eric :>

The following steps can be taken:

(1) Since Pieter is original author, he could create and own the organization
(2) He can transfer original GitX project repo into GitX organization
(3) He can make other authors as either owners or commiters
(4) All other forks may shutdown with commits removing all files except README.md informing users that project has been merged into one at gitx.github.io
(5) All forks may issue Sparkle update pointing to single gitx.github.io version

WDYT?

Final question why I am rising this. Actually I have already submitted several changes to Rowan fork, and I have more pending. And I am willing to update GitX on daily basis as well, as I am actively using it everyday.

[sugarmo]

👍

[claybridges]

@rowanj Hey, I sent you an email on this. I just wanted to check if you got it. Thanks.

[claybridges]

@nanoant Looks like there is already a @gitx user on github, though very inactive. Absent permission, etc. I'd figure that would preclude creating a GitX project with that id, but I don't know. GitX-org?

[claybridges]

Clearly, since I've raised this issue myself (#259), I'm 👍. @rowanj's achievements are many, but the sad and confusing history of single-dev GitX instructs on the way forward.

[nanoant]

Let us try to contact @gitx and see if he wishes to give the name to our project, there's an option just to rename user, then creating organization should be rather straightforward.

[nanoant]

Well, after short investigation I can tell this user has not set any traces how to contact him up. Maybe I we try to contact GitHub crew and ask if they can rename this user?

[nanoant]

Thanks to amazing GitHub team @gitx was recovered and now it is an OSS organization with all previous fork authors being owners of it.

I have also migrated @rowanj website to Jekyll which should be available within couple of minutes (GH having some problems with hooks today) at gitx.gitlab.io.

So... next steps would be @rowanj moving his gitx project to @gitx organization account, since it is most recent and having issues open, so to keep these on new account it is best to move it rather than clone it.

Finally @pieter & @laullon would be gently requested to push some README.md only commits (removing all other files) pointing to new gitx.github.io.

Now waiting for @rowanj feedback! Of course he may be on holidays, since it is a summertime. But I think there is no rush.

[claybridges]

@nanoant Great work. Kudos & thanks.

[ngrilly]

@nanoant Thanks a lot Adam for having worked out that!

[sugarmo]

@nanoant Great work! Looking forward to the new @gitx.