These days when I collaborate with other developers, we do it all in a git repo that is simply hosted on a VM everyone has ssh access to. Project management is done in a plan/ directory which has task entries like 1000-add_logout_button.txt Where 1000 is the priority. There is also a directory plan/done/ where tasks go that have been completed. In the plan/done/ directory, the priority gets replaced by the completion…
I like the simplicity, but does everyone actually log in to the server and edit the files directly in the same repo, or is the repo exposed over SSH and everyone works in forks on their own machines? The first one doesn't really scale beyond a handful of people, since you risk losing work if the same file is being worked on by multiple people. Vim shouting at you that the file you're editing has changed on disk is no…
Since everybody pulls the changes of the others and sees if something collides with their own changes, its pretty much possible to do it manually. Thats how I started this approach.
It's really just a 0815 git based workflow. Just not for code but for a tasklist.
Meanwhile I wrote a bit of tooling around it. But using it is not at all a must.