Exactly what I tried to ask: why is that so that bitcard users get "discriminated" by CPAN? Isn't the "inept interface" a community decision against bitcard?? | [reply] |
Okay. I was just a bit surprised when I followed your link and saw what looked like a direct answer to the question you asked.
You might like to add the "Why do bitcard logins get an inept UI?" question to the OP.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Ironically, if you want to log in to rt.perl.org (at least, for perl5 bugs, I wouldn't know about the perl6 side), Bitcard is all that's on offer.
Luckily, there's also a no passwords required email interface if you want to comment on bugs. | [reply]
[d/l] |
My experience of rt has been woeful. The only time I ever go there these days is if google throws up a link when I'm searching for something.
Even then, it usually only turns up a synopsis, and if I click on a link to actually read the details, it takes me to a login screen that has never worked for me.
I'd report an aweful lot more of the bugs I encounter, if it'd let me. Without requiring me to become a detective to work out how. I reason that if "they" really wanted the information, they'd make it easy for me to give it to them. They don't, so I don't.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
I'd report an aweful lot more of the bugs I encounter, if it'd let me.
The perlbug utility isn't working for you? There's no need to use rt.perl.org to report bugs.
| [reply]
[d/l]
[select] |