Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 306BDDBD9 for ; Thu, 20 Sep 2012 17:27:24 +0000 (UTC) Received: (qmail 39948 invoked by uid 500); 20 Sep 2012 17:27:24 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 39917 invoked by uid 500); 20 Sep 2012 17:27:24 -0000 Mailing-List: contact ooo-commits-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-commits@incubator.apache.org Received: (qmail 39909 invoked by uid 99); 20 Sep 2012 17:27:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2012 17:27:24 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2012 17:27:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id q8KHR0Uk005291 for ; Thu, 20 Sep 2012 17:27:00 GMT Date: Thu, 20 Sep 2012 13:27:00 -0400 (EDT) From: confluence@apache.org To: ooo-commits@incubator.apache.org Message-ID: <20778162.34.1348162020024.JavaMail.confluence@thor> Subject: [CONF] Apache OpenOffice Community > User Guides Revisted MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Auto-Submitted: auto-generated Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS) Page: User Guides Revisted (https://cwiki.apache.org/confluence/display/OOOUSERS/User+Guides+Revisted) Comment: https://cwiki.apache.org/confluence/display/OOOUSERS/User+Guides+Revisted?focusedCommentId=30736429#comment-30736429 Comment added by Ricardo Berlasso: --------------------------------------------------------------------- I agree with you: it will be really difficult to do this on time for 3.5... but it will be a good "selling point" for 4.0. A possibility is to build short documents that show differences between 3.4 and 3.5, a sort of "what's new" and use those document plus the existing ones as transition to the new documentation for 4.0. We can even use those documents to "promote" the 4.0 effort (something like "we are thinking on the future"). And after all, we are not on a hurry: on my experience providing user support, people tend to use documentation as the last resource to solve a problem. In reply to a comment by Keith N. McKenna: I think I understand what you are saying Ricardo and I do not necessarily disagree. My concern with starting over and why I believe t is more an option or AOO 4.0 and beyond is the amount of work and the current lack of resources to accomplish anything for the 3.5 release. It definitely a lot of work. The question that I have is can we get the resources that we need to do that large a re-write. Also there is nothing that says this cannot be a phased process, indeed that is how I envision it. The first phase being getting something ready or the 3.5 release and also planning what the next iteration should look like. I look forward to hearing more of your thoughts on this. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action