Difference between revisions of "Documentation/OpenOffice.org needs YOU"

From Apache OpenOffice Wiki
Jump to: navigation, search
(New page: <title>OpenOffice.org Needs YOU!</title> </head> <body> <div style="padding:3pt; background-color: #d8e6eb; margin-top: 10pt; margin-bottom: 10pt;"> {|border=0 style="background-color:inh...)
 
 
(12 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<title>OpenOffice.org Needs YOU!</title>
+
{{DISPLAYTITLE:OpenOffice.org Needs YOU!}}
</head>
+
{{NeedsRework|EN}}
<body>
+
{{Old|EN}}
 
+
 
<div style="padding:3pt; background-color: #d8e6eb; margin-top: 10pt; margin-bottom: 10pt;">
 
<div style="padding:3pt; background-color: #d8e6eb; margin-top: 10pt; margin-bottom: 10pt;">
 
{|border=0 style="background-color:inherit!important" celpadding=0 cellspacing=0
 
{|border=0 style="background-color:inherit!important" celpadding=0 cellspacing=0
Line 8: Line 7:
 
|valign="top"|[[Image:documentation_note.png]]||The following text is an edited copy of a text by Dan Kegel.  
 
|valign="top"|[[Image:documentation_note.png]]||The following text is an edited copy of a text by Dan Kegel.  
 
  You can find the original text with more information for developers at
 
  You can find the original text with more information for developers at
  [http://www.kegel.com/openoffice/triage.html/Dan Kegels web site].
+
  [http://www.kegel.com/openoffice/triage.html Dan Kegels web site].
 
|}
 
|}
 
</div>
 
</div>
  
Note: 
+
==Introduction==
 +
Apache OpenOffice is the leading open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more. It is available in many languages and works on all common computers. It stores all your data in an international open standard format and can also read and write files from other common office software packages. It can be downloaded and used completely free of charge for any purpose.
  
<h1><a name="top">OpenOffice.org Needs YOU!</a></h1>
+
Documents in Version 4.0 of OpenOffice and Microsoft Office 14.3.8 (for Mac) are compatible. Users will likely not notice any problems when exchanging documents with MS Office users.
  
<h2><a name="contents">Contents</a></h2>
+
OpenOffice is constantly evolving with the help of its users. If you notice a problem while using OpenOffice, you have an opportunity to help make the program better and easier to use.
<ul>
+
There are two ways you can help:
<li><a href="#intro">Introduction</a></li>
+
 
+
<li><a href="#intro.backlog">The Problem Report Backlog</a></li>
+
<li><a href="#intro.triage">Triage</a></li>
+
<li><a href="#howtohelp">How to help</a></li>
+
<li><a href="#workflow">Workflow</a></li>
+
<li><a href="#priorities">Priorities, Priorities</a>
+
<ul>
+
<li><a href="#query.mybugs">Bugs you've already commented on, but which are still open</a></li>
+
<li><a href="#query.recent">Recently Reported Bugs</a></li>
+
<li><a href="#query.compat">Microsoft Office Compatibility Bugs</a></li>
+
 
+
<li><a href="#query.crash">Crash Bugs</a></li>
+
<li><a href="#query.votes">Bugs with Votes</a></li>
+
<li><a href="#query.versions">Bugs reported against particular versions</a></li>
+
</ul></li>
+
<li><a href="#dump">Capturing Stack Dumps</a></li>
+
<li><a href="#valgrind">Running OpenOffice with Valgrind</a></li>
+
<li>Link: <a href="ooo111.html">OpenOffice 1.1.1 Changes</a>
+
<li>Link: <a href="q.html">OpenOffice 2.0 Issue Overview</a>
+
 
+
<li><a href="#links">Other Links</a></li>
+
</ul>
+
 
+
<h2><a name="intro">Introduction</a></h2>
+
<a href="http://www.openoffice.org/">OpenOffice.org</a> is a free,
+
Microsoft Office-compatible office suite which is becoming increasingly
+
popular.  Individuals, schools, governments, and companies are
+
evaluating OpenOffice.org as an effective and inexpensive alternative
+
to Microsoft Office.
+
<p>
+
I recently tested compatibility between OpenOffice.org and Microsoft Office
+
by checking whether OpenOffice could correctly display Microsoft Office documents.
+
My unscientific impression is that Version 1.0.3 of OpenOffice.org scores
+
about a 70 out of 100 on MS Office compatibility, and Version 1.1.0 scores about a 90. 
+
The new version is so good that many people won't
+
notice any problems when exchanging documents with MS Office users.
+
<p>
+
However -- if you *do* notice problems, you face a choice.  You could:
+
 
<ol>
 
<ol>
<li>do nothing, and wait for someone else to notice and fix the problems,
+
<li>file bug reports for the problems you see
<li>file bug reports for the problems you see, or
+
<li>help the team sort through bug reports filed by others
<li>file bug reports for problems you see, and help the team sort through bug reports filed by others
+
</ol>
  
</ol>
 
 
The more you help, the more likely the problems you care about will be solved in the next release.
 
The more you help, the more likely the problems you care about will be solved in the next release.
I personally have helped sort through a number of bug reports, and
 
have been very happy to discover that my efforts made a big difference -
 
the <a href="http://www.openoffice.org/project/www/issues/show_bug.cgi?id=14053">crash bugs I sent on to the developers</a> are getting fixed rapidly.
 
<p>
 
This page assumes you're already familiar with filing bug reports,
 
and tries to show you how to help sort through other people's bug reports effectively.
 
  
<h2><a name="intro.backlog">The Problem Report Backlog</a></h2>
+
To file a bug report, register a Bugzilla account [https://issues.apache.org/ooo/createaccount.cgi]. You can also track your issue and view other issues from fellow users. For more information, follow this link: http://www.openoffice.org/qa/ooQAReloaded/ooQA-ReportBugs.html
OpenOffice.org is good software, but like all software, it has imperfections.
+
 
Lately, so many people are using the OpenOffice.org office suite that
+
==The Problem Report Backlog==
they're actually running into even fairly hard-to-trigger problems.
+
OpenOffice, like all software, has imperfections.
 +
So many people are using OpenOffice that
 +
they're even running into hard-to-trigger problems.
 
Many of these users are helpfully filing problem reports in IssueZilla,
 
Many of these users are helpfully filing problem reports in IssueZilla,
and the OpenOffice.org developers are working on resolving the issues as
+
and OpenOffice developers are working on resolving the issues as
they press on towards the release of version 1.1.1.
+
they press on towards the next release.
<p>
+
 
Problem is, problem reports are coming in faster than they can be dealt with,
+
However, problem reports are coming in faster than they can be dealt with  
 
because many of the problem reports are duplicates or system problems.
 
because many of the problem reports are duplicates or system problems.
The result is a backlog of over a thousand unexamined problem reports from users,
+
The result is a backlog of over a thousand unchecked problem reports from users,
and every day, another four new reports are added to the backlog.
+
and every day another four new reports are added to the backlog.
 
This backlog is both a shame, and a treasure trove.  Many of the
 
This backlog is both a shame, and a treasure trove.  Many of the
 
problem reports in the backlog contain enough information for
 
problem reports in the backlog contain enough information for
 
developers to quickly find and solve the problem - but it takes time
 
developers to quickly find and solve the problem - but it takes time
 
to sort through the reports.
 
to sort through the reports.
<p>
+
 
 
That's where <b>you</b> come in.  You can help the developers do what they do
 
That's where <b>you</b> come in.  You can help the developers do what they do
 
best.  All you have to do is help sort through the incoming bug reports.
 
best.  All you have to do is help sort through the incoming bug reports.
 
This is called <i>triage</i>.
 
This is called <i>triage</i>.
  
</p>
+
==Triage==
 
+
<h2><a name="intro.triage">Triage</a></h2>
+
  
 
Triage is what medics do when wounded soldiers arrive at a field hospital
 
Triage is what medics do when wounded soldiers arrive at a field hospital
Line 122: Line 76:
 
That lets the developers focus on fixing problems in the code.
 
That lets the developers focus on fixing problems in the code.
  
<h2><a name="howtohelp">How to help</a></h2>
+
==How to help==
  
 
Here's how to get started:
 
Here's how to get started:
  
 
<ol>
 
<ol>
<li><a href="http://www.openoffice.org/servlets/Join">Register as a member of OpenOffice.org</a>
+
<li>[http://www.openoffice.org/servlets/Join Register as a member of OpenOffice.org]
 
<li>Request to be a member of the QA project by clicking the "Join This Project" link at the upper
 
<li>Request to be a member of the QA project by clicking the "Join This Project" link at the upper
right hand of <a href="http://qa.openoffice.org/">qa.openoffice.org</a>
+
right hand of [http://qa.openoffice.org/ qa.openoffice.org]
<li>Review <a href="http://qa.openoffice.org/helping.html">qa.openoffice.org/helping.html</a> and
+
<li>Review [http://qa.openoffice.org/helping.html qa.openoffice.org/helping.html] and
<a href="http://qa.openoffice.org/priorities.html">qa.openoffice.org/priorities.html</a>
+
[http://qa.openoffice.org/priorities.html qa.openoffice.org/priorities.html]
<li><a href="http://qa.openoffice.org/servlets/ProjectMailingListList">Join the dev@qa.openoffice.org mailing list</a>
+
<li>[http://qa.openoffice.org/servlets/ProjectMailingListList Join the dev@qa.openoffice.org mailing list]
 
<li>Request the ability to set issue status by emailing dev@qa.openoffice.org with
 
<li>Request the ability to set issue status by emailing dev@qa.openoffice.org with
subject line <b>"Volunteer Privileges - &lt;OOo.org userid&gt;"</b>.
+
subject line <b>"Volunteer Privileges - <OOo.org userid>"</b>.
 
Mention your OOo.org userid again in the message body, and
 
Mention your OOo.org userid again in the message body, and
 
while you're at it, introduce yourself to the group - it's nice to know who we're working with.
 
while you're at it, introduce yourself to the group - it's nice to know who we're working with.
Line 141: Line 95:
  
 
</ol>
 
</ol>
Then pick an <a href=
+
Then pick an [http://www.openoffice.org/project/www/issues/buglist.cgi?issue_type=DEFECT&amp;issue_status=UNCONFIRMED&amp;changedin=5&amp;keywords=oooqa&amp;keywords_type=nowords&amp;order=%27Importance%27 unconfirmed bug report] (or <i>issue</i>, as the OpenOffice
"http://www.openoffice.org/project/www/issues/buglist.cgi?issue_type=DEFECT&amp;issue_status=UNCONFIRMED&amp;changedin=5&amp;keywords=oooqa&amp;keywords_type=nowords&amp;order=%27Importance%27">
+
unconfirmed bug report</a> (or <i>issue</i>, as the OpenOffice
+
 
team calls them), and help triage it as follows:  
 
team calls them), and help triage it as follows:  
  
 
<ul>
 
<ul>
 
<li>
 
<li>
See if you can find a similar bug in the list of <a href=
+
See if you can find a similar bug in the list of frequently-duplicated issues or by [http://www.openoffice.org/project/www/issues/query.cgi searching Issuezilla]. If you think it's a duplicate of issue 12345, say
"dups.html">frequently-duplicated issues</a> or by <a href=
+
"http://www.openoffice.org/project/www/issues/query.cgi">searching
+
Issuezilla</a>. If you think it's a duplicate of issue 12345, say
+
 
something like <i>"Looks like a duplicate of issue 12345"</i> in
 
something like <i>"Looks like a duplicate of issue 12345"</i> in
 
the Comment box. The word 'issue' followed by a number gets turned
 
the Comment box. The word 'issue' followed by a number gets turned
Line 166: Line 115:
  
 
<li>
 
<li>
If it's a crash or freeze bug, try to get a <a href=
+
If it's a crash or freeze bug, send the automatic report that the Crash Reporter offers you to send.
"#dump">stack dump</a> and attach it to the bug report.
+
  
 
<li>If you *can* reproduce the bug, mark it 'NEW' to signal the
 
<li>If you *can* reproduce the bug, mark it 'NEW' to signal the
Line 193: Line 141:
 
When you get the reply, go to the bug's page in IssueZilla, and
 
When you get the reply, go to the bug's page in IssueZilla, and
 
finish triaging the bug if you can.  
 
finish triaging the bug if you can.  
(If you forgot to add your email address, you can
 
still <a href="#query.mybugs">check for replies; see below.</a>)
 
  
<h2><a name="workflow">Workflow</a></h2>
+
==Workflow==
 
A helpful diagram of the life cycle of a bug report
 
A helpful diagram of the life cycle of a bug report
is online at <a href="http://qa.openoffice.org/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_confirm.html">qa.openoffice.org/issue_handling/taskhandling_workflow_issuetracker_confirm.html</a>.
+
is online at [http://qa.openoffice.org/issue_handling/workflowcharts/taskhandling_workflow_issuetracker_confirm.html qa.openoffice.org/issue_handling/taskhandling_workflow_issuetracker_confirm.html].
  
<h2><a name="priorities">Priorities, Priorities</a></h2>
+
==Priorities, Priorities==
  
 
There are so many bug reports that it's vital to tackle the ones
 
There are so many bug reports that it's vital to tackle the ones
Line 207: Line 153:
 
others might care more about crash bugs, others
 
others might care more about crash bugs, others
 
might care more about Microsoft Office compatibility.
 
might care more about Microsoft Office compatibility.
<p>
+
 
 
No matter what area you care about,  
 
No matter what area you care about,  
 
you can probably come up with an IssueZilla query that pulls up
 
you can probably come up with an IssueZilla query that pulls up
 
bug reports about it.  Below are a few example queries,
 
bug reports about it.  Below are a few example queries,
 
enough for you to get started with.
 
enough for you to get started with.
<p>
+
 
 
Note: these example queries aren't perfect - they miss a few bugs,
 
Note: these example queries aren't perfect - they miss a few bugs,
 
and pull up a few issues that aren't really what they were meant to find, so take
 
and pull up a few issues that aren't really what they were meant to find, so take
Line 218: Line 164:
 
on the "Edit Query" link on the bottom right of the query result page.
 
on the "Edit Query" link on the bottom right of the query result page.
  
<h3><a name="query.mybugs">Bugs you've already commented on, but which are still open</a></h3>
 
If you've already started triaging some bugs, you should periodically check on
 
their status to make sure they don't fall through the cracks.  Easiest way to
 
do that is to enter your @OpenOffice.org email address in this box and press ENTER:
 
<form method=get action="http://www.openoffice.org/project/www/issues/buglist.cgi">
 
<input TYPE="hidden" NAME="issue_type" VALUE="DEFECT">
 
<input TYPE="hidden" NAME="issue_status" VALUE="UNCONFIRMED">
 
<input TYPE="hidden" NAME="emailassigned_to1" VALUE="1">
 
<input TYPE="hidden" NAME="emaillongdesc1" VALUE="1">
 
<input TYPE="hidden" NAME="emailtype1" VALUE="substring">
 
<input TYPE="hidden" NAME="order" VALUE="Issue Number">
 
<input NAME="email1" VALUE="@openoffice.org">
 
<input TYPE="submit" VALUE="Submit query">
 
  
</form>
+
=Recently Reported Bugs=
 
+
<h3><a name="query.recent">Recently Reported Bugs</a></h3>
+
  
 
Recently reported bugs are important to check because a user is
 
Recently reported bugs are important to check because a user is
 
waiting for help, and is probably willing to provide additional
 
waiting for help, and is probably willing to provide additional
 
information or testcases if you need them to reproduce the bug.  
 
information or testcases if you need them to reproduce the bug.  
<p>
+
 
You can find a daily list of recently reported bugs, plus excerpts from developer blogs, at http://planet.go-oo.org/
+
You can find a daily list of recently reported bugs, plus excerpts from developer blogs, at [http://planet.go-oo.org/ Planet go-oo].

Latest revision as of 12:32, 9 July 2018

Edit-find-replace.png This article should be checked for accuracy and conformity to style.

Book-old.png    This article is outdated.    
Documentation note.png The following text is an edited copy of a text by Dan Kegel.
You can find the original text with more information for developers at
Dan Kegels web site.

Introduction

Apache OpenOffice is the leading open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more. It is available in many languages and works on all common computers. It stores all your data in an international open standard format and can also read and write files from other common office software packages. It can be downloaded and used completely free of charge for any purpose.

Documents in Version 4.0 of OpenOffice and Microsoft Office 14.3.8 (for Mac) are compatible. Users will likely not notice any problems when exchanging documents with MS Office users.

OpenOffice is constantly evolving with the help of its users. If you notice a problem while using OpenOffice, you have an opportunity to help make the program better and easier to use. There are two ways you can help:

  1. file bug reports for the problems you see
  2. help the team sort through bug reports filed by others

The more you help, the more likely the problems you care about will be solved in the next release.

To file a bug report, register a Bugzilla account [1]. You can also track your issue and view other issues from fellow users. For more information, follow this link: http://www.openoffice.org/qa/ooQAReloaded/ooQA-ReportBugs.html

The Problem Report Backlog

OpenOffice, like all software, has imperfections. So many people are using OpenOffice that they're even running into hard-to-trigger problems. Many of these users are helpfully filing problem reports in IssueZilla, and OpenOffice developers are working on resolving the issues as they press on towards the next release.

However, problem reports are coming in faster than they can be dealt with because many of the problem reports are duplicates or system problems. The result is a backlog of over a thousand unchecked problem reports from users, and every day another four new reports are added to the backlog. This backlog is both a shame, and a treasure trove. Many of the problem reports in the backlog contain enough information for developers to quickly find and solve the problem - but it takes time to sort through the reports.

That's where you come in. You can help the developers do what they do best. All you have to do is help sort through the incoming bug reports. This is called triage.

Triage

Triage is what medics do when wounded soldiers arrive at a field hospital so fast they can't all be helped. They decide one of three things about each arriving patient, namely: he/she is either

  • well enough that they don't really need a doctor,
  • sick, and could get better if they get to see a doctor, or
  • need last rites more than they need the doctor.

Similarly, triage is also what QA people do when bug reports come in too fast for developers to handle by themselves. They look at each incoming bug report, and decide whether it:

  • is a duplicate of a known bug, in which case they can often email a workaround to the user,
  • is a bug in some other piece of software, in which case they try to direct the user to the right place for support for that software, or
  • is a reproducible and novel bug, in which case they send a recipe for reproducing the bug to the developers.

That lets the developers focus on fixing problems in the code.

How to help

Here's how to get started:

  1. Register as a member of OpenOffice.org
  2. Request to be a member of the QA project by clicking the "Join This Project" link at the upper right hand of qa.openoffice.org
  3. Review qa.openoffice.org/helping.html and qa.openoffice.org/priorities.html
  4. Join the dev@qa.openoffice.org mailing list
  5. Request the ability to set issue status by emailing dev@qa.openoffice.org with subject line "Volunteer Privileges - <OOo.org userid>". Mention your OOo.org userid again in the message body, and while you're at it, introduce yourself to the group - it's nice to know who we're working with. After your request is granted, you should be able to add the oooqa keyword and modify all fields in an issue.

Then pick an unconfirmed bug report (or issue, as the OpenOffice team calls them), and help triage it as follows:

  • See if you can find a similar bug in the list of frequently-duplicated issues or by searching Issuezilla. If you think it's a duplicate of issue 12345, say something like "Looks like a duplicate of issue 12345" in the Comment box. The word 'issue' followed by a number gets turned into a handy hyperlink, so people who look at the bug report can click on those words to see how issue 12345 was solved.
  • Try to reproduce the bug on your computer. In the Comment box, say whether you were able to or not, and how you did it (if you weren't following a recipe already in the bug report). If you can't reproduce the bug, also ask for more details if there wasn't enough info in the original report.
  • If it's a crash or freeze bug, send the automatic report that the Crash Reporter offers you to send.
  • If you *can* reproduce the bug, mark it 'NEW' to signal the developers to have a look.
  • If you can't reproduce the bug, and you're pretty sure you have all the info you need, mark the bug WORKSFORME.
  • If you want to get email when someone replies (and you probably do), put your @openoffice.org email address (the one given to you when you registered to use Issuezilla) in the CC: field in the upper right.
  • Add the keyword 'oooqa' to show someone's started triaging it.
  • Then press the Submit button.

That's all there is to it!

If you asked for more information from the original submitter, and you remembered to put your OpenOffice.org email address in the CC: field in the upper right, you'll get email when they reply to your question. When you get the reply, go to the bug's page in IssueZilla, and finish triaging the bug if you can.

Workflow

A helpful diagram of the life cycle of a bug report is online at qa.openoffice.org/issue_handling/taskhandling_workflow_issuetracker_confirm.html.

Priorities, Priorities

There are so many bug reports that it's vital to tackle the ones with the highest potential payoff first. This is a matter of taste. Some people might want to look just at fresh bugs, others might care more about crash bugs, others might care more about Microsoft Office compatibility.

No matter what area you care about, you can probably come up with an IssueZilla query that pulls up bug reports about it. Below are a few example queries, enough for you to get started with.

Note: these example queries aren't perfect - they miss a few bugs, and pull up a few issues that aren't really what they were meant to find, so take them with a grain of salt. You can edit the queries by clicking on the "Edit Query" link on the bottom right of the query result page.


Recently Reported Bugs

Recently reported bugs are important to check because a user is waiting for help, and is probably willing to provide additional information or testcases if you need them to reproduce the bug.

You can find a daily list of recently reported bugs, plus excerpts from developer blogs, at Planet go-oo.

Personal tools