Hi Nadeem, Let's start with the Apache repo, (GitHub - apache/openoffice-docs: Apache OpenOffice Documentation <https://github.com/apache/openoffice-docs/tree/main>). To see the Getting Started files, you have to switch to the Getting-Sarted-Guide (sic) branch. There is a button fairly near the top of the screen with a drop down list that you can use to switch branches. It probably will say Main when you first access the site. When you change it to Getting-Sarted-Guide, you should see two folders: Published and Review. The documents in Published have been moved there by Keith. The documents in Review are as they were after I modified the originals and need to be reviewed. In the Review folder, you can click on, say, AOO41GS4.odt. That will take you to a new page with a Download button on the right side. Click that and you should get the document.
My repository has the same Review folder, though not all of the branches of the Apache repo, and you can also download from there. You just have to switch to the desired branch, as in the Apache repo. You could also just clone the whole repo onto your system. The procedure for editing has been rather clumsy so far. Dick Groskamp (user DiGro) downloaded the documents, made suggested changes while recording them (menu Edit -> Changes -> Record in Writer) and then emailed the document to me on my personal email, I then accepted the changes, made any other changes, and pushed the document to my repository. There has to be a better way to do that but Dick ran into problems pushing commits to my repository. Let's not worry about that at the moment. If you can just download a document, that will be a good start. I cannot make any changes on the Apache repo because I am not a commiter on the project. Keith has to handle everything on that repo. As for developing new content, you can certainly do that. What gets done on an Apache project is up to the volunteers and the only limits are the need to keep the project compatible with the Apache license other such legal requirements, e.g. don't violate trademarks or copyrights. Since the email is too long already, I will just mention two possible kinds of new content that span the range of possible documents. A few months ago, someone suggested writing some Quick Start materials. The Getting Started guide is about 300 pages and rather intimidating. That could probably be done relatively quickly. If you want to go big, there is no Base guide at all. That would probably be 300 pages and require knowing the Base application quite well. Francis On Wed, Jun 2, 2021 at 3:38 PM Nadeem Patel <nadeemp....@gmail.com> wrote: > Hello Francis, > > I can certainly help out with this. I would also like to help develop new > content if that is something you guys need. Feel free to bring Keith into > this conversation if you think that's best. I have used Git for past > projects. I would appreciate a breakdown of how to navigate around the > GitHub repo and how to go about the workflow. I only see four files and not > sure where and how to make edits/changes. Thanks! > > Best, > > Nadeem > > On Wed, Jun 2, 2021 at 1:05 PM F Campos Costero <fjcc.apa...@gmail.com> > wrote: > > > Hi Nadeem, > > What I have been working on for a while now is updating the user guides. > > The old guides are available at [1]. Keith has set up a Git repository > [2] > > where a branch is dedicated to each guide. I forked that repository [3] > and > > I have done initial revisions of the Getting Started guide and the Writer > > guide. I am slowly working my way through the Calc guide and I am about > > half done with that. As far as I know, only the first three chapters of > the > > Getting Started guide (A0041GS1.odt - A0041GS3.odt) have been reviewed by > > anyone else. If you are willing to jump into reviewing the other > chapters, > > there is plenty to do. Each guide is a few hundred pages and each chapter > > is typically 20 - 40 pages. > > The documentation process was dormant for quite a while and Keith has > been > > trying hard to revive it. We have just recently started to use Git and we > > may well have to change the process as we learn how to work with it. Are > > you familiar with Git? We only use the most basic features. > > If you are interested in helping with the guides, I can tell you more > about > > the workflow we have been using. If that isn't the kind of thing you were > > looking for, I am sure we can find something else. > > I would like to give Keith a chance to participate in this conversation. > > He has more experience with the broader documentation process than I do. > > > > Francis > > > > [1] > > > > > https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT > > [2] GitHub - apache/openoffice-docs: Apache OpenOffice Documentation > > <https://github.com/apache/openoffice-docs> > > [3] GitHub - FJCC/openoffice-docs: Apache OpenOffice Documentation > > <https://github.com/FJCC/openoffice-docs> > > > > On Tue, Jun 1, 2021 at 10:50 PM Nadeem Patel <nadeemp....@gmail.com> > > wrote: > > > > > I would like to add that I am interested in developing new content, > > > editing, proofreading, research or possibly even helping to create UML > > > diagrams. Thanks! > > > > > > On Tue, Jun 1, 2021 at 11:37 PM Nadeem Patel <nadeemp....@gmail.com> > > > wrote: > > > > > > > Hello, > > > > > > > > My name is Nadeem Patel. I came across the Apache OpenOffice > Community > > > and > > > > would love to contribute. I have been looking to build my > > > > documentation/technical writing portfolio while also improving the > > > > necessary skills for such writing. > > > > > > > > I graduated from Northwestern University, where I studied journalism > > and > > > > computer science. Currently, I am working as a digital producer at a > > > major > > > > news network while working on data science projects during my free > > time. > > > > The majority of my experiences include writing, development or both. > > > > Through this volunteering opportunity, I hope to continue utilizing > my > > > > skills and continue to build on my experiences. Thank you for your > time > > > and > > > > look forward to being involved! > > > > > > > > Best, > > > > > > > > Nadeem Patel > > > > > > > > > >
