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
Next revisionBoth sides next revision
io500:rules:committee [2019/09/23 18:45] – john_bentio500:rules:committee [2019/11/09 20:11] – john_bent
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 +  - 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]] 
-    -  An announcement is any newly initiated thread +    - Exception: notifying submitters of invalid submissions only requires two committee members. 
-  - All replies to questions initiated by the community . . .  +    - 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. 
-    - . . . that cannot be answered with the existing documentation: +  - Slack communication is fine as long as no official statement is made.
-      - The immediate answer: “The committee will discuss and get back to you within 48 hours” +
-      - Immediately create a board vote. +
-      - 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.txt · Last modified: 2020/08/13 17:09 by 127.0.0.1
Impressum Privacy Driven by DokuWiki CC Attribution-Share Alike 4.0 International