Re: CC License on Externally-Produced Documentation

2021-01-31 Thread Keith N. McKenna
On 1/24/2021 5:54 PM, Andrea Pescetti wrote: > On 22/01/2021 Dennis Hamilton wrote: >> In the case of documentation projects and their repositories, the >> exception is not workable. > > Hello Dennis, nice to hear from you... it's been a while! > > I basically I agree to everything, but I go a bi

Re: CC License on Externally-Produced Documentation

2021-01-31 Thread Keith N. McKenna
On 1/25/2021 12:00 PM, Mike Cullen wrote: > Unsubscribe To unsubscribe send an e-mail to doc-unsubscribe. You will receive a reply that may end up in your spam folder so be sure to check there. click reply and you will receive a reply that you are unsubscribed, again be sure to check your spam fol

Re: CC License on Externally-Produced Documentation

2021-01-26 Thread Michael Reynolds
I do not work with your company On Fri, Jan 22, 2021, 2:33 PM Jean Weber wrote: > Dennis, > > Thank you for the clear explanation of the situation with regard to a > possible user-docs effort external to AOO itself and what needs to be done > if the group wants to move in that direction. > > If

Re: CC License on Externally-Produced Documentation

2021-01-25 Thread DaveB
There is nothing to discuss by the PMC or anyone else about having the documentation on an ASF-owned repository. This has been happening since AOO first came into existence see: https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT All of those are under GNU General

Re: CC License on Externally-Produced Documentation

2021-01-25 Thread Mike Cullen
Unsubscribe On Fri, Jan 22, 2021, 5:31 PM Dennis Hamilton wrote: > The TL;DR: Creating an external AOOAuthors GitHub project for deriving > documentation of current AOO releases is not difficult. Many of us could > do that. It just takes some minimal initial organization and agreement on > th

Re: CC License on Externally-Produced Documentation

2021-01-25 Thread F Campos Costero
How do we bring to a close the question of how to host the working texts? Should a thread be opened, perhaps on dev, to allow the PMC to express opinions and then vote on having the documentation on an ASF-owned repository? Francis On Sun, Jan 24, 2021 at 3:55 PM Andrea Pescetti wrote: > On 22

Re: CC License on Externally-Produced Documentation

2021-01-24 Thread Andrea Pescetti
On 22/01/2021 Dennis Hamilton wrote: In the case of documentation projects and their repositories, the exception is not workable. Hello Dennis, nice to hear from you... it's been a while! I basically I agree to everything, but I go a bit further in that I don't see a restriction on using an

Re: CC License on Externally-Produced Documentation

2021-01-22 Thread Jean Weber
Dennis, Thank you for the clear explanation of the situation with regard to a possible user-docs effort external to AOO itself and what needs to be done if the group wants to move in that direction. If I were 15 years younger (and not heavily involved in a different project), I’d volunteer to do

CC License on Externally-Produced Documentation

2021-01-22 Thread Dennis Hamilton
The TL;DR: Creating an external AOOAuthors GitHub project for deriving documentation of current AOO releases is not difficult. Many of us could do that. It just takes some minimal initial organization and agreement on the contributor mechanism, working languages, etc. At some point soon, t