> The hassle with registration was reason enough to not participate there.
Yes. Why does Purism not use Reportbug?
PureOS isn’t Debian. Debian doesn’t want bug reports for PureOS.
I guess it could be used, but how much setup/support?
1 Like
I don’t care about the software used for bug-tracking and also not about the method to protect the page (at least mostly). But if I have to wait an unspecific time, just to get a mail where I have to response just in time (when I am probably not available), just to get locked out after this time and have to communicate again with the admin in a not documented way, because the GUI is broken and such, just to wait another unspecific time to not know if I response in time … the issue of this process starts with the “response in time”.
PureOS isn’t Debian. Debian doesn’t want bug reports for PureOS.
They would need to install and configure debbugs on one of their servers, of course. There is a debbugs package. I don’t know how difficult it is to configure.
I don’t care about the software used for bug-tracking and also not about the method to protect the page (at least mostly). But if I have to wait an unspecific time, just to get a mail where I have to response just in time (when I am probably not available), just to get locked out…
Reportbug eliminates all that. You type “reportbug ”, follow instructions, and you’re done. No account required.
Reportbug-gtk provides a GUI.
What would stop spammers from spamming? This is the stated reason for having the manual approval process:
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this page for instructions on how to get full permissions. Sorry for the inconvenience.
(I have no information about the circumstances surrounding the appearance of that message on the web site, and it has been there for quite some years, so I don’t know how current it is.)