Posts by LibreELEC

    Source: LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support – LibreELEC

    Source: LibreELEC (Leia) 9.0.2 MR – LibreELEC

    Source: LibreELEC (Leia) 9.0.1 MR – LibreELEC

    Source: LibreELEC (Leia) 9.0.0 RELEASE – LibreELEC

    Source: LibreELEC (Leia) v8.95.3 BETA – LibreELEC

    Source: LibreELEC (Leia) v8.95.2 BETA – LibreELEC

    Source: LibreELEC (Leia) v8.95.1 BETA – LibreELEC

    Source: LibreELEC (Leia) v8.90.009 ALPHA – LibreELEC

    Source: LibreELEC (Leia) v8.90.008 ALPHA – LibreELEC

    Source: LibreELEC (Leia) v8.90.007 ALPHA – LibreELEC

    Source: LibreELEC (Leia) v8.90.006 ALPHA – LibreELEC

    Source: LibreELEC (Leia) v8.90.005 ALPHA – LibreELEC

    Source: Development Update – LibreELEC

    Source: LibreELEC (Leia) v8.90.004 ALPHA – LibreELEC

    Source: LibreELEC (Leia) v8.90.003 ALPHA – LibreELEC

    This forum area is for users of LibreELEC community software releases. If you have chosen to run CoreELEC releases on your device please report your problems to their support forum: CoreELEC Forums where people familiar with their codebase hang out. Posts on CoreELEC will be closed and moved to an "unsupported" forum to ensure the focus of support here remains on LibreELEC users seeking help with LibreELEC software.

    This morning LibreELEC board member @xe received written notices from GDPR-2 and GDPR-1 demanding their GDPR Article-17 right to have all personal information held by the project deleted from our systems. They have further requested we remove all of their forum posts and purge any data stored on team webspace. To prevent further creation and propagation of their data while we clarify our GDPR obligations and investigate what technical steps may be required, we have suspended their accounts.

    It's a shame to see this level of deliberately awkward activity, but we aren't going to fight their decision. Other forks in our ecosystem (Lakka, OpenPHT, PlexEmbedded, etc.) exist happily as derivatives of LibreELEC and their team members regularly and proactively contribute to our codebase. From the outset CoreELEC proclaimed total independence and leading team members have repeatedly stated they will not contribute back to LibreELEC. We don't really care that CoreELEC exists and we've been ignoring derogatory statements for the sake of peace, but continuing to host their drama and noise in our forum has zero upside for LibreELEC if they refuse to participate in our project. It is unclear whether other CoreELEC contributors with presence in our forum will request the same trip to /dev/null or would prefer to retain their status and become supportive and helpful participants to our project.

    The Board

    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.

    The Board

    Source: Community Builds – LibreELEC