Posts by 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

    Team voting has concluded and the following nominees are elected to the project board:

    • cvh is our forum admin and resident DVB/Tvheadend expert
    • davu is a forum super-moderator and enthusiastic bug hunter
    • lrusak has been the project technical lead over the last two years
    • milhouse is well known for his bleeding edge community test images
    • xe is our IRC channel admin and a FOSS advocate

    In statistics: 22/22 team members cast their vote. 1/5 of the board are Canadian, 2/5 are German, 2/5 are from the UK. 3/5 board members are also Team Kodi members. 4/5 board members come from the original group that forked from OpenELEC. 5/5 board members have contributed something to our GitHub repo. 3/5 board members (cvh, lrusak, milhouse) will serve a 24-month term while 2/5 board members (davu, xe) will serve a 12-month term.

    Thanks to all team members for voting (and agreeing to be team-members) and congratulations! to our new board members 🙂

    Source: Board Election 2018 (results) – LibreELEC

    LibreELEC (Krypton) 8.2.5 is now available with updates to Raspberry Pi firmware to address issues seen with the initial firmware release supporting the new 3B+ hardware (which also affected the Slice box). We also bump both nVidia drivers in the Generic x86_64 image, resolve an MCE remote problem, add support for the WeTek Pro remote control unit in WeTek images, the Allo DigiOne DAC in Raspberry Pi images, and updated u-boot in the Odroid C2 image now supports mild overclocking to boost performance.

    See detailed changes on GitHub.

    Enjoy 🙂

    have you visited the LibreELEC shop?

    Source: LibreELEC (Krypton) 8.2.5 MR – LibreELEC

    On Tuesday 10th we called time on the initial registration of LibreELEC team members and nominations for the board. In total there were 22 people who signed up and 7 who accepted nominations. Our independent helper has emailed Condorcet vote links so members can rank nominees in personal order of preference and cast their vote. We have allowed 10-days for voting, but if all votes have been cast sooner we will end the election and announce the results.

    The team has decided to elect a five-person board, and to stop us replacing the entire board at each election the three highest ranked board members will serve a 24-month term while the next two members will serve a 12-month term. This means that each year there will be an opportunity for board changes, but we also ensure continuity.

    The first priority for the board will be creating bylaws for the project and then running a membership vote to accept them. The second priority is to agree and assign roles and responsibilities to the board members and establish any other management structures the project deems to be necessary (technical steering committee, infrastructure admin team, etc.).

    Next update will be to announce the results!

    Source: Board Election 2018 (Part 2) – LibreELEC

    In the last 18-months we invited many developers to collaborate and work in our extended team, but not many non-developer helpers. Developers doing development is essential, but non-developer contributors have an equally important role because these are the volunteers who manage forums, respond on social media, and often volunteer to help with less exciting admin tasks.

    Over time our developer/helper imbalance has contributed to the project depending on a couple of long-term contributors and people have raised issues with the way things operate (claims of dictatorship, external influences, etc.) which has led to friction and even inspired a minor code fork. The dictator claim is part-true because the project runs as a meritocracy where those who step-up and take initiative are ultimately those who create outcomes and set project direction. Another factor is “spectator syndrome” which often occurs when a project grows rapidly but the number who take initiative grows at a slower pace. In the last year situations where many can see that a task needs doing but everyone waits for someone else to do it have become frustrating. Tasks become concentrated in a few regular (older) hands, and recent invitees who lack a long-term perspective on how the status-quo evolved perceive those hands to be dictators.

    Recent Slack debate concluded that we aren’t being true to our original vision for governance so things must change. To drive shared responsibility and checks/balances our first action is to finally form an elected board. For the next week the current ~95 people in our Slack team are invited to declare themselves as formal team members and propose nominations for an initial board to represent them and write initial bylaws. An impartial observer to the project is helping us to register members and then run a Condorcet vote on the list of accepted nominations.

    This is a long-overdue but exciting move. We will be publishing updates on the team-member and board nominations process as things unfold as it’s important we keep you all informed.

    Source: Board Election 2018 – LibreELEC

    Source: Sponsored Slaves Required! – LibreELEC