open source developers do not want tasks
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
Discussion
Fine if we call 'em "issues" then?
Same for me.