Differences

This shows you the differences between two versions of the page.

--- io500:rules:committee [2019/11/09 20:11] – john_bent
+++ io500:rules:committee [2020/08/13 17:09] (current) – external edit 127.0.0.1
@@ Line 12: / Line 12: @@
   -  By default, all submissions marked VALID by the io500.sh script are accepted.  However, any committee member can raise an objection if they think a submission violates any of the IO500 rules.  In typical situations, the committee will discuss the concerns with the submitter.  After this discussion, the committee will vote.  If 50% or more think the submission should be rejected, it will be rejected.
   - All requests for media interviews are discussed by the full committee who most unanimously decide how to respond.
-  - 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 and must cc [[committee@io500.org]]
+  - There are two official channels of communication for the IO500: the twitter handle and the email address committee@io500.org.  The only mechanism for communicating official IO500 announcements, policies, statements, or decisions is via the email address (hereafter referred to as The Email Address).  All communication from The Email Address must be unanimously pre-approved by the full committee. Official communication will also be echoed to the twitter handle.
-    - Exception: notifying submitters of invalid submissions only requires two committee members.
+    - 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.
-    - Exception: questions about whether a submission was received can be answered by a single member. Questions about whether a submission is valid require full committee approval for an unqualified affirmation.  Questions about whether a submission is valid can be answered with the approval of just two members but must say, “Note that we reserve our right to reject this submission should we discover problems in the future.”  All answers must cc committee@io500.org.
+    - 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).
-  - Slack communication is fine as long as no official statement is made.
+    - 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.”  This covers face-to-face conversations, conversations in slack, social media such as LinkedIn and Facebook, and all other communication methods not explicitly mentioned elsewhere in these rules.
+    - Community members can ask individual committee members for clarification about existing policies.  However, if the question has not yet been publicly answered, then the committee member must bring the question to the full committee and the answer must be issued from The Email Address and twitter in accordance with these rules.
+    - 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

Virtual Institute for I/O

User Tools

Site Tools

Differences

Virtual Institute
for
I/O