![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
I've seen at least one or two people respond to the question. For some reason you don't appear to be seeing all the posts here. In particular you didn't respond to one of my own, specifically addressing your font issue wherein I provided a possible resolution.
This particular message I'm sending now I would normally provide privately. But since everyone on this list seems to be up in arms about sharing info. I post it here.
In fact it was explained twice before, so perhaps some of the list mail
is going in to your spam folder?
AOO is the apache branch of OpenOffice
It was answered in this message:
http://listarchives.libreoffice.org/global/users/msg22778.html
And also (unnecessarily snarkily) in this one:
http://listarchives.libreoffice.org/global/users/msg22784.html
AOO = Apache Open Office
Ok, I've received your message of 2 paragraphs [still below] -
you state you will answer the question; where is the answer
??? 
Maybe I'm not receiving all the messages ... maybe your message was
clipped for some reason ...
but if you sent more than is below, could you please explain how
to view it.
I've seen at least one or two people respond to the question. For some
Thank you.
It was answered in this message:
Thank you.
Obviously, some of the list mail is not getting through -
BTW - as for me, these can't be landing in the 'spam folder' since I
always check to be sure there's nothing there by mistake, before deleting
these
In fact it was explained twice before, so perhaps some of the list mail
You don't seem to understand what I wrote. Bottom line is, it's in the archives - search for it there. I'm sure someone else can help you with that - don't ask me because I don't know how.
Hi 
Interesting thought and a good diagram, thanks
Something i have wondered for a while is how to utilise what this particular list has to offer, perhaps confirming bug-reports could be partially done through this list?
Occasionally someone new on this list expresses an interest in getting more involved or somehow repaying the community. Also this list is quite good at eventually pinning-down exactly what an initial question was probably really asking.
People here generally don't have much time or experience but might be willing to push a couple of buttons to see if something really doesn't work, especially if it's not risky.
Could we have a weekly report listing unconfirmed bug-reports generated during the week? Would it be easier to have a link that listed all the 'thousands' of unconfirmed bug-reports? Is it thousands or (as i suspect) much much lower?
Ideally it would be great to have devs doing development rather than devs spending time trying to work at customer-relations and guessing at what people meant by certain bug-reports.
Just my 2pence-worth
Regards from
Tom
Hi
There is so much work that things do often get overlooked for quite a long time! It's not that it's not appreciated!!
I thought one of the drop-down options allowed people to choose "Feature request" or "Wish-list" to make it clearer? Sorry, i don't know much about bugzilla or posting bug reports but it might be on this page
http://wiki.documentfoundation.org/BugReport
(if not then it would be great if someone could add it in a useful place there)
Regards from
Tom
And now someone has jumped on my bug and changed my reporting so that it shows that it is only in 3.3 - that's the last straw. I will not have anything further to do with bug reporting. All those fine devs can choke on their bloody buggy product. Congratulations! You have alienated yet another volunteer.
Grrrrr, can't you just change it back?
Don't go! If you do you will be missed!
Regards from
Tom
Grrrrr, can't you just change it back?
<rant>
That is not the point, Tom.
This bug was only really a matter of a file having been dropped. But the
devs have spent more time fiddling with how it is listed than if they
had just added the missing file. More importantly, the most recent
change was apparently made because in trying to reopen the bug I failed
to do things the way they want them done, though there is no
documentation of how that is supposed to work.
Specifically, the documentation states:
"Version: The "Version" field is usually used for versions of a product
which have been released, and is set to indicate which versions of a
Component have the particular problem the bug report is about."
In many bug systems that means the reporter can in fact select all the
versions in which the errors appears, but this product does not allow
that. So what is one to do? Especially where a bug has been closed. I
reopened and set the version to the most recent version in which I
observed the bug. I thought this would be reasonable especially in as
much as the history reflects the initial appearance of the bug. So then
a dev steps in and changes the version, stating, "'Version' is most old
version where bug is reproducible. Not current version. Changing to
3.3.1 back"
I DID then change it back to 3.5.2 and commented that devs should spend
time writing tracker context help instead of fiddling with bugs that
were never going to be fixed. My response IS NOT productive (as was
initially noted in this list, lol) but isn't it so much fun to be
passive aggressive?
Don't go! If you do you will be missed!
Thanks for that (and I did get a chuckle from Marc Paré's reference to
the wiki provisions on top vs bottom posting, lol) but life is too short
to piss into the wind. It is one thing to work collaboratively with
people who see things differently, another to labor in the dark with no
one listening - did you see any comment from any dev on THIS list
apologizing to users, acknowledging issues, etc? Maybe if we start a
discussion about whether paragraphs are appropriate in list posts we
could attract some attention?
I don't know that I am "going" anywhere..... but I am certainly not
interested in putting in time to run down bugs if this is how users are
treated.
</rant>
Hi Marc,
But the devs have spent more time fiddling with how it is listed
One thing that frustrates me, since I've only just subscribed is that
we seem to be talking about a load of bugs with no numbers I can easily
lookup.
I'd greatly appreciate it if some kind soul could scrape the thread in
their mailbox for a list of bug links to the most significant issues and
aggregate them in a single mail - so I can go and triage them.
did you see any comment from any dev on THIS list apologizing to
users, acknowledging issues, etc. ?
I just subscribed [ for some reason my original subscription
bounced ]; if an apology is missing here it is:
Sorry !
The aim is not to annoy users, but to close a large number of old bugs
with (apparently) no response to them, that may have been mis-classified
in the past, due to random technical reasons (around not being able to
set bugs back to the UNCONFIRMED state) that will not affect new bugs.
We don't want to upset people. Having said that - I'm reasonably
optimistic that people watching bugs that have had 4x duplicate messages
(an unfortunate mistake) closing them will notice and re-open any
bugs that they care about - at least that is my hope; so it's not the
end of the world.
It should be noted, that doing this sort of mass-close is a response to
having a QA team which has no time to do a massive manual triage of each
of these old / indeterminate issues to see if they are already fixed /
obsolete etc.
There is a fairly easy solution here though - for all those who
complain about the consequences of the problem to get stuck into helping
out with triage / reproducing and confirming bugs etc.
Of course, suddenly reminding a load of people that their bug is still
not fixed generates some angst - but bugs don't magically fix themselves
over time, it takes real work
Apologies,
Michael.
The latest from Florian in misspelled CAPS (which now brings us to the
fact that the devs have touched this bug some 8 times without ever
bothering to actually read it) - Bravo Florian, we read you 5 by 5:
https://bugs.freedesktop.org/show_bug.cgi?id=35361
Florian Reisinger <reisi007@gmail.com> changed:
What |Removed |Added
And here is the best bit:
https://bugs.freedesktop.org/show_bug.cgi?id=35361
--- Comment #42 from Björn Michaelsen <bjoern.michaelsen@canonical.com>
2012-08-16 16:58:22 UTC ---
@Marc:
Seeing you boasting here:
that you knew you are creating extra work for the volunteers on the QA
team with intend is really disgusting given the workload of this team.
Also note that the version is clearly documented to be _first_ version
showing the bug:
http://wiki.documentfoundation.org/QA-FAQ
Even if it wasnt documented: If you take a moment to think about this,
there is also no other way the version field can be used: If the bug is
not present in the latest release the bug is closed anyway. If the bug
is present in the latest release, the bug is open and and the only
relevant information is: since when?
Please refain from continuing with abusive behaviour like the one you
are boasting about. I dont think repeating such behaviour is going to be
tolerated.
I put the bug back into Resolved->Invalid status.
Done. Excuse me while I go abuse myself
Michael,
It is pretty rare for specifics of bugs to be entered on the Users list, where there might have a passing comment that a bug would be or had been filed. But often no additional details of the bug in the discussion. But, that said, the threads are pretty descriptive.
Being a new subscriber, maybe the Nabble web interface would be of use to efficiently identify substantive issues that may have associated bugs.
http://nabble.documentfoundation.org/Users-f1639498.html
Stuart
Hi
A dev might have more joy with the very functional GMane interface rather than the gui prettiness of Nabble.
Even so i think this list is too high-volume to be data-mined for the required information and anyway it's extremely rare that specific bug reports are referenced either by name (however vague and inaccurate) or number.
Where threads do mention bug-report numbers it's done in a very inconsistent way, sometimes as part of a url sometimes with or without a # (as in bug #blah) and sometimes just the number so you would have had to be following the thread to realise it was a bug-report number.
That might all sound very negative but this list is mainly trying to solve problems partly to avoid people having to post bug-reports. Often answers here will be work-arounds or explain quirks or why things work slightly differently in LO than other products a new users might have used previously. It's very rare that people ask a question here that results in a bug-report getting posted and even then it's usually a feature request or wish-list item.
So, although i think your idea to try to do a bit of data-mining is good i think it's impractical for this list and that Michael Meeks handled it best by just asking for people to list specific examples.
Good luck all and much appreciated
Regards from
Tom
Come on - self abuse is something best shared! As in "Stop misbehaving myself, you"
Aware of the high esteem in which my opinion is held, by myself, I thoroughly enjoyed your rude essay, but have happily set my filter to reject any message with the phrase
"Excuse me but"
I enjoy a technical list on cycling which veers wildly off topic. We've been discussing recipes for bread recently, but topics have included Tom Lehrer, and National idiosyncrasies, notably that Yorkshire did very well in t'Olympic medals table and (counting former colonies) Great Britain romped home with the lion's share of Olympian bling. If the subject doesn't interest me, I'll pass it by.
But god help anyone who starts discussing H*lm*ts
This is a fantastic resource for rapid answers to those dumb questions you end up feeling very embarrassed having asked when the answer is pretty much RTFM.
Happily top posting despite all the efforts of the system to set me off at the bottom, and banging in the acr*n*ms as often as practically possible.
Probably the worst sins are similar - grandstanding, and overt commercial promotion, get substantial tut tutting from those in the online community.
As for RTFM, that's a WIGATI, until then I'll PIBE
In case you are wondering I'll explain when I Get Around To It, but meantime I'll play it by ear, with fond memories of Claire G.
Dave H
* Vicky Pollard is a character from Little Britain (UK TV series)
It is pretty rare for specifics of bugs to be entered on the Users
list, where there might have a passing comment that a bug would be or
had been filed. But often no additional details of the bug in the
discussion. But, that said, the threads are pretty descriptive.
I'm sure.
Being a new subscriber, maybe the Nabble web interface would be of use
to efficiently identify substantive issues that may have associated
bugs.
http://nabble.documentfoundation.org/Users-f1639498.html
I saw that, and I saw only Leif's bug linked there, in a monster thread
of vagueness. It is hard to justify dedicating the time to try to
reverse engineer people's names into bugzilla queries to dig out exactly
what bug they're talking about indirectly; and it's difficult to grok
the thread thus far. Better to ask for help - hence my request so
here goes again:
If you have a bug that you're particularly concerned about having been
marked NEEDINFO / RESOLVED INVALID, can you mail me a link ?
At least - it doesn't seem a good use of my time, when I could be
fixing bugs, reviewing patches etc. - I was hoping that some volunteer
might help me by building a list of the specific issues; so I can trawl
through them and get down to the grist of the technical issues fast.
That of course, is an ask not -that- different from asking people to
check if their bugs are still relevant vs. the latest version.
All the best,
Michael.