T-Craft Platforms is a collaborative initiative primarily focused on building Minecraft plugins, mods, and the infrastructure required to run them on servers. The organization aims to keep projects open-source whenever possible.
- Be respectful, constructive, and professional.
- Assume good intent and communicate openly.
- Follow common open-source etiquette.
- Create repositories as
private/internalfirst if you are unsure. - If you want to mark a repository as internal only (only visible for members), you must:
- Mark the repository as
private - Add the
@Everyoneteam with at leastReadaccess
- Mark the repository as
- Only set a repository to public if you are sure it is intended for open-source.
- Never make a repository public if it:
- Uses proprietary software
- Depends on private or demo environments
- If a repository's purpose cannot be justified, it may be archived or removed at any time at the discretion of the organization administrators.
- Do not migrate repositories to or away from T-Craft Platforms without prior approval from the relevant code owners and organization administrators.
- Pushing directly to
mainis discouraged, especially on public repositories.- For public and internal repositories, a branch protection rule protecting at least the default branch is highly advised.
- For private repositories, branch protection is the responsibility of the repository maintainers, but is also highly advised.
- Use the GitHub Issues Workflow correctly:
- Create an issue
- Create a branch linked to that issue
- Open a pull request
- Merge into
mainafter review
- Use branch name prefixes whenever possible:
feature/bug/security/
- Avoid loose or unnamed branches.
- Use repository issues for detailed, specific feature requests or tasks.
- Always consider:
- Is this limited to one repository?
- Or does it affect multiple repositories?
- Use GitHub Projects (Kanban recommended) for planning and tracking.
Use Discussions for:
- Announcements
- Ideas and coarse feature requests
- Polls
- Questions & answers