Update the Foundation's repo and shift devel there. #7752

Open
opened 2023-03-15 18:57:18 +01:00 by ParaplegicRacehorse · 0 comments
ParaplegicRacehorse commented 2023-03-15 18:57:18 +01:00 (Migrated from github.com)

Since the SEC decision will likely cause LBRY, Inc. to go out of business, it makes sense to move development to a place where it can be continued with few interruptions. I propose updating the LBRY Foundation's lbry-desktop repository to match this repo's state, marking this repository as a read-only public archive, and shifting new devel there.

While a purchase of digital assets by the Foundation is a possibility, the open-source nature of this software means that forks can become "official" -- accepted by preference of the community -- with or without permission of the original software author(s). Thus, shifting the development to a fork maintained by the Foundation makes a lot of sense even if other assets cannot be acquired.

In fact, I propose moving all actively developed LBRY, Inc. repositories to the Foundation. It can be done without purchase of digital assets by simply forking and shifting development repository targets.

Since the SEC decision will likely cause LBRY, Inc. to go out of business, it makes sense to move development to a place where it can be continued with few interruptions. I propose updating the LBRY Foundation's `lbry-desktop` repository to match this repo's state, marking this repository as a read-only public archive, and shifting new devel there. While a purchase of digital assets by the Foundation is a possibility, the open-source nature of this software means that forks can become "official" -- accepted by preference of the community -- with or without permission of the original software author(s). Thus, shifting the development to a fork maintained by the Foundation makes a lot of sense even if other assets cannot be acquired. In fact, I propose moving all actively developed LBRY, Inc. repositories to the Foundation. It can be done without purchase of digital assets by simply forking and shifting development repository targets.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#7752
No description provided.