Hi Julian, Thank you for your in-depth analysis, it's very informative.
# Resolving/avoiding conflicts: If I understand correctly, in git-dit you allow a non linear history of edit. A maintainer then can (has ?) to decide how to resolve the conflict, that is, how to order the operations. I think it's a question of taste here. I personally very much prefer a tool with low friction, that does it's job without requiring any specific attention. I think the automatic merge where you get the last word, combined with the fact that the merge happen on a pull and not a push, should works reasonably well. A bug tracker is a communication tool, not a code versioning system where you need to control everything exactly. With communication tools, you can tolerate a small degree of "errors" as long as it's easily detected and corrected. Also as I said in my previous email, there is ways to improve on that if the need arise. # Remotes git-bug can push/pull to any remote. Most of the time, users will want to use a single remote, hence the default remote configuration, to remove some friction. In git-dit, you have a list of remotes with descending priority. Is that to have a fallback if the default remote fail ? I'm not sure which approach would be best (unique default remote, fallback, multiple remote) so I will wait to get feedback from users to decide. # Pull-/Merge-requests That's neat. Pull-request are way out of the scope of git-bug for now but I'll have a look if this time comes. # "Issue states" This is definitively a subject where git-bug need to improve to support other bug-trackers. I don't have a clear plan here yet though. Thank you for explaining how it works in git-dit. It's an approach worth looking at. Do you have a link for where this is worked on ? # E-Mail It's something I didn't think about until you mentioned it. In my mind it's something that could be left to the regular bug-trackers, either via a bidirectional sync bridge with git-bug or if they pick-up the git-but data model. It could also be a feature of the webUI if it grows into a full-blown hosting solution, but again, that's way out of the scope for now. Best regards, -- Michael _______________________________________________ dist-bugs mailing list [email protected] https://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
