- Choose a focused kebab-case name, description, topics, and link to https://raphael.app where relevant.
- Start from RaphaelAI-OpenLab/open-source-template, then replace all project-specific placeholders before publication.
- State project status and scope honestly. Avoid unsupported counts, performance claims, and promised integrations.
- Include a working example, setup instructions, relevant validation, and known limitations.
- Choose and document the license; preserve third-party notices. Review rights for prompts, screenshots, datasets, and references separately.
- Check that no secrets, internal endpoints, customer data, or unlicensed assets are present, including in Git history.
- Use
mainas the default branch. Use issues and pull requests for traceable collaboration; run only checks that actually apply. - Verify community files and issue forms appear. Enable private vulnerability reporting for public code repositories where available.
- For Node projects, pin the package manager and use pnpm. Do not add deployment workflows or paid services until the project needs them.
- Before release, follow the template's release checklist. Pin useful, ready repositories on the organization homepage.
Organization owners administer settings. Members are intended to have repository creation permission and Write base permission across organization repositories. This includes future private repositories, so only place material here that the whole member group is authorized to access. Repository-specific or organization-level controls may impose additional restrictions.
Invited accounts gain membership only after accepting their invitations. Check the People page for current status; this document is not evidence of live permissions.