Music Committee
Contents
Mission Statement of Vega Strike Music Committee (Draft)
To enhance the musical aspect of the Vega Strike experience through the establishment and maintainence of a series of requirements, guidelines and best practices in regards to its music; ensuring the music submissions meet these requirements and are of sufficient merit to be included in the game; promoting the project to prospective composers; providing training, mentoring, and support services to assist composers with completing their tasks; and, providing Vega Strike's developers with the necessary feedback they need to improve the music component of the game engine.
Why a Music Committee?
The primary reasons for organizing a music committee are:
- Standardization is lacking in Vega Strike's current music - styles are all over the place and there are very few common themes. A music committee can bring standardization and also provide training and mentoring to the composers to improve their musical skills.
- A committee is generally not overly dependant on any single individual to be able to function. Due to the open source nature of the product and hours required for a musical director-type role, it is unlikely the project would be able to secure an experienced musical director willing to or having the time to take on a project of this magnitude without compensation.
- Committees are more compatible with the open-source ideal that people working together at a common task can accomplish great things.
Representation of the Committee (Draft)
The Music Committee shall be composed primarily of composers but with developers and story-writers also participating. The committee will have a 10 member limit to prevent bloat from overly slowing proceedings.
Breakdown of the committee is as follows:
- Chairman/Vice-Chairman: Responsible for breaking a tie vote - vice-chair acts in Chair's stead if absent.
- Personnel & PR section: Responsible of recruiting people, and mediating with other organizations (eg: magnatune proceedings)
- Creative section: Responsible for executing and proposing activities for the creative staff (composers). That includes organizing work on pending tasks, recognizing/proposing/planifying new tasks, organizing tutorials, etc...
- Storyboard liason: Communicates the needs of storytelling to the creative section and back. Important task source and consulting body.
- Development liason: Communicates the needs of the creative section to engine development and back, organizing changes in the API that are required or desired by the creative section.
People on the comittee could belong to one or more section/role, with priorities attached to those functions. For example, the Chairman could also be a part of the Creative section. He could also be secondarily a part of another section, but to avoid overcommiting personnel we are avoiding "tertiary assignments". To avoid undercommitment, though, only primary assignments should be taken into account for "staff allocation". So... if a section has no primary assignee, it would be considered understaffed.
Inclusion or separation from the commitee does not relate to contribution, but rather decision-making. If you contribute a lot of high-quality music, but do not wish to take part in decision-making affairs, you would become a staff member reporting to the Committee, not a Committee member.
Meetings
The idea is to let the chairman open up proceedings, posting top-priority tasks, along with a motion for "further tasks".
Each meeting would gather tasks for processing and would be quickly treated, in order of proposition. Should the task grow and require a lengthy treatment, a specific thread would start and run in parallel with the main meeting. That's an advantage of message boards, it makes easier for people to divide their attention in multiple subjects. As well, at each meeting, each section should have a unified (let's let the details of that to the specific organization of each section) progress report as first post.
Those would be "organized meetings". There's the option for special-call "realtime meetings", carried out through the VS IRC channel preferrably, or through any other interactive messaging system at everybody's reach. Those would be necessary when a certain task needs important discussion in the sense of interactive exchange of ideas, where delays present in message board-based systems would hinder the effort.
