incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From p...@apache.org
Subject [01/51] incubator git commit: Basic site using jbake, converted couple of guides.
Date Thu, 06 Jul 2017 00:20:32 GMT
Repository: incubator
Updated Branches:
  refs/heads/master fe67c80d0 -> 77571fe45


http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/pages/policy/incubation.ad
----------------------------------------------------------------------
diff --git a/pages/policy/incubation.ad b/pages/policy/incubation.ad
new file mode 100644
index 0000000..f6c2cdd
--- /dev/null
+++ b/pages/policy/incubation.ad
@@ -0,0 +1,256 @@
+= Incubation Policy
+Apache Incubator PMC
+2002-10-16
+:jbake-type: policy
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+In October 2002 the Board of Directors of the Apache Software Foundation passed a resolution
creating the Apache Incubator PMC (referred to as the "Incubator PMC" in this document) charged
with "accepting new products into the Foundation, providing guidance and support to help each
new product engender their own collaborative community, educating new developers in the philosophy
and guidelines for collaborative development as defined by the members of the Foundation,
and proposing to the board the promotion of such products to independent PMC status once their
community has reached maturity" (reference Board Resolution).
+
+The Incubator was tasked with the following responsibilities (reference Board Resolution):
+
+- the acceptance and oversight of new products submitted or proposed to become part of the
Foundation;
+- providing guidance and ensuring that subprojects under its purview develop products according
to the Foundation's philosophy and guidelines for collaborative development; and
+- regularly evaluating products under its purview and making the determination in each case
of whether the product should be abandoned, continue to receive guidance and support, or proposed
to the board for promotion to full project status as part of an existing or new Foundation
PMC; and be it further.
+
+== About this Document
+
+This document is the normative reference for the policies and procedures put in place by
the Incubator PMC for the Incubation process, which is used by the Incubator PMC to discharge
their duties as described above. It contains the minimum requirements that all new products
and projects must meet before they will be fully accepted into the Apache Software Foundation.
 The document makes use of the terms MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD
