Keith, My impression is that everyone was waiting for you. I assume you have bounced your ideas off the PMC.
If you set up an off-ASF public GitHub project, there are a number of things you need to deal with. (I am assuming you can't do it on-ASF because it violates the rule about non-Apache licensing in a public ASF repository.) NOTE: You don't have to do this all at once, but there needs to be enough foresight in an initial organization being able to evolve. It would be useful to know what was sufficient for ODFAuthors to get work done. I Also think it is sensible to see how LibreOffice organized for successful production of user documentation. And check on the AOO Community Forum for interest and ideas. 1. There needs to be some degree of a governance structure. Nothing majestic, but enough for ground rules about usage and contribution to be understood. And there is the usual matter of granting commit rights and also how to handle push requests or other ways for folks to submit changes/contributions, etc. Because there is no merging with respect to binary content, collisions need a mechanism for resolution also. There might be designated editors. 2. There needs to be some organization for production. Probably with release tags and also migration to drafts, derivation of candidate versions of documents, and the creating of final flavors (the editable, any non-editable form such as PDF). Also, anywhere that web versions will be posted and how versioning works there. 3. An archive of the core base documents would be handy also. There might also be style guides, style sheets (template documents?), etc. That sort of thing might be grown into. 4. Jean Weber tends to prefer the ODFAuthors CC-BY and GPL dual licensing, although maybe that is mainly about her "Getting Started" book on AOO. That has to be nailed down at the beginning, because contributors need to know what licensing they are contributing under. I am interested in seeing this sort of thing work. I'm not an AOO committer and not interested in AOO dev these days. Given that, I can help at the outset. I still have an interest in documentation [;<). - Dennis -----Original Message----- From: Keith N. McKenna <keith.mcke...@comcast.net> Sent: Thursday, January 21, 2021 13:25 To: doc@openoffice.apache.org Subject: Re: Proposed Process for Documentation On 1/15/2021 1:01 AM, F Campos Costero wrote: > Keith - Have you looked into using Git with the odt file format. I did > a quick search and it seems that Git can only handle a plain text [orcmid] [ ... ] > > regards, > Francis > Yes I did. In fact all the revisions of the proposal were done using my GitHub account and it worked quite well. It will offer to open the binary file in the external application. You are correct that it does not handle a diff, but that is not why I was suggesting using it. It was simply as this is the version control system that the project has chosen to use and trying to implement anything different would require yet another VM for the project and the incumbent overhead of finding volunteers with the necessary skills to maintain it. As I am seeing no other comments from the documentation team I am planning on writing this attempt off as one more failure on my part. I will continue on my own to attempt to get a usable 4.1.x and 4.2.x Getting Started guide completed. Any help in getting these done will be greatly appreciated. Regards Keith > On Thu, Jan 14, 2021 at 10:26 AM Keith N. McKenna > <keith.mcke...@comcast.net> > wrote: > >> On 1/13/2021 6:17 PM, Dennis Hamilton wrote:
