Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create an org for omake #41

Closed
bobzhang opened this issue Sep 8, 2016 · 11 comments
Closed

create an org for omake #41

bobzhang opened this issue Sep 8, 2016 · 11 comments

Comments

@bobzhang
Copy link
Collaborator

bobzhang commented Sep 8, 2016

thanks for your hard work on omake, forks are not friendly for search github(there is no need to fork my branch since you did the most work), are you interested in making an omake-org to make it look more official

@gerdstolpmann
Copy link
Collaborator

Sure, how does this work?

@bobzhang
Copy link
Collaborator Author

bobzhang commented Sep 9, 2016

@gerdstolpmann you can create a new organization https://help.github.com/articles/creating-a-new-organization-from-scratch/
I am not sure this will require paid account, but if it does, let me know since I have one

@bobzhang
Copy link
Collaborator Author

ping @gerdstolpmann ?

@gerdstolpmann
Copy link
Collaborator

Seems to be possible without paid account, if the repo is public. However, I currently don't see the benefits (e.g. teams), but rather disadvantages like that we lose the issue tracker. It is not that much in it - but still. So, what do we gain?

@rgrinberg
Copy link
Collaborator

I don't really see the need in an org either. Gerd is the de facto maintainer. I would remove the fact that it's a fork of Bob's repo as it does confuse people about which repository is the "upstream" one.

@bobzhang
Copy link
Collaborator Author

I know currently it might not have technical benefits.
But it has marketing value which is generally ignored by programmers but sometimes matter more than the tech itself: for beginner who does not know anything about omake, it is hard to sell since it looks like one man's project, just my 2 cents.
I am fine to remove the fork
You can create an org and create the repo, how do you loose the issue tracker?

@gerdstolpmann
Copy link
Collaborator

To my knowledge, you cannot move anything beyond core git data between repos. So, we cannot move the existing issues to the new org. They are not lost in the meaning that they are deleted, but they can effectively not be found by users not knowing that there is an older repo.

@alainfrisch
Copy link

It is possible to transfer ownership of a repo from a personal user account to an organization account; this preserves all non-Git data (issues, PRs) and GitHub redirects old URLs.

@gerdstolpmann
Copy link
Collaborator

Thanks, Alain, this was the missing piece of information. The org is called ocaml-omake (omake was already taken).

@alainfrisch
Copy link

Does anyone know how to remove the "forked from bobzhang/omake-fork" info?

@bobzhang
Copy link
Collaborator Author

I deleted my repo, it looks good now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants