Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

docs: add contributing guidelines #62

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

hugocaillard
Copy link
Collaborator

@hugocaillard hugocaillard commented Jun 16, 2023

  • Make this repository the official home of Clarity improvement ideas.
  • Suggest a light process to go from an idea to a SIP

@hugocaillard hugocaillard force-pushed the docs/add-contributing-guidelines branch from cfb94e4 to a00bb84 Compare June 16, 2023 15:56
README.md Outdated Show resolved Hide resolved
Co-authored-by: Brice Dobry <brice@obycode.com>

- Make sure that a similar issue doesn't already exists (check the closed ones)
- Be specific
- Give use cases and usage exemples
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Give use cases and usage exemples
- Give use cases and usage examples


## From candidate to SIP

Once an issue is opened, it can have the tag `clarity-3-candidate`, meaning that the idea will be considered to be added to the upcoming version clarity.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Once an issue is opened, it can have the tag `clarity-3-candidate`, meaning that the idea will be considered to be added to the upcoming version clarity.
Once an issue is opened, it can have the tag `clarity-3-candidate`, meaning that the idea will be considered to be added to the upcoming version of Clarity.

- `icebox` meaning that this idea won't be included in the next Clarity version but maybe in later ones
- `wontfix` this idea will not be included in Clarity (and close the issue).

The Blockchain team should be responsible for setting this tags.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Blockchain team should be responsible for setting this tags.
The Blockchain team should be responsible for setting these tags.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants