Skip to content

Conversation

@database64128
Copy link
Contributor

shadowsocks-go has been in active development since 2022. It is also the reference implementation of the 2022 protocol edition.

shadowsocks-go has been in active development since 2022. It is also the reference implementation of the 2022 protocol edition.
[ss-libev]: https://github.com/shadowsocks/shadowsocks-libev
[go-ss2]: https://github.com/shadowsocks/go-shadowsocks2
[ss-rust]: https://github.com/shadowsocks/shadowsocks-rust
[ss-go]: https://github.com/database64128/shadowsocks-go
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider forking to shadowsocks org first? You can follow go-ss2's way to maintain your repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given previously what happened to my membership in the organization, I'm not interested in having the project living in the organization. If this is a hard requirement for being listed in the page, please close the PR.

You can follow go-ss2's way to maintain your repo.

Because of how Go's import paths work, there's no good way of keeping multiple forks of a Go project alive, unless you enjoy resolving merge conflicts for every single commit. go-ss2's original repo outside the organization seems unmaintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants