logo
Virtual Institute
for
I/O

User Tools

Site Tools

You are here: Virtual Institute for I/O » IO500 » Rules » Committee

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
io500:rules:committee [2019/09/23 18:45] – john_bentio500:rules:committee [2020/08/13 17:09] (current) – external edit 127.0.0.1
Line 11: Line 11:
     - 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.  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.   -  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 requests for media interviews are discussed by the full committee who most unanimously decide how to respond. 
-  - All announcements (via email, twitter, etc) must be approved ahead of time by the entire committee and must be signed as the IO500 committee +  - 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. 
-    -  An announcement is any newly initiated thread +    - 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 replies to questions initiated by the community . . .  +    - 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). 
-    - . . . that cannot be answered with the existing documentation: +    - 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. 
-      - The immediate answer: “The committee will discuss and get back to you within 48 hours” +    - 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. 
-      - Immediately create a board vote. +    - 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.
-      - If 100% approval, then reply with the answer (signed by committee). +
-      - If less than 100% approval, but no dissent, then reply with ‘preliminary answer’ (signed by committee). +
-      - If dissent, then we must wait until the next meeting to officially reply.  Reply in meantime with, “Committee will need more time to discuss” +
-    - . . . that can be answered with existing documentation (e.g. virtual machines and 10 Node Challenge) or is a technical question not directly related to IO500 (e.g. how to compile IOR) +
-      - An individual committee member can reply and sign as an individual.+
   - All lists of names should follow alphabetical order   - All lists of names should follow alphabetical order
     - For casual material, first name ordering is fine     - For casual material, first name ordering is fine
io500/rules/committee.1569257159.txt.gz · Last modified: 2019/09/23 18:45 by john_bent
Impressum Privacy Driven by DokuWiki CC Attribution-Share Alike 4.0 International