Enhance Go+ contributing guidelines and introduce code of conduct #1829
Comments
aofei
added a commit
to aofei/.goplus.gop
that referenced
this issue
Mar 29, 2024
Updates goplus#1829 Signed-off-by: Aofei Sheng <aofei@aofeisheng.com>
aofei
added a commit
to aofei/.goplus.gop
that referenced
this issue
Mar 29, 2024
Updates goplus#1829 Signed-off-by: Aofei Sheng <aofei@aofeisheng.com>
aofei
added a commit
to aofei/.goplus.gop
that referenced
this issue
Mar 29, 2024
Updates goplus#1829 Signed-off-by: Aofei Sheng <aofei@aofeisheng.com>
aofei
added a commit
to aofei/.goplus.gop
that referenced
this issue
Mar 29, 2024
As our project grows, we want to ensure that our community understands
how to contribute effectively and feels welcomed to do so. This update
to our contribution guidelines aims to clarify the process and encourage
more developers to get involved.
Key changes include:
- Simplified the language to make the guidelines more accessible to
non-native English speakers and newcomers to open source.
- Included a step-by-step guide on setting up the development
environment, submitting a pull request, and what to expect during
the review process.
- Added a new section on community standards and code of conduct to
foster a respectful and inclusive community atmosphere.
- Provided clear examples of desirable contributions, such as bug
fixes, feature proposals, and documentation improvements.
Updates goplus#1829
Signed-off-by: Aofei Sheng <aofei@aofeisheng.com>
|
Due to some tasks still pending completion (primarily updates to the goplus.org website), this issue cannot yet be closed. I'm currently occupied with writing the language spec and will revisit this once that work is completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal
Introduce a code of conduct and revise the contributing guidelines to streamline the contribution process, enhance inclusivity, and improve commit message clarity across the Go+ project.
Background
The Go+ project has grown significantly, with contributions spanning multiple repositories. However, the absence of a unified code of conduct and inconsistent contributing guidelines across repositories have led to challenges. These include a lack of a standardized approach to contributions and difficulties in understanding the project's current developments due to unclear commit history.
Workarounds
N/A
The text was updated successfully, but these errors were encountered: