> > I just spoke with some people of the httpd-docs project and found out > that they are either not subscribed to [email protected] or do > not have time to look through the mails. I fully understand this as > > 1. Most stuff is not about documentation. > 2. bugs@ is a high volume list. > > First question: Is this true for most httpd-docs people or did I > just speak to the wrong people :-)?
Having seen the responses so far, as well as hearing Sander's thoughts on what solutions are possible, here's a few remarks. I'm subscribed to the bugs list, but typically ignore it because I can't keep up, and most of it is not something that I can be of help with. Docs bugs are frequently submitted by people who have an immediate itch and want fast results. It's a bit different from code bugs, which require more diagnosis to submit a bug for. A docs bug is typically a matter of a few seconds to find and report. So if we don't see the report, and don't respond quickly, that person will almost certainly lose interest, and be unavailable/unwilling to comment on possible solutions. Rapid responses in docs bugs are important. Having a different list where I could see the docs bugs, and not all the other bugs, would be very useful for me. At the same time, the main bugs list needs to see the docs bugs, as they often are actually a code bug. And vice versa, too, I suppose. (This doesn't work like the docs say it should. Which one is right?) > [EMAIL PROTECTED] > > and changing the configuration of bugzilla in a way that bugs for the > component Documentation below Apache httpd-2 / Apache httpd 1.3 are sent > to this list? So, +1 Sander says, however, that there's not a way to send the same bug to two different lists, and so this would require those interested to subscribe to both lists, which is probably not ideal. It would be nice to have a way to send it both places. Joshua's suggestion of a web link to a saved search doesn't work, simply because I forget to go click the link. In fact, I have that very search bookmarked, and forget to go look for long periods of time, during which the submitted docs bugs get neglected, and the submitters move on to other concerns. One other suggestion - In Thunderbird there's a notion of a "saved search." Every mail client has this, but they call it different things. Do a search, save that search as a folder, which then gets updated dynamically. I have a "saved search" for stuff in the svn commit list that has 'docs' in the subject line. A similar thing could (I think) be set up for the bugs@ list so that docs bugs would be shown in that "virtual folder". I haven't tried this yet, so I don't know how easy it is, but I'm sure it's possible. Colm also tells us that the new version of Bugzilla has RSS support, at which point I'll just drop the mailing list entirely, and use RSS for the bits I'm interested in. Any notion on the timeline for this new version? --Rich
