![]() Rationale: In order to guarantee order in future decision-making, it must be made clear to all who qualifies as a member of the Development Team. Board to perform one or more specific roles that necessitate write access to the Version Control System repository or repositories.Īctive developers are understood to be members of the Development Team who have produced tangible output under the terms of points (a) or (b) above at least once every three months within the last 12 calendar months, and have no stated reasons to be considered inactive or intent to become inactive within the next 12 months. Persons eligible to become members of the Development Team are either: a) contributors who have either made at least three non-trivial contributions of code, graphics, sounds, music, or other resources used by the Project's product b) contributors who perform housekeeping contributions or tasks at any level in a consistent and regular fashion c) persons who on behalf of the Project run and manage computer systems used to support the Project's operations and its product d) individuals appointed by the Wesnoth, Inc. Members of the Development Team have write access to the version control system repositories managed by the Project, as well as privileged access to their associated issue trackers. Rationale: Re-stating the volunteer-driven nature of the Project is paramount to settling any potential disputes surrounding people's responsibilities within the Project, but it is equally important to remind people that their ultimate purpose is the betterment of Wesnoth and not the aimless production of code for their own goals.Īrticle 5. The Battle for Wesnoth Project has a Development Team comprised of volunteers dedicated to the betterment of the game. Rationale: It is imperative to guarantee that no decisions emanating from the Project Council can ever contradict Wesnoth's license or purpose as an Open Source Software development team. The Battle for Wesnoth Project's product and all associated code it publishes is compliant with the Open Source Definition as published by the Open Source Initiative. ![]() without making contributors perceive themselves as employees of the company, with all the legal consequences this carries.Īrticle 3. Likewise, the Project cannot be absorbed into Wesnoth, Inc. Its existence is an absolute legal necessity and it cannot be disbanded. exists in order to represent the Project in the real world. Its structure and that of its Board of Directors shall be defined by a dedicated charter. ![]() It is also able to make executive decisions in cases where any such are needed to guarantee the fulfillment of the Project's stated mission, as well as the Project's integrity. is a registered non-profit organization which exists to support the Battle for Wesnoth Project's operations by handling finances as well as holding funds, intellectual properties, and other assets for the Project. Rationale: The Battle for Wesnoth Project exists and this is its purpose.Īrticle 2. The Battle for Wesnoth Project is a game development organization that exists for the continued development, improvement, and maintenance of the The Battle for Wesnoth. Non-normative text is indented in quote blocks. This version of the Battle for Wesnoth Project Constitution was written by Iris Morelle (shadowm) and reviewed by Charles Dang (Vultraz), Soliton, and Pentarctagon.
0 Comments
Leave a Reply. |