Contributor principles

Clear scope before shared work.

Volunteer collaboration should respect the contributor, the project, the families who will play, and the source custody that lets the work survive.

A conversation or application does not transfer ownership, grant repository access, create employment, or authorize work. An accepted contribution begins only after a written scope explains the task and its custody.

01

Relationship

Independent volunteer collaboration.

There is no guaranteed compensation, employment, or future role. Any paid engagement would require a separate written agreement.

02

Custody

Know where the work belongs before making it.

The written contribution scope identifies the repository, license or assignment terms, attribution, review path, and whether the result may be used in the game.

03

Safety

Family, privacy, and no-harm laws apply to every contribution.

No ads, surveillance, weapons, harm, exploitative monetization, secret-bearing submissions, or unreviewed personal data belong in the project.

04

Proof

Show the work and accept review.

Contributions should be reproducible, testable, accessible where applicable, and open to product, engineering, visual, security, and release critique.

Keep exploring

The next useful conversation starts with the work.