Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ParaplegicRacehorse opened this issue Mar 15, 2023 · 0 comments
Open

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

ParaplegicRacehorse opened this issue Mar 15, 2023 · 0 comments
Labels
type: new feature New functionality that does not exist yet

Comments

@ParaplegicRacehorse
Copy link

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.

@ParaplegicRacehorse ParaplegicRacehorse added the type: new feature New functionality that does not exist yet label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: new feature New functionality that does not exist yet
Projects
None yet
Development

No branches or pull requests

1 participant