Do not exist as a fork

[Qing0731]

It is suggested to separate the repository. That way, it will be easier for everyone to search for it. Do not exist as a fork. Anyway, no code will be made public upstream

[JingMatrix]

Somehow, being a fork, serves as a good practice to respect the previous contributions made by the LSPosed team.

But surely, I would like to listen to the discussions in this commuity.

[Qing0731]

I don't think it's necessary to limit the distribution of the fork version to respect the previous contributors. Keeping their names in the author section and preserving the commits they contributed before is already sufficient as a sign of respect. Moreover, even if it is separated into a separate repository in the future, it can be stated in the Readme that this is a fork.

[Qing0731]

https://github.com/PerformanC/ReZygisk

https://github.com/qwq233/TrickyStore

For similar open-source forks, they all set up their own independent repositories for distribution. We should do the same.

[JingMatrix]

By the way, I cannot leave the fork network, as said by GitHub in the repo settings:

Can't leave the fork network because this fork has child forks.

[Qing0731]

PerformanC/ReZygisk#64

Then I think you can ask the author of Rezygisk for advice. He separated his repository 10 months ago, but all the forks, issues and pull requests of Rezygisk from 10 months ago were retained.

[Qing0731]

https://github.com/testrvx/ReZygisk

For instance, this fork was created when re was still a fork of zygisknext. Even after rezygisk became independent, it was still retained.

[Keeperorowner]

You respect those so-called official developers of lsposed, but they don't respect you at all🤨🤨