-
Notifications
You must be signed in to change notification settings - Fork 410
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
Update CODE_OF_CONDUCT.md #1215
Conversation
SonarCloud Quality Gate failed. 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We encourage productive discussions about our roadmap. Rejecting any changes that suggest otherwise.
@@ -32,6 +32,10 @@ Project maintainers have the right and responsibility to remove, edit, or reject | |||
|
|||
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. | |||
|
|||
## Roadmap | |||
|
|||
Those not affiliated with Confio should not discuss the roadmap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was never any attempt on your part to discuss the roadmap with our team, nor any message asking us about it. We felt we published a decent amount of clarity in February and gladly answered any questions that came up around the Cosmos Hub Proposal 103. This item is untrue and does not represent either current reality or our desired reality
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kindly ask you to review our current standards. I do believe your behavior had fallen into the unacceptable areas a number of times, completely unrelated to any recent PRs.
Now that you bring this up, I would like you to reflect on how you could contribute in a way aligned with the current code of conduct. I am happy to discuss this with you in private as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You write me in DMs many times. If you asked me a simple question there, I could have clarified any doubts easily
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ethanfrey for your response. I had kept this PR intentionally open for some time to let it sink and see if there is any community feedback or opinion that seconds this claim by a different party.
I appreciate feedback from the community and @faddat and Notional have been valuable contributors to the project in
the past. Nevertheless there are much better ways to participate and make changes than using PRs as platform.
Public channels:
- Regular community calls
- Public support and discussions on our discord server
- Proposals as Github issues
As part of proposal #103, Confio had shared a roadmap for this year and hosted Twitter spaces to discuss this and answer questions.
As a contributor to the project, @faddat has also a direct channel to me on discord. I have neither received a question or feature requests in DM.
To move on:
- I see this PR as an expression of @faddat opinion and feelings at the point in time and not more. 🚨: Public Goods work halted #1198 was leaving a gab that was not filled.
- Let us get back to a professional attitude and work on features instead of this
This PR adjusts the wasmd code of conduct document to fit policies outlined in #1209