Consider collaborating as a GitHub organization

[brylie]

Lets consider collaborating on this project as a GitHub organization. This way, we can have multiple contributors to the same repository, rather than doing this work separately.

[brylie]

I have an organization, called Meteorcrowd, where we are collaborating on several open-source projects. I can invite @radiegtya and @martinhbramwell to the organization, as part of the Meteoris team.

[brylie]

My main experience is currently as a project manager and Meteor developer.

[martinhbramwell]

I'm not sure how GitHub organizations work, but it seems as if placing a repo within an organization makes it the intellectual property of the organization. I mean, if you removed Ega from the org would he still own Meteoris? or would he no longer have control over it?

[brylie]

The IP rights would still belong to the authors (i.e. each committer). GitHub organizations are a collaboration mechanism, and do not supersede Copyright law.

[martinhbramwell]

I understand about the law. My question is about who controls the code. Will you be in a position to take Ega's control away from his own project? If so, he should create the organization. That's all.

[radiegtya]

@brylie & @martinhbramwell : I think that's correct, if it will be organization project. let's make an organization "Meteoris" by ourself and the main contributor was me, @martinhbramwell , and @brylie. Because after all, if you take meteoris to another organization, they can simply kick us and they have right to do that.

[brylie]

Ah, I understand. Lets make sure that the code is safe by agreeing not
to remove each other from the organization, keeping local mirrors of the
code, and possibly syncing commits and releases on a third party
service. Do these steps seem reasonable for code and community safety?

On 18.06.2015 17:43, martinhbramwell wrote:

I understand about the law. My question is about who controls the
code. Will you be in a position to take Ega's control away from his
own project? If so, he should create the organization. That's all.

—
Reply to this email directly or view it on GitHub
#82 (comment).

[radiegtya]

Better still on current way. That open sourcing meteoris with not part of organization will be still better option.

[brylie]

let's make an organization "Meteoris" by ourself and the main contributor was me

Alright. That is a good idea. Will you please invite us to the Meteoris organization?

[radiegtya]

Sorry but it seems the old meteoris cannot be used for new organization. I can't find the setting to make old meteoris repo change the owner as organization

[brylie]

All good. You can simply transfer this repository to the Meteoris organization you created.
https://help.github.com/articles/transferring-a-repository/