How to join

guide for the community on how to join flipper one development this page explains the overall structure of the flipper one project, the sub projects it consists of, and how you can contribute to its development flipper one is currently in active development as a community driven project, we’ve made the entire development process open — so you can see how things are built and even take part in shaping flipper one’s future sub projects structure of flipper one flipper one is a large and complex project, divided into several sub projects each sub project is managed by a dedicated flipper team, with its own structure, rules, and workflows this developer portal acts as a wiki and the main entry point into all sub projects, hosting their documentation and contribution guides ‎ currently, we have the following sub projects hardware docid\ nmkfutofpywq8fp40mnmx electrical hardware development this is where the printed circuit boards (pcbs), antennas, and everything related to the electrical connections of chips, connectors, and processors are designed the hardware team works closely with the mechanics team to ensure the electronics are compatible with the enclosure learn more → docid\ nmkfutofpywq8fp40mnmx mechanics docid\ y89apq jum63hgqwzaq4v mechanical and industrial design this is where the enclosure, buttons, plastic and metal parts, and mounting components are designed everything the user physically interacts with many mechanical tasks are tightly coupled with the hardware team learn more → docid\ y89apq jum63hgqwzaq4v linux (cpu software) docid\ bdmplcyr sy0560cbhil linux kernel, modules, drivers, userspace, bootloader, rockchip tools, etc this is the largest and most complex sub project, spanning many repositories it contains the core software that users will interact with directly learn more → docid\ bdmplcyr sy0560cbhil mcu firmware docid\ ttkaocxw0ukc5qwxvbjyw firmware for the rp2350 microcontroller (mcu), which controls the display, power subsystem, and cpu boot process, and handles button and touchpad events learn more → docid\ ttkaocxw0ukc5qwxvbjyw user interface docid\ llpzmovg4vdrsxdpqh6qq ui/ux development this is where the user interface, visual communication of the device, all graphics, and visual design are developed learn more → docid\ llpzmovg4vdrsxdpqh6qq docs docid 0qacsa2ejito2hwqfzgjh developer portal wiki, technical docs, guides, and datasheets all documentation — including this wiki — is developed here it covers both the flipper one product documentation and descriptions of development processes and contribution guides learn more → docid 0qacsa2ejito2hwqfzgjh testing docid\ rvvadwks7cxz 5srk9zm0 tools for testing device subsystems and hardware validation includes various scripts and programs for testing power, networking, cpu, audio, graphics, etc also includes interface prototypes, demos, and sample audio and video files learn more → docid\ rvvadwks7cxz 5srk9zm0 inside a sub project a sub project within the flipper one project is a collection of entities used by the development team each sub project includes at least three types of entities 📚 documentation — explains the sub project structure, provides an overview of assets and platforms, and contribution guidelines ✅ task tracker — used to track and discuss tasks, including those where the community can help 📁 assets & platforms — includes source code, files, firmware builds, 3d models, ui mockups, images, and apis available for community review and contribution 📚 documentation each sub project is different, so it has its own documentation explaining how it is organized and how it works you can access this documentation through the flipper one developer portal (this wiki) or in the readme file of the sub project’s github repository documentation usually includes an overview of the sub project structure task tracker rules contribution guidelines for those who want to explore further, some sub projects provide more in depth materials, such as datasheets, test results, logs, and design guides you can contribute to the documentation this wiki is a sub project of its own, and anyone can contribute by editing its source files on github https //github com/flipperdevices/flipperone docs learn more in the docs sub project docid 0qacsa2ejito2hwqfzgjh ✅ task tracker tasks for each sub project are managed in a task tracker — a kanban board on github each task on the board is a github issue from the sub project repository you can view all task trackers on github https //github com/orgs/flipperdevices/projects mcu firmware task tracker ‎ what’s the difference between github issues and task tracker issues? there’s no difference the task tracker simply organizes the existing github issues into a kanban board it also allows issues from different repositories to be grouped together in one place and managed as a single large task with sub tasks for example, here is a list of github issues https //github com/flipperdevices/flipperone mcu firmware/issues from the mcu firmware sub project and how they are organized on the kanban board https //github com/orgs/flipperdevices/projects/8 ‎ open tasks some of our tasks are open this means the community can interact with them just as they would with any issue in a classic github repository — leaving comments, attaching files, and so on each task includes a short title and a detailed description, often with links and screenshots to help you understand it example of an open task in mcu firmware sub project tasks can be marked with different labels help wanted — tasks where we actively invite the community to participate and contribute to the solution example operating modes discussion https //github com/flipperdevices/flipperone ui/issues/1 locked — tasks that are closed to the community this means we are not ready to discuss the task or accept feedback you can still see flipper team’s internal discussions ⚠️ contributions only — no flooding to keep collaboration productive, please keep comments on topic open tasks are for contribution related discussion only if you have an idea or concern, first turn it into a concrete contribution and share it as a comment on a task for general questions or discussions, you’re always welcome to join the conversation on social media https //x com/flipper rnd or discord https //discord com/invite/flipper ! bad vs good comments ❌ — i like the green button instead of the orange one 👍 — i think the green button works better here's an example i made mypicture jpg 📁 assets & platforms sub projects may include various assets and platforms for the community to explore depending on the sub project, these can include source code repositories, design files, 3d models, schematics, ui mockups, and more you can view, download, and edit the assets, as well as share your feedback with us however, each of the flipper teams defines its own contribution steps — make sure to review them before contributing you can find contribution guides on the sub project page how to start feel free to jump in — you can contribute by joining task discussions, sharing ideas, asking questions, or suggesting improvements if you have feedback or notice something that could be better, your input is always welcome step 1 read the sub project docs find a sub project that interests you explore its documentation in this developer portal to understand how it works, how it’s structured, and how you can contribute step 2 check the task tracker go to the task tracker of the sub project you’re interested in to explore current tasks open tasks where your help is welcome are labeled help wanted read through a task and follow the contribution guidelines when submitting your input open tasks you can also visit the 🚧 open tasks docid 1dnw86l7gp8fmwqhjfvp3 to find tasks that need community help or feedback step 3 join discussions in our socials follow us on x and join our discord server to hang out, ask questions, and connect with other contributors x com/flipper rnd https //x com/flipper rnd follow updates and project announcements on x com flipper devices discord https //discord com/invite/flipper chat with the community and flipper team on our discord server step 4 subscribe to our weekly digest each week, we'll share a quick update on how things are coming along and flag any areas where extra help would be welcome no pressure to jump in right away — you might just spot something in a future update that catches your eye! ⚠️ nerds warning this is a developer focused, highly technical newsletter