"Why do I have to get an account to report bugs?" is a FAQ I get asked. The Bugzilla Helper used to explain the need for an account; now it's been replaced by a CGI which is only accessible to those with accounts, so I anticipate getting asked it a lot more. Now we have the page.cgi template display system, we should use it to display a page I've written explaining all the good reasons why getting an account on Bugzilla is compulsory. This would then be linked from the login page by customising the b.m.o template. Myk: if you could confirm this is a reasonable idea, I'll attach the template for review. Gerv

Don't do this until page.cgi has been fixed up. :-) Gerv

Couldn't the login page display this information when the user is using the "guided" format?

It could do; but I don't think there's a 100% correspondence between people who might ask this question, and people using format=guided. A link is the usual way of providing optional further information, should people need it. Gerv

OK, the CVS version of page.cgi is now ready for this to happen, if we want it to. Myk: are you happy with a patch which adds a link "Why do I need to get an account?" to the login template (unconditionally), and drops the explanation into the pages directory? I don't know if you could just copy the new page.cgi in, though - the error stuff, for example, might not work on b.m.o's version. What are your current plans about upgrade timings, if any? Gerv

>Myk: are you happy with a patch which adds a link "Why do I need to get an >account?" to the login template (unconditionally), and drops the explanation >into the pages directory? Seems reasonable to me. >What are your current plans about upgrade timings, if any? I want to get the request tracker in soon and then schedule an upgrade to synchronize up with a Bugzilla development release.

No-one's moaned about this in ages - probably scared off by http://www.gerv.net/hacking/before-you-mail-gerv.html . So let's not bother doing this. Gerv