You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jeff Scheel 284b440273 Miscellaneous updates:
- Open 1.1 version (_pre2)
- Add the mailing list to the abstract
- Add support for starting a new local project
- Add "git init" workaround to Troubleshooting for JAR dependency on git.
- Move "Understanding" section forward in document.
- Clarify "Workgroup POM" terminology.
- Further cleanup of "Master Template" naming change to "Document Development Guide".
- Additional explanation about publishing of documents, including flow charts
- Add recommendation of installation of Croscore fonts in new Install fonts section
- Include a policy on document versioning
- Add examples of special docbook extensions available in our tooling
- Increase the number of levels of sections in the TOC

Signed-off-by: Jeff Scheel <scheel@us.ibm.com>
8 years ago
template Miscellaneous updates: 8 years ago
.gitignore Updated app_foundation.xml to use foundation doc public causeway urls. 9 years ago
LICENSE Initial source priming 9 years ago
README.md Update README.md 8 years ago
pom.xml Restructure Project to use Docs-Master Project 9 years ago

README.md

Master Template Document Project for OpenPOWER Foundation Documentation

This repository hold the source for the master document template for OpenPOWER Foundation. The PDF and HTML generated from the doc/template/ directory build a document that both describes how to build a new document and contains examples and directions on how to do it.

To build this project, one must ensure that the Docs-Master project has also been cloned at the same directory level as the Docs-Template project. This can be accomplished with the following steps:

  1. Clone the master documentation project (Docs-Master) using the following command:
$ git clone https://github.com/OpenPOWERFoundation/Docs-Master.git
  1. Clone this project (Docs-Template) using the following command:
$ git clone https://github.com/OpenPOWERFoundation/Docs-Template.git
  1. Build the project with these commands:
$ cd Docs-Template
$ mvn clean generate-sources

The online version of the document can be found in the OpenPOWER Foundation Document library at OpenPOWER Foundation Documentation Development Guide

The project which control the look and feel of the document is the Docs-Maven-Plugin project.

License

This project is licensed under the Apache V2 license. More information can be found in the LICENSE file or online at

http://www.apache.org/licenses/LICENSE-2.0

Contributions

To contribute to the OpenPOWER Foundation template document project, contact Jeff Scheel [scheel@us.ibm.com](mailto://scheel@us.ibm.com) or Jeff Brown [jeffdb@us.ibm.com](mailto://jeffdb@us.ibm.com).

Contributions to this project should conform to the Developer Certificate of Origin as defined at http://elinux.org/Developer_Certificate_Of_Origin. Commits to this project need to contain the following line to indicate the submitter accepts the DCO:

Signed-off-by: Your Name <your_email@domain.com>

By contributing in this way, you agree to the terms as follows:

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
660 York Street, Suite 102,
San Francisco, CA 94110 USA

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.