This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
io500:rules:committee [2019/06/10 17:09] – john_bent | io500:rules:committee [2019/12/20 19:07] – john_bent | ||
---|---|---|---|
Line 10: | Line 10: | ||
- Exception: removing accidentally revealed internal information requires 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. | - 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. | + | - By default, all submissions marked VALID by the io500.sh script are accepted. |
- | - All requests for media interviews are discussed by the full committee who most unanimously decide how to respond. | + | - All requests for media interviews are discussed by the full committee who most unanimously decide how to respond. |
+ | - There are two official channels of communication for the IO500: the twitter handle and the email address committee@io500.org. | ||
+ | - The twitter handle can be used without pre-approval to advertise IO500 and to rebroadcast any official statements issued from The Email Address. Retweets of news reports including IO500 and other IO500 mentions do not require committee approval. | ||
+ | - All private conversations between community members and committee members must be reported back to the committee with the only exception being requests for clarification of existing published information (this includes technical information available on GitHub). | ||
+ | - Any and all communications from individual committee members are merely expressions of their personal opinion and represent neither official positions nor opinions of the IO500. When committee members reply as individuals to questions asked about official IO500 policies, they must include the following statement, “These statements merely reflect my own personal view; the only mechanism for announcing official IO500 policies and decisions is the committee@io500.org email address.” | ||
+ | - Community members can ask individual committee members for clarification about existing policies. | ||
+ | - These rules apply to the benchmark applications used in the IO500 when the context is IO500 related but do not apply to general conversations about IO unrelated to IO500. | ||
+ | - 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]]. | ||