|
|
@@ -0,0 +1,214 @@
|
|
|
+---
|
|
|
+layout: page
|
|
|
+title: Committee | Torque 3D
|
|
|
+---
|
|
|
+
|
|
|
+<div class="banner"><div class="container">
|
|
|
+ <h1 id="what-is-the-steering-committee">What is the Steering Committee?</h1>
|
|
|
+</div></div>
|
|
|
+
|
|
|
+<div class="container">
|
|
|
+ <p>
|
|
|
+ The Torque 3D Steering Committee is the hand-picked body of community members
|
|
|
+ who are responsible for maintaining the core version of the Torque 3D codebase.
|
|
|
+ The first Committee was chosen by GarageGames, but new recruitments are made
|
|
|
+ by the Committee itself when necessary.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <p>
|
|
|
+ The Committee's operations include evaluating pull-requests made on the engine
|
|
|
+ repository, deciding on a roadmap for the engine's future, and of course doing
|
|
|
+ some programming in order to make that happen!
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <p>
|
|
|
+ The Committee's actions are governed by its Charter, which is laid out in the
|
|
|
+ section below.
|
|
|
+ </p>
|
|
|
+</div>
|
|
|
+
|
|
|
+<div class="banner"><div class="container">
|
|
|
+ <h1 id="current-membership">Current Membership</h1>
|
|
|
+</div></div>
|
|
|
+
|
|
|
+<div class="container">
|
|
|
+ <div class="row">
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Luis Anton</h4>
|
|
|
+ <p><b>Expertise:</b> Rendering and cross-platform code.</p>
|
|
|
+ <p><b>Known for:</b> Porting to <a href="http://www.garagegames.com/community/forums/viewthread/133262">OpenGL</a>
|
|
|
+ and <a href="http://www.garagegames.com/community/forums/viewthread/135114">Linux</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Bank</h4>
|
|
|
+ <p><b>Expertise:</b> Networking.</p>
|
|
|
+ <p><b>Known for:</b> <a href="http://www.afterworld.ru/">AfterWorld MMO</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Daniel Buckmaster</h4>
|
|
|
+ <p><b>Expertise:</b> Gameplay code.</p>
|
|
|
+ <p><b>Known for:</b> <a href="http://daniel.buckmasterfamily.id.au/walkabout/">Walkabout Navigation Toolkit</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Thomas Fischer</h4>
|
|
|
+ <p><b>Expertise:</b> Physics and platform coding.</p>
|
|
|
+ <p><b>Known for:</b> <a href="http://www.beamng.com/content/">BeamNG physics engine</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Andrew Mac</h4>
|
|
|
+ <p><b>Expertise:</b> Everything!</p>
|
|
|
+ <p><b>Known for:</b> <a href="http://steamcommunity.com/sharedfiles/filedetails/?id=223336592">Blood and Mana</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+
|
|
|
+ <div class="media col-sm-6">
|
|
|
+ <div class="media-body">
|
|
|
+ <h4 class="media-heading">Jeff Raab</h4>
|
|
|
+ <p><b>Expertise:</b> Gameplay code.</p>
|
|
|
+ <p><b>Known for:</b> <a href="http://www.garagegames.com/community/forums/viewthread/134222">Entity/component framework</a>.</p>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+ </div>
|
|
|
+</div>
|
|
|
+
|
|
|
+<div class="banner"><div class="container">
|
|
|
+ <h1 id="steering-committee-charter">Steering Committee Charter</h1>
|
|
|
+</div></div>
|
|
|
+
|
|
|
+<div class="container">
|
|
|
+ <h2 id="charter-vision">1. Vision</h2>
|
|
|
+ <p>
|
|
|
+ We are dedicated to making the best core version of Torque 3D possible, a
|
|
|
+ reliable foundation for others to build upon. We will ensure that Torque
|
|
|
+ 3D is a modern, user-friendly, open-source game engine suitable to the needs
|
|
|
+ of students, hobbyists, independent game makers, and professional studios.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <h2 id="charter-goals">2. Goals</h2>
|
|
|
+ <ol>
|
|
|
+ <li>To maintain the best possible ‘master’ version of Torque 3D measured
|
|
|
+ in terms of performance, reliability, versatility, maintainability and
|
|
|
+ scalability.</li>
|
|
|
+
|
|
|
+ <li>To represent the goals and wishes of the engine’s user community.</li>
|
|
|
+
|
|
|
+ <li>To actively communicate in a clear and transparent manner.</li>
|
|
|
+
|
|
|
+ <li>To sustain the steering committee itself as a meritocratic and
|
|
|
+ effective organisation.</li>
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ <h2 id="charter-duties-and-responsibilities">3. Duties and Responsibilities</h2>
|
|
|
+ <ol>
|
|
|
+ <li>Create and regularly revise the engine roadmap after:
|
|
|
+ <ol>
|
|
|
+ <li>Consultation with the community.</li>
|
|
|
+ <li>Review of the technical merits and feasibility of proposals.</li>
|
|
|
+ </ol>
|
|
|
+ </li>
|
|
|
+
|
|
|
+ <li>Review and act appropriately on all community contributions by:
|
|
|
+ <ol>
|
|
|
+ <li>Providing clear and timely feedback on the status of
|
|
|
+ submissions.</li>
|
|
|
+ <li>Ensuring that all contributions are free from intellectual
|
|
|
+ property encumbrances in order to maintain the integrity of the
|
|
|
+ product.</li>
|
|
|
+ </ol>
|
|
|
+ </li>
|
|
|
+
|
|
|
+ <li>Performing rigorous testing of all source code contributions,
|
|
|
+ separately and integrated with trunk code.</li>
|
|
|
+
|
|
|
+ <li>Act in a professional manner by:
|
|
|
+ <ol>
|
|
|
+ <li>Dealing ethically and professionally with other individuals
|
|
|
+ and organizations.</li>
|
|
|
+ <li>Acting in accordance with publicly-available guidelines such
|
|
|
+ as this document.</li>
|
|
|
+ </ol>
|
|
|
+ </li>
|
|
|
+
|
|
|
+ <li>Periodically review the charter and composition of the committee.</li>
|
|
|
+
|
|
|
+ <li>Regularly participate in private and public discussions relating to
|
|
|
+ the committee’s activities.</li>
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ <h2 id="charter-membership">4. Membership</h2>
|
|
|
+ <p>
|
|
|
+ Members of the steering committee must be willing and able to commit time
|
|
|
+ and energy to fulfilling the committee’s mission. The total committee size
|
|
|
+ should remain close to six members.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <p>
|
|
|
+ To be considered as a member of the committee, the prospective member should:
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <ol>
|
|
|
+ <li>Be available for at least 10 hours a week of work on the Torque 3D
|
|
|
+ open source product such as programming, documentation, administration, etc.</li>
|
|
|
+
|
|
|
+ <li>Have expert knowledge in game, game engine, or tool development,
|
|
|
+ such as documentation, C++ engine programming, operating system platform programming, the creation and application of game art and content, etc.</li>
|
|
|
+
|
|
|
+ <li>Agree to the Open Source Software Agreement available on the
|
|
|
+ GarageGames web site.</li>
|
|
|
+ </ol>
|
|
|
+
|
|
|
+ <p>
|
|
|
+ If a member is unable to serve on the committee for any reason, the vacancy
|
|
|
+ may be filled or left empty at the discretion of the committee. If the
|
|
|
+ committee as a whole is unable to perform its duties, it can vote to
|
|
|
+ transfer the project to another person or entity.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <h2 id="charter-reports">5. Reports</h2>
|
|
|
+ <p>
|
|
|
+ To facilitate the committee’s operation while accounting for members in
|
|
|
+ varied timezones, reports are the primary method of internal communication.
|
|
|
+ At the end of the month, each committee member will summarize their activity
|
|
|
+ into a monthly work report in a publicly available format.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <h2 id="charter-voting">6. Voting</h2>
|
|
|
+ <p>
|
|
|
+ Any actions to be undertaken by members of the committee in an official
|
|
|
+ capacity should be voted on where there is any disagreement. Voting will
|
|
|
+ take place in forum threads, emails, or any other appropriate method of
|
|
|
+ communication available to all members. Each member of the committee has one
|
|
|
+ vote. Any member who has not voted seven days after the vote is initiated
|
|
|
+ will count as having abstained. Decisions must be approved by a two-thirds
|
|
|
+ majority of all members (not only members who participate in the vote).
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <h2 id="charter-removal">7. Removal</h2>
|
|
|
+ <p>
|
|
|
+ If a committee member is unable to fulfill their requirements, or fails to
|
|
|
+ uphold the charter, they may be removed from the committee after having had
|
|
|
+ a chance to respond. They may also be removed by a vote if their activities
|
|
|
+ are deemed to no longer align with the guidelines in sections
|
|
|
+ <a href="#charter-duties-and-responsibilities">3</a> and
|
|
|
+ <a href="#charter-membership">4</a> above.
|
|
|
+ </p>
|
|
|
+
|
|
|
+ <h2 id="charter-amendments">8. Amendments</h2>
|
|
|
+ <p>
|
|
|
+ This charter is a living document and may be amended by the committee as
|
|
|
+ outlined in section <a href="#charter-voting">6</a>.
|
|
|
+ </p>
|
|
|
+</div>
|
Daniel Buckmaster
11 years ago
