Review and approve technical charter
asajeffrey opened this issue · comments
We have a template draft of the project Technical Charter to adapt and approve.
1(a) needs a mission statement, which is #2.
We need to decide who the initial Committers (2(c)(ii)) are to the project, A first pass would be people who have r+ privileges on servo/servo?
7(b)Ii) is worded in terms of "the project license" but there may well be different subprojects which have different licenses. We need to reword it to describe how different subprojects declare their licenses, and something about getting the SC to okay any new projects which use licenses other than MPL-2, and maybe a CC license for docs. See also #6.
7(b)(ii) requires a developer certificate of origin, which will be a new requirement.
Finished my first pass.
I've made some suggested edits to the google doc (see the servo-formation mailing list for the link).
Closed by #20