Skip to content
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.

Sign up for GitHub

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

Improve Community Page #153

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Improve Community Page #153

Show file tree
Hide file tree
Changes from 7 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
5a6add9
improve community section
mhmohona Aug 20, 2023
759e0bd
update
mhmohona Aug 20, 2023
56bd8c0
Merge branch 'main' into community
mhmohona Aug 20, 2023
0aa7cd6
added roadmap link
mhmohona Aug 20, 2023
10aac51
add about ecosystem
mhmohona Aug 20, 2023
692e152
Merge branch 'community' of https://github.com/mhmohona/WasmEdge_docs…
mhmohona Aug 20, 2023
265bcaf
fix typo
mhmohona Aug 20, 2023
c1713ee
updating Ecosystem section
mhmohona Sep 10, 2023
e157778
small fix
mhmohona Sep 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 23 additions & 4 deletions docs/contribute/contribute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,22 @@ Please submit a pull request broken down into small changes bit by bit. A pull r
If you split your pull request into small changes, please ensure any changes that go to the main branch will not break anything. Otherwise, it can only be merged once this feature is complete.
:::

## Understanding the WasmEdge Ecosystem

Contributing to WasmEdge is more than just code. It's about understanding where WasmEdge fits into the broader ecosystem of WebAssembly and edge computing. Here are a few key aspects of the WasmEdge ecosystem:

- **WasmEdge Runtime**: The high-performance, extensible WebAssembly runtime for cloud native infrastructure and edge IoT devices.
- **WasmEdge Extensions**: A series of function-as-a-service extensions for the WasmEdge Runtime, such as Tensorflow Lite and Image Magick.
mhmohona marked this conversation as resolved.
Show resolved Hide resolved
- **Cargo-wasi**: A lightweight WebAssembly CDN service built on the WasmEdge Runtime.
mhmohona marked this conversation as resolved.
Show resolved Hide resolved
- **SSVM**: A server-side WebAssembly VM optimized for server-side applications. It powers server-side functions in Node.js, Rust, and Golang to provide high-performance execution of applications in a sandboxed environment.
mhmohona marked this conversation as resolved.
Show resolved Hide resolved

