-
Notifications
You must be signed in to change notification settings - Fork 519
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
[proposal] create a minimal CONTRIBUTING.md #1111
Comments
IMO this is a good idea, but fairly low priority. If we do it, it should be more thorough than the 3-line suggestion. I don't think we should complain about limited time there. |
Topics I would like to cover: for maintainers
for one-time, occasional, or other contributors
|
Exercism's community process for contributing and maintaining lives here. |
This was referenced Feb 24, 2021
ghost
closed this as completed
Mar 8, 2021
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a new contributor I would like to understand and respect the maintenance standards for this repository.
I propose we create a
CONTRIBUTING.md
to briefly document what to expect contributing to this repository.I and @coriolinus are strapped for time so I am on the fence about doing this. I am on the fence because I do not want to drain from our primary goal of high-quality concept exercises for the v3 launch.
So, the first step would be to decide whether we add one.
Then, let's define simple content.
I would appreciate even if this was something like:
As an aside, I feel like contributing
concept/
entries is quite well-defined and self-contained. So it may lend to us documenting clearly how to do it. But it is technical writing. Writing about Rust versus writing Rust. In fact, I would argue most of the v3 concept exercise development has been this kind of meta. Encoding teaching Rust in Exercism's format!The text was updated successfully, but these errors were encountered: