malenki wrote:
In short: I'd like a straightforward interface at OpenOffice.org for
looking after and filing bugs without need of registering.
In long:
This will be a bit longer and some kind of a rant. I don't know where
else I should place this topic. This list matches best, I think.
Today I encountered a bug in OOo (the app). The bug itself is from minor
interest, but I want to tell what fun I had with it.
From the last bug I experienced I knew, that the searching for bugs at
the OOo-site was pretty ugly but though I tried to go there.
Hm, which way I took last time?
OpenOffice.org => Support? Nope. Fulltextsearch for bug and (as I later
found out _Issue_ would be the right thing) issue doesn't hit anything
of relevance.
So back to OpenOffice.org, look what else we can find. => Participate?
Mmh, maybe. It links to a page with again several topics to choose. =>
User Experience sounds like newspeech for "tell us what you think of
OOo".
Now indeed at this page on the left shows up a link => Issue Tracker.
Why, this is straightforward, isn't it? (later I had a look to =>
Projects since one would also could think to find a bug tracker but
there too it can't be found)
Anyway, I have found the Bug^W^WIssue Tracker so I can proceed.
Clicking at the link, a neat trim page shows up with one search field -
a bit small maybe. Ha, it's just for searching for issue numbers as the
# sais. A pity I am no halfgod who could guess the right one
straightforward -.-
So, surely I have to => Query Database to see if I can find "my" bug
As the ~1MB page has loaded I have to scroll two times to see it all
since I am at my netbook. But I guess I am happy for I don't see all
the disgusting searchfields at once with a lot more possibilities to
scroll inside of them. Sweet indeed. I don't fiddle with all these
fields but just search some words for in "Summary" and "A description
entry" but either I get no hits or about several hundred so I give up
here.
(A small interlude: since I am native german I realised, that with
de.OpenOffice.org I would have found the Issue Tracker more easily but
searching it still is a PITA since except the big lot of fields some
time I just don't have the right english programmer vocabulary to
search for.)
I turn to irc.freenode.org/#OpenOffice.org. There after short my bug is
confirmed, I am shown to
http://qa.openoffice.org/issue_handling/submission_gateway.html to
report it. Since it affects ooweb I am again baffled where to put the
bug. At IRC I am told, that oowriter is the right topic. How
straightforward indeed again! Clicking it I am shown a "Permission
denied!" and told, that guest hasn't rights to do what I tried and that
I should log in. Anyway, since in IRC I was told that a part of my bug
is already filed I just was fed up and let it be.
I guess I wasted twenty minutes for trying to research or reporting the
bug. Some parts of the OpenOffice.org-site look already like the
feature-monster OpenOffice, including the lost feeling users experience
among the tons possibilities which don't work out as expected but one
hasn't the power to change that.
If there would be a straightforward way of searching for and reporting
bugs, I won't say that OOo would get better or more detailed bug
reports, but maybe the "normal user" (yes, ha! :P) would have a chance
to report things he found or wants to have improved without getting
lost in the depths of the OpenOffice.org-site
exhausted -.-
malenki
+1
Links we can easily fix: this page [1] needs a link to Issue Tracker,
labeled something obvious, like "Bug Reports".
[1] http://support.openoffice.org/
But just for fun, if we wanted to write an Issue Wizard to front-end
Issuezilla, what language would it be in? Presumably it would involve
forms, and some JavaScript thereon, but processing the returned info?
(My guess is that this is the greatest productivity improvement -- for
OO.o itself -- that we could invest time in. The ramifications are huge.)
--
/tj/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
