Current state of this repository - do we need a community fork?
SlySven opened this issue · 1 comments
Given #306 (comment) is this repository archived or not (it doesn't seem to be read-only!)
As it is - that will not prevent motivated individuals (or groups thereof) from forking in order to fix outstanding issues! So I am hoping that it does not get locked down again. On the other hand those proposing Pull-Requests might wish to cooperate and create a community-maintained repository given that it looks like their PRs are not going to be merged into this one. For those of us who cannot use the shiny replacement (but non-open-source compatible) SDK this is probably the best we can hope for.
Of the 200-odd forks that have been made of these repository would it be possible for those (seems to be around 30-ish from the committers list: https://github.com/discord/discord-rpc/graphs/contributors ) who have done so to fix/improve the library to indicate who they are (but not those who have forked it just to make use of it in their own project) - as a start I guess the following three open PR authors fall in to the former catagory:
- Kein
- DjDeveloperr
- adill
I have my fork here: https://github.com/harmonytf/discord-rpc
Though it doesn't include everything that all the forks have, it has working support for opening guild and activity invite dialogs as I think the only existing fork so far