Following the recent board election we started the important work of defining project bylaws. We also started to review project policies, some of which are long-running and documented but need revising, while others are more informal and need to be written down. One of those policies is our definition of a LibreELEC Community Build and the responsibilities of Community Build creators.
Our requirements are simple and now apply retrospectively to all Community Releases. They can be read on the Wiki here:
Minimum requirements for a LibreELEC Community Build
Recognising what is/is-not a LibreELEC Community Build and defining common-sense rules allows the project team to focus on supporting community developers and the users they serve. We often provide dedicated sub-forums and webspace to help builders distribute and support their releases without incurring personal costs. In some cases we also hook their releases into core project assets such as the update mechanism and our add-on repository.
In the next week we will reach out to a small number of community developers identified as non-compliant. If they are willing to work with the LibreELEC project team and address discrepancies we will be happy to allow continued use of our infrastructure. If they are not, we will be encouraging them to provide their own.