3 ms·
I did qualify "for me," indicating that system is not the way that I want to interact with a project The answer to your question is that searching years of ema
by mdaniel 5y ago
I did qualify "for me," indicating that system is not the way that I want to interact with a project
The answer to your question is that searching years of email threads is not the same UX as navigating to a dedicated page for managing the lifecycle of a (bug|feature) that tracks when I can expect a new, or working, version of -- in this case awscli-v2 -- to show up, or (if reasonable) that I can indicate to others that I'm willing to take responsibility for doing the work to package it, in order to avoid duplicated effort
Plus, again for me, I don't need more email traffic in my life
- alnja8a 5y agoI understand for you, and i understand the UX is different but i dont see how github issues are much better, compared to something like lists.sr.ht or lkml. I find github issues are just as disorganized in a lot of projects with lots of closed due to duplicate and etc. guix has a bug tracker backed on email that has the ux i think you might expect, i find at least, it worked (while i contributed to it) just as well as a non email workflow. Anyway I didnt really consider that this is a personal thing so fair enough to not want to deal with the different problems.