How is LibreBooking supposed to be consumed by it's users?

[barakiva]

Even though LibreBooking is distributed as code rather than a binary, service or a docker image, I assume users shouldn't make any changes to the code as they will lock themselves out of future updates. That is, unless they intend to submit those changes as PRs upstream (which my org up until recently has not done).

Considering that, how is LibreBooking intended to be consumed?

1. Are users (who don't intend to open PRs) expected to NEVER make any changes to source code?
2. If the answer to 1 is 'yes', how would those users be able to upgrade to new versions without getting merge conflicts?
3. Are there limited cases (i.e. changing CSS or static files) where users can change the project? If so, do we expect them to be competent enough in git to .gitignore all those changes to keep up with new releases?