You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking for additional collaborators for this repo. π οΈ
I haven't been playing Valheim in quite a while and currently other repos consume most of my time. So I only get to check in here every couple of weeks. There are four other collaborators with commit access to this repo (@Addyvan, @armanatz, @InB4DevOps, @TheCatLady) but I'm guessing they're in the same boat.
Recently we had a pull request #666 (of all numbers π ) that was laying around for over a month, which is less than ideal.
If you're comfortable with the technologies this repo is made of (Docker π³, Bash π₯οΈ, Golang πΉ, Python π), are actively playing Valheim and would like to contribute, please let me know.
The Go logfilter and Python config generator rarely change (and are pretty trivial pieces of code tbh) so it's fine if you only have a superficial understanding of those.
A solid Docker and Bash foundation are a requirement as almost all changes will touch those. Also a good understanding of how the different moving parts of this container image work.
Personally I found the most challenging part was to develop for all kinds of container runtime environments and configurations. For instance, a change that works fine on your Linux 6.7 server running podman might not work on a Synology NAS running some highly backported 3.9 Kernel. A change that's fine for vanilla Valheim might break BepInEx installs and vice versa. If you check the commit history, I had to revert several PRs because they worked fine in one environment but broke another. Between GHCR and DockerHub this image has about 1.6M downloads per month or 55k per day, so there is a certain responsibility associated with the role. The ideal collaborator will have a good intuition about the effects a change will have in different environments. Not writing this to scare anyone off, just the reality of the role.
I need your help to keep this project strong and reliable π‘οΈ. If you're ready to dive into some real-world challenges and contribute to a project that impacts thousands of gamers daily, I'd love to have you on board. Just drop a comment here or reach out directly (my email is on my profile) if you're interested. Looking forward to hearing from you!
Best,
-- Lukas
The text was updated successfully, but these errors were encountered:
In case you need another helping hand, I would also offer my help. I am currently not playing valheim but that game has a special place in my heart - so does this repo - and I'm getting back to it occasionally, also I'm kinda active on github; atleast reading-wise.
Hi there all π,
I'm looking for additional collaborators for this repo. π οΈ
I haven't been playing Valheim in quite a while and currently other repos consume most of my time. So I only get to check in here every couple of weeks. There are four other collaborators with commit access to this repo (@Addyvan, @armanatz, @InB4DevOps, @TheCatLady) but I'm guessing they're in the same boat.
Recently we had a pull request #666 (of all numbers π ) that was laying around for over a month, which is less than ideal.
If you're comfortable with the technologies this repo is made of (Docker π³, Bash π₯οΈ, Golang πΉ, Python π), are actively playing Valheim and would like to contribute, please let me know.
The Go logfilter and Python config generator rarely change (and are pretty trivial pieces of code tbh) so it's fine if you only have a superficial understanding of those.
A solid Docker and Bash foundation are a requirement as almost all changes will touch those. Also a good understanding of how the different moving parts of this container image work.
Personally I found the most challenging part was to develop for all kinds of container runtime environments and configurations. For instance, a change that works fine on your Linux 6.7 server running podman might not work on a Synology NAS running some highly backported 3.9 Kernel. A change that's fine for vanilla Valheim might break BepInEx installs and vice versa. If you check the commit history, I had to revert several PRs because they worked fine in one environment but broke another. Between GHCR and DockerHub this image has about 1.6M downloads per month or 55k per day, so there is a certain responsibility associated with the role. The ideal collaborator will have a good intuition about the effects a change will have in different environments. Not writing this to scare anyone off, just the reality of the role.
I need your help to keep this project strong and reliable π‘οΈ. If you're ready to dive into some real-world challenges and contribute to a project that impacts thousands of gamers daily, I'd love to have you on board. Just drop a comment here or reach out directly (my email is on my profile) if you're interested. Looking forward to hearing from you!
Best,
-- Lukas
The text was updated successfully, but these errors were encountered: