Replace the current Article 2:
Wesnoth, Inc. 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. 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. Its structure and that of its Board of Directors shall be defined by a dedicated charter.
Rationale: Wesnoth, Inc. exists in order to represent the Project in the real world. Its existence is an absolute legal necessity and it cannot be disbanded. Likewise, the Project cannot be absorbed into Wesnoth, Inc. without making contributors perceive themselves as employees of the company, with all the legal consequences this carries.
With:
The Project's funds, intellectual properties, and other assets will be held by Software in the Public Interest, Inc. (SPI). Interaction with SPI on the project's behalf will be done by the Board of Directors.
Rationale: The costs of having taxes done by the current (as of this writing) legal entity holding the Project's funds and other assets (Wesnoth, Inc) is the single largest cost for the Project by a large margin. Joining SPI removes this cost entirely, with SPI instead taking 5% of donations made to Wesnoth. Additionally, SPI is a 501(c)(3) organization, which provides guarantees to those donating that their money will be used for a proper purpose.
---
Add a new Section V defining the Board (since we were actually supposed to create our own Charter defining our roles and responsibilities but never did):
## V. On the Board of Director's structure
**Article 21.** The Board of Directors will consist of three members.
> **Rationale:** An odd number of people makes it much more likely that a majority can make a decision when needed rather than becoming deadlocked indefinitely.
**Article 22.** There will be elections for the entire Board of Directors every other development cycle. This election will take place immediately after the election for Project Manager for development cycles where both elections take place. If a member of the Board resigns, then an election for the open position on the Board will be held within two weeks of their resignation. The people who are able to vote in the Board elections are the same as the people who are able to vote in the Project Manager elections. Anyone can be nominated to be a member of the Board by someone who is eligible to vote in the Board elections.
> **Rationale:** There needs to be a structured way to change who is on the Board of Directors. Development experience is also not necessary to handle the responsibilities of being a member of the Board.
**Article 23.** Interacting with SPI on behalf of the Project will be done by the Board of Directors, which will designate one member of the Board to be the primary liason to SPI. The remaining members of the Board will be secondary liasons to SPI in case the primary liason is unable to fulfill their role. If that occurs, the Board will decide which of the secondary liasons will become the new primary liason. Whoever becomes the new primary liason will remain so until the Board decides otherwise.
> **Rationale:** SPI requires we provide someone they can contact if needed, and the Project requires someone whose reponsibility it is to initiate contact if needed for any reason.
---
Additionally, remove Transitory Provisions I and II since the things they are for have already happened, so these two provisions are no longer relevant.