how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve: Leave a 👍 or a 👎 on this comment to describe your experience.

Ask questions about the proposal, how the syntax works, what the semantics mean, etc.

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

and let us know how you are putting Hypothesis Help to good use

While this tutorial has content that we believe is of great benefit to our community, we have not yet tested or edited it to ensure you have an error-free learning experience. It's on our list, and we're working on it! You can help us out by using the "report an issue" button at the bottom of the tutorial.

please feel free to open an issue here on GitHub with questions/comments/improvements/etc

The exact form of the platform is yet to be finalized, and we want to involve you, the community, in helping to provide ideas and test the new contribution workflow!

I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)

Please don’t be shy to submit your project if you’re just starting out!

I am new to the ecosystem and really looking forward to feedback

FWIW, I would have raised it earlier if I thought it would have made a difference.

I honestly don't know what you find unclear about this question. I think you initially misread. I edited out your title change because it wasn't what I'd intended and it misled others. I edited in two more sections to clarify. The last section makes it as clear as I can: A single question provokes 1 of 3 responses (not necessarily answers). To chose between them I need to understand acceptable scope of both question and answers. Yes this topic is a muddy one, that's why I'm asking! I want others to help me clarify the unclear!

Your comments are welcome.

Edit this page Request docs changes

Help & feedback Docs Edit this page to fix an error or add an improvement in a merge request Create an issue to suggest an improvement to this doc Show and post comments to review and give feedback on this doc

Request features

As part of the beta program, if you or someone on your team can give us quick feedback every 1-2 weeks, we'll keep extending your free trial (normally 2 weeks) indefinitely!

You can contact me via anything listed in the Contact section - preferably E-Mail or Matrix. Other places to give feedback are GitHub (Issues, Stars, Following) and Google Play.