In this session we will openly discuss and strive to achieve consensus on how best to govern SWEET as a longstanding, domain level, semantic web resource. As such, there are several outstanding questions which either need to be addressed or past decisions confirmed and then documented (likely on the SWEET wiki). Examples, though not comprehensive, include:
1. How are SWEET issues or proposals raised?
2. What are the criteria used to evaluate SWEET issues or proposals?
3. Who, or whom, evaluates the issues or proposals?
4. Is there a ‘statute of limitations’ for any such issues or proposals?
5. How does the community arrive at a decision?
6. How is that decision recorded and/or documented for the community?
7. How or what is put in place to help ensure every member is abiding by those decisions?
8. Based on discussion of previous items, is a SWEET manager required or can the community self manage under a more specific set of guidelines?
View Notes
