Page Comparison

...

1. The ORAC would advise on both content and process and would draw from interested higher ed parties and experience open source developers.
   1. Any higher ed (.edu or .ac.) institution with an interest in the OpenRegistry initiative is eligible to participate on the Committee.
   2. Any commercial or non-profit organization with experience in open source development and an interest in seeing the OpenRegistry initiative grow would also be eligible
2. OpenRegistry Developer Institutions are ineligible to participate on the Committee.
3. The ORAC would meet once a month to review the progress of the OpenRegistry development and provide guidance or feedback to the Developer Institutions.
4. The Committee members would be active on OpenRegistry development email list and would weigh in on discussions where Developer Institutions have questions about the universality of functionality or about open source development processes
5. Initial membership is by invitation, however any eligible institutions may ask either the Committee or a Developer Institution for an invitation.
6. Participating Institutions may select one representative to the Committee.
7. Representatives may be removed if they are found by the consensus of Committee members or the consensus of Developer Institutions to be not participating.
8. All activities of the Committee are public. Notes from any meetings are to be posted.
9. The Committee is not a binding authority – it does not make decisions that the initiative must follow.
10. The Committee may be disbanded if a formal Steering Committee is established or if the initiative becomes dormant.
11. ORAC reviews and feedback is to be presented to the Jasig incubation committee for quarterly reviews to ensure the project is making progress

Potential Candidates for Invitation

...