Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The bug tracker, which is where people expect to be able to submit bugs...

    How do people find the bug tracker? Magic powers?

    (My theory is that they look for suggestions on how to report a bug on the Parrot website.)

    • Well, I'm used to rt.cpan.org where I have a convenient "New Bug" link at the top. And a bug tracker is the first place I'd expect to find that, because that's where every other project expects you to submit bugs.

      So it is bad usability.

      • I'm used to rt.cpan.org...

        Not everyone is. Not every Parrot contributor is a CPAN contributor or even a Perl user. I'm not sure why you think this matters.

        ... a bug tracker is the first place I'd expect to find that...

        Again, how do you expect people to find the bug tracker? Magic powers? Innate knowledge? Is it part of Joseph Campbell's monomyth, or some sort of Jungian archetype that me in my pushes-pull-doors-occasionally cluelessness have failed to integrate into my worldview?

        Me, I think that the link to the Parrot Bugs Page on the Parrot homepage trumps knowledge mystically encoded into our DNA, because not everyone in the world is Shlomi Fish.

        ... that's where every other project expects you to submit bugs.

        Every other project? In the world? All 6,784 of them? You counted and surveyed all of them?

        So it is bad usability.

        Shlomi Fish is mortal. A cat is mortal. Therefore, all of the cats in the world are Shlomi Fish.

        • chromatic, most of the large or semi-large projects I know allow you to submit bugs using the bug tracker: KDE [kde.org], Mozilla [mozilla.org], GNOME [gnome.org], all the Various SourceForge projects [sourceforge.net], CPAN [cpan.org]. Etc. This is the default behaviour of most bug trackers, and it meets the users' expectations.

          And as for my generalisation, let me invoke Joel's Generalisation [perl.net.au] here: if it applies to me, it applies to everybody. I'm probably not the first one to make this mistake, and I won't be the last.

          When someone points a usability problem in

          • ... most of the large or semi-large projects I know...

            Now it's merely most, not every. A good UI is consistent. Please be consistent.

            ... if it applies to me, it applies to everybody.

            Thus clearly we should publish all of our documentation in Hebrew first, as it's your native language. It's easier for everyone to understand their native languages than secondary or tertiary languages.

            My corollary to Joel's law is: Joel is wrong.

            When someone points a usability problem in your system, the easy-wa

          • The wiki page you linked says this:

            Now a generalisation of this generalisation is “If it happens to you, it happens to everybody.” or “if it applies to you, it applies to everybody”, which may or may not be true depending on the context.

            You’ll note that the first tenet of usability is “you are not your user.”