Changes between Version 1 and Version 2 of CharterAndBylaws


Ignore:
Timestamp:
10/13/15 21:34:51 (9 years ago)
Author:
gschadow
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CharterAndBylaws

    v1 v2  
    44
    55To publish, maintain and promote the Unified Code for Units of Measure.
    6 
    7 == General Principles of Engagement ==
    8 
    9 It is in the nature of the field of Units of Measure that it is very stable and maintenance activity may be very low.
    10 For this reason, the UCUM Organization is constitutes as a light-weight organization.
    11 The central interaction device is around an active management web site, http://unitsofmeasure.org.
    12 Face to face or telephone meetings are held minimal.
    13 There are no standing meetings.
    146
    157== Members ==
    … …  
    3729== Decision Making ==
    3830
    39 The Board of Advisors makes decision by simple majority.
     31It is in the nature of the field of Units of Measure that it is very stable and maintenance activity may be very low.
     32For this reason, the UCUM Organization is constituted as a light-weight organization.
     33The central interaction device for all decision making is an active management web site, http://unitsofmeasure.org.
     34Face to face or telephone meetings are held minimal.
     35There are no standing meetings.
    4036
    41 '''Decisions which alter the structure or bylaws of the organization''' must be made with at least the chairman of the board, one ex-officio member present and two other board members voting (not abstaining) in a real time discussion via telephone or per discussion convened electronically on the web site. All members of the Board of Advisors must be notified with motions to change bylaws or organization submitted at least 30 days prior to the voting.
     37All decisions are made by the Board of Advisors by simple majority.
     38
     39'''Decisions which alter the structure or bylaws of the organization''' must be made with at least the chairman of the board, one ex-officio member present and two other board members voting (not abstaining) in a real time discussion via telephone or per discussion convened electronically on the web site. All members of the Board of Advisors must be notified with motions to change bylaws or organization submitted in writing on the web site at least 30 days prior to the voting.
    4240
    4341'''Technical Decisions:''' are made on tickets by at least 2 board members documenting assent to the proposal. When only one board member engages in the adjudication and no other board member weighs in in opposition, the decision of the single member may be implemented. However, decisions by a single member cannot bind the UCUM Organization to implement this decision if the single member so deciding does not himself implement the decision.
    … …  
    4543All technical decisions are made on a ticket which may be submitted by any Member of the UCUM organization (even non-verified new members). A ticket must be accepted by a board members to be turned into action. Any verified member can comment on tickets by commenting on the ticket. Board members can decide on the ticket status.
    4644
    47 [to be continued]
     45The process of action on a technical ticket is as follows:
     46 1. A board member or secretary reviews the request and triages it.
     47   * Possibly revising the category.
     48   * Drafting a quick excerpt of the essence of the request and proposes one of the determinations:
     49 2. Accept, in which case the board member or secretary will be the owner and make a concrete change proposal to the specification.
     50   * A ticket cannot be accepted without a concrete change proposal to the specification.
     51   * Other board members ''should'' review and opine to the change.
     52   * If the proposal was accepted by a secretary, at least one board member must approve the proposal.
     53 3. Reject, in which case the board member or secretary will give a rationale to the proposal to reject.
     54   * The status of such tickets are "reject_proposed".
     55   * At least one other board member needs to agree with the rejection proposal, in which case the next status will be "wontfix" (will not change).
     56   * The member who submitted the ticket may provide further comment and justification, thus disputing the rejection decision.
     57   * If the rejection decision is disputed, another board member may adopt the ticket and take it to Reconsider status, but such board member must then accept the responsibility of seeing the change request through.
     58     * A proposal for reconsideration must be actionable, it must explain how the issue can be resolved, how the concerns of the rejecting board member can be addressed, the emphasis is ''how'' not just ''why''.
     59 4. Other statuses may exist to determine that the request is not actionable or doesn't identify a specific change need, is out of scope or suggests a problem that is not a real problem. These determinations can be made by one board member or secretary.
    4860
     61The web site can be used to create ticket reports. The "timeline" function of the web site, and most ticket information can only be seen by registered users, this is necessary and highly effective to prevent ticket spam, i.e., by removing the pay-off for a spammer to place spam tickets: links they place in their spam tickets will not end up on search engines.