Yes, it appears that GitHub Projects are amenable for managing workflow and coordinating the documentation. Ideally, you want Issues (because they can be tied into commit messages and vice versa), discussions (ditto), and Projects.
- Dennis -----Original Message----- From: Keith N. McKenna <keith.mcke...@comcast.net> Sent: Friday, February 5, 2021 13:07 To: doc@openoffice.apache.org Subject: Re: Repository Organization On 2/5/2021 3:10 PM, Dave wrote: > > 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. > That could work, the other thing I was thinking was checking with infra if GitHub projects can be used in our repository and using that to track who is doing what. Regards Keith > 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
