プロジェクト憲章/English

## Project Charter

### Foreword

The Project Charter was made with a view to list and clearly set his mod’s various rules, making them known to all the dev team and thus facilitating the development of The Sun Shining on the World. To participate in the development, you have to take a look at this page and get a rough idea of what this mod is about.

There are two different subjects to this charter, pertaining to effort and performance respectively, which are also summarized in the Rules page. In the unlikely event of contradicting contents, the ones in the Rules page will take precedence.

### What is The Sun Shining on the World?

The Sun Shining on the World (SSW for short) is a large-scale, alt-history mod for Hearts of Iron IV. The mod starts in 1950 during a timeline where the Axis Powers – Japan, Germany, and Italy – won World War II. SSW is different from other post-Axis victory alt-history mods, of which there are many, like “Thousand Week Reich”. That is why we strive to create a mod which gives players a unique game experience.

### List of Resources

For this project there are various materials for the mod and its development progress. All of these are maintained and updated by one of the project members. Also, the project managers have to make the appropriate arrangements to allow the other members to access them. See the detailed list below.

### Releases Method

For official, or beta, releases, one of the project managers will upload the master branch of the Github repository and its contents from the to the Steam Workshop page. The same applies to the English translation. The release dates are decided via vote during the regular meetings. Although unofficial, the dates proposed by the Administrators are usually historic occurrence-related.

### Limits of this Project

The project is made up of a non-profit team of volunteers, meaning some limits apply:

·       Task progress depends largely on the skills and free time of the person assigned to it, so it may be subject to pauses and delays. Therefore, release plans are also subject to delays.

·       There is no budget. The cost of eventual paid tools needed for development are each member’s responsibility.

### Scheduling and Management

Available tasks depend on the release plans. So, a backlog listing each one in order of relevance for the future release is needed. This is usually found on the Trello Project Board. The release plan is set via vote during a regular meeting, and should always be written down. They can be found as meeting minutes on the dev Discord server. A backlog has to be included in all proposed release plan.

### HR and Skills

Skilled Human Resources are needed to progress this project, and must be able to either:

·       consider game design, plan regional and nation-specific scenarios, insert political parties, ministers, companies, national foci and decisions (collectively known as “content”), possessing the necessary knowledge to implement them;

·       process in-game images like portraits and flags, possessing the necessary knowledge and software for this purpose;

·       code in content and input game design-compliant key logic;

·       translate Japanese into English at an academic level for translation and intra-server communication.

The project managers are responsible to procure the necessary human resources. At the time of writing, the used method to contact these is via DM on the Discord server or in the modding community.

Main Risks and Countermeasures
 Disappearance of task-assigned HRs

### Organization and Roles

Below is the organization chart for the project’s implementation. Positions and/or teams not listed here don’t exist and have no authority. If changes in the organization are made, revising this page as soon as possible is recommended. In this chart, the appearing usernames are the “managers”.

* Supreme Commander: 黴饅頭 (pron. Kabimanju)
* Sub-commander: hisamatya
	+ Coding Leader: ばいおず (pron. VaioZ5)
	+ Coding Sub-leader: chiyo(pron. chiyo)
	+ Plenipotentiary of Mapping, Flag and Country Adding (PMFC): Blitz Reisdusche
	+ Graphics Leader: hisamatya
	+ Graphics Sub-leader: ばいおず (pron. VaioZ5)
	+ Translation Leader: H\_Jonathan
	+ Translation Sub-leader: akunososhiki
	+ Scenario Leader: 見習いイェーガー (pron. Jeager\_Lehrling)
	+ Scenario Sub-leader: MEIAS.RO
	+ Tech Leader: ぷりっつ (pron. Pretz\_3280)
	+ Tech Sub-leader: ぷりっつ (pron. Pretz\_3280)
	+ Writer Leader: 島風(人間のような何か) (pron. Shimakaze)
	+ PR Leader: ばいおず(pron. VaioZ5)