NOT, RECOMMENDED, MAY and OPTIONAL. Where capitalised, these terms are to be used as per the
definitions found in link:http://www.ietf.org/rfc/rfc2119.txt[RFC 2119].
+
+== Scope
+This document contains the minimum requirements and processes that must be met by products
and projects wishing to become part of the Apache Software Foundation.
+
+This document does not apply outside the process of Incubation. Policies and processes that
need to be met by products under incubation are not mandated (by this document) for other
projects and sub-projects within the ASF.
+
+== Relationship to Other Documents
+This document is the normative set of requirements for Incubation. Where other documents
are in conflict, this document should be taken as correct.
+
+== Changing this Document
+The contents of this document are formally approved by the Incubator PMC. All changes must
be authorised by the Incubator PMC.
+
+== Objectives of the Process
+To provide a clear path for potential projects and sub-projects within the ASF to move from
proposal stage through to fully membership in such as way as to ensure:
+- new projects and sub-projects are developing products according to the ASF's philosophy
and guidelines for collaborative development;
+- the ownership of any code initially submitted by the project is formally and legaly transferred
to the ASF; and
+- only those products that meet the Apache's requirements are fully accepted into the ASF.
+
+=== Overview of the Process
+The incubation process covers the establishment of a candidate, acceptance (or rejection)
of a candidate leading to the potential establishment of a Podling and associated incubation
process, which ultimately leads to the establishment or a new Apache Top-Level-Project (TLP)
or sub-project within an existing Apache Project.
+
+image::incubation-process.png[Incubation Process]
+
+== Entry to Incubation
+Please read the link:/guides/entry.html[guide] to the process in conjunction with this policy.
+
+In order to enter the Incubator, a Candidate MUST
+
+- be nominated for incubation by a member of the Apache Software Foundation (The Champion);
and
+- be approved by a Sponsor.
+
+=== Proposal
+To start the approval process, a proposal MUST be submitted to the Sponsor. Please read the
link:/guides/proposal.html(Guide For Proposals).
+
+=== Approval of Proposal by Sponsor
+The decision to approve the candidate proposal MUST be taken on a vote by the Sponsor, in
accordance with that Entity's charter.
+
+=== Acceptance By Incubator
+Upon a successful result, the PMC Chair of the Sponsor SHOULD request that the Incubator
PMC take on the Candidate as a new Podling.
+
+However when the Sponsor is the Incubator PMC, then they were the group of people who just
voted. So the normal vote summary is sufficient.
+
+Otherwise the Sponsor is an existing top-level project PMC, which now needs to notify the
Incubator PMC. The request, which should be sent to the Incubator PMC on the link:/howtoparticipate.html#Mailing+lists[general]
list, MUST contain the following information:
+
+- a reference to the results of the vote (so as to provide an audit trail for the records);
+- a reference to the Candidate's proposal;
+- the Mentors, nominated by the Sponsor, who will guide the Candidate through the Incubation
Process. At least one nominated Mentor MUST be a member of the Apache Software Foundation.
+
+Any Incubator PMC member can send an acknowledgement that the request was received, then
a 72 hour waiting period starts. After this time has elapsed and no Incubator PMC member objects,
the status file may be committed and the podling started.  If any Incubator PMC member says
"hold" before the 72 hours are up, a formal discussion/vote will be conducted.
+
+==== Acceptance of Mentors
+
+The nominated Mentors MAY be immediately accepted by the Incubator PMC. However the Incubator
PMC MAY also suggest replacement Mentors.  The Incubator PMC has the final choice of Mentors.
+
+=== Creation of Podling
+Upon acceptance by the Incubator PMC, the Candidate becomes a Podling under the care of the
Incubator PMC.
+
+Upon acceptance by the Incubator PMC, the Podling's Mentor becomes a member of the Incubator
PMC (should they not already be one).
+
+== Incubation Activities
+The following sections detail the minimum activities that must be undertaken by the various
parties during an Incuabation process.
+
+=== Setting Up a New Podling
+
+Once a proposal has been link:#acceptance_by_incubator[accepted] and the podling link:#creation_of_podling[created]
Mentor SHOULD initiate the creation of:
+
+- the link:/guides/mentor.html#Overview[podling metadata] and the reporting schedule;
+- the link:#ongoing_activities[project status] page;
+- the mailing lists;
+- the repository space;
+
+Your project's mentors are able to undertake many of the setup tasks. See link:/guides/mentor.html[the
mentor guide] for guidelines about the setup process.  See notes about how to https://www.apache.org/dev/infra-contact[request
project resources] such as new committer accounts and new mailing lists. (Note that a committer
account will not be created link:http://www.apache.org/dev/pmc.html#newcommitter[until the
Contributor License Agreement (CLA) has been recorded.]
+
+The source code that comes into the ASF as part of the podling project must pass through
the IP clearance process; details are in the mentor guide linked above.
+
+Your project committers/PPMC members need to become familiar with the link:http://www.apache.org/dev/#infrastructure[ASF
Infrastructure information] and in particular the link:http://www.apache.org/dev/#pmc[PMC]
notes. Also see the link:/guides/pmc.html[Incubator PMC Guide]
+
+=== Ongoing Activities
+The progress of a Podling SHALL be tracked in a "project status" document. This SHALL be
stored in http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ and so
become available at https://incubator.apache.org/projects/
+
+The "project status" document SHALL include the following minimum content :
+
+- status of setup tasks;
+- all exit criteria (see link:#Exiting_the_Incubator[Exiting the Incubator]);
+- status of Podling against exit criteria.
+
+The Mentors MUST ensure that the "project status" document is up to date at all times. See
these link:/guides/website.html#Edit+your+project+status+page[instructions].
+
+
+=== Review of Activity
+Each Podling in Incubation SHALL undergo a regular review of progress by the Incubator PMC.
Such reviews SHALL occur at least quarterly. The Incubator PMC MAY, at their discretion, choose
to review individual Podlings with greater frequency. The Incubator PMC SHALL inform Podlings
of review dates at least 4 weeks in advance.  At least one week prior to each review, the
Mentor MUST produce a report for the Incubator PMC detailing overall progress with a focus
on the preceding review period. It is RECOMMENDED that the report be based on the "project
status" document for the Podling.  After each review, the Incubator PMC SHALL produce an Assessment
of the project. The Assessment SHALL contain one of three recommendations:
+
+- that the Podling be Terminated;
+- that the Podling continue in Incubation; or
+- that the Podling be Graduated from Incubation.
+
+Termination and Graduation are discussed in more detail in section "Graduating from the Incubator".
+
+=== Disputing an Assessment
+If the Podling or Mentor disagree with an assessment, they MAY request the Incubator PMC
review the report. Such a request MUST include a details of what the Podling and/or Mentor
is disputing, and their reasons for doing so.  Upon receipt of an Assessment Dispute, the
Incubator PMC SHALL review the request and provide feedback to the Podling and Mentor. Such
feedback MAY include a change to the original Assessment.
+
+Should the Podling and/or Mentor still disagree with the contents of the report, they MAY
appeal to the Board of the Apache Software Foundation. Such an appeal MUST include
+
+- the original assessment;
+- the request for review to the Incubator PMC;
+- the response from the Incubator PMC; and
+- the reason the Podling and/or Mentor still dispute the report.
+
+The Board of the Apache Software Foundation MAY, after reviewing the appeal, choose to
+
+- ammend the incubation Assessment;
+- validate the assessment of the Incubator PMC; or
+- take any other action it deems appropriate to the circumstance.
+
+The decision of the Board of the Apache Software Foundation is final.
+
+=== Continuation
+A recommendation by the Incubator PMC for continuation of incubation SHALL include development
recommendations. The Incubator PMC SHALL ensure that the recommended actions are tangible
and quantifiable.
+The Mentor SHALL review the contents of the continuation recommendation and ensure that the
development recommendations are carried out over the following review period.
+
+== Podling Constraints
+While in Incubation, Podlings are constrained in the actions they can undertake.
+
+=== Branding
+Please consult the guide to link:/guides/branding.html[Podling Branding].
+
+=== Releases
+
+See the guidelines for link:/guides/releasemanagement.html[Podling releases] in conjunction
with this policy. Podlings are not yet fully accepted as part of the Apache Software Foundation.
No release made by a Podling will be endorsed by the ASF.  Unendorsed releases may be made
by Podlings subject to the following policy. Podlings in Incubation SHALL NOT perform any
releases of software without the explicit approval of the Incubator PMC. Such approval SHALL
be given only after the Incubator PMC has followed the process detailed in these guidelines,
and SHALL NOT occur until all source has been legally transferred to the ASF. Therefore, should
a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's
public dev list. At least three +1 votes are required (see the http://www.apache.org/foundation/voting.html[Apache
Voting Process] page). If the majority of all votes is positive, then the Podling SHALL send
a summary of that vote to the Incubator's
  link:/howtoparticipate.html#Mailing+lists[general] list and formally request the Incubator
PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example
showing how an incubating project managed this process:
+
+- link:++http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43C1C0A0.7040401@roguewave.com%3e++[Post
to the Podling dev list calling the vote.]
+- link:++http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/%3c43D7AC9E.30205@roguewave.com%3e++[Post
to the Incubator's general list requesting approval from the Incubator PMC.]
+
+Should the Incubator PMC, in accordance with these guidelines vote to approve the request,
the Podling MAY perform the release under the following constraints:
+
+- the release archive MUST contain the word "incubating" in the filename; and
+- the release archive MUST contain an Incubation disclaimer (as described in the previous
section), clearly visible in the main documentation or README file.
+
+Releases for *podling* MUST be distributed through *++http://www.apache.org/dist/incubator/++_podling_*
In addition, the Podling MAY choose to distribute approved releases through other channels
like the central Maven repository.
+
+=== Use of Apache Resources
+The Podling is not yet an Apache project, and it should thus always
+refer to the Incubator Project Resource usage Guidelines, that are as
+follows.
+
+=== Website
+Please consult the guide to link:/guides/sites.html[Podling Websites] for the current policies
for websites.
+
+== Graduating from the Incubator
+This section describes the requirements and process for graduating from the Incubator.
+
+=== Minimum Graduation Requirements
+Prior to graduation, a Podling needs to show that :
+
+- it is a worthy and healthy project;
+- it truly fits within the ASF framework;and
+- it "gets" the Apache Way.
+
+This is achieved by imposing a set of Graduation Criteria that, when met,
+will demonstrate these objectives.
+
+Therefore, to successfully graduate from the Incubator
+into the ASF, a Podling SHALL meet the minimum requirements
+detailed below. The Incubator PMC MAY set additional requirements at
+their discretion. Such additional requirements MAY be proposed by the
+Mentor or the Sponsor, however only the Incubator PMC is authorised
+to formally place such requirements on a Podling.
+
+The minimum requirements that a Podling SHALL meet prior to being
+graduated to the ASF are :
+
+==== Legal
+- All code AL'ed
+- The code base must contain only ASL or ASL-compatible dependencies
+- License grant complete
+- CLAs on file.
+- Check of project name for trademark issues
+
+==== Meritocracy / Community
+
+- Demonstrate an active and diverse development community
+- The project is not highly dependent on any single contributor (there are at least 3 legally
independent committers and there is no single company or entity that is vital to the success
of the project)
+- The above implies that new committers are admitted according to ASF practices
+- ASF style voting has been adopted and is standard practice
+- Demonstrate ability to tolerate and resolve conflict within the community.
+- Release plans are developed and excuted in public by the community.
+- Engagement by the incubated community with the other ASF communities
+
+==== Votes
+- Incubator PMC has voted for graduation
+- Destination PMC, or ASF Board for a TLP, has voted for final acceptance
+
+==== Alignment / Synergy
+- Use of other ASF subprojects
+- Develop synergistic relationship with other ASF subprojects
+
+==== Infrastructure
+- SVN module has been created
+- Mailing list(s) have been created
+- Mailing lists are being archived
+- Issue tracker has been created
+- Project website has been created and complies with the Apache Project Branding Requirements
+- Project ready to comply with ASF mirroring guidelines
+- Project is integrated with GUMP if appropriate
+- Releases are PGP signed by a member of the community
+- Developers tied into ASF PGP web of trust
+
+=== Termination of a Podling
+If you receive a recommendation for termination then you have a
+problem. Chances are that there are either legal or structural
+problems with your project that in the opinion of the Incubator PMC
+are not resolvable within a reasonable time frame. A termination
+decision is basically time to close down the project. However, you do
+have the right to appeal a termination decision with the Board of
+Directors and/or your Sponsor. You should be aware that several
+Members of the Board are also Members of the Incubator PMC and as
+such, an appeal is unlikely to be successful.
+
+=== Graduation as a Top Level Project
+In cases where a Podling has successfully completed Incubation, and
+is graduating from the Incubator to become a Top Level Project, the Incubator
+PMC SHALL provide a recommendation to the board that the Podling is
+ready to gradualate. The recommendation SHALL include a draft
+resolution for the board to vote on.
+
+=== Graduation as a sub-project
+In cases where a Podling has successfully completed Incubation, and
+is graduating from the Incubator to become a sub-project within an already
+existing Top Level Project, the Incubator PMC SHALL provide a
+recommendation to the TLP that the Podling is ready to graduate.
+
+=== Post-Graduation Check List
+See link:/guides/graduation.html[Graduation Guide].
+
+== Roles Defined
+Definitions of the roles involved in the Incubation process can be found on the link:/incubation/Roles_and_Responsibilities.html[Roles
and Responsibilities] page.

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/pages/policy/process.ad
----------------------------------------------------------------------
diff --git a/pages/policy/process.ad b/pages/policy/process.ad
new file mode 100644
index 0000000..614cc2b
--- /dev/null
+++ b/pages/policy/process.ad
@@ -0,0 +1,73 @@
+= Incubation Process
+Apache Incubator PMC
+2002-10-16
+:jbake-type: policy
+:jbake-status: published
+:idprefix:
+:toc:
+:imagesdir: ../images/
+
+== Introduction
+This document is an overview of the process. Read it in conjunction with the "Incubation
Policy" and the various guides. Also review the Roles and Responsibilities for a description
of the various parties involved in the Incubation process.
+
+== The Process of Incubation
+The incubation process covers the establishment of a candidate, acceptance (or rejection)
of a candidate leading to the potential establishment of a Podling and associated incubation
process, which ultimately leads to the establishment or a new Apache Top-Level-Project (TLP)
or sub-project within an existing Apache Project.
+
+image::incubation-process.png[]
+
+== Establishment
+image::howtoincubateaproject.png[]
+The first thing you will want to do is find a Champion for your project. One way to do this
is to explore the existing Apache projects to find similar projects. Spend some time reading
their project web pages and mailing lists (follow links at each project website). By simply
lurking on the project mailing lists (and also the Incubator general list and other Incubating
project lists) you may get ideas about who you would like to contact directly to help you
with your project proposal.
+
+Simply email that person directly (e.g. username@apache.org, see the committer list to find
the username), describe informally yourselves and your project, and ask kindly if she would
be willing to act as your Champion for your project within the Apache incubator. Remember
that all Apache Committers and Members are volunteers with limited spare time, but you will
hopefully find that the person is honoured by your request to be a Champion and sees a potential
for your project as a future Apache project.
+
+Once you have found an eligible person who is willing to act as Champion, you can use this
person to help you determine if and how your proposal can fit within the ASF, and if the "Apache
Way" of open development would be right for your project. This might happen over a series
of emails, telephone calls or online chat sessions, and should cover any practical concerns
such as project infrastructure (e.g. mailing lists, web, source code repositories, issue tracker,
wiki) but also the implications of licensing, governance and Intellectual Property management.
+
+If you and your Champion are convinced that your candidate project would fit with the "Apache
Way", your Champion can help you to get it established.
+
+The establishment of a candidate involves the preparation of a Project Proposal (consistent
with the candidate description detailed below) endorsed by a Champion.
+
+A Candidate project description should be submitted to the relevant mailing list(s) of a
Sponsor. The Sponsor is usually the Incubator (IPMC), (general@incubator.apache.org), assuming
your project would aspire to become a top-level project (TLP). In the special case of your
project aspiring to become a sub-project of an existing Apache top-level project (e.g. a plugin
for Apache OpenOffice), then that project should be your champion and their dev@ mailing list
would be where to send the proposal first.
+
+Please see:
+
+- a Guide to Proposal Creation
+- existing project proposals for examples
+- Typically a Candidate is submitted under a message tagged with [PROPOSAL]. Such a message
will normally trigger some discussions on the receiving mailing list(s). Your Champion will
be involved in these discussions acting as your advocate.
+
+As a proposer you should consider the feedback and attempt to gauge a sense of consensus.
Do not be put off by extended threads under your initial post that have little or nothing
to do with your proposal - however, if you feel that your candidate project is not being addressed,
you may want to specifically request a decision on the Candidate by the Sponsor. Sometimes
a vote will be announced without you asking for it (perhaps you have done some homework and
have a PMC member assisting you though the process), other times you may need to cut through
discussions and push your request forward for a decision.
+
+== Acceptance
+The decision to accept a project is taken on a vote by the Sponsor. The format of this vote
will depend on the rules of the entity in question. Here again it helps if you have a PMC
Member (or board member if the Sponsor is the ASF board) aligned with your project (preferably
as your Champion) because you stand a better chance of getting feedback about what is actually
happening. The Sponsor will typically take about 7-10 days before announcing a vote result.
+
+If that vote is affirmative, the Sponsor (unless the Sponsor is already the Incubator PMC)
will propose to the Incubator PMC(referencing the voting result e-mail) that your candidate
project be accepted by the Incubator as a Podling. The Sponsor will assign Mentors. The Mentors
may include your original Champion. If not, it is expected your Champion will remain involved
during the rest of the Incubation process, providing as much assistance as possible.
+
+The Mentors are there to protect you, but be warned - Mentors are holding a big stick. The
Mentors are members of the Incubator PMC, and report to both the PMC and the Sponsor about
your overall health and suitability for eventual inclusion within the Apache Community (or
recommendation to terminate). However, the Mentors (with the assistance of the Champion) are
also looking after you through the incubation.
+
+One of the roles of the Mentors is to keep away the wolves - and in the case of incubation
the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy and delays.
The Mentors can help you by guiding and protecting you from much of this based on their experience
in the process and familiarity with the policy and procedures of incubation. In performing
their role, the Mentors are representing the Sponsor.
+
+Your Sponsor, represented by your Mentors, has specific responsibilities towards you and
the Incubator PMC. There are a bunch of administrative and technical actions to take care
of. Your Mentors are responsible for ensuring that these things happen quickly and efficiently.
Also, your Mentors are going to help you out with the getting in place of the policies and
procedures you use for introducing new comitters, decision making, etc. These aspects will
be watched closely by the Incubator PMC as they provide a good indication of community dynamics,
health and correlation with Apache practices.
+
+== Review
+As your project sorts things out and things stabilize (infrastructure, communications, decision
making) you will inevitably come under an assessment by the Incubator PMC concerning the exit
of your project from the incubator. Keep in mind that exit can be a good thing and bad thing.
Exit via graduation to a top-level project or perhaps a subproject of an existing PMC would
typically be viewed as a positive exit. On the other-hand, termination is also an exit condition
that may be considered. With an upcoming assessment it is generally a good idea to have your
STATUS file right up to-date and to ensure that your Mentor is doing his/her job of evangelizing
your project and has good picture of where you are relative to acceptance or the last assessment
point. This information will help the Incubator PMC to recommend the best action for your
project.
+
+Conclusion of a review process will be a recommendation (to the Sponsor) of one of the following:
+
+- termination;
+- continuation under incubation with recommendations; or
+- graduation into Apache.
+
+Note that whilst this is a recommendation, it carries a lot of weight. A Sponsor will only
over-ride the recommendation of the Incubator in exceptional circumstances, and even then
it is likely that the issue in question would be escalated to the ASF board for their consideration.
+
+== Termination or Retirement
+There are two ways for a project to cease incubation: Termination or Retirement. If you receive
a recommendation for termination then you have a problem. Chances are that there are either
legal or structural problems with your project that in the opinion of the Incubator PMC are
not resolvable within a reasonable time frame. A termination decision is basically time to
close down the project. However, you do have the right to appeal a termination decision with
the Board of Directors and/or your Sponsor. You should be aware that several Members of the
Board are also Members of the Incubator PMC and as such, an appeal is unlikely to be successful.
Retirement is typically an internal decisions by PPMC. A retired project is a project which
has been closed down by the PPMC or by the IPMC for various reasons. It is not longer developed
at the Apache Incubator and does not have any other duties. Retirement can also be suggested
by IPMC on the grounds of lack of releases for more than a year
 . However, since unlike termination, retirement is a voluntary process, the suggestion will
have to be discussed and voted upon. It's important to view this process as being the retirement
of the podling community, not the code. It should not be implied that the code is not for
use - just that it has no community. The source code of a retired project is available in
ASF repository, when the copyright requirements are fullfilled. This is indicated through
the incubator status page. For more details on Retirement please see our Guide to Retirement
+
+== Continuation
+A recommendation by the Incubator PMC for continuation of incubation shall include development
recommendations. The Incubator PMC has a responsibility to ensure that the recommended actions
are tangible and quantifiable. For example, an assessment could be that your project has not
established a sufficient community to be viable, in which case the Incubator PMC is obliged
to state specific targets that they consider as viable. This does not necessarily mean that
if you meet this target by the next review that you are out of incubation - but it does give
you concrete achievements that you can cite. Your Mentor is also specifically accountable
to you for ensuring that the recommendations for continuation are usable, substantive and
tangible. If this is not the case, you have every right to appeal an Incubator decision to
the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios
should arise.
+
+== Graduation
+For Podlings that aim to establish sub-projects or products within existing communities you
are almost home-free. The main issues you need to deal with now is migration of your code
into the target project, something you should be confident in doing based on the contacts
and understanding you gained during initial establishment and incubation.
+
+For projects aiming to be a Top-Level-Project (TLP), you have an additional obstacle, namely
the ASF Board. While the ASF Board might be your Sponsor, this does not mean they have formally
accepted you as a TLP. To establish a TLP you need to draft a board motion that identifies
the project scope, mission and charter. You can submit the motion to the Board using the board
at apache dot org email address. Well-prepared projects will have already developed contacts
with members of the Board so this should not be a surprise agenda item. Keep in mind that
the Board can approve your motion as supplied, amend it, or reject it. If you are rejected
then you need to sort this out with the Incubator PMC and allies you have developed during
the incubation process. In other words, for a TLP objective the Incubator PMC okay is only
half of the story.
+
+However, in practice, assuming you are building contacts with members in Apache, the Incubator
PMC, and the ASF Board, the transition from Podling to TLP should be a smooth and painless
process.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/archive.gsp
----------------------------------------------------------------------
diff --git a/templates/archive.gsp b/templates/archive.gsp
new file mode 100644
index 0000000..59fe96f
--- /dev/null
+++ b/templates/archive.gsp
@@ -0,0 +1,28 @@
+<%include 'header.gsp'%>
+
+	<%include 'menu.gsp'%>
+	
+	<div class="page-header">
+		<h1>Blog Archive</h1>
+	</div>
+	
+	<!--<ul>-->
+		<%def last_month=null;%>
+		<%published_posts.each {post ->%>
+			<%if (last_month) {%>
+				<%if (new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)
!= last_month) {%>
+					</ul>
+					<h4>${new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)}</h4>
+					<ul>
+				<%}%>
+			<% } else { %>
+				<h4>${new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)}</h4>
+				<ul>
+			<% }%>
+			
+			<li>${post.date.format("dd")} - <a href="${content.rootpath}${post.uri}">${post.title}</a></li>
+			<%last_month = new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)%>
+		<%}%>
+	</ul>
+	
+<%include "footer.gsp"%>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/feed.gsp
----------------------------------------------------------------------
diff --git a/templates/feed.gsp b/templates/feed.gsp
new file mode 100644
index 0000000..d587ac3
--- /dev/null
+++ b/templates/feed.gsp
@@ -0,0 +1,25 @@
+<% import static groovy.xml.XmlUtil.escapeXml %><?xml version="1.0"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>JBake</title>
+    <link>${config.site_host}</link>
+    <atom:link href="${config.site_host}/${config.feed_file}" rel="self" type="application/rss+xml"
/>
+    <description>JBake Bootstrap Template</description>
+    <language>en-gb</language>
+    <pubDate>${new java.text.SimpleDateFormat("EEE, d MMM yyyy HH:mm:ss Z", Locale.ENGLISH).format(published_date)}</pubDate>
+    <lastBuildDate>${new java.text.SimpleDateFormat("EEE, d MMM yyyy HH:mm:ss Z", Locale.ENGLISH).format(published_date)}</lastBuildDate>
+
+    <%published_posts.each {post -> %>
+    <item>
+      <title>${post.title}</title>
+      <link>${config.site_host}/${post.uri}</link>
+      <pubDate>${new java.text.SimpleDateFormat("EEE, d MMM yyyy HH:mm:ss Z", Locale.ENGLISH).format(post.date)}</pubDate>
+      <guid isPermaLink="false">${post.uri}</guid>
+      <description>
+      ${escapeXml(post.body)}
+	  </description>
+    </item>
+    <%}%>
+
+  </channel> 
+</rss>

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/footer.gsp
----------------------------------------------------------------------
diff --git a/templates/footer.gsp b/templates/footer.gsp
new file mode 100644
index 0000000..97cd685
--- /dev/null
+++ b/templates/footer.gsp
@@ -0,0 +1,19 @@
+		</div>
+		<div id="push"></div>
+    </div>
+    
+    <div id="footer">
+      <div class="container">
+        <p class="muted credit">&copy; 2014 | Mixed with <a href="http://getbootstrap.com/">Bootstrap
v3.1.1</a> | Baked with <a href="http://jbake.org">JBake ${version}</a></p>
+      </div>
+    </div>
+    
+    <!-- Le javascript
+    ================================================== -->
+    <!-- Placed at the end of the document so the pages load faster -->
+    <script src="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>js/jquery-1.11.1.min.js"></script>
+    <script src="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>js/bootstrap.min.js"></script>
+    <script src="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>js/prettify.js"></script>
+    
+  </body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/guide.gsp
----------------------------------------------------------------------
diff --git a/templates/guide.gsp b/templates/guide.gsp
new file mode 100644
index 0000000..2d677bd
--- /dev/null
+++ b/templates/guide.gsp
@@ -0,0 +1,11 @@
+<%include "header.gsp"%>
+
+<%include "menu.gsp"%>
+
+<div class="page-header">
+    <h1>Guide :: ${content.title}</h1>
+</div>
+
+<p>${content.body}</p>
+
+<%include "footer.gsp"%>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/header.gsp
----------------------------------------------------------------------
diff --git a/templates/header.gsp b/templates/header.gsp
new file mode 100644
index 0000000..be4d7b6
--- /dev/null
+++ b/templates/header.gsp
@@ -0,0 +1,32 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8"/>
+    <title><%if (content.title) {%>${content.title}<% } else { %>Apache
Incubator<% }%></title>
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <meta name="description" content="">
+    <meta name="author" content="">
+    <meta name="keywords" content="">
+    <meta name="generator" content="JBake">
+
+    <!-- Le styles -->
+    <link href="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>css/bootstrap.min.css" rel="stylesheet">
+    <link href="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>css/asciidoctor.css" rel="stylesheet">
+    <link href="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>css/base.css" rel="stylesheet">
+    <link href="<%if (content.rootpath) {%>${content.rootpath}<% } else { %><%
}%>css/prettify.css" rel="stylesheet">
+
+    <!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
+    <!--[if lt IE 9]>
+      <script src="<%if (content.rootpath) {%>${content.rootpath}<% } else {
%><% }%>js/html5shiv.min.js"></script>
+    <![endif]-->
+
+    <!-- Fav and touch icons -->
+    <!--<link rel="apple-touch-icon-precomposed" sizes="144x144" href="../assets/ico/apple-touch-icon-144-precomposed.png">
+    <link rel="apple-touch-icon-precomposed" sizes="114x114" href="../assets/ico/apple-touch-icon-114-precomposed.png">
+    <link rel="apple-touch-icon-precomposed" sizes="72x72" href="../assets/ico/apple-touch-icon-72-precomposed.png">
+    <link rel="apple-touch-icon-precomposed" href="../assets/ico/apple-touch-icon-57-precomposed.png">-->
+    <link rel="shortcut icon" href="<%if (content.rootpath) {%>${content.rootpath}<%
} else { %><% }%>favicon.ico">
+  </head>
+  <body onload="prettyPrint()">
+    <div id="wrap">
+   
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/index.gsp
----------------------------------------------------------------------
diff --git a/templates/index.gsp b/templates/index.gsp
new file mode 100644
index 0000000..0c86535
--- /dev/null
+++ b/templates/index.gsp
@@ -0,0 +1,29 @@
+<%include "header.gsp"%>
+
+	<%include "menu.gsp"%>
+
+<h1>About the Apache Incubator</h1>
+The Incubator project is the entry path into The Apache Software Foundation (ASF) for projects
and codebases wishing to become part of the Foundation's efforts. All code donations from
external organisations and existing external projects wishing to join Apache enter through
the Incubator.
+
+The Apache Incubator has two primary goals:
+<ul>
+    <li>Ensure all donations are in accordance with the ASF <a href="http://www.apache.org/licenses/">legal
standards</a></li>
+    <li>Develop new communities that adhere to our <a href="http://www.apache.org/foundation/how-it-works.html">guiding
principles</a></li>
+</ul>
+See also the <a href="http://www.youtube.com/watch?v=KopPbWS87fw">Life In The Apache
Incubator video</a>, where former Incubator PMC chair Jukka Zitting presents the Incubator,
at ApacheCon EU 2012.
+
+<h2>About The Apache Software Foundation</h2>
+The Apache Software Foundation provides organizational, legal, and financial support for
a broad range of open source software projects. The Foundation provides an established framework
for intellectual property and financial contributions that simultaneously limits the potential
legal exposure for the contributors. Through a collaborative and meritocratic development
process, Apache projects deliver enterprise-grade, freely available software products that
attract large communities of users. The pragmatic Apache License makes it easy for all users,
commercial and individual, to deploy Apache products.
+
+<br/><br/>
+You can find out <a href="http://www.apache.org/foundation/">more about the ASF</a>.
+<br/><br/>
+<ul>
+<%
+	def rootNode = new groovy.util.XmlSlurper().parse(new java.io.File("pages/podlings.xml"))
+%>
+<%rootNode.children().each {podling -> %>
+<li>${podling.@name}</li>
+<%}%>
+</ul>
+<%include "footer.gsp"%>

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/menu.gsp
----------------------------------------------------------------------
diff --git a/templates/menu.gsp b/templates/menu.gsp
new file mode 100644
index 0000000..5f5bceb
--- /dev/null
+++ b/templates/menu.gsp
@@ -0,0 +1,38 @@
+	<!-- Fixed navbar -->
+    <div class="navbar navbar-default navbar-fixed-top" role="navigation">
+      <div class="container">
+        <div class="navbar-header">
+          <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+            <span class="sr-only">Toggle navigation</span>
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+          </button>
+          <a class="navbar-brand" href="<%if (content.rootpath) {%>${content.rootpath}<%
} else { %><% }%>">Apache Incubator</a>
+        </div>
+        <div class="navbar-collapse collapse">
+          <ul class="nav navbar-nav">
+            <li><a href="<%if (content.rootpath) {%>${content.rootpath}<%
} else { %><% }%>index.html">Home</a></li>
+            <li><a href="<%if (content.rootpath) {%>${content.rootpath}<%
} else { %><% }%>about.html">About</a></li>
+            <li><a href="<%if (content.rootpath) {%>${content.rootpath}<%
} else { %><% }%>${config.feed_file}">Subscribe</a></li>
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">Policies <b
class="caret"></b></a>
+              <ul class="dropdown-menu">
+                <%policys.each {policy -> %>
+                  <li><a href="${config.site_host}/${policy.uri}">${policy.title}</a></li>
+                <%}%>
+              </ul>
+            </li>
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">Guides <b
class="caret"></b></a>
+              <ul class="dropdown-menu">
+                <%guides.each {guide -> %>
+                  <li><a href="${config.site_host}/${guide.uri}">${guide.title}</a></li>
+                <%}%>
+              </ul>
+            </li>
+          </ul>
+        </div><!--/.nav-collapse -->
+      </div>
+    </div>
+    <div class="container">
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/page.gsp
----------------------------------------------------------------------
diff --git a/templates/page.gsp b/templates/page.gsp
new file mode 100644
index 0000000..44936a8
--- /dev/null
+++ b/templates/page.gsp
@@ -0,0 +1,15 @@
+<%include "header.gsp"%>
+
+	<%include "menu.gsp"%>
+	
+	<div class="page-header">
+		<h1>${content.title}</h1>
+	</div>
+
+	<p><em>${new java.text.SimpleDateFormat("dd MMMM yyyy", Locale.ENGLISH).format(content.date)}</em></p>
+
+	<p>${content.body}</p>
+
+	<hr />
+
+<%include "footer.gsp"%>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/policy.gsp
----------------------------------------------------------------------
diff --git a/templates/policy.gsp b/templates/policy.gsp
new file mode 100644
index 0000000..3608589
--- /dev/null
+++ b/templates/policy.gsp
@@ -0,0 +1,11 @@
+<%include "header.gsp"%>
+
+<%include "menu.gsp"%>
+
+<div class="page-header">
+    <h1>${content.title}</h1>
+</div>
+
+<p>${content.body}</p>
+
+<%include "footer.gsp"%>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/post.gsp
----------------------------------------------------------------------
diff --git a/templates/post.gsp b/templates/post.gsp
new file mode 100644
index 0000000..f7fb4f8
--- /dev/null
+++ b/templates/post.gsp
@@ -0,0 +1,15 @@
+<%include "header.gsp"%>
+	
+	<%include "menu.gsp"%>
+	
+	<div class="page-header">
+		<h1>${content.title}</h1>
+	</div>
+
+	<p><em>${new java.text.SimpleDateFormat("dd MMMM yyyy", Locale.ENGLISH).format(content.date)}</em></p>
+
+	<p>${content.body}</p>
+
+	<hr />
+	
+<%include "footer.gsp"%>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/sitemap.gsp
----------------------------------------------------------------------
diff --git a/templates/sitemap.gsp b/templates/sitemap.gsp
new file mode 100644
index 0000000..ffecd25
--- /dev/null
+++ b/templates/sitemap.gsp
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
+<%published_content.each {content -> %>
+    <url>
+    	<loc>${config.site_host}/${content.uri}</loc>
+    	<lastmod>${content.date.format("yyyy-MM-dd")}</lastmod>
+    </url>
+<%}%>
+</urlset>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator/blob/dd598af5/templates/tags.gsp
----------------------------------------------------------------------
diff --git a/templates/tags.gsp b/templates/tags.gsp
new file mode 100644
index 0000000..cdec2e6
--- /dev/null
+++ b/templates/tags.gsp
@@ -0,0 +1,28 @@
+<%include "header.gsp"%>
+
+	<%include "menu.gsp"%>
+	
+	<div class="page-header">
+		<h1>Tag: ${tag}</h1>
+	</div>
+	
+	<!--<ul>-->
+		<%def last_month=null;%>
+		<%tag_posts.each {post ->%>
+		<%if (last_month) {%>
+			<%if (new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)
!= last_month) {%>
+				</ul>
+				<h4>${new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)}</h4>
+				<ul>
+			<%}%>
+		<%} else {%>
+			<h4>${new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)}</h4>
+			<ul>
+		<%}%>
+		
+		<li>${post.date.format("dd")} - <a href="${content.rootpath}${post.uri}">${post.title}</a></li>
+		<% last_month = new java.text.SimpleDateFormat("MMMM yyyy", Locale.ENGLISH).format(post.date)%>
+		<%}%>
+	</ul>
+	
+<%include "footer.gsp"%>
\ No newline at end of file


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message