2016-10-26 00:11:51 +00:00
|
|
|
ifdef::env-github[]
|
|
|
|
|
:tip-caption: :bulb:
|
|
|
|
|
:note-caption: :information_source:
|
|
|
|
|
:important-caption: :heavy_exclamation_mark:
|
|
|
|
|
:caution-caption: :fire:
|
|
|
|
|
:warning-caption: :warning:
|
|
|
|
|
endif::[]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
= Infrastructure Enhancement Proposals
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This repository is for tracking enhancement proposals to the
|
|
|
|
|
link:https://jenkins.io[Jenkins project's]
|
|
|
|
|
infrastructure. The goal of this repository is to collect and codify proposals
|
|
|
|
|
in a transparent and historically reviewable fashion. It can be thought of
|
|
|
|
|
similar to efforts such as the
|
|
|
|
|
link:http://www.ietf.org/rfc.html[IETF's RFC process]
|
|
|
|
|
or the Python project's
|
|
|
|
|
link:https://www.python.org/dev/peps/[PEPs].
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
= Creating a proposal
|
|
|
|
|
|
|
|
|
|
|
2016-10-26 00:22:45 +00:00
|
|
|
. Prepare an AsciiDoc file outlining your proposal, using requirement verbiage following
|
2016-10-26 00:11:51 +00:00
|
|
|
link:http://www.faqs.org/rfcs/rfc2119.html[RFC 2119]
|
2016-12-12 21:11:13 +00:00
|
|
|
and the directions from
|
|
|
|
|
link:https://github.com/jenkins-infra/iep/tree/master/iep-001[IEP-001].
|
|
|
|
|
. Copy `template.adoc` into the new `iep-xxx/` folder as `README.adoc`,
|
|
|
|
|
numbering the directory sequentially from the previous IEP.
|
|
|
|
|
. Write proposal
|
2016-10-26 00:22:45 +00:00
|
|
|
. Open a pull request.
|
