openoffice-doc mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith N. McKenna" <keith.mcke...@comcast.net>
Subject Re: Is it time to re-evaluate the viability of internal documentation?
Date Wed, 19 Mar 2014 02:46:38 GMT
Rob Weir wrote:
> On Tue, Mar 18, 2014 at 12:34 AM, Keith N. McKenna
> <keith.mckenna@comcast.net> wrote:
>> Greetings All;
>>
>> With the documentation list active for over a year now I believe it is
>> time to re-evaluate where we are with the documentation effort and if it
>> is worth continuing.
>>
>> My personal perspective is that very little progress has been made nor
>> do I see the likelihood of that changing in the near future. It has
>> become very frustrating answering inquiries with detailed e-mails about
>> what the needs are and where current information is being worked and
>> then never hearing from many people again.
>>
>> We seem not to have been able to attract skilled technical writers who
>> can give of there time to drive the infrastructure needed and to mentor
>> volunteers who want to help but have not done this type of writing before.
>>
>> I would pose a number of questions that should be considered and answered.
>>
>> 1: Is there a need for user documentation?
>> 2: Is this the place for that documentation to come from?
>>
>> I firmly believe that there is a need for high quality user oriented
>> documentation for OpenOffice. I am just not sure of the best way to go
>> about filling that need.
>>
>> I hope that this effort can generate a renewed interest in how to go
>> about giving the users of this wonderful software documentation of the
>> same quality and professionalism as the code base itself.
>>
> 
> I think it could be interesting to look at two other areas of the
> project where we have had greater success with integrating new
> volunteers.  Maybe there are lessons there.  I'm thinking of QA and
> Translation volunteers.
> 
> In those two cases we also get many emails from volunteers offering to
> help.  I'm not sure of the exact percentage of those who stick around
> longer term.  Certainly we see many express some interest, but then
> are never heard of again.  But we also see solid contributors who
> anchor the effort, become committers, etc.
> 
> So what is common between QA and Translation?
> 
> 1) The presence of more experienced volunteers to structure the work,
> break it into smaller pieces, help new volunteers get started, etc.
> You see, for example with QA, Yuzhen taking the lead on defining test
> cases, Rainer taking the lead in how use Bugzilla effectively, Juergen
> and Andrea reminding translation volunteers of deadlines and helping
> them get started, etc.   This is partially a question of "critical
> mass".
> 
This is a problem in that there are no experienced tech writers active
to give that type of structure and mentoring to volunteers. I do the
best I can, but like you I am not a documentation expert but an engineer
that has done some tech writing along the way.

> 2) The work is naturally "bite sized".  You can be an effective QA
> volunteer working 1 hour a week or 40 hours a week.  There are tasks
> of every size.  Ditto for Translators.
> 
This is also true with documentation. There are a number of tasks that
can be performed in an hour or possibly even less. One difference with
translation is that that are a number of tasks that are needed that are
only tangentially related to writing such as screen shots and comparing
written documentation to the software. It can keep things from getting
boring, but at the same time requires more skills than just writing or
grammar.

> 3) Both QA and Translation have deadlines, based on our release
> schedule, to motivate progress.   Although we're volunteers, the fact
> that these efforts are tied to a specific release gives some urgency
> to get the tasks done.
> 
This is something that documentation currently lacks. There will often
be a certain lag between release of the software to release of the
documentation depending on how much writing and checking can be done
with developer builds and beta releases.

> 4) Both areas have a solid way of tracking progress toward release
> goals, with the easy ability for one volunteer to step and finish a
> task that someone else has started.  So we're rarely stuck waiting for
> a specific volunteer who might not be available at a given time.
> 
This is a something we have been missing. We do have a status page, but
it depends on people remembering to use it and the dialog on the mailing
list has been less than what it should be for good communication. Couple
this with the need for a writer to have a good working knowledge of the
the part that they are documenting can limit the number of people that
can jump in and take over.

> So how is it with Doc?   You've done much if 1) above.  I know you've
> personally done a lot to make this happen.  2) as well.
> 
> I wonder if 3) could be part of the issue?  Doc is not aligned with a
> release schedule, at least not in the same way that QA and Translation
> are.
> 
3 could be be a part of the problem. There is a disconnect from the
release schedule of the actual software.

> How are with 4)?   Could this be a factor?
> 
Four is definitely a factor.
> Any other factors?
> 
Another factor is the lack of infrastructure. Things like a style guide,
writers guide etc. These are documents that experienced technical
writers would do to be used by volunteers to help them learn what needs
to be done.

> I do think documentation is important to users.  But I don't claim to
> be an expert in this area, or to know exactly what kind of
> documentation they need most, tutorials versus reference material,
> PDF's versus videos, etc.  Maybe this could be the subject of a
> survey?
> 
I am no expert either, just someone that believes that users deserve
quality documentation to use the software. I do not know what is best
either. A survey may help to shed some light on what users want and can
point us in some better directions to recruit the types of people to
push this effort forward.

Keith
> Regards,
> 
> -Rob
> 
> 
>> Regards
>> Keith
>>



Mime
View raw message