You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,8 @@ Selecting the appropriate tag helps maintain organization in the table and provi
70
70
71
71
### Adding new multicodecs to the table
72
72
73
+
#### Guidelines for submitters
74
+
73
75
The process to add a new multicodec to the table is the following:
74
76
75
77
1. Fork this repo
@@ -88,6 +90,28 @@ Codec names should be easily convertible to constants in common programming lang
88
90
89
91
The `validate.py` script can be used to validate the table once it's edited.
90
92
93
+
Before submitting a new code please:
94
+
-[ ] Consider if an existing code works for you
95
+
-[ ] Submit a link to the specification the code refers to so that others may reference and use it
96
+
-[ ] Give some context on the intended use
97
+
98
+
To keep the initial review process lightweight and encourage experimentation, newly added codes are probationary.
99
+
100
+
Six months after submission, the submitter should comment on the merged PR with an update on usage.
101
+
If there is no comment or the code is no longer in use, a PR to remove it will be opened. If no objections are raised within 3 months, the code will be removed.
102
+
103
+
#### Guidelines for reviewers:
104
+
105
+
For reviewers of new codes please consider:
106
+
-[ ] Does the code fit within the relevant tagged category?
107
+
-[ ] Is this code needed or could it be served by an existing code?
108
+
-[ ] Is the byte size of the requested code suitable or should it be higher?
109
+
-[ ] Is the number of codes requested suitable?
110
+
-[ ] Is approval of the code unlikely to cause the need for many more codes in a way that is avoidable or would warrant a new category?
111
+
-[ ] Is the name of the code unlikely to be confusing or problematic for users?
112
+
113
+
While reviewers are frequently experienced in the projects of the managed categories and can give guidance around the usage of codes and potential alternatives that better fit the guidelines they are not meant to gate a user's ability to leverage multicodec tooling. If a user has a code that fits the guidelines it should be approved even if the reviewer thinks an alternative approach should be acceptable but the submitter disagrees.
0 commit comments