Conversation
Draft guideline for contributing.
|
Draft for comment - @aef- @WarpEngineer @tburghart @hmmr |
| If feedback is not received on the proposal, then please escalate via the `open-riak` channel on the Erlang Ecosystem Foundation Slack channel. | ||
|
|
||
| Note that without positive feedback, it may be difficult to pass any proposal through the PR review stage. It is easier to find maintainer review-time for PRs in support of proposals with a broad consensus. | ||
|
|
There was a problem hiding this comment.
I would insert the following paragraph here:
If, and once, a sufficient amount of feedback has been collected, and consensus is reached on all major points of a proposal, the author can proceed to Stage 2 with reasonable assurance that no more substantive objections to their work can arise.
This is to guard against objections in principle coming too late, after Discussion stage is formally ended. Such objections can potentially derail an effort behind the proposal and lead to much friction, frustration and unhappiness.
| - Reference; reference to any issues or PRs raised for the feature (to be added later). | ||
| - Planned Release for Inclusion. | ||
|
|
||
| If feedback is not received on the proposal, then please escalate via the `open-riak` channel on the Erlang Ecosystem Foundation Slack channel. |
There was a problem hiding this comment.
This is not public, and how to join is not clear at all. Maybe add a line saying "Sign up for a free EEF Basic membership here, and request access to Slack via the member portal."
3 participants
Draft guideline for contributing.