github.com/wasilibs/wazerox@v0.0.0-20240124024944-4923be63ab5f/site/content/community/_index.md (about)

     1  +++
     2  title = "Community"
     3  layout = "single"
     4  +++
     5  
     6  wazero is the only zero dependency WebAssembly runtime written in Go. It is
     7  used as a library dependency, allowing Go applications to embed or execute code
     8  written in other languages. It is also used as a CLI, to invoke WebAssembly
     9  binaries, a.k.a. wasm files.
    10  
    11  ### wazero community
    12  
    13  [tetratelabs/wazero][1] holds the Apache licensed, open source code and tests
    14  that ensure the project. A team of full-time staff at [Tetrate](https://tetrate.io/)
    15  steward the wazero, and you can read [history]({{< relref "/history.md" >}}) for how everything
    16  began!
    17  
    18  Today, wazero is a vibrant community of dozens of community members,
    19  leveraged by many open source projects and commercial products. Please have a
    20  look at our [users]({{< relref "/users.md" >}}) page, as you may find something you need!
    21  
    22  ### Keeping up to date
    23  
    24  wazero writes detailed release notes. Click Watch, Custom then Releases on the
    25  [tetratelabs/wazero][1] repository to automatically get notifications. You can
    26  also watch for the tag #wazero on various social media.
    27  
    28  We also have a [gophers slack](https://gophers.slack.com/) `#wazero` channel
    29  for support, updates and conversation! Note: You may need an [invite][2] to
    30  join gophers.
    31  
    32  Regardless, if you like what we are doing, please [star][3] our repo as folks
    33  appreciate it.
    34  
    35  ### How change works in wazero
    36  
    37  Most wazero efforts start as localized experiments, then progressively build
    38  traction before becoming a feature. Before you start a large effort, be it docs or
    39  a test framework or a feature, check with one of the above channels. Someone may
    40  already have worked on this in the past and might join your effort. Sometimes,
    41  features are intentionally absent, usually with rationale documented in an issue.
    42  Regardless, the best advice is to join the community before proposing change, and
    43  read one of our [CONTRIBUTING](https://github.com/tetratelabs/wazero/blob/main/CONTRIBUTING.md) files
    44  which explains technical aspects of change culture.
    45  
    46  [1]: https://github.com/tetratelabs/wazero
    47  [2]: https://invite.slack.golangbridge.org/
    48  [3]: https://github.com/tetratelabs/wazero/stargazers