zlacker

[return to "Why users cannot create Issues directly"]
1. eviks+zd[view] [source] 2026-01-02 03:39:59
>>xpe+(OP)
> This pattern makes it easier for maintainers or contributors to find issues to work on since every issue is ready to be worked on.

How is this not trivially solved via a "ready-to-be-worked-on" tag?

◧◩
2. voxl+Ej[view] [source] 2026-01-02 04:50:54
>>eviks+zd
How is it not trivially solved by a discussion section? Why is your solution better for someone else's work flow? Why do you feel like you get to impose your way of doing work on an open source project?
◧◩◪
3. eviks+ik[view] [source] 2026-01-02 05:00:13
>>voxl+Ej
Why do you feel like it's ok to make up nonsense about imposing? How can I impose anything on that project? Why break the expected/established workflow of users if the explanation doesn't work? Why are you asking 3 questions without answering 1?
◧◩◪◨
4. em-bee+0o[view] [source] 2026-01-02 05:44:12
>>eviks+ik
each project has its own workflow. no established workflow is broken. github traditionally imposed a different workflow because initially it didn't even have discussions.
[go to top]