Hi Nadeem, It looks like Keith has been restructuring the repo. If you click on the link to the commit that starts with 8928b59 (there is a link on the right just above the file names) you can see that the files were all moved into a single folder.
In case you cannot see the link. the URL is Move all files to Getting-Started-Guide · apache/openoffice-docs@8928b59 · GitHub <https://github.com/apache/openoffice-docs/commit/8928b59a4295ca79d5ee49ae40f9656be54c1f05> Please let me know if there is anything I can do to help you get started on something. I know it is hard to know where to start. There is no one to assign tasks, so a new person has to find something for themself or help with one of the few ongoing efforts.. I simply got copies of the user guides and started editing. Only a few people have edited any documentation lately, so you are unlikely to step on any toes. Francis On Wed, Jun 16, 2021 at 6:29 PM Nadeem Patel <nadeemp....@gmail.com> wrote: > Hello, > > I just wanted to follow up and get some clarification. When I go to > > https://github.com/apache/openoffice-docs/tree/Getting-Sarted-Guide/Getting-Started-Guide > , > I don't see a published and review folder. Am I missing something? > > Best, > > Nadeem > > > > > On Thu, Jun 3, 2021 at 4:19 PM Keith N. McKenna <keith.mcke...@comcast.net > > > wrote: > > > On 2021-06-02 14:05, F Campos Costero wrote: > > Greetings Francis and Comments in line. > > > > > 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. > > > > I apologize for that Francis. Some things in my personal life came up in > > mid-May that took a lot of my time. I am at this point back working on > > reviewing Chapter 4 of the getting started guide. > > Some new information on who the Copyright holder should be listed as on > > the copyright page. It should be The Apache Software Foundation.Also > > traditionally we follow the American English use headline style > > capitalization. Follow American English capitalization guidelines for > > headings. Capitalize the first letter of every word except conjunctions, > > articles, prepositions of fewer than four letters, and the "to" in > > infinitives. I am doing this as I review the the chapters of the > > Getting Started Guide. > > > > > 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. > > > > I am making some changes know that I believe will help with the process > > of review and merging. Instead of using review and release folders for > > each branch I am adding Guide Folders in Main that will always hold the > > currently published complete guide as well as the chapters.This should > > make the review and merge process much easier.I will make the changes in > > GitHub today. > > > > I am also going to create a how to contribute guide as well as some > > style guides, that will give some guidance on Heading styles and other > > things so that we create a consistent look and feel across the > > documentation we create. > > > > Regards > > Keith > > > > > > > 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 > > >>> > > >> > > > > > > >
