On Fri, Sep 30, 2022 at 04:34:08PM +0000, Artem S. Tashkinov wrote: > On 9/30/22 16:19, Bird, Tim wrote: > > E-mails sent from a web interface could have as much structure as you'd like. > > So one avenue would be to set up a nice interface for bug reporting, that just > > delivered the form data in e-mail format to the proposed bug-receiving mail list. > > > > Also, if an e-mail receiver (something automated) gave a quick response on missing fields, I think > > you could quickly train users (even first-time bug submitters) to provide required > > data, even if they're sending from a free-form e-mail client. > > > > Just my 2 cents. > > > > -- Tim > > Debian uses an email based bug tracker and you know what? Most people > avoid it like a plague. It's a hell on earth to use. Ubunutu's Launchpad > which looks and feels like Bugzilla is a hundred times more popular. It would be pretty sad if the only options we could come up with for bug tracking would be either popular with reporters and ignored by maintainers, or the other way around. Ideally we wouldn't have to decide which of those two classes of users to prioritize, but I fear that, given resource starvation, we'll have to make a decision there that will be unpopular with one of the two sides. > Sometimes programmers have to realize that most people around are not as > smart as they are. I wouldn't equate familiarity with classes of tools (and related usage habbits) and intelligence. Some tools may be easier to learn and use, but it doesn't mean they're good for the problem at hand. I used to joke several years ago that the younger generation will force older maintainers to switch to doing code review on facebook (nowadays I would probably say tik-tok). And then https://github.blog/2021-05-13-video-uploads-available-github/ happened. And that https://www.videocode.review/ (meanwhile, git..b still don't support commenting on a commit message in a review). -- Regards, Laurent Pinchart
