Community and Governance - endlessm/threadbare GitHub Wiki

🌐 Core Thread 5 - Community & Governance

Threadbare is an open-source project built by the Endless Access team and a growing community of contributors from around the world - including learners, educators, artists, musicians, developers, and game designers.

This Core Thread covers how the Threadbare community is organised, how we work together, and the rules and processes that keep contributions fair, legal, and high quality.

About Endless Access

Threadbare is developed by Endless Access, a company dedicated to building accessible learning experiences through game development. The Threadbare core team at Endless Access determines the overall game design and direction, ensuring the game serves both players and learners.

Anyone can join the community to find a place to help out. See the Threadbare repository for current issues and discussions.

The Community

How to Get Involved

Channel Purpose
GitHub Issues Browse tasks, report bugs, suggest features
GitHub Discussions Ask questions, share ideas, discuss the project
Discord Real-time discussion with the team
Pull Requests Contribute code, assets, or StoryQuests

New contributors - browse good first issues to find something to tackle.

Language

Threadbare's code, comments, and development discussion are written in English. If English is not your first language, don't worry - it's not the first language for about half of the core team at Endless Access, and contributions in other languages are welcome for StoryQuest content.

Code of Conduct

All contributors and community members are expected to follow the Endless Access Community Code of Conduct.

➡️ Code of Conduct

In brief: all dialogue in the game and all community interaction should be respectful, inclusive, and free from harassment, discrimination, and harmful content. Jokes and humour are encouraged but must not be insulting to particular groups of people.

Licensing

All contributions to Threadbare must be under open-source licenses that allow the game to be distributed freely on the web, PC, mobile, and potentially consoles.

➡️ Licensing - Full guide to asset and code licensing, acceptable licenses, AI-generated assets, and how to annotate files

In brief:

  • Original code → MPL 2.0
  • Original assets (art, audio) → CC-BY-SA 4.0
  • Third-party assets must be under a compatible license - check before you use them
  • Assets may not knowingly infringe somebody else's intellectual property

Content Guidelines

Threadbare is a game for people aged 13 and older, designed for use in homes, classrooms, and beyond.

➡️ Content Guidelines - Full guide to themes, violence, language, and appropriate content

Contributing

➡️ Contributing - The full contribution guide covering coding style, language conventions, Godot conventions, PR format, and co-authorship

The Review Process

Reviewing General Contributions

Anyone can review pull requests, not just maintainers. Community review helps contributors improve their work and helps maintainers focus their attention where it's most needed.

➡️ Reviewing Contributions - Playtesting checklist, style/legal/attribution review, fixing issues on behalf of submitters, and the squash-merge strategy

Reviewing StoryQuest Submissions

StoryQuest PRs can be large and complex. This guide covers the technical process of reviewing them locally.

➡️ Reviewing a StoryQuest submission - Git commands for checking file scope, detecting orphan resources, finding large files, and crediting multiple authors

For Maintainers

Merge Strategy

All pull requests are merged using Squash and merge. The PR title and description become the commit message. Ensure the title and description match the style guide and that all contributors are identified before merging.

Crediting Contributors

  • All contributors must be credited, either as commit authors or with Co-authored-by: tags
  • Use gh api to generate no-reply email addresses for GitHub users without public emails (see Reviewing a StoryQuest submission)

For Learning Programme Coordinators

  • Ensure learners understand their contributions will be public and attributed to their GitHub profile before they begin
  • Guide learners through the PR submission process at each milestone
  • Use Reviewing a StoryQuest submission to check PRs before escalating to maintainers
  • See Making a StoryQuest for the full learner journey

Releasing, updating addons, etc

Contributed Work

A running record of artwork, sound, and game design contributed to Threadbare by the community.

➡️ Contributed artwork - Enemy concepts, UI assets, sound effects, music, level designs, and more

← [Building the Game]] ](/endlessm/threadbare/wiki/Back-to:-[[Home) →