Hardfork feedback

[prplwtf]

Hi!

We're considering hardforking Pterodactyl to make catching up with updates easier. Please feel free to chip in with your thoughts in this discussion post!

[ohemilyy]

This is most certainly a interesting idea. Hard forking could def make sense if the goal is to reduce friction around updates and allow faster iteration without being blocked by upsteram deicisons. but the long term maintenance burden is smthn to srsly account for i feel like esp keeping security patches and wat not aligned where it matters

Also curious whether a lighter approach (patch set / downstream fork with regular rebases) was considered, and what specific pain points in the current update process you’re aiming to solve

[prplwtf]

Good points, yeah.

I'm honestly personally more for a lighter approach than a complete hardfork. What is clear to me is that I can no longer maintain the framework all on my own, so I'm getting another person to join in.

[26bz]

Good points, yeah.

I'm honestly personally more for a lighter approach than a complete hardfork. What is clear to me is that I can no longer maintain the framework all on my own, so I'm getting another person to join in.

Instead of hardforking.. why not try to work with the pterodactyl team to see if you can lead/manage the plugin aspect of pterodactyls "new vision" given that you ran BP for 3+ years now.