This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
io500:rules:committee [2019/06/03 16:20] – kunkel | io500:rules:committee [2019/10/26 21:36] – john_bent | ||
---|---|---|---|
Line 5: | Line 5: | ||
The committee governs itself with the following rules: | The committee governs itself with the following rules: | ||
- | | + | |
- | | + | |
- | | + | - Exception: additions to the News page require only 2 members to approve but must email edits out to the full committee. |
- | | + | - Exception: removing accidentally revealed internal information requires only 2 members to approve but must email edits out to the full committee. |
+ | - Exception: updating the webpage with new lists requires only the members attending the particular BoF. | ||
+ | - By default, all submissions marked VALID by the io500.sh script are accepted. | ||
+ | | ||
+ | - All communication (via email, twitter, except Slack) must be approved ahead of time by the entire committee and must be signed as the IO500 committee | ||
+ | - Slack communication is fine as long as no official statement is made. | ||
+ | - All lists of names should follow alphabetical order | ||
+ | - For casual material, first name ordering is fine | ||
+ | - For official purposes, last name ordering should be used | ||
+ | - Bibtex, any documentation about the list or the benchmarks should use {author: IO500 Committee; editors: alpha names by last} | ||
+ | - For academic publishing (e.g., analysis of the list), name order should follow contribution effort. If equal contributions, | ||
The committee can be reached at [[committee@io500.org]]. | The committee can be reached at [[committee@io500.org]]. | ||