Development Board

The Overture development board is...

Members

Augusto Ribeiro, Nick Battle, Luis Diogo Couto, Joey Coleman

Responsibilities

The Overture development board is the principal source 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
• Track the Contributions
• Assist on major code projects (ex: migration to GitHub)

Ongoing Issues:

Code Licenses

Overture will use the following licensing setup:

1. All code is GPL
2. All contributions in the main Overture code repository must be GPL or they will be rejected
3. All files must have a "(C) , "* assertion of ownership in the header comment
4. 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

Module List

For each module in Overture, we will keep a document with some information on its status. Each module has a rep whose responsibility is to keep the document up to date. Towards this end, the following tasks have been set:

1. Compile a list of module representatives
2. Prepare templates for information documents. Two templates are available. The maintainer can pick the one he wants
3. Seed the repository with the template files
4. Additional readme files must be written for the repository root and the core/ide/etc. folders

Current status: We have a list of all folders and reps and will seed the repository with the template files.

Documentation on the repository

We need to clean up the documentation folder in the Overture code repository. The following has been decided:

1. Documents that are packaged with releases (such as the manual) will be kept in the main repository
2. There is a dedicated documentation branch and work on the docs should be done in that branch
3. The document sources will be also be kept in the dev and master branches to keep the build process simple
4. Non release documents (such as planning, development guides, etc.) will be moved out to the wikis
5. Outdate documents will be deleted

Current Status: We are running through the documentation folder and compiling a list of all documents in order to classify them.

Archived Issues

See them here