Skip to content
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

Adding a clear process to Contributing guidelines for non technical discussions. #13603

Closed
simpss opened this issue Feb 22, 2018 · 7 comments
Closed
Assignees
Labels
Milestone

Comments

@simpss
Copy link

simpss commented Feb 22, 2018

As issue #13457 and #13597 indicated, the community wants to talk about potential ethical and competitive pitfalls of the AMP project. There were some misunderstandings on where these questions are welcome and where the core contributors would respond.

I personally think this discussion should be welcome and public, while establishing a clear uncensored papertrail. Of-course moderation is warranted once comments go against the CoC, but actions should not be preemptive and there should be no filter between documentation and discussion.

Having a documented way to raise non-technical issues and listening to concerned voices is crucial for AMP to succeed as an open technology.

@dreamofabear
Copy link

Sounds reasonable, I think we can spell this out more clearly. Related: #13600 (comment)

/cc @mrjoro

@mrjoro mrjoro self-assigned this Feb 22, 2018
@mrjoro
Copy link
Member

mrjoro commented Feb 22, 2018

Makes sense to me; I'll take a stab at this.

@ampprojectbot
Copy link
Member

This issue hasn't been updated in awhile. @mrjoro Do you have any updates?

1 similar comment
@ampprojectbot
Copy link
Member

This issue hasn't been updated in awhile. @mrjoro Do you have any updates?

@mrjoro
Copy link
Member

mrjoro commented Oct 11, 2018

Once the new governance model is in place, these meta conversations will likely be something the Advisory Committee or the Technical Steering Committee would take up. They will be publishing details of how they operate; I'll add links to those here once they are ready.

@ampprojectbot
Copy link
Member

This issue hasn't been updated in awhile. @mrjoro Do you have any updates?

@stale
Copy link

stale bot commented Jul 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale Inactive for one year or more label Jul 17, 2020
@stale stale bot closed this as completed Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants