You are viewing a plain text version of this content. The canonical link for it is here.
Posted to doc@openoffice.apache.org by F Campos Costero <fj...@gmail.com> on 2021/01/25 16:03:26 UTC
Getting Started Guide (was Proposed Process for Documentation)
I think discussion specific to a new Getting Started Guide should have its
own thread, so i am launching this one.
@Marcia - It is great that you are working on a guide. Did you start it
from scratch or is it based on some other document? How far have you gotten?
@Robert - You expressed interest in working on a Getting Started Guide.
Have you seen the links that Jean provided to her book?
PDF http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
ODT http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt
Would you be interested in working on that?
Francis
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by F Campos Costero <fj...@gmail.com>.
It seems we have two possible projects for Robert to work on: a Mac version
of a brief Getting Started guide and the updating of Jean's Taming AOO
book.
I like the idea of short OS-specific guides. The people most likely to need
a Getting Started guide are also probably the most likely to get confused
by information that is not relevant to their OS and 300 pages is
intimidating if you are really a total novice. Each OS also has quirks
associated with installation that would be well handled in a dedicated
guide. Writing the guides from scratch would allow licensing them however
the author prefers. If they are relatively brief, we could have new content
up quickly and such visible progress would be welcome.
A huge advantage of revising Taming AOO is that it probably does not need a
lot of changes. Though the revision would probably take quite a while, I
expect the rate of producing up-to-date content would be high.
I think I will start to go through the Taming AOO book and make notes on
what changes should or could be made.
@Robert - Are you interested in writing a Mac Getting Started guide from
scratch? Alternatively, you and I could survey different sections of Taming
AOO for necessary revisions.
@Marcia - If Robert is interested in writing a Mac guide, would it make
sense to coordinate the content of the two guides so the scopes are similar?
Francis
On Wed, Jan 27, 2021 at 3:28 AM marcia wilbur <ai...@well.com> wrote:
> Hi.
>
> I did start from scratch. I am in content development phase of the get
> started for GNU Linux.
>
> @Robert,
>
> What Mac users need is a guide for specific Mac Options and functionality.
> One issue is Mac user options are not represented in current documentation
> - comprehensively. In fact, in some cases, in documentation, GNU Linux
> users and Mac users are represented as a second class to Windows.
>
> Using the Taming guide as an example:
>
>
> Page 18:
>
> Using the Quickstarter in Linux and Mac OS X
> Apache OpenOffice under Linux has a Quickstarter that looks and acts like
> the one described
> above for Windows. (The checkbox on the Memory page is labeled Enable
> systray quickstarter.
> If you do not have this checkbox, the Quickstarter module is not installed
> on your system.)
> Mac OS X provides similar functionality through a pop-up menu from the
> dock.
>
>
> There is no GNU Linux or Mac images, just a textual description of ----
> this is like the windows one here.
> Could be improved!
>
>
> also the preface states:
>
> Anyone who wants to get up to speed quickly with Apache OpenOffice will
> find this book valuable.
>
>
> 316 pages seems a bit much to get up to speed "quickly".
>
>
> One thing to mention - is the taming doc is under CC 3.0.
> This requires attribution and indication changes were made with a deriv
>
> http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
>
>
>
> ----- Original Message -----
> From: "Robert Farrell" <ro...@embarqmail.com>
> To: doc@openoffice.apache.org
> Sent: Wednesday, January 27, 2021 12:53:22 AM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> Yes, I can work on that. Tell me what needs to be done. I do not want to
> double up on someone else’s efforts.
>
> Robert
>
> Robert Farrell
> robertfarrell@embarqmail.com
>
>
>
> > On Jan 25, 2021, at 10:03 AM, F Campos Costero <fj...@gmail.com>
> wrote:
> >
> > I think discussion specific to a new Getting Started Guide should have
> its
> > own thread, so i am launching this one.
> >
> > @Marcia - It is great that you are working on a guide. Did you start it
> > from scratch or is it based on some other document? How far have you
> gotten?
> >
> > @Robert - You expressed interest in working on a Getting Started Guide.
> > Have you seen the links that Jean provided to her book?
> > PDF http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
> > ODT http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt
> >
> > Would you be interested in working on that?
> >
> > Francis
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 1/30/2021 10:23 PM, F Campos Costero wrote:
> I think Keith's preference was to use Git. I have only used Git a little to
> track my own work but that choice seems fine to me.
> Marcia - are you OK with that choice? If so, we would have to ask how one
> gets a repository set up under the project's ownership.
>
> Francis
>
Yes, that was my preference as laid out in the Proposed Documentation
flow. I proposed it that way because that is where the other projects
repositories are. We completed the move of everything from SVN to Git
just recently. Like everything in an Apache project it needs to be
decided by consensus. The only thing that document was meant to do was
act as a gateway to the discussion.One of the goals in my mind when I
started this latest push was to get better revision control of the
documentation and since the project used Git for for its other
repositories that was the logical starting point. If others have
differing opinions lets talk them out and come to a consensus.
Regards
Keith.
> On Sat, Jan 30, 2021 at 6:22 PM marcia wilbur <ai...@well.com> wrote:
>
>> Thanks for the resource!
>> I am wondering, I know we use styles etc... within writer, but do we have
>> a style guide or a style cheatsheet?
>>
>> Also, was there a determination on options for collaboration?
>> For example, I have marked up portions of the taming document - what is
>> the process for sharing?
>> The wiki? Gitbox area? e-mail?
>>
>> Thanks,
>>
>> ----- Original Message -----
>> From: "Keith N. McKenna" <ke...@comcast.net>
>> To: doc@openoffice.apache.org
>> Sent: Saturday, January 30, 2021 4:34:39 PM
>> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>>
>> On 1/28/2021 1:37 PM, F Campos Costero wrote:
>>> Another benefit of Marcia writing a Linux guide is that it could be used,
>>> with her approval, as a template for other guides. Maybe I am being too
>>> optimistic but I expect most of the topics would be the same among the
>>> three guides and the general organization should be the same.
>>>
>>> Francis
>>>
>> I have a document template .ott file that is based on the Version 3.3
>> OOo documentation. It has all of the styles used there as well as the
>> ones in Jeanne's Taming Guide as well as couple from he later that
>> where new and I felt where better than those supplied in the
>> original.The use of AOO and its designed in use of templates are, in my
>> opinion, important for 2 reasons. First it gives the documentation a
>> consistent and professional look and feel. Second it showcases the
>> strengths of the product and is in itself a strong marketing tool.
>>
>> There may be a few additions or deletions that could be made, but it is
>> usable as it stands. It can be copied from:
>>
>> https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott
>> .
>> Any Questions on its use or suggestions for how to make it better are
>> always welcome and can be addressed to this list.
>>
>> Regards
>> Keith
>>
>> <snip>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: doc-help@openoffice.apache.org
>>
>>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by F Campos Costero <fj...@gmail.com>.
I think Keith's preference was to use Git. I have only used Git a little to
track my own work but that choice seems fine to me.
Marcia - are you OK with that choice? If so, we would have to ask how one
gets a repository set up under the project's ownership.
Francis
On Sat, Jan 30, 2021 at 6:22 PM marcia wilbur <ai...@well.com> wrote:
> Thanks for the resource!
> I am wondering, I know we use styles etc... within writer, but do we have
> a style guide or a style cheatsheet?
>
> Also, was there a determination on options for collaboration?
> For example, I have marked up portions of the taming document - what is
> the process for sharing?
> The wiki? Gitbox area? e-mail?
>
> Thanks,
>
> ----- Original Message -----
> From: "Keith N. McKenna" <ke...@comcast.net>
> To: doc@openoffice.apache.org
> Sent: Saturday, January 30, 2021 4:34:39 PM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> On 1/28/2021 1:37 PM, F Campos Costero wrote:
> > Another benefit of Marcia writing a Linux guide is that it could be used,
> > with her approval, as a template for other guides. Maybe I am being too
> > optimistic but I expect most of the topics would be the same among the
> > three guides and the general organization should be the same.
> >
> > Francis
> >
> I have a document template .ott file that is based on the Version 3.3
> OOo documentation. It has all of the styles used there as well as the
> ones in Jeanne's Taming Guide as well as couple from he later that
> where new and I felt where better than those supplied in the
> original.The use of AOO and its designed in use of templates are, in my
> opinion, important for 2 reasons. First it gives the documentation a
> consistent and professional look and feel. Second it showcases the
> strengths of the product and is in itself a strong marketing tool.
>
> There may be a few additions or deletions that could be made, but it is
> usable as it stands. It can be copied from:
>
> https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott
> .
> Any Questions on its use or suggestions for how to make it better are
> always welcome and can be addressed to this list.
>
> Regards
> Keith
>
> <snip>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 1/30/2021 8:22 PM, marcia wilbur wrote:
> Thanks for the resource!
> I am wondering, I know we use styles etc... within writer, but do we have a style guide or a style cheatsheet?
>
> Also, was there a determination on options for collaboration?
> For example, I have marked up portions of the taming document - what is the process for sharing?
> The wiki? Gitbox area? e-mail?
>
> Thanks,
>
The closets thing we have for a Style Guide are the following two links.
They are mainly aimed at the mwiki, much of the information in them is
applicable our use as well.
https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide#Formats
https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy
As I remember correctly ODFAuthors used the Chicago Manual of Style, or
we could choose our own. Do you know what LO uses for there style guide?
Regards
Keith
> ----- Original Message -----
> From: "Keith N. McKenna" <ke...@comcast.net>
> To: doc@openoffice.apache.org
> Sent: Saturday, January 30, 2021 4:34:39 PM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> On 1/28/2021 1:37 PM, F Campos Costero wrote:
>> Another benefit of Marcia writing a Linux guide is that it could be used,
>> with her approval, as a template for other guides. Maybe I am being too
>> optimistic but I expect most of the topics would be the same among the
>> three guides and the general organization should be the same.
>>
>> Francis
>>
> I have a document template .ott file that is based on the Version 3.3
> OOo documentation. It has all of the styles used there as well as the
> ones in Jeanne's Taming Guide as well as couple from he later that
> where new and I felt where better than those supplied in the
> original.The use of AOO and its designed in use of templates are, in my
> opinion, important for 2 reasons. First it gives the documentation a
> consistent and professional look and feel. Second it showcases the
> strengths of the product and is in itself a strong marketing tool.
>
> There may be a few additions or deletions that could be made, but it is
> usable as it stands. It can be copied from:
> https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott.
> Any Questions on its use or suggestions for how to make it better are
> always welcome and can be addressed to this list.
>
> Regards
> Keith
>
> <snip>
>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by marcia wilbur <ai...@well.com>.
Thanks for the resource!
I am wondering, I know we use styles etc... within writer, but do we have a style guide or a style cheatsheet?
Also, was there a determination on options for collaboration?
For example, I have marked up portions of the taming document - what is the process for sharing?
The wiki? Gitbox area? e-mail?
Thanks,
----- Original Message -----
From: "Keith N. McKenna" <ke...@comcast.net>
To: doc@openoffice.apache.org
Sent: Saturday, January 30, 2021 4:34:39 PM
Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
On 1/28/2021 1:37 PM, F Campos Costero wrote:
> Another benefit of Marcia writing a Linux guide is that it could be used,
> with her approval, as a template for other guides. Maybe I am being too
> optimistic but I expect most of the topics would be the same among the
> three guides and the general organization should be the same.
>
> Francis
>
I have a document template .ott file that is based on the Version 3.3
OOo documentation. It has all of the styles used there as well as the
ones in Jeanne's Taming Guide as well as couple from he later that
where new and I felt where better than those supplied in the
original.The use of AOO and its designed in use of templates are, in my
opinion, important for 2 reasons. First it gives the documentation a
consistent and professional look and feel. Second it showcases the
strengths of the product and is in itself a strong marketing tool.
There may be a few additions or deletions that could be made, but it is
usable as it stands. It can be copied from:
https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott.
Any Questions on its use or suggestions for how to make it better are
always welcome and can be addressed to this list.
Regards
Keith
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 1/28/2021 1:37 PM, F Campos Costero wrote:
> Another benefit of Marcia writing a Linux guide is that it could be used,
> with her approval, as a template for other guides. Maybe I am being too
> optimistic but I expect most of the topics would be the same among the
> three guides and the general organization should be the same.
>
> Francis
>
I have a document template .ott file that is based on the Version 3.3
OOo documentation. It has all of the styles used there as well as the
ones in Jeanne's Taming Guide as well as couple from he later that
where new and I felt where better than those supplied in the
original.The use of AOO and its designed in use of templates are, in my
opinion, important for 2 reasons. First it gives the documentation a
consistent and professional look and feel. Second it showcases the
strengths of the product and is in itself a strong marketing tool.
There may be a few additions or deletions that could be made, but it is
usable as it stands. It can be copied from:
https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott.
Any Questions on its use or suggestions for how to make it better are
always welcome and can be addressed to this list.
Regards
Keith
<snip>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by F Campos Costero <fj...@gmail.com>.
Another benefit of Marcia writing a Linux guide is that it could be used,
with her approval, as a template for other guides. Maybe I am being too
optimistic but I expect most of the topics would be the same among the
three guides and the general organization should be the same.
Francis
On Wed, Jan 27, 2021 at 10:32 PM marcia wilbur <ai...@well.com> wrote:
> Hi. According to CC 3.0 - there must be information regarding changes
> being made in general. "if changes were made" However, I did not see any
> indication of specifics (that might be time consuming but maybe like a
> changelog for docs)
> Here is the link to cc 3.0 info:
>
> https://creativecommons.org/licenses/by/3.0/
> Under the following terms:
> Attribution — You must give appropriate credit, provide a link to the
> license, and indicate if changes were made. You may do so in any reasonable
> manner, but not in any way that suggests the licensor endorses you or your
> use.
>
> No additional restrictions — You may not apply legal terms or
> technological measures that legally restrict others from doing anything the
> license permits.
>
>
> I did not realize the GNU Linux user base was so low... even then.
> However, I will continue the effort for the 3% or so - because I'm weird
> like that. I started the Get Started, I'll see it through. Thank you for
> the information.
>
> In this case, I would say - an effort for the larger user base is
> important.
>
> Someone who is willing to take on the Windows content - making this more
> current would be a good idea.
> Are we using gitbox?
>
> I won't touch Windows, I don't have windows... but I can mark up and give
> feedback for that taming or whatever doc using OO and provide
> feedback/recommendations for documentation. However, do not associate me
> with any Windows effort - haha :)
>
> The feedback is for everyone.
>
> Thanks.
>
>
>
>
> ----- Original Message -----
> From: "Dennis Hamilton" <or...@msn.com>
> To: doc@openoffice.apache.org
> Sent: Wednesday, January 27, 2021 10:29:52 AM
> Subject: RE: Getting Started Guide (was Proposed Process for Documentation)
>
> Two things,
>
> 1. It is useful to know the demographics of Apache OpenOffice users. The
> latest board report does not break out downloads by platforms and languages
> any longer. In October 2015 this was the breakdown for AOO 4.1.1
> downloads at that point in time:
>
> 87.7% were for Windows
> 9.1% were for Macintosh
> 3.2% were for everything else, including Linux
>
> The prevalent languages have tended to toggle between English and French.
>
> I would be surprised to learn that this pattern has changed in any
> significant way.
>
> The Community Forums activity might also be valuable in this respect, and
> easier to find.
>
> Of course, for documentation, how different platforms are supported is up
> to those willing to develop such documentation. I have no quarrel,
> especially for Getting Started, with addressing whatever platforms an
> author wants to specialize for to accommodate the readers.
>
> 2. I understand that the contributor of a document under CC-BY specifies
> how attribution is to be made. I am not aware that there is any
> requirement to specify the changes made. Normally, one simply provides the
> attribution and source of the document(s) on which the derivative is based.
>
> Marcia, can you point us to where in the CC-BY description that changes
> must be identified?
>
> - Dennis
>
> -----Original Message-----
> From: marcia wilbur <ai...@well.com>
> Sent: Wednesday, January 27, 2021 02:28
> To: doc@openoffice.apache.org
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> [orcmid] [ ... ]
>
> One thing to mention - is the taming doc is under CC 3.0.
> This requires attribution and indication changes were made with a deriv
>
> [ ... ]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
>
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by marcia wilbur <ai...@well.com>.
Hi. According to CC 3.0 - there must be information regarding changes being made in general. "if changes were made" However, I did not see any indication of specifics (that might be time consuming but maybe like a changelog for docs)
Here is the link to cc 3.0 info:
https://creativecommons.org/licenses/by/3.0/
Under the following terms:
Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
I did not realize the GNU Linux user base was so low... even then.
However, I will continue the effort for the 3% or so - because I'm weird like that. I started the Get Started, I'll see it through. Thank you for the information.
In this case, I would say - an effort for the larger user base is important.
Someone who is willing to take on the Windows content - making this more current would be a good idea.
Are we using gitbox?
I won't touch Windows, I don't have windows... but I can mark up and give feedback for that taming or whatever doc using OO and provide feedback/recommendations for documentation. However, do not associate me with any Windows effort - haha :)
The feedback is for everyone.
Thanks.
----- Original Message -----
From: "Dennis Hamilton" <or...@msn.com>
To: doc@openoffice.apache.org
Sent: Wednesday, January 27, 2021 10:29:52 AM
Subject: RE: Getting Started Guide (was Proposed Process for Documentation)
Two things,
1. It is useful to know the demographics of Apache OpenOffice users. The latest board report does not break out downloads by platforms and languages any longer. In October 2015 this was the breakdown for AOO 4.1.1 downloads at that point in time:
87.7% were for Windows
9.1% were for Macintosh
3.2% were for everything else, including Linux
The prevalent languages have tended to toggle between English and French.
I would be surprised to learn that this pattern has changed in any significant way.
The Community Forums activity might also be valuable in this respect, and easier to find.
Of course, for documentation, how different platforms are supported is up to those willing to develop such documentation. I have no quarrel, especially for Getting Started, with addressing whatever platforms an author wants to specialize for to accommodate the readers.
2. I understand that the contributor of a document under CC-BY specifies how attribution is to be made. I am not aware that there is any requirement to specify the changes made. Normally, one simply provides the attribution and source of the document(s) on which the derivative is based.
Marcia, can you point us to where in the CC-BY description that changes must be identified?
- Dennis
-----Original Message-----
From: marcia wilbur <ai...@well.com>
Sent: Wednesday, January 27, 2021 02:28
To: doc@openoffice.apache.org
Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
[orcmid] [ ... ]
One thing to mention - is the taming doc is under CC 3.0.
This requires attribution and indication changes were made with a deriv
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
RE: Getting Started Guide (was Proposed Process for Documentation)
Posted by Dennis Hamilton <or...@msn.com>.
Two things,
1. It is useful to know the demographics of Apache OpenOffice users. The latest board report does not break out downloads by platforms and languages any longer. In October 2015 this was the breakdown for AOO 4.1.1 downloads at that point in time:
87.7% were for Windows
9.1% were for Macintosh
3.2% were for everything else, including Linux
The prevalent languages have tended to toggle between English and French.
I would be surprised to learn that this pattern has changed in any significant way.
The Community Forums activity might also be valuable in this respect, and easier to find.
Of course, for documentation, how different platforms are supported is up to those willing to develop such documentation. I have no quarrel, especially for Getting Started, with addressing whatever platforms an author wants to specialize for to accommodate the readers.
2. I understand that the contributor of a document under CC-BY specifies how attribution is to be made. I am not aware that there is any requirement to specify the changes made. Normally, one simply provides the attribution and source of the document(s) on which the derivative is based.
Marcia, can you point us to where in the CC-BY description that changes must be identified?
- Dennis
-----Original Message-----
From: marcia wilbur <ai...@well.com>
Sent: Wednesday, January 27, 2021 02:28
To: doc@openoffice.apache.org
Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
[orcmid] [ ... ]
One thing to mention - is the taming doc is under CC 3.0.
This requires attribution and indication changes were made with a deriv
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by marcia wilbur <ai...@well.com>.
Hi.
I did start from scratch. I am in content development phase of the get started for GNU Linux.
@Robert,
What Mac users need is a guide for specific Mac Options and functionality.
One issue is Mac user options are not represented in current documentation - comprehensively. In fact, in some cases, in documentation, GNU Linux users and Mac users are represented as a second class to Windows.
Using the Taming guide as an example:
Page 18:
Using the Quickstarter in Linux and Mac OS X
Apache OpenOffice under Linux has a Quickstarter that looks and acts like the one described
above for Windows. (The checkbox on the Memory page is labeled Enable systray quickstarter.
If you do not have this checkbox, the Quickstarter module is not installed on your system.)
Mac OS X provides similar functionality through a pop-up menu from the dock.
There is no GNU Linux or Mac images, just a textual description of ---- this is like the windows one here.
Could be improved!
also the preface states:
Anyone who wants to get up to speed quickly with Apache OpenOffice will find this book valuable.
316 pages seems a bit much to get up to speed "quickly".
One thing to mention - is the taming doc is under CC 3.0.
This requires attribution and indication changes were made with a deriv
http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
----- Original Message -----
From: "Robert Farrell" <ro...@embarqmail.com>
To: doc@openoffice.apache.org
Sent: Wednesday, January 27, 2021 12:53:22 AM
Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
Yes, I can work on that. Tell me what needs to be done. I do not want to double up on someone else’s efforts.
Robert
Robert Farrell
robertfarrell@embarqmail.com
> On Jan 25, 2021, at 10:03 AM, F Campos Costero <fj...@gmail.com> wrote:
>
> I think discussion specific to a new Getting Started Guide should have its
> own thread, so i am launching this one.
>
> @Marcia - It is great that you are working on a guide. Did you start it
> from scratch or is it based on some other document? How far have you gotten?
>
> @Robert - You expressed interest in working on a Getting Started Guide.
> Have you seen the links that Jean provided to her book?
> PDF http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
> ODT http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt
>
> Would you be interested in working on that?
>
> Francis
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: Getting Started Guide (was Proposed Process for Documentation)
Posted by Robert Farrell <ro...@embarqmail.com>.
Yes, I can work on that. Tell me what needs to be done. I do not want to double up on someone else’s efforts.
Robert
Robert Farrell
robertfarrell@embarqmail.com
> On Jan 25, 2021, at 10:03 AM, F Campos Costero <fj...@gmail.com> wrote:
>
> I think discussion specific to a new Getting Started Guide should have its
> own thread, so i am launching this one.
>
> @Marcia - It is great that you are working on a guide. Did you start it
> from scratch or is it based on some other document? How far have you gotten?
>
> @Robert - You expressed interest in working on a Getting Started Guide.
> Have you seen the links that Jean provided to her book?
> PDF http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
> ODT http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt
>
> Would you be interested in working on that?
>
> Francis
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org