Add Code of Conduct and Contributing guide #45
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chshersh
added
component: documentation
qexat
approved these changes
Feb 3, 2025
Collaborator
What kind of things do you mean here? |
Collaborator
|
@heathhenley actually nevermind I just noticed that what I thought about was already in the README 😌 |
Contributor
|
Looks good to me! 👍 |
Collaborator
|
Looks good to me 🚀 |
Owner
Author
|
Thanks everyone for the quick review! Since we got approvals from everyone, I'll merge it earlier. There's always a possibility to discuss and change it later if anything comes up. |
thezbm
reviewed
Feb 4, 2025
|
|
||
| That's all so far! | ||
|
|
||
| > ![NOTE] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding some guidelines for ensuring we don't stress from working on this project (stressing out about breaking the rules doesn't count).
TL;DR: Be respectful, behave like an adult and prefer discussing issues first to avoid conflicts and unexpected ambiguity.
Please, read it and let me know if the wording doesn't make sense or if something is unclear.
cc @heathhenley @thezbm @loadre @qexat since you contributed in the past and may want to contribute in the future
I'll keep this PR open for 1 week to give you folks some time to review and discuss, and then I'll merge it on February 9th.
As for long-term goals, I plan to work on this project today, tomorrow, in one week, in one month and this year. Then we'll see.
Maybe Microsoft will recognise this wholesome effort and pay me huge bucks. But to be realistic, most likely, people will try GitHub TUI and just start constantly complaining a lot about something not working.
My plan is to make the 1.0 release this year (see milestones for the roadmap).
The current stage is pre-alpha. I'll continue to exercise my power of BDFL and push to
maindirectly until alpha is done. Obviously, I'll be reasonable to avoid conflicts with current PRs.Then, I'll slow down and start working through PRs (if we still have contributors who can review the code).
Happy to discuss further!