THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Info | ||
|---|---|---|
| ||
This is an original note that identifies options under consideration in September, 2011, when the Apache OpenOffice project was being started. Please see the Orientation modules or the User Documentation Plan area the for more current information on contributing to Apache OpenOffice documentation efforts. |
There are various planning topics regarding user docs:
- Content
- Target Audience
- Modality
- Source format
- Delivery format
- Relationship with other forms of user support
- Licensing
Many of these These are related, but not the same. Some content may work better in some formats (both source and delivery) than others.
...
Each choice, and combination of content/source/delivery choices, has pros and cons. We certainly don't have the resources (people or, in some cases, tools and/or skills) to produce a full range of content types or deliver in all possible formats, but we could have a "wish list" as well as a plan for what we are going to do over the next 6-12 months.
RELATIONSHIP WITH OTHER FORMS OF USER SUPPORT: This page summarises some recent discussion on this topic.
LICENSING: All official project user documentation should be under the Apache license. However, the existing user guides are not, and tracking down all the contributors to get agreement to change the license would be difficult if not impossible, and there is no guarantee that all would agree. We have a record of who contributed to each chapter (on the copyright page) but not who did what within the chapter. Therefore it may be necessary to completely replace the existing user guides or reconsider whether they are needed as part of an overall user documentation/user support strategy. See this page for a more detailed discussion.