Anyone can fork the repo on GitHub. That's better for working in the open on the side of the project. Then work can be pushed (via pull request) to the Apache/openoffice-docs repo. Someone with authority over integration of requested pushes does the final integration. People can also review the pull request and comment on it before action is taken.
I don't recommend cloning the repository directly. You probably cannot sync directly to it. But you can clone from a fork to your computer, keep them synchronized as you make edits, and then push from the fork to the original when ready. There is a procedure for updating your fork from changes to the official repo. This is all a bit geeky. It comes with choosing to use git in the open. It works better with diff-able text files rather than ODF Packages [;<). - Dennis -----Original Message----- From: F Campos Costero <fjcc.apa...@gmail.com> Sent: Friday, February 5, 2021 12:22 To: doc@openoffice.apache.org Subject: Re: Repository Organization At the moment, I am only planning changes by inserting comments. Some of the images need to be updated, there are a few erroneous statements, and there are some out-of-date statements that should be revised or deleted. I hope to hold off on real editing until I see what Marcia has done, which she hopes to post tomorrow. She and I will have to coordinate, probably by chapter, if we will both be working on Taming. I had also thought of using a tracking document so people can record what they are working on. Most of the guides are available as standalone chapters, so one could have a reasonably granular view of the work in progress. I think all of the 3.3 user guides could be loaded in the repository at this point. I would be surprised if I can push to the repository or create branches, I have no official Apache status and I suppose random people are not allowed to do such things. Francis On Fri, Feb 5, 2021 at 1:10 PM Dave <b...@apache.org> 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. > > 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
