You are viewing a plain text version of this content. The canonical link for it is here.
Posted to doc@openoffice.apache.org by "Keith N. McKenna" <ke...@comcast.net> on 2020/12/19 00:27:20 UTC
How We Implament the new Documentation Process
Greetings All;
Now that the proposal is finalized unless there are major objections to
it, I would like to start a disscussion on how do we best implament it. I
see two possible ways to go with it.
1. We start fresh and write all new documentation Under the ALV2 license
for 4.2.x and take what is currently on the mwiki for the 4.1.x series and
convert it to Writer files and get it under version control if it is
needed for a possible 4.1.9 Release.
2. Start with the already published 3.3 odt documents and upgrade those to
version 4. This could require the work being done outside of the project
made up of the people on doc@ do to the 3.3 docs being under what is
considered a catagory X license and may not be able to be stored in an
Apache repository.
If we want to go with #2 there is a way around the possible repository
problem.
I hope that this will generate a lot of comment on how this should happen
so that we as a group can move forward with creating professional quality
documentation for the project.
Regards
Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by Jean Weber <je...@gmail.com>.
Additional comments, for information:
The "OOoAuthors" website referred to in the OO3.3 user guides no
longer exists; that domain name now redirects to LO Docs.
The reference in the OO3.3 guides and wiki to printed copies at
Lulu.com is out of date; I removed those books some years ago as they
were obsolete.
Jean
On Sat, Dec 19, 2020 at 1:57 PM Jean Weber <je...@gmail.com> wrote:
>
> Or just update the existing OOo 3.3 guides. They're all available in
> .ODT format on the old OOo wiki. Seriously, updating existing material
> is likely to be much faster than starting from scratch, especially
> with a very small team.
>
> Jean (former Co-Lead of OOo Docs and editor/publisher of most of the
> OOo user guides)
>
> On Sat, Dec 19, 2020 at 1:46 PM Jean Weber <je...@gmail.com> wrote:
> >
> > A consideration:
> > The two licenses under which the OOo 3.3 user guides were published
> > are the same licenses as for the current LibreOffice user guides. If
> > the AOO Docs team chooses to go with Keith's #2, you might be able to
> > reuse quite a bit of LO 4.x material, with some amendment (and new
> > screenshots) as needed to account for differences between the
> > programs. That could potentially speed up the publication process
> > quite a bit.
> >
> > Jean
> >
> > On Sat, Dec 19, 2020 at 10:27 AM Keith N. McKenna
> > <ke...@comcast.net> wrote:
> > >
> > > Greetings All;
> > >
> > > Now that the proposal is finalized unless there are major objections to
> > > it, I would like to start a disscussion on how do we best implament it. I
> > > see two possible ways to go with it.
> > >
> > > 1. We start fresh and write all new documentation Under the ALV2 license
> > > for 4.2.x and take what is currently on the mwiki for the 4.1.x series and
> > > convert it to Writer files and get it under version control if it is
> > > needed for a possible 4.1.9 Release.
> > >
> > > 2. Start with the already published 3.3 odt documents and upgrade those to
> > > version 4. This could require the work being done outside of the project
> > > made up of the people on doc@ do to the 3.3 docs being under what is
> > > considered a catagory X license and may not be able to be stored in an
> > > Apache repository.
> > >
> > > If we want to go with #2 there is a way around the possible repository
> > > problem.
> > >
> > > I hope that this will generate a lot of comment on how this should happen
> > > so that we as a group can move forward with creating professional quality
> > > documentation for the project.
> > >
> > > Regards
> > > Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by Jean Weber <je...@gmail.com>.
Or just update the existing OOo 3.3 guides. They're all available in
.ODT format on the old OOo wiki. Seriously, updating existing material
is likely to be much faster than starting from scratch, especially
with a very small team.
Jean (former Co-Lead of OOo Docs and editor/publisher of most of the
OOo user guides)
On Sat, Dec 19, 2020 at 1:46 PM Jean Weber <je...@gmail.com> wrote:
>
> A consideration:
> The two licenses under which the OOo 3.3 user guides were published
> are the same licenses as for the current LibreOffice user guides. If
> the AOO Docs team chooses to go with Keith's #2, you might be able to
> reuse quite a bit of LO 4.x material, with some amendment (and new
> screenshots) as needed to account for differences between the
> programs. That could potentially speed up the publication process
> quite a bit.
>
> Jean
>
> On Sat, Dec 19, 2020 at 10:27 AM Keith N. McKenna
> <ke...@comcast.net> wrote:
> >
> > Greetings All;
> >
> > Now that the proposal is finalized unless there are major objections to
> > it, I would like to start a disscussion on how do we best implament it. I
> > see two possible ways to go with it.
> >
> > 1. We start fresh and write all new documentation Under the ALV2 license
> > for 4.2.x and take what is currently on the mwiki for the 4.1.x series and
> > convert it to Writer files and get it under version control if it is
> > needed for a possible 4.1.9 Release.
> >
> > 2. Start with the already published 3.3 odt documents and upgrade those to
> > version 4. This could require the work being done outside of the project
> > made up of the people on doc@ do to the 3.3 docs being under what is
> > considered a catagory X license and may not be able to be stored in an
> > Apache repository.
> >
> > If we want to go with #2 there is a way around the possible repository
> > problem.
> >
> > I hope that this will generate a lot of comment on how this should happen
> > so that we as a group can move forward with creating professional quality
> > documentation for the project.
> >
> > Regards
> > Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by Jean Weber <je...@gmail.com>.
A consideration:
The two licenses under which the OOo 3.3 user guides were published
are the same licenses as for the current LibreOffice user guides. If
the AOO Docs team chooses to go with Keith's #2, you might be able to
reuse quite a bit of LO 4.x material, with some amendment (and new
screenshots) as needed to account for differences between the
programs. That could potentially speed up the publication process
quite a bit.
Jean
On Sat, Dec 19, 2020 at 10:27 AM Keith N. McKenna
<ke...@comcast.net> wrote:
>
> Greetings All;
>
> Now that the proposal is finalized unless there are major objections to
> it, I would like to start a disscussion on how do we best implament it. I
> see two possible ways to go with it.
>
> 1. We start fresh and write all new documentation Under the ALV2 license
> for 4.2.x and take what is currently on the mwiki for the 4.1.x series and
> convert it to Writer files and get it under version control if it is
> needed for a possible 4.1.9 Release.
>
> 2. Start with the already published 3.3 odt documents and upgrade those to
> version 4. This could require the work being done outside of the project
> made up of the people on doc@ do to the 3.3 docs being under what is
> considered a catagory X license and may not be able to be stored in an
> Apache repository.
>
> If we want to go with #2 there is a way around the possible repository
> problem.
>
> I hope that this will generate a lot of comment on how this should happen
> so that we as a group can move forward with creating professional quality
> documentation for the project.
>
> Regards
> Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 12/24/2020 12:47 AM, marcia wilbur wrote:
> I agree. I'm on it.
>
You are on what? What version of the software are you using as a base,
4.1.8, 4.2.0? What guide are you starting with; Getting Started, Writer,
calc, or something else? How are you going to share what you have
written to be reviewed by others?
All these questions need to be answered so that everyone knows who is
doing what and fir it to be a collaborative effort.
Regards
Keith
> ----- Original Message -----
> From: "Keith N. McKenna" <ke...@comcast.net>
> To: doc@openoffice.apache.org
> Sent: Sunday, December 20, 2020 5:23:11 PM
> Subject: Re: How We Implament the new Documentation Process
>
> On Sun, 20 Dec 2020 14:15:18 -0800, marcia wilbur wrote:
>
>> Hi.
>>
>> The LO docs not only have a dual license, but content includes multiple
>> Operating systems within the same document with screenshots for MS, Mac
>> and GNU Linux mixed up within. There would be significant clean up.
>>
>
> Hi Marcia;
>
> Given that and the definate problems with with using the 3.3 docs it is
> looking more and more like it is going to have to be start writing from
> scratch and go from there. Definitely going to be an uphill grind. Though
> this is the way to go in the long run, is going to be difficult unless we
> can attract more people to the team.
>
> I will investigate potential ways around the difficulties with the 3.3
> docs as well.
>
> If you have any other ideas now is the time to put them out.
>
> Regards
> Keith
>
>
> <snip>
>> ---------------------------------------------------------------------
>> 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: How We Implament the new Documentation Process
Posted by marcia wilbur <ai...@well.com>.
I agree. I'm on it.
----- Original Message -----
From: "Keith N. McKenna" <ke...@comcast.net>
To: doc@openoffice.apache.org
Sent: Sunday, December 20, 2020 5:23:11 PM
Subject: Re: How We Implament the new Documentation Process
On Sun, 20 Dec 2020 14:15:18 -0800, marcia wilbur wrote:
> Hi.
>
> The LO docs not only have a dual license, but content includes multiple
> Operating systems within the same document with screenshots for MS, Mac
> and GNU Linux mixed up within. There would be significant clean up.
>
Hi Marcia;
Given that and the definate problems with with using the 3.3 docs it is
looking more and more like it is going to have to be start writing from
scratch and go from there. Definitely going to be an uphill grind. Though
this is the way to go in the long run, is going to be difficult unless we
can attract more people to the team.
I will investigate potential ways around the difficulties with the 3.3
docs as well.
If you have any other ideas now is the time to put them out.
Regards
Keith
<snip>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On Sun, 20 Dec 2020 14:15:18 -0800, marcia wilbur wrote:
> Hi.
>
> The LO docs not only have a dual license, but content includes multiple
> Operating systems within the same document with screenshots for MS, Mac
> and GNU Linux mixed up within. There would be significant clean up.
>
Hi Marcia;
Given that and the definate problems with with using the 3.3 docs it is
looking more and more like it is going to have to be start writing from
scratch and go from there. Definitely going to be an uphill grind. Though
this is the way to go in the long run, is going to be difficult unless we
can attract more people to the team.
I will investigate potential ways around the difficulties with the 3.3
docs as well.
If you have any other ideas now is the time to put them out.
Regards
Keith
<snip>
> ---------------------------------------------------------------------
> 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: How We Implament the new Documentation Process
Posted by marcia wilbur <ai...@well.com>.
Hi.
The LO docs not only have a dual license, but content includes multiple Operating systems within the same document with screenshots for MS, Mac and GNU Linux mixed up within. There would be significant clean up.
----- Original Message -----
From: "Keith N. McKenna" <ke...@comcast.net>
To: doc@openoffice.apache.org
Sent: Saturday, December 19, 2020 2:56:46 PM
Subject: Re: How We Implament the new Documentation Process
On Sat, 19 Dec 2020 14:51:59 +0100, Arrigo Marchiori wrote:
> Hello Keith, All,
>
> I don't have any proposals at the moment, but one question:
>
> On Sat, Dec 19, 2020 at 12:27:20AM -0000, Keith N. McKenna wrote:
>
>> Greetings All;
>>
>> Now that the proposal is finalized unless there are major objections to
>> it, I would like to start a disscussion on how do we best implament it.
>> I see two possible ways to go with it.
>>
>> 1. We start fresh and write all new documentation Under the ALV2
>> license for 4.2.x and take what is currently on the mwiki for the 4.1.x
>> series and convert it to Writer files and get it under version control
>> if it is needed for a possible 4.1.9 Release.
>>
>> 2. Start with the already published 3.3 odt documents and upgrade those
>> to version 4. This could require the work being done outside of the
>> project made up of the people on doc@ do to the 3.3 docs being under
>> what is considered a catagory X license and may not be able to be
>> stored in an Apache repository.
>>
>> If we want to go with #2 there is a way around the possible repository
>> problem.
>
> I understand from your words that there are some issues with licensing
> but I cannot fully understand what is the problem. Could you please make
> it more explicit?
The old OpenOffice.org (ooo) documentation was duel licensed under either
the GNU General Public License or the Creative Commons Attribution
License, version 3.0 or later. Both are considered Catagory X licenses as
defined at: https://apache.org/legal/resolved.html#category-x. I believe
that this would mean that we can not have them in the projects repository
although I need to verify that.
>
> Did you also mention rewriting the docs for AOO 4.2 _from scratch_?
>
Yes I did. It was Item 2 in my initial post.
> I browsed through the archives of this ML until November 2017 but I
> could not find any information about this issue.
>
There was a heated discussion either on this list or one dev@When we were
first discussing documentation wheteher to continue using the then OOo
Authors ( the seperate project that did the original documentation) web
site and continuing with there lisences or starting from scratch on the
mwiki with new documentation under the ALV2 licenses which was what won
out.
> Thank you in advance and best regards,
Regards
Keith
---------------------------------------------------------------------
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: How We Implament the new Documentation Process
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On Sat, 19 Dec 2020 14:51:59 +0100, Arrigo Marchiori wrote:
> Hello Keith, All,
>
> I don't have any proposals at the moment, but one question:
>
> On Sat, Dec 19, 2020 at 12:27:20AM -0000, Keith N. McKenna wrote:
>
>> Greetings All;
>>
>> Now that the proposal is finalized unless there are major objections to
>> it, I would like to start a disscussion on how do we best implament it.
>> I see two possible ways to go with it.
>>
>> 1. We start fresh and write all new documentation Under the ALV2
>> license for 4.2.x and take what is currently on the mwiki for the 4.1.x
>> series and convert it to Writer files and get it under version control
>> if it is needed for a possible 4.1.9 Release.
>>
>> 2. Start with the already published 3.3 odt documents and upgrade those
>> to version 4. This could require the work being done outside of the
>> project made up of the people on doc@ do to the 3.3 docs being under
>> what is considered a catagory X license and may not be able to be
>> stored in an Apache repository.
>>
>> If we want to go with #2 there is a way around the possible repository
>> problem.
>
> I understand from your words that there are some issues with licensing
> but I cannot fully understand what is the problem. Could you please make
> it more explicit?
The old OpenOffice.org (ooo) documentation was duel licensed under either
the GNU General Public License or the Creative Commons Attribution
License, version 3.0 or later. Both are considered Catagory X licenses as
defined at: https://apache.org/legal/resolved.html#category-x. I believe
that this would mean that we can not have them in the projects repository
although I need to verify that.
>
> Did you also mention rewriting the docs for AOO 4.2 _from scratch_?
>
Yes I did. It was Item 2 in my initial post.
> I browsed through the archives of this ML until November 2017 but I
> could not find any information about this issue.
>
There was a heated discussion either on this list or one dev@When we were
first discussing documentation wheteher to continue using the then OOo
Authors ( the seperate project that did the original documentation) web
site and continuing with there lisences or starting from scratch on the
mwiki with new documentation under the ALV2 licenses which was what won
out.
> Thank you in advance and best regards,
Regards
Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org
Re: How We Implament the new Documentation Process
Posted by Arrigo Marchiori <ar...@yahoo.it.INVALID>.
Hello Keith, All,
I don't have any proposals at the moment, but one question:
On Sat, Dec 19, 2020 at 12:27:20AM -0000, Keith N. McKenna wrote:
> Greetings All;
>
> Now that the proposal is finalized unless there are major objections to
> it, I would like to start a disscussion on how do we best implament it. I
> see two possible ways to go with it.
>
> 1. We start fresh and write all new documentation Under the ALV2 license
> for 4.2.x and take what is currently on the mwiki for the 4.1.x series and
> convert it to Writer files and get it under version control if it is
> needed for a possible 4.1.9 Release.
>
> 2. Start with the already published 3.3 odt documents and upgrade those to
> version 4. This could require the work being done outside of the project
> made up of the people on doc@ do to the 3.3 docs being under what is
> considered a catagory X license and may not be able to be stored in an
> Apache repository.
>
> If we want to go with #2 there is a way around the possible repository
> problem.
I understand from your words that there are some issues with licensing
but I cannot fully understand what is the problem. Could you please
make it more explicit?
Did you also mention rewriting the docs for AOO 4.2 _from scratch_?
I browsed through the archives of this ML until November 2017 but I
could not find any information about this issue.
Thank you in advance and best regards,
--
rigo
http://rigo.altervista.org
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
For additional commands, e-mail: doc-help@openoffice.apache.org