User Tools

Site Tools


Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
io500:rules:committee [2019/06/25 17:47] john_bentio500:rules:committee [2019/09/23 18:45] john_bent
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.   -  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
 +    -  An announcement is any newly initiated thread
 +  - All replies to questions initiated by the community . . . 
 +    - . . . that cannot be answered with the existing documentation:
 +      - 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
 +    - 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, then follow the other rules.
 +
  
 The committee can be reached at [[committee@io500.org]]. The committee can be reached at [[committee@io500.org]].