This repository holds organization-wide defaults and community documentation for ByByte.DIY on GitHub. It defines how we collaborate, communicate, and present the project across all repositories in the ecosystem.
ByByte.DIY™ is an open robotics and STEM education ecosystem. We develop open-source robotics platforms, hands-on learning materials, and structured courses so that children, students, educators, makers, and technology enthusiasts can learn through building real projects.
Our work is guided by openness, accessibility, and learning by creating — from robotics and electronics to programming and engineering thinking. Anyone can build, adapt, teach with, or contribute to the ecosystem; we grow knowledge and skills together as a community.
Core platforms: ByByte Nano™, ByByte Mega™, ByByte NanoBoy™
For the full mission statement, see MISSION.md.
English documents are the authoritative versions. Ukrainian translations (.uk.md) are provided where available.
| Document | Description |
|---|---|
| MISSION.md | Why ByByte.DIY exists — open STEM education, DIY culture, and our vision for the next generation of creators. |
| PROJECT_PRINCIPLES.md | Core values: educational purpose, inclusivity, peaceful use of technology, and responsible collaboration. |
| CONTRIBUTING.md | How to contribute: areas of work, pull request expectations, quality standards, licensing, and community norms. |
| CODE_OF_CONDUCT.md | Expected behavior, educational environment, reporting, and maintainer responsibilities for a welcoming community. |
| BRAND_GUIDELINES.md | Correct use of names, logos, and visual identity in educational, community, and commercial contexts. |
| TRADEMARK.md | Trademark policy: allowed and prohibited uses, forks, logo rules, and how open licenses relate to branding. |
| LICENSE | Canonical licensing policy: which license applies to software, hardware, and documentation across the ecosystem. |
| Document | English source |
|---|---|
| MISSION.uk.md | MISSION.md |
| PROJECT_PRINCIPLES.uk.md | PROJECT_PRINCIPLES.md |
| CODE_OF_CONDUCT.uk.md | CODE_OF_CONDUCT.md |
| TRADEMARK.uk.md | TRADEMARK.md |
If translations differ from the English text, the English version prevails.
GitHub treats the organization .github repository specially:
- This README can appear on the organization’s GitHub profile when configured.
- Community health files in the root (for example
CONTRIBUTING.md,CODE_OF_CONDUCT.md) may serve as defaults for repositories that do not define their own. - Brand assets (such as
img/logo.png) are the canonical reference for logos used in docs and community materials.
Individual project repositories may add their own CONTRIBUTING.md, issue templates, or workflows; when in doubt, start here for org-wide policies.
Organization-wide licensing rules are in LICENSE (MIT for software, CERN-OHL-S v2 for hardware, CC BY-SA 4.0 for documentation). Individual repositories may also include their own LICENSE file.
Use of ByByte.DIY™ names and logos is governed by TRADEMARK.md and BRAND_GUIDELINES.md, independent of open-source licenses.
- Read MISSION.md and CONTRIBUTING.md.
- Follow CODE_OF_CONDUCT.md in all interactions.
- Respect BRAND_GUIDELINES.md and TRADEMARK.md when naming or branding work.
- Open issues and pull requests in the relevant project repository, or start a discussion for larger changes.
Questions about branding, partnerships, certification, or trademark use: contact the project maintainers (see BRAND_GUIDELINES.md).
ByByte.DIY™, ByByte Nano™, ByByte Mega™, ByByte NanoBoy™, and associated logos are trademarks of the ByByte.DIY project maintainers. See TRADEMARK.md for permitted use.