Hi, http://boost.org/more/bugs.htm
Submit a bug report to either boost-users list, boost mailing list, or our bug tracking facility;
IIRC Trac accounts are only for developers. Maybe it's a good idea to include a Register link anyway and explain this?
submitting it to either of the mailing lists is a preferred way - because many of the Boost developers read the lists on a daily basis, this way you are likely to get a quicker response, and the discussions that often arise there from (possible) bug reports are quite interesting and educational as well;
Why aren't reports from Trac forwarded to the mailing lists then? Greetings, Olaf
on Sat Dec 15 2007, "Olaf van der Spek" <olafvdspek-AT-gmail.com> wrote:
Hi,
http://boost.org/more/bugs.htm
Submit a bug report to either boost-users list, boost mailing list, or our bug tracking facility;
IIRC Trac accounts are only for developers. Maybe it's a good idea to include a Register link anyway and explain this?
IS something missing from the new page content? http://beta.boost.org/support/bugs.html
submitting it to either of the mailing lists is a preferred way - because many of the Boost developers read the lists on a daily basis, this way you are likely to get a quicker response, and the discussions that often arise there from (possible) bug reports are quite interesting and educational as well;
Why aren't reports from Trac forwarded to the mailing lists then?
A maintainer of the library against which the bug is being reported will be automatically notified by email. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
On Dec 17, 2007 3:24 AM, David Abrahams <dave@boost-consulting.com> wrote:
on Sat Dec 15 2007, "Olaf van der Spek" <olafvdspek-AT-gmail.com> wrote:
Hi,
http://boost.org/more/bugs.htm
Submit a bug report to either boost-users list, boost mailing list, or our bug tracking facility;
IIRC Trac accounts are only for developers. Maybe it's a good idea to include a Register link anyway and explain this?
IS something missing from the new page content? http://beta.boost.org/support/bugs.html
Yes (IMO), the else clause.
If you have a userid on the Boost Trac server, please log in.
I'd add that 'userids' are only for developers. Otherwise I'd still be looking for a sign up link.
submitting it to either of the mailing lists is a preferred way - because many of the Boost developers read the lists on a daily basis, this way you are likely to get a quicker response, and the discussions that often arise there from (possible) bug reports are quite interesting and educational as well;
Why aren't reports from Trac forwarded to the mailing lists then?
A maintainer of the library against which the bug is being reported will be automatically notified by email.
That's not equivalent. If it's enough, you can drop the 'submitting it to either of the mailing lists is a preferred way' bit. If it's not enough, you should forward them to the mailing list automatically and again drop that bit. Greetings, Olaf
on Mon Dec 17 2007, "Olaf van der Spek" <olafvdspek-AT-gmail.com> wrote:
On Dec 17, 2007 3:24 AM, David Abrahams <dave@boost-consulting.com> wrote:
on Sat Dec 15 2007, "Olaf van der Spek" <olafvdspek-AT-gmail.com> wrote:
Hi,
http://boost.org/more/bugs.htm
Submit a bug report to either boost-users list, boost mailing list, or our bug tracking facility;
IIRC Trac accounts are only for developers. Maybe it's a good idea to include a Register link anyway and explain this?
IS something missing from the new page content? http://beta.boost.org/support/bugs.html
Yes (IMO), the else clause.
If you have a userid on the Boost Trac server, please log in.
How is the very next item not an else clause? "**Even if you don't have a userid**, visit the settings page to enter or confirm an email address at which you can be reached. Most bug reports require some interaction with the reporter, and if we can't follow up with you, chances are good that your efforts at reporting the bug will be wasted."
I'd add that 'userids' are only for developers.
That's not strictly true, but doesn't http://svn.boost.org explain well enough?
Otherwise I'd still be looking for a sign up link.
submitting it to either of the mailing lists is a preferred way - because many of the Boost developers read the lists on a daily basis, this way you are likely to get a quicker response, and the discussions that often arise there from (possible) bug reports are quite interesting and educational as well;
Why aren't reports from Trac forwarded to the mailing lists then?
A maintainer of the library against which the bug is being reported will be automatically notified by email.
That's not equivalent.
I know.
If it's enough, you can drop the 'submitting it to either of the mailing lists is a preferred way' bit. If it's not enough, you should forward them to the mailing list automatically and again drop that bit.
It's been dropped already. http://beta.boost.org/support/bugs.html is a complete rewrite. Please re-read it with fresh eyes and let me know if there's really a problem. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
On Dec 18, 2007 6:15 PM, David Abrahams <dave@boost-consulting.com> wrote:
Yes (IMO), the else clause.
If you have a userid on the Boost Trac server, please log in.
How is the very next item not an else clause?
"**Even if you don't have a userid**, visit the settings page to
To me, that would indicate 'anonymous' reports are allowed, not that they're required (for users). I'd still try to find a sign up page. I'm still wondering, why can't users sign up? Other tracs allows this. I guess the settings page uses cookies? I'm sure I'll lose my cookie one day and forget to re-enter my email address. Or enter a wrong email address.
enter or confirm an email address at which you can be reached. Most bug reports require some interaction with the reporter, and if we can't follow up with you, chances are good that your efforts at reporting the bug will be wasted."
I'd add that 'userids' are only for developers.
That's not strictly true, but doesn't http://svn.boost.org explain well enough?
Yes, if you read it. ;) I've used other tracs and I didn't read the frontpage. I wanted to login, and went searching for the register link. Note that hiding menu items instead of disabling them is considered bad UI design (IIRC). I think this applies to links too. A register link is expected.
on Tue Dec 18 2007, "Olaf van der Spek" <olafvdspek-AT-gmail.com> wrote:
I've used other tracs and I didn't read the frontpage. I wanted to login, and went searching for the register link.
Note that hiding menu items instead of disabling them is considered bad UI design (IIRC). I think this applies to links too. A register link is expected.
You don't get a register link for Trac without installing a special plugin that displays it, and if you disable the plugin, well, the link disappears. So I think you ought to complain to the Trac developers ;-) -- Dave Abrahams Boost Consulting http://boost-consulting.com
participants (2)
-
David Abrahams -
Olaf van der Spek