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

request for comments on contributing standards and acceptance criteria #70

Merged
merged 1 commit into from Dec 7, 2020

Commits on Jul 13, 2018

  1. request for comments on contributing standards and acceptance criteria

    As the pull requests pile up, and as contributors may have motives that stray from the purpose of helping other developers (promotion, spam, etc.), I wanted to start a conversation on what the criteria should be for accepting new contributions. To start it off, here are some things I thought of:
    
    * What falls under the scope of developer tools? If it's outside (e.g. DApps) should we include a separate heading for well-built DApps that aid people's understanding of them
    * Should proposed tools have met a certain threshold of usage? Could this be captured in a number of Github stars or forks?
    * Should repo maintainers be required to use and evaluate the tools before adding/removing from the list?
    * What reasons/feedback should be provided by maintainers if a proposed tool is rejected?
    
    These are the opinions of myself, not ConsenSys.
    pakaplace committed Jul 13, 2018
    Copy the full SHA
    dd16eeb View commit details
    Browse the repository at this point in the history