FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Move library to new organisation · Issue #263 · github-tools/github · GitHub

Move library to new organisation #263

Description

We've been discussing in the Gitter channel about creating a new parent organisation to collect various bits of code (specifically JavaScript at the moment but could be expanded to other languages or extensions of JS like TypeScript) that interact with GitHub, mainly those that use Github.js but not exclusively (Some examples might be github-release-notes — the author, @alexcanessa, has already expressed interest in the plan — and my Axis for GitHub project).

githubjs is taken and apparently active (I've contacted GitHub's support team, asking about claiming that org name due to the lack of visible activity in that org, but apparently it is active to some degree). Thus we've started compiling a list of alternative names:

  • github-js
  • github-tools
  • GitHub4JS
  • Githug
  • GitHubFriends

Moving the library to a new org would help enormously with administration (adding webhooks, etc.) and help ensure github.js continues to be supported into the future.

Any thoughts, @michael? Whether we do this is ultimately contingent upon whether you're willing to move the repo to a new org.

That said, for this to be successful, we also need feedback from community stakeholders. Please, if you either use or contrinute to github.js and have a strong opinion, post it here!

Thanks, everyone!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


Back | FazBrowse Home | New Git URL