-
Notifications
You must be signed in to change notification settings - Fork 25
Development Board
The Overture development board is...
Augusto Ribeiro, Nick Battle, Kenneth Lausdahl, Luis Diogo Couto, Joey Coleman
The Overture development board is the principal code advocate in the Overture project.
More specifically, the board has the following responsibilities
- Answer questions on the code, whether from direct knowledge or by pointing to the right person
- Approve code from remote collaborators
- Provide feedback on major decisions
- Assist on major code projects (ex: migration to GitHub)
It has been decided that we will use the following licensing setup:
- All code is GPL
- All contributions in the main Overture code repository must be GPL or they will be rejected
- All files must have a "(C) , "* assertion of ownership in the header comment
- All files point to a top level copy of the GPL and a LICENSES file.
Current Status: We are in the process of seeding the files in the repository with the new copyright headers
The board needs to decide its level of involvement in the Overture code tasks (see Code-Tasks).
We're working through a major renaming of the branches (see Branch Renaming). This work is mostly completed. The next step is to decide the level of enforcement (will be high) policy and what to do with the branch table.
We have finished compiling the list of modules and reps. The info templates are finalised and up on GitHub. Luis has prepared a list of folders and stub files. Joey is in the process of seeding the repository with the stub files. The files will simply point to the templates page so the maintainer can pick what he wants
We need to investigate the possibilities of removing the documentation from the Overture main repository into a documentation repository.
The board decided Overture should move to GitHub. The historic bugs were also moved to GitHub. Upon release 2.0.0 all the bugs were validated and if the ones that no longer existed were removed. The GitHub move has been completed. Yay!