CONTRIBUTING.md 3.19 KB
Newer Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
# Contributing to the next revision of the OpenPGP spec (RFC 4880bis)

If you're new to this, in addition to the text below, you may also
want to read the [Tao of the IETF](https://www.ietf.org/tao.html).

Be aware that all contributions to the specification fall under the
"NOTE WELL" terms outlined below.

1. The best way to provide feedback (editorial or design) and ask
questions is sending an e-mail to [our mailing
list](https://www.ietf.org/mailman/listinfo/openpgp). This will assure
that the entire Working Group sees your input in a timely fashion.

2. If you have **editorial** suggestions (i.e., those that do not
change the meaning of the specification), you can either:

  a) Fork this repository and submit a pull request; this is the
  lowest friction way to get editorial changes in.
  
  b) Submit a new issue to Gitlab, and mention that you believe it is
  editorial in the issue body. It is not necessary to notify the
  mailing list for editorial issues.
  
  c) Make comments on individual commits in Gitlab. Note that this
  feedback is processed only with best effort by the editors, so it
  should only be used for quick editorial suggestions or questions.

3. For non-editorial (i.e., **design**) issues, you can also create an
issue on Gitlab. However, you **must notify the mailing list** when
creating such issues, providing a link to the issue in the message
body.

  Note that **gitlab issues are not for substantial discussions**; the
  only appropriate place to discuss design issues is on the mailing
  list itself.


# NOTE WELL

Any submission to the [IETF](https://www.ietf.org/) intended by the
Contributor for publication as all or part of an IETF Internet-Draft
or RFC and any statement made within the context of an IETF activity
is considered an "IETF Contribution". Such statements include oral
statements in IETF sessions, as well as written and electronic
communications made at any time or place, which are addressed to:

 * The IETF plenary session
 * The IESG, or any member thereof on behalf of the IESG
 * Any IETF mailing list, including the IETF list itself, any working group 
   or design team list, or any other list functioning under IETF auspices
 * Any IETF working group or portion thereof
 * Any Birds of a Feather (BOF) session
 * The IAB or any member thereof on behalf of the IAB
 * The RFC Editor or the Internet-Drafts function
 * All IETF Contributions are subject to the rules of 
   [RFC 5378](https://tools.ietf.org/html/rfc5378) and 
   [RFC 3979](https://tools.ietf.org/html/rfc3979) 
   (updated by [RFC 4879](https://tools.ietf.org/html/rfc4879)).

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and
[RFC 3979](https://tools.ietf.org/html/rfc3979) for details.

A participant in any IETF activity is deemed to accept all IETF rules
of process, as documented in Best Current Practices RFCs and IESG
Statements.

A participant in any IETF activity acknowledges that written, audio
and video records of meetings may be made and may be available to the
public.