Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 577587F4D for ; Thu, 1 Sep 2011 00:36:16 +0000 (UTC) Received: (qmail 14270 invoked by uid 500); 1 Sep 2011 00:36:15 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 14011 invoked by uid 500); 1 Sep 2011 00:36:15 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 14001 invoked by uid 99); 1 Sep 2011 00:36:14 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 00:36:14 +0000 Received: from localhost (HELO mail-ey0-f173.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 00:36:14 +0000 Received: by eyb7 with SMTP id 7so1454230eyb.18 for ; Wed, 31 Aug 2011 17:36:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.16.86 with SMTP id g62mr598495eeg.128.1314837372847; Wed, 31 Aug 2011 17:36:12 -0700 (PDT) Received: by 10.14.188.2 with HTTP; Wed, 31 Aug 2011 17:36:12 -0700 (PDT) In-Reply-To: References: <961143A7-AE5F-450D-8266-E982FD590610@gmail.com> Date: Wed, 31 Aug 2011 20:36:12 -0400 Message-ID: Subject: Re: What could Doc be? From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 On Wed, Aug 31, 2011 at 6:24 PM, Jean Weber wrote: > > Rob, > Thanks for the comments and encouraging ideas. Before I can answer the > more substantial questions in a useful way, I'll need to do some > research and dust off my docs-project-scoping skills from my years at > IBM Australia. So for now I'll just respond to this one: > Thanks, but no presentation decks, please! That is one IBM skill I hope to escape by working on open source ;-) My general view is this: After 10 years of OpenOffice.org we have about as many volunteers as the status quo will ever get us. If someone is really interested and able to contribute to the project, they either are doing so already, do doing so for LibreOffice. This is due to the great work OOo did over the years raising awareness of the project. The move to Apache changes things somewhat. The project is now a community-led project, not a corporate-led project. It now has a permissive license. This changes the equation and could bring in some new contributors. I think this will mainly be new corporate-sponsored contributors. Not exclusively, but the changes that the move to Apache will bring will be particularly attractive to such contributors. If we want to do better than that, then we need to do more then the status quo. We cannot just do the same things and expect better results. We need to do more than just migrate/translate/rehost/move OOo to Apache. We need to up our game. This requires more volunteers, of course. But the magic is, by expressing a bolder vision we can attract the kinds of volunteers that can make this happen. Ask yourself, if you were not already involved, and had a history with the project, what would interest a person of your skills in volunteering? That's the kind of person we want to attract! I'm not a documentation expert, but I've noticed some trends: 1) Moves to using structured formats that allow content to be more easily sliced and diced and targeted to different outputs. DITA is one way of doing it, but similar approaches could be based on ODF. 2) Collaboration with users. Several companies do this their online doc. Each page allows comments, a thread at the bottom of the page for user's to enter additional observations, tips, corrections, etc. 3) Multi-media. It is amazing what a 30 second video clip can teach you about pivot tables that would take pages of text to explain. 4) Tightening the bounds between documentation, product help, support and training. That goes back a to 1) above, the structuring of the information to make it reusable. Would things like the above attract more interest? -Rob