Thanks for your interest in contributing to tls-redirector!
This guide assumes you are somewhat familiar with Git and have contributed to open source software beforehand.
If you are struggling with anything -- Git, Go, C, Docker, or anything else -- please don't hesitate to send an email to the mailing list (public) or the maintainer (private).
- Source Code: https://git.sr.ht/~ancarda/tls-redirector/
- Issue Tracker: https://todo.sr.ht/~ancarda/tls-redirector/
- Mailing List: https://lists.sr.ht/~ancarda/tls-redirector/
- GitHub Mirror: https://github.com/ancarda/tls-redirector/
- Public Inbox: https://lists.sr.ht/~ancarda/public-inbox/
- Maintainer: Mark Dain <[email protected]> (ancarda)
- PGP Fingerprint: 9612 F6C7 92C9 FB40 2EA6 1AC1 A440 BD5C DE5C A1F7
- PGP URI: https://meta.sr.ht/~ancarda.pgp
Email is the primary way to send patches to this project. If you are new to
git send-email
, the website https://git-send-email.io/ has a good intro.
Once you have setup SMTP, you should run this command in the directory where
you checked out this project:
git config sendemail.to "~ancarda/[email protected]"
You don't need to subscribe to the mailing list to participate.
If you are not able or willing to use git send-email
, you can you can send
patches via GitHub's "Pull Request" feature. The mirror can be forked and is
monitored by the maintainer.
You will need a GitHub account and may need to run non-free JavaScript to send patches this way.
To discuss features or report bugs, send an email to the mailing list. The GitHub mirror cannot be used for issue tracking.
Please do not directly submit to the issue tracker.
Discussions that affect all ancarda projects can be sent to the Public Inbox.
And of course, any discussion that is better off-the-record - such as security reports - can be sent directly to the maintainer. Feel free to use PGP.