Hey guys! I just got involved helping develop PyraOS. My main goal is to unify and stabilize development of the OS and create a build system which can reliably generate images cross platform. To start, I have created an official fork of the kernel which I will be maintaining. It lives inside the kernel group on Pyra's official git repo (link below). In the future, expect anything within this group to be officially maintained. Also expect this post to be updated as things progress. For now, I am looking for anyone with hardware to help me test. If you have Pyra development hardware and want to help me out, go ahead and pull a merge request (after reading the comments to see the status ) and load it up. Please help me! In terms of contributing, the repo rules are a little strict to keep things clean. No one is allowed to push directly to pyra or master (upstream). If you have a feature or fix you wish to push, create a feature or fix branch titled feature/<my-feature> or fix/<my-fix> respectively. Push your branch and create a merge request. Only a maintainer can actually merge in changes. At the moment, that will be me, aTc, or ED. Also remember, the repo is configured for fast-forward merges only, so make sure your merge request is rebased on top of the up-to-date pyra branch. Gitlab kernel group: https://dev.pyra-handheld.com/kernel UPDATE 8/4/19: I have built a docker based build system for building the Pyra kernel, U-Boot, and root filesystem. The build system will automatically download the most recent sources and tools. The best starting point if you are interested in starting to play with PyraOS is to check out the imagebuild group (link below) and read the pyra-docker repository’s README. I will be updating this in the coming weeks to establish a stable environment for building the OS as well as applications, Debian packages, and DBPs, so keep an eye out for updates to the system. I’ll post about significant updates here. For now, the kernel and bootloader the build system utilizes are my forks (as no patches are currently required). However, I will update this once all the details have been worked out (read the thread for more information on this situation). Please feel free to contribute to any of the repos I’ve linked to here. I’ll add more explicit instructions in the README soon, but just push a feature or fix branch (rebased onto the default branch) and create a merge request. The modifications will be tested and discussed before being merged so check in with the discussions on your merge request Gitlab imagebuild group: https://dev.pyra-handheld.com/imagebuild UPDATE 8/14/19: The build system now supports building image files which should be ready to flash directly onto SD cards. I am unable to test this, so there may be some issues. If you are able to test, please report any issues you run into in the issue tracker of the pyra-docker repository. There is a README in this repository with instructions on how to use the build system. Warning: In order to build image files, the system currently relies the use of loopback devices. In order to utilize these within the docker container, it is provided privileged access to the host machine so use this at your own risk. Just read the build script and make sure you’re ok with everything it is doing before using it I am working on a better way to handle this, but for now this is the way it works.