-
Notifications
You must be signed in to change notification settings - Fork 693
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
Proposals repository #1235
Comments
We already have this information here: https://webassembly.org/docs/future-features/ |
@jfbastien: I don't want to see duplication either, but we've had folks mention before that it's hard to follow how proposals are moving forward currently. Moving them into a repository would make this easier. |
@binji works for me, all I'm saying is we shouldn't duplicate things even more. Ideally it would all auto-generate from the issue tracker 😉 |
I added an agenda item to discuss this here. |
@binji should we move https://github.com/chicoxyzzy/WebAssembly-proposals to WebAssembly organization or create new repository? |
I don't know how the permissions work for moving the project. Since there isn't much in https://github.com/chicoxyzzy/WebAssembly-proposals yet, let's create a new repo and we can move the content there. OK done :-) : https://github.com/WebAssembly/proposals I've also given you edit privileges to that repo. |
OK, I've moved the tracking issues to that repo, updated FutureFeatures.md to point to these new issues, and copied the content from https://github.com/chicoxyzzy/WebAssembly-proposals. Anything I'm forgetting? |
Thank you. I think that's all for now. |
@binji should we add proposals repository as pinned repository of WebAssembly organization? |
Done. |
Hi. I just creates WebAssembly proposals tracking repository as I proposed on September 18 CG meeting.
Please let me know what you think about it. I'll try to keep it up-to-date. I'll be happy to transfer this repo to WebAssembly organization if it makes sense.
The text was updated successfully, but these errors were encountered: