When you found this page you probably looked at one of my projects. It’s nice to see that you are interested in contributing to it. There are multiple ways to make this happen. The preferred way is to use the SI-GitLab. If you just want to do a one time contribution and feel way to bothered to create and account on SI-Auth, then you can send me an email as described below.
Just in case you want to report a security issue, please use the email icon in the sidebar to generate an encrypted email and send it to me using your mail client. I’ll get back to you as soon as possible. It shouldn’t take more than 72 hours to get back to you. If it does, please try to reach out to me using another method like Mastodon or Matrix to figure out why I didn’t get your email.
There are no bug bounties available. Sorry, I’m not rich. I might start a security hall of fame when there is something to show in there. If you have deadlines or similar, please let me know and also try to include a detailed write-up about the issue. If it’s an issue in an upstream project, I might redirect you there, as it’s of course in my interest to get this stuff fixed, but I don’t want to become the disclosure manager of everyone.
Using the SI-GitLab to contribute (preferred)
There are a few steps needed to become a contributor:
- Get an account -> Go to https://auth.shivering-isles.com, select ‘Sign In’, then select ‘Register’, fill the form and wait for the confirmation email
- With your email address verified and TOTP set up, you are able to use the “Sign In” button on GitLab
When you just want to raise a bunch of issues and follow them, then you can just go ahead and start your requests.
If you want to contribute code, you have to request access to the project you want to contribute to. As I try to keep the resource usage at a minimum as well as legal risks, GitLab users are external users by default. Therefore they can’t have own repositories. When granting access, I’ll also give you a few free repositories to play with.
You can now push your changes and we can move forward in making better software for everyone!
Using email for one time contributions
If you just found this one thing that you want to correct and consider the steps above as too much hassle, how about sending me an email with a patch file?
You should create your commit in an own branch. Once done, use
git format-path <upstream branch>..HEAD to generate the set of patches that is required to recreate your branch. Once that’s done, use
git imap-send or your mail client to send them to the project email address.
The project’s email address is setup like this:
<group name>[.<optional subgroup name>].<project name>@contribute.shivering-isles.com So as example ->
Please keep in mind, that this will all land in my inboxes and therefore further restricts my time. Try to use the SI-GitLab method if possible. As this reduces my workload on those things a lot.
Sharing ideas or saying thank you
I really appreciate it when people tell me how they use stuff I built, because it’s awesome to hear that I inspired people. And it’s great to stay in contact with you. So as mentioned, joining one of the channels would be great and sometimes there is a little bit more exclusive content in for you as well.
When you would like to throw money at me, I have to disappoint you, I hate doing taxes and therefore try to avoid getting donations. But if you want to make sure I get something from you, just invite me for a coke1 or two, if we ever meet. I enjoy trying new sorts of coke as other people look for different kinds of coffee.
If this ever changes, you most likely will get it through the channels linked above. So feel free to join, it’s also your chance to figure out if I’m somewhere close to you at a certain point in time.
preferably a local one ↩