2 ms·
> The same way you "coordinate" work across your open source dependencies, you post an issue in their issue tracker Please let’s not confuse the record of a co
by asplake 4y ago
> The same way you "coordinate" work across your open source dependencies, you post an issue in their issue tracker
Please let’s not confuse the record of a conversation with the conversation itself. I’ve seen tracking tools used in this way and it easily turns dysfunctional.
- sirwhinesalot 4y agoGood point. Though I am suggesting a flip of the typical approach here. Rather than you first having a meeting, and then registering the task in the issue tracker, I'm suggesting the opposite. An issue is posted in the tracker, which may or may not trigger a meeting depending on severity or if more information is needed. The issue tracker is a starting point for discussion, rather than the end.