They mention email and non-email work flows. Certainly you can have a HTML interface as well as others, if wanted, but any protocols and formats used ought to b

They mention email and non-email work flows. Certainly you can have a HTML interface as well as others, if wanted, but any protocols and formats used ought to be documented. I don't use git, although I am not complaining about whether or not other projects do. > You also need to have an internet connection at the moment that you try to use the web forum. If NNTP is supported, then you do not. You will need NNTP to send or receive messages, but you can manage, read, and write them locally without an internet connection. (The same is true for email, although email is better for private communications between one user and one other; NNTP is better for forums with many messages with many readers/writers.) (Also, you can have both NNTP and web forum interface for the same messages if wanted; I have NNTP server software, and a part of a web interface but currently only the NNTP is working. The web interface includes a link to the NNTP so that you can use that anyways even if someone links to the web page instead.) They actually mention NNTP in their comments, and I really suggest using it. If it is specifically a ticketing/bug-tracking system, Fossil has a ticketing system that can be used locally as well as remote. While the implementation currently uses the web interface for tickets (there is a command-line interface for the tickets but isn't very good) and doesn't just let you handle the artifacts directly enough, the Fossil web interface can be used without an internet connection, and the artifact format is simple enough that you could probably write your own program to construct and verify them, too (or use libfossil, I suppose).