Don't Tasks and Issues overlap significantly? #GitViaNostr
The specs are nearly identical and working with both as a team smells like double work all over the place.
Why can't we just tag the repo in a Task and, boom, have an Issue that's in the list with all the other Tasks of a Team (Linear-style)?
Relevant NIPs:
https://github.com/danieldaquino/nostr-nips/blob/tasks-nip/XXA.md
Tasks is the most finite of git building blocks. Example tasks: “Clean up CI/CD”, “merge PR”. I think in Linear task most closely maps to “sub-issue”.
Issues are a step above that can be used to describe bug reports, user stories.
Milestones are collections of issues.
Yeah lol, not talking about Git tasks indeed :winkwithtongue:
Tasks (can) have sub-tasks.
So then I still see Issues as a type of Task.
And I don't want to embed an Issue into a Task (in my Community / Team group), when they' the same thing.
Would be curious in general how you would re-imagine the product management event stack. Without the silos that force imo more copy-pasting / embedding and levels then is needed.
Blank canvas in an interop world.
What do you minimally need?
