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

Move to pyenchant organisation #157

Closed
dmerejkowsky opened this issue Dec 16, 2019 · 1 comment
Closed

Move to pyenchant organisation #157

dmerejkowsky opened this issue Dec 16, 2019 · 1 comment

Comments

@dmerejkowsky
Copy link
Member

@dmerejkowsky dmerejkowsky commented Dec 16, 2019

By "moving the repo", I mean using the transfer ownership button in the Danger Zone of the admin settings, not creating a fork.

Poke @rfk - I'm not admin on this repo so I can't do it myself.

Doing so will allow us to:

  • Use gh-pages to host the website - the current one is dead and I can't configure gh-pages on this repo
  • Allow more (or different) maintainers in the future :)

If this takes too long, we can always fork this repo in the pyenchant organization but then we'd lost all the stars, forks and issues of this project :/

@rfk
Copy link
Member

@rfk rfk commented Dec 16, 2019

Done 👍

@rfk rfk closed this Dec 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.