-
Notifications
You must be signed in to change notification settings - Fork 59
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
GSoD workplace: Create new WasmEdge plug-in contributor guides in C, C++, and Rust #85
Labels
enhancement
New feature or request
Comments
alabulei1
changed the title
Create new WasmEdge plug-in contributor guides in C, C++, and Rust
GSoD workplace: Create new WasmEdge plug-in contributor guides in C, C++, and Rust
Jun 6, 2023
This was referenced Jun 12, 2023
Update until today, 20 June -Pull Request - #102 Improved existing documentation -
Created new documentation -
|
@mhmohona Please update your work progress here. Thanks. |
Update till July 31 -
|
Update till September - |
This was referenced Nov 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Project Name: Create new WasmEdge plug-in contributor guides in C, C++, and Rust
Description:
This issue serves as a centralized place to track the progress of the WasmEdge plug-in contributor guides project, which is part of the Google Season of Docs (GSoD) program. The objective of this project is to create comprehensive guides for developers who want to contribute to the WasmEdge ecosystem by implementing plug-ins in C, C++, or Rust.
The purpose of this issue is to keep a record of the pull requests (PRs) submitted by me throughout the course of this project. By linking the PRs here, it will be easier to track and review the progress and provide feedback as needed.
Project Details:
Outline
Getting Started with WasmEdge Plugins
Developing WasmEdge Plugins
WasmEdge Plugin API Reference
Understanding WasmEdge Plugins
Conclusion
Recap of WasmEdge Plug-in System
Future Development Roadmap
PRs Submitted:
The text was updated successfully, but these errors were encountered: