openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <>
Subject Re: Status of existing OOo user guides
Date Tue, 06 Sep 2011 01:34:36 GMT

On Sep 5, 2011, at 6:04 PM, Jean Weber wrote:

> On Tue, Sep 6, 2011 at 10:54, Rob Weir <> wrote:
>> On Mon, Sep 5, 2011 at 7:28 PM, Jean Weber <> wrote:
>>> On Mon, Sep 5, 2011 at 23:02, Rob Weir <> wrote:
>>>> On Mon, Sep 5, 2011 at 8:34 AM, Jean Weber <> wrote:
>>>>> I think Rob's suggestions for "boldly going where OOo Docs have not
>>>>> gone before" are good ones, but they won't happen immediately. In the
>>>>> short term (for the next release of the software), we are most likely
>>>>> to have a choice between updated CC-BY-licensed user guides, or no
>>>>> user guides at all.
>>>> Take a  look at the Subversion home page and the link they have on the
>>>> left.  We could do something like that if we wanted.  That is a good
>>>> short-term approach.  It could even work longer term, though I think
>>>> it is a growth-limiting choice.
>>> I think that is the most workable solution for the short term. We
>>> discussed it here some time ago and I at least looked at the
>>> Subversion home page and link and thought it was a good way to go.
>>> However, I am not sure where we should put the documents so they could
>>> be linked from the AOOo website. ODFAuthors is a production site, not
>>> really suitable in its present state for delivery of documents IMO. I
>>> suppose we could redesign this page
>>> and add whatever other pages
>>> might be needed.
>> What is the concern with hosting the doc at ODFAuthors? Is the
>> load/bandwidth a concern?  If so, one alternative would be to upload
>> the doc to  Projects there are hosted by Google
>> Code, and also agree to these guidelines:
>> This is a good option for things that are not part of the project, but
>> somehow related to the project.
>> -Rob
> My main concern is that I don't think the design of the website is
> really suitable for consumers of the docs. It's set up to be a
> production site. Past experience suggests that trying to get it to
> serve both purposes will mean it serves neither well.

> sounds good; I'll read the guidelines to see if I can
> spot anything of concern to me (not that I expect to).

We can always have web pages at both and
link directly to resources at and apache-extras/. Which depends on whether
the link is about authoring or downloading documentation.


> --Jean

View raw message