Good idea, The repository issues could be used for exactly that purpose, using tasks. By assigning the issue around, and by also using the issue comments to coordinate. (It is also possible to create issue templates.)
There is GitHub support for workflows and continuous integration. Applying that to documentation projects is unclear. -----Original Message----- From: Dave <b...@apache.org> Sent: Friday, February 5, 2021 12:11 To: doc@openoffice.apache.org Subject: Re: Repository Organization Would a Document/Chapter "Status" spreadsheet be a possible option? Whereby a contributor "checks out" a file they will be working on by updating the spreadsheet and updates again upon returning the file. On 05/02/2021 19:29, Dennis Hamilton wrote: > Oh. I would have thought the starting base documents would go in there > first. Under an OOo3.2 or something. > > How are Frances and Marcia avoiding collisions and/or duplication ? > > -----Original Message----- > From: Keith N. McKenna <keith.mcke...@comcast.net> > Sent: Friday, February 5, 2021 10:30 > To: doc@openoffice.apache.org > Subject: Re: Repository Organization > > [orcmid] [ ... ] > > Both Frances and Marcia are marking up possible changes to Jean's taming aoo > book and nothing is in the repository yet as it was just created a couple of > days ago. > > Regards > Keith --------------------------------------------------------------------- To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org For additional commands, e-mail: doc-h...@openoffice.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org For additional commands, e-mail: doc-h...@openoffice.apache.org
