Create CONTRIBUTING.md

[martinsumner]

Draft guideline for contributing.

[martinsumner]

Draft for comment - @aef- @WarpEngineer @tburghart @hmmr

[hmmr]

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.

[pjaclark]

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."

[WarpEngineer]

We should add the instructions to join in the primary Riak README instead. There are already some lines towards the bottom which we can add to.

[WarpEngineer]

Suggested change

	See http://developercertificate.org/ for a copy of the Developer Certificate of Origin license.
	See https://developercertificate.org/ for a copy of the Developer Certificate of Origin license.

[WarpEngineer]

So we don't want to explicitly call out AI contributions? The 4 clauses technically should cover it.

[hmmr]

This was my attempt to clarify the use of AI in contributions:

(e) If any sort of AI was used to write substantive portions
    of a contribution, the human person submitting it must:
  (1) provide a description of the session in which their
      contribution was created, at least including the model(s)
      and harness(es) used and prompts given, which should be
      sufficient for others to recreate it independently.
  (2) provide, to all significant parts of a contribution
      (such as functions or modules), meaningful in-line
      human-written comments sufficiently explaining why
      that part is written in this particular way, for others
      to be able to read, understand and reason about relevant
      parts of the code, and maintain it in future.
  (3) use their own, actual email and user name in all commits.

[WarpEngineer]

I like it. We should put something like that in.