Roles are set for each title. If a person has multiple titles, they will be in charge of all the respective roles.

#### About the Managers

The term includes the Supreme Commander, Sub-commander, Leader, Sub-leader, Flag and Map Authority, GUI Manager and Scenario Advisor. An SSW manager has the following authority and obligations:

·       Work can be delegated to subordinates;

·       Efforts must be made to adjust one’s workload through delegating.

#### Supreme Commander

·       Unless otherwise stated in this document, they are responsible for assigning all project-related tasks, leading the project and proactively propose a general direction the MOD should head towards. When assigning lower positions (Sub-commander, Leader, Sub-leader) after a Congress vote, they must provide guidance by explaining the position’s details. They are responsible for the production, maintenance and management of all necessary deliverables for the progression of the project.

#### Sub-commander

·       Has the same authority of the Supreme Commander when said person is absent or busy.

#### Coding Team

Members of the Coding Team have the following, position-related authority and obligations.

##### Coding Leader

·       Managing coding progress;

·       Induction and dismissal authority over team members;

##### Coding Sub-leader

·       Assisting the Coding Leader;

·       Has the same authority of the Coding Leader when said person is absent or busy.

##### Plenipotentiary of Mapping, Flag and Country Adding (PMFC)

·       Adding nation flags and creating maps;

·       Managing the creation of the above according to each country’s devs requests;

·       Can share requested work created by members under his jurisdiction;

·       Has to know who has done what change to nation flags and maps;

·       Can freely modify nations with no assigned devs (scenario included).

##### GUI Manager

§  Creating and changing GUI for multiple nations;

§  Free reign over GUI changes, but has to comply with change/deletion requests by devs assigned to the related nation;

§  Has to know who is in charge of each GUI.

##### Nation Head Devs

·       Editing data of the assigned county;

·       Comply with the scenario set by the Scenario Team;

·       Free reign over editing the nation if there are no Scenario Team devs assigned to it.

When editing is done by someone not listed above, the direction set by those in charge must be respected as much as possible. Still, it’s recommended to contact this person/these persons before starting the editing work.

#### Scenario Team

Members of the Scenario Team have the following, position-related authority and obligations.

##### Scenario Leader

·       Instructing new team members;

·       Checking and reporting on tasks and their progress;

·       Drafting lore and setting-compliant National Foci;

·       Fandomwiki;

·       Dismissing members with problematic behavior and/or meet dismissal conditions.

##### Scenario Sub-leader

·       Assisting the Scenario Leader;

·       Has the same authority of the Scenario Leader when said person is absent or busy.

##### Scenario Advisor (none currently)

·       NOT in charge of task progress;

·       Providing advice to devs in charge of each region;

·       Checking scenario consistency;

·       Checking game balance.

#### Tech Team

Members of the Tech Team have the following, position-related authority and obligations.

##### Tech Leader

·       Instructing new team members;

·       Has final say inside the Tech Team and its overall management, excluding in case of emergency;

·       Keeping track of each team member’s progress and reporting it during meetings.

#### Writer Team

Members of the Writer Team have the following, position-related authority and obligations.

#### Writer Leader

·       Checking team progress and managing team members;

·       Dividing tasks that prove too large and assigning tasks to team members when progress slows down.

#### PR Team

Members of the PR Team have the following, position-related authority and obligations.

##### PR Leader

·       Coordinating the team, setting PR policy and recruiting new human resources, giving tasks to PR team members.

##### PR Staff

·       Posting on Twitter and Discord according to set policy, contacting new HR and communicating with them until their induction into the related team.

·       Answering to SSW-related questions and suggestions.

#### Graphics Team

Members of the Graphics Team have the following, position-related authority and obligations.

##### Graphics Team Members

·       Reporting on task progress to team manager within a week from assignment;

·       Has to find suitable image if no image or processing is specified during dev request.