Changeset 3728ed0


Ignore:
Timestamp:
Apr 15, 2011, 6:05:35 PM (15 years ago)
Author:
Alex Dehnert <adehnert@…>
Branches:
master, space-access, stable, stage, test-hooks
Children:
0089335
Parents:
9a6c6886
git-author:
Alex Dehnert <adehnert@…> (04/15/11 18:05:00)
git-committer:
Alex Dehnert <adehnert@…> (04/15/11 18:05:35)
Message:

Fix spelling and line breaks

  • unix2dos
  • Fix spelling of consensus
File:
1 edited

Legend:

Unmodified
Added
Removed

  • design/agreement.txt

    r9a6c6886 r3728ed0  
    3030The ASA database code will be made publicly available. Anyone at MIT (or elsewhere in the world) will be able to read the code and the history of changes to it (though not configuration such as passwords, or group data such as signatories). (Moira, the system MIT uses for handling user accounts, mailing lists, hostnames, etc., similarly has publicly-available source.) The mailing list asa-db-commits@mit.edu will receive commit information and will be public.
    3131
    32 Any stakeholder will be able to propose an individual for commit access or server access by contacting core stakeholders. A core stakeholder (generally whichever stakeholder is proposing the individual) must sponsor the request. If no objection is made within one week, they may be given access. If an objection occurs, the core stakeholders should attempt to reach a concensus.
     32Any stakeholder will be able to propose an individual for commit access or server access by contacting core stakeholders. A core stakeholder (generally whichever stakeholder is proposing the individual) must sponsor the request. If no objection is made within one week, they may be given access. If an objection occurs, the core stakeholders should attempt to reach a consensus.
    3333
    34343. Infrastructure
    … …  
    40404. Development Process
    4141
    42 a) Major changes should be discussed first with the stakeholders. Concensus should be achieved that the change is desirable. For particularly large, complex, and potentially objectionable changes, one should solicit opinions for at least a week, via email and possibly an in-person meeting.
     42a) Major changes should be discussed first with the stakeholders. Consensus should be achieved that the change is desirable. For particularly large, complex, and potentially objectionable changes, one should solicit opinions for at least a week, via email and possibly an in-person meeting.
    4343
    4444b) Develop and test the change.
    … …  
    5050e) Move the changes to production. This should be announced to at least the core stakeholders.
    5151
    52 When a concensus is reached among the core stakeholders or for simple, time-critical bugfixes, exceptions to this process can be made. In all cases, core stakeholders should be informed of changes.
     52When a consensus is reached among the core stakeholders or for simple, time-critical bugfixes, exceptions to this process can be made. In all cases, core stakeholders should be informed of changes.
    5353
    54545. Amendments
    5555
    56 This document may be amended through concensus decision of the stakeholders. Minor changes can be made through concensus decision of the core stakeholders only, if desired. Amendments must be discussed for at least a week over email before they can be made.
     56This document may be amended through consensus decision of the stakeholders. Minor changes can be made through consensus decision of the core stakeholders only, if desired. Amendments must be discussed for at least a week over email before they can be made.
Note: See TracChangeset for help on using the changeset viewer.