You can check out more [about the WasmEdge ecosystem](https://github.com/WasmEdge/WasmEdge/blob/master/docs/ecosystem.md) to understand how these parts work together.

By understanding the ecosystem, you can make more impactful contributions and see how your work advances the overall goals of WasmEdge and WebAssembly in the cloud and edge computing.

### Fork and Clone the Repository

Fork [the WasmEdge repository](https://github.com/WasmEdge/WasmEdge) and clone the code to your local workspace
Fork [the WasmEdge repository](https://github.com/WasmEdge/WasmEdge) and clone the code to your local workspace.

### Branches and Commits

Expand All @@ -50,9 +63,11 @@ LD_LIBRARY_PATH=$(pwd)/lib/api ctest

When ready for review, push your branch to your fork repository on github.

Then visit your fork at <https://github.com/$user/WasmEdge> and click the `Compare & Pull Request` button next to your branch to create a new pull request. The pull request description should refer to all the issues it addresses. Remember to reference issues (such as Closes #XXX and Fixes #XXX) in the comment so that the issues can be closed when the PR is merged. After creating a pull request, please check that the CI passes with your code changes.
Then visit your fork at <https://github.com/$user/WasmEdge> and click the `Compare & Pull Request` button next to your branch to create a new pull request. Description of a pull request should refer to all the issues that it addresses. Remember to put a reference to issues (such as Closes #XXX and Fixes #XXX) in the comment so that the issues can be closed when the PR is merged. After creating a pull request, please check that the CI passes with your code changes.

After creating a pull request, please ensure that the CI passes with your code and documentation changes.

Once your pull request has been opened, it will be assigned to one or more reviewers. Those reviewers will do a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and coding style.
Once your pull request has been opened it will be assigned to one or more reviewers. Those reviewers will do a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and coding style.

Commit changes made in response to review comments to the same branch on your fork.

Expand All @@ -77,4 +92,8 @@ Update the documentation if you are creating or changing features. Good document

You can propose new designs for existing WasmEdge features. You can also design new features; please submit a proposal via the GitHub issues.

WasmEdge maintainers will review this proposal as soon as possible to ensure the overall architecture is consistent and to avoid duplicated work in the roadmap.
WasmEdge maintainers will review this proposal as soon as possible. This is necessary to ensure the overall architecture is consistent and to avoid duplicated work in the [roadmap](https://github.com/WasmEdge/WasmEdge/blob/master/docs/ROADMAP.md).

## Code of Conduct

We value the participation and collaboration of every member of our community. Therefore, we require all participants to adhere to our [Code of Conduct](https://github.com/WasmEdge/WasmEdge/blob/master/docs/CODE_OF_CONDUCT.md).
27 changes: 23 additions & 4 deletions i18n/zh/docusaurus-plugin-content-docs/current/contribute/contribute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,22 @@ Please submit a pull request broken down into small changes bit by bit. A pull r
If you split your pull request into small changes, please ensure any changes that go to the main branch will not break anything. Otherwise, it can only be merged once this feature is complete.
:::

## Understanding the WasmEdge Ecosystem

Contributing to WasmEdge is more than just code. It's about understanding where WasmEdge fits into the broader ecosystem of WebAssembly and edge computing. Here are a few key aspects of the WasmEdge ecosystem:

- **WasmEdge Runtime**: The high-performance, extensible WebAssembly runtime for cloud native infrastructure and edge IoT devices.
- **WasmEdge Extensions**: A series of function-as-a-service extensions for the WasmEdge Runtime, such as Tensorflow Lite and Image Magick.
- **Cargo-wasi**: A lightweight WebAssembly CDN service built on the WasmEdge Runtime.
- **SSVM**: A server-side WebAssembly VM optimized for server-side applications. It powers server-side functions in Node.js, Rust, and Golang to provide high-performance execution of applications in a sandboxed environment.

You can check out more [about the WasmEdge ecosystem](https://github.com/WasmEdge/WasmEdge/blob/master/docs/ecosystem.md) to understand how these parts work together.

By understanding the ecosystem, you can make more impactful contributions and see how your work advances the overall goals of WasmEdge and WebAssembly in the cloud and edge computing.

### Fork and Clone the Repository

Fork [the WasmEdge repository](https://github.com/WasmEdge/WasmEdge) and clone the code to your local workspace
Fork [the WasmEdge repository](https://github.com/WasmEdge/WasmEdge) and clone the code to your local workspace.

### Branches and Commits

Expand All @@ -50,9 +63,11 @@ LD_LIBRARY_PATH=$(pwd)/lib/api ctest

When ready for review, push your branch to your fork repository on github.

Then visit your fork at <https://github.com/$user/WasmEdge> and click the `Compare & Pull Request` button next to your branch to create a new pull request. The pull request description should refer to all the issues it addresses. Remember to reference issues (such as Closes #XXX and Fixes #XXX) in the comment so that the issues can be closed when the PR is merged. After creating a pull request, please check that the CI passes with your code changes.
Then visit your fork at <https://github.com/$user/WasmEdge> and click the `Compare & Pull Request` button next to your branch to create a new pull request. Description of a pull request should refer to all the issues that it addresses. Remember to put a reference to issues (such as Closes #XXX and Fixes #XXX) in the comment so that the issues can be closed when the PR is merged. After creating a pull request, please check that the CI passes with your code changes.

After creating a pull request, please ensure that the CI passes with your code and documentation changes.

Once your pull request has been opened, it will be assigned to one or more reviewers. Those reviewers will do a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and coding style.
Once your pull request has been opened it will be assigned to one or more reviewers. Those reviewers will do a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and coding style.

Commit changes made in response to review comments to the same branch on your fork.

Expand All @@ -77,4 +92,8 @@ Update the documentation if you are creating or changing features. Good document

You can propose new designs for existing WasmEdge features. You can also design new features; please submit a proposal via the GitHub issues.

WasmEdge maintainers will review this proposal as soon as possible to ensure the overall architecture is consistent and to avoid duplicated work in the roadmap.
WasmEdge maintainers will review this proposal as soon as possible. This is necessary to ensure the overall architecture is consistent and to avoid duplicated work in the [roadmap](https://github.com/WasmEdge/WasmEdge/blob/master/docs/ROADMAP.md).

## Code of Conduct

We value the participation and collaboration of every member of our community. Therefore, we require all participants to adhere to our [Code of Conduct](https://github.com/WasmEdge/WasmEdge/blob/master/docs/CODE_OF_CONDUCT.md).