For WeKan Open Source kanban
https://wekan.github.io , very lightweight process. I release new versions very often
https://github.com/wekan/wekan/blob/master/CHANGELOG.md .
WeKan has MIT license, used in most countries of the world https://snapcraft.io/wekan . Everything is Open Source, all updates are free, no registration required. WeKan is translated to about 70 languages https://transifex.com/wekan/wekan so it's about 3x more translations than Trello or Jira.
Someone sends PR, I check it, merge if it works. I'll create new release for all platforms. For Snap, it updates all servers automatically worldwide. For other platforms, users update when they like.
If there are any problems, like something does not work, someone adds new issue to https://github.com/wekan/wekan/issues . It is fixed by me or some other contributor, and I make new release, usually same or following day problem has been reported.
WeKan users usually keep daily backups, and restore if something gets messed up.
About who is held accountable:
- If I broke something, I try to fix it.
- If some other contributor sent PR that broke something, I usually revert that change, release new version of WeKan, and that other contributor will send fixed PR later, that is then added to WeKan.
- If some customer has problems, customer contacts Commercial Support https://wekan.team/commercial-support/ , I fix it and document steps to wiki like for example https://github.com/wekan/wekan/wiki/Repair-MongoDB , and for anyone else asking about same thing I send link to that wiki page.
- If someone has installed WeKan to their own server, has not made backups, and has not paid anything for support, that someone is responsible for not making backups.