-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 emscripten GitHub organization #4880
Comments
Seems like a good idea to me. Curious what others think. |
I like this idea too. We already have emscripten, emsdk, the fastcomp repos, ports, the website, etc. I'd also like to eventually move system libs and ports out of the emscripten repo a la https://github.com/kripken/musl-emscripten (obviously we can discuss that in a separate thread). But in any case it seems like a good idea even with the repos we already have. |
Hmm, so there already exists an emscripten organization, https://github.com/emscripten . It has no public members and no apparent way to tell who created it or when? Looks like a placeholder. I guess we could just create something with an alternative name like emscripten-org? |
@kripken I have had success with Github transferring ownership of dormant accounts. Try contacting them to see what they can do. |
Thanks, I contacted them now. |
This issue has been automatically marked as stale because there has been no activity in the past 2 years. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant. |
There might be still some repositories which aren't transferred yet (?), but there is now an emscripten org. |
Right now it's harder to get an overview of all emscripten repositories as it needs to be.
The best approach currently is to scroll through the list of all repositories of @kripken - but the official advertised SDK is here: https://github.com/juj/emsdk
Using an organistation would solve that. Also don't worry about old links, GitHub is redirecting from the previous place.
The text was updated successfully, but these errors were encountered: