Convert all policies/*.html to .md

.gitignore

@@ -26,6 +26,11 @@ news/vulnerabilities*.inc
 news/vulnerabilities*.md
 news/*.html
 newsflash.inc
+policies/*.html
+policies/general/*.html
+policies/general/*.inc
+policies/technical/*.html
+policies/technical/*.inc
 source/*.gz*
 source/*.patch
 source/.htaccess

Makefile

@@ -63,10 +63,11 @@ H_TOP = $(addsuffix .html,$(basename $(shell git ls-files -- *.md)))
 H_COMMUNITY = $(addsuffix .html,\
                 $(basename $(shell git ls-files -- community/*.md)))
 H_NEWS = $(addsuffix .html,$(basename $(shell git ls-files -- news/*.md)))
-H_SUPPORT = $(addsuffix .html,$(basename $(shell git ls-files -- support/*.md)))
 H_POLICIES = $(addsuffix .html,\
-               $(basename $(shell git ls-files -- policies/general/*.md \
+               $(basename $(shell git ls-files -- policies/*.md \
+                                                  policies/general/*.md \
                                                   policies/technical/*.md)))
+H_SUPPORT = $(addsuffix .html,$(basename $(shell git ls-files -- support/*.md)))
 
 SIMPLE = $(H_TOP) \
 	 newsflash.inc \

policies/cla.md

@@ -0,0 +1,66 @@
+---
+breadcrumb: Contributor Agreements
+---
+# Contributor Agreements
+
+Every non-trivial contribution needs to be covered by a signed
+Contributor License Agreement (CLA) from all original authors. We have
+modelled our policy based on the practice of [the Apache Software
+Foundation](https://www.apache.org). You can see their CLA policy
+[here](https://www.apache.org/licenses/#clas). Our policy is:
+
+OpenSSL requires that all non-trivial contributors of ideas, code, or
+documentation complete, sign, and submit (via postal mail, fax or email)
+an [Individual Contributor License Agreement (ICLA)](openssl_icla.pdf).
+The purpose of this agreement is to clearly define the terms under which
+intellectual property has been contributed to OpenSSL and thereby allow
+us to defend the project should there be a legal dispute regarding the
+software at some future time.
+
+A submission is trivial if it is considered trivial under copyright law.
+Since we are not lawyers, we place the bar for trivial contributions
+very high. For example: corrections of grammatical or typographical
+errors (including misspelled function names in manual pages), simple
+whitespace changes and in some cases one-line bugfixes might be accepted
+as trivial without requiring a CLA.
+
+In practice, it is required that the author (in the git commit message)
+and all approving team members (in the pull request thread) agree that a
+change is trivial. The author has to add `CLA: trivial` in the commit
+message separated by an empty line from the rest of the message. The
+reviewers will normally post a statement to the effect of "I agree that
+it is a trivial change."
+
+*When filling in the CLA, please make sure that the email address
+matches the one that you use for the "Author" in your git commits.
+List multiple email addresses if necessary.*
+
+For a corporation that has assigned employees to work on OpenSSL, a
+[Corporate Contributor License Agreement (CCLA)](openssl_ccla.pdf) is
+available for contributing intellectual property via the corporation,
+that may have been assigned as part of an employment agreement. Note
+that a Corporate CLA does not remove the need for every developer to
+sign their own ICLA as an individual.
+
+If you have not already done so, please complete and sign a printout of
+the above ICLA (and CCLA if necessary), then scan and email a pdf file
+of the Agreement(s) to <legal@opensslfoundation.org>.
+
+If you prefer snail mail, send an original signed Agreement to the
+
+OpenSSL Software Foundation\
+40 East Main Street\
+Suite 744\
+Newark, DE 19711\
+United States
+
+Please read the document(s) carefully before signing and keep a copy for
+your records.
+
+Your Full name will be published unless you provide an alternative
+Public name. For example if your full name is Andrew Bernard Charles
+Dickens, but you wish to be known as Andrew Dickens, please enter the
+latter as your Public name. If you do not wish to have your name listed
+as a contributor, use *Anonymous*. We reserve the right to reject rude
+or obscene nick-names. The email address and other contact details are
+not published.

policies/general/index.md

@@ -1,5 +1,5 @@
 ---
-title: OpenSSL General Policies
+breadcrumb: OpenSSL General Policies
 ---
 These are the general policies and procedures established by the OMC.
 

policies/index.md

@@ -0,0 +1,46 @@
+---
+breadcrumb: Policies
+---
+# Policies
+
+In this section we try to document as many of our policies and
+procedures as possible. We do this for two reasons:
+
+-   First, we want to to make sure everyone knows how the project is run.
+    For example, when we announce a forthcoming fix for a high-severity bug,
+    the [Security Policy](general/security-policy.html) explains what that
+    means.
+-   Second, it helps us be consistent.
+    For example, the [Release Strategy](releasestrat.html) defines the plan
+    of record of when, and how long, various releases will be supported.
+
+By being as transparent as possible, we hope to reduce the chance that
+people are surprised by what we do, and we hope to help maintain
+predictable behavior within the project. This includes how spend some
+money, as detailed in the [travel reimbursement policy](travel.html).
+
+If you want to contribute code or fixes to the project, please read the
+[Coding Style](technical/coding-style.html) page. For legal obligations
+of contributors, see the page on [Contributor Agreements](cla.html). If
+you want to become a committer, make sure to also read our
+[Guidelines for Committers](general/committer-policy.html).
+
+The OpenSSL project is managed by the OpenSSL Management Committee
+(OMC), as defined by the [project bylaws](omc-bylaws.html). It is
+represented in most legal and formal capacities by the OpenSSL Software
+Foundation, a Delaware (US) non-profit corporation which has its own
+[bylaws](osf-bylaws.pdf) as a legal document. Signing one of our CLA's
+grants certain rights to OSF.
+
+In addition, the OMC establishes and maintains the [general policies](general/),
+and a [general glossary](glossary.html) of terms and what we mean with them.
+
+The technical aspects of the OpenSSL project are managed by the OpenSSL
+Technical Committee (OTC) which establishes and maintains the [technical
+policies](technical/) based on the project bylaws and the requirements
+specified by the OMC.
+
+We are pleased to mention that
+[we follow](https://bestpractices.coreinfrastructure.org/projects/54)
+the [best practices](https://bestpractices.coreinfrastructure.org) of the
+Core Infrastructure Initiative.