Moving WAMRs Home#5006
Merged
Merged
Conversation
lum1n0us
previously approved these changes
Jul 20, 2026
yamt
reviewed
Jul 21, 2026
Contributor
Author
|
When used outside of a url it should be capitalised as it’s a name. It is
also a brand name with its own capitalisation rule. The correct
capitalisation in this context is “GitHub” :
https://linguix.com/english/common-mistake/github
Inside a url it’s unusual, and not intentional. I am travelling, at the
moment, please feel free to change. Also note that DNS names are case
insensitive:
https://datatracker.ietf.org/doc/html/rfc4343
This has no impact on the effectiveness of the URLs provided.
…On Mon, 20 Jul 2026 at 23:58, YAMAMOTO Takashi ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In README.md
<#5006 (comment)>
:
> +During the week in transition (Monday 27 July - Friday July 31) we will be moving the GitHub repositories we use to new locations. We hope to keep the disruption to a minimum during this week, and as our GitHub repositories are moving, we will be posting updates on our progress via our mailing list - please feel free to join this to stay informed. Please visit this URL [https://groups.google.com/g/wamr-dev](https://groups.google.com/g/wamr-dev), and click “join group”.
+
+Once this transition process completes there will be no impact for users of WAMR. The project will continue to be run and continue to be supported by the same people and teams that support WAMR today. The only visible change will be the new GitHub repository locations we will use. GitHub should redirect you automatically, but just in case the table below lists the old and new locations of the repositories we use.
+
+The WAMR project joined the Bytecode Alliance on May 3rd 2019 - about 7 years ago. The Bytecode Alliance is home to some amazing projects and people and we’d like to thank them for all the help and support, and to wish our friends at the Bytecode Alliance all the best for the future.
+
+Speaking of the future, the WAMR team has some exciting plans for the project. Once this transition is complete we hope to share these plans with the wider community via our mailing list and new GitHub repositories. Please do join the mailing list as we’d love to hear your feedback [https://groups.google.com/g/wamr-dev](https://groups.google.com/g/wamr-dev).
+
+### Location Table
+
+| Description | Current Location | New Location |
+| --- | --- | --- |
+| **Wasm Micro Runtime** | https://GitHub.com/bytecodealliance/wasm-micro-runtime | https://GitHub.com/wasm-micro-runtime/wasm-micro-runtime |
+| **wamr-rust-dsk** |https://GitHub.com/bytecodealliance/wamr-rust-sdk | https://GitHub.com/wasm-micro-runtime/wamr-rust-sdk |
+| **wamr-app-framework** | https://GitHub.com/bytecodealliance/wamr-app-framework | https://GitHub.com/wasm-micro-runtime/wamr-app-framework |
+| **wamr-python** | https://GitHub.com/bytecodealliance/wamr-python | https://GitHub.com/wasm-micro-runtime/wamr-python |
it seems a bit unusual to capitalize the hostname. (Github.com) is it
intentional?
—
Reply to this email directly, view it on GitHub
<#5006?email_source=notifications&email_token=ABOJW6KMWATWAXMTPW7XEBD5F3S5BA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTINZUGEYDQNJZG4Y2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#pullrequestreview-4741085971>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABOJW6KLYHGRKCALONQK3V35F3S5BAVCNFSNUABFKJSXA33TNF2G64TZHMYTQNBWGU2DEOJYHNEXG43VMU5TIOJTGI2TGMRYHA32C5QC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
yamt
approved these changes
Jul 21, 2026
lum1n0us
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An announcement describing how WAMR will transition to its new home.
Notice: Moving WAMR's Home
The Wasm Micro Runtime (WAMR) project will begin transitioning to a new home on Monday, July 27, 2026, with the process expected to be completed by Friday, July 31, 2026.
This marks the beginning of an exciting new chapter for WAMR. Following discussions between the WAMR maintainers and the Bytecode Alliance, it was jointly agreed that WAMR would continue its development as an independent open source project. While this changes the project's organizational home, it does not change WAMR's mission, maintainers, or commitment to the community. The same people and teams who have built and supported WAMR will continue to lead the project, and we're excited about the opportunities ahead as we continue to grow WAMR together with our community.
During the week in transition (Monday 27 July - Friday July 31) we will be moving the GitHub repositories we use to new locations. We hope to keep the disruption to a minimum during this week, and as our GitHub repositories are moving, we will be posting updates on our progress via our mailing list - please feel free to join this to stay informed. Please visit this URL https://groups.google.com/g/wamr-dev, and click “join group”.
Once this transition process completes there will be no impact for users of WAMR. The project will continue to be run and continue to be supported by the same people and teams that support WAMR today. The only visible change will be the new GitHub repository locations we will use. GitHub should redirect you automatically, but just in case the table below lists the old and new locations of the repositories we use.
The WAMR project joined the Bytecode Alliance on May 3rd 2019 - about 7 years ago. The Bytecode Alliance is home to some amazing projects and people and we’d like to thank them for all the help and support, and to wish our friends at the Bytecode Alliance all the best for the future.
Speaking of the future, the WAMR team has some exciting plans for the project. Once this transition is complete we hope to share these plans with the wider community via our mailing list and new GitHub repositories. Please do join the mailing list as we’d love to hear your feedback https://groups.google.com/g/wamr-dev.
Location Table