3 ms·
I am not sure a GraphViz digraph is the way to go. If you want to keep track of what is done and what is remaining eventually you will need to update that file
by partycoder 9y ago
I am not sure a GraphViz digraph is the way to go.
If you want to keep track of what is done and what is remaining eventually you will need to update that file.
This will quickly lead to version control conflicts.
Issue trackers I think are the way to go. You can integrate with one using their API.
- zwischenzug 9y agoI think version control conflicts are good in this case - they indicate the level to which there is conflict within the team around what the project consists of.
- partycoder 9y agoVersion control conflicts in this case don't necessarily map to disagreement. Imagine 2 team members that are in agreement add leaf 2 nodes. That would trigger a version control conflict. Now imagine that situation in a team of 5, or 10. It becomes hard to maintain.