diff --git a/config.toml b/config.toml
index 0557e333d32fa4f4a2a2d81280ab1ebe82b77920..506ad6ea9e73c9724a05d2c2ca5412449a89f33b 100644
--- a/config.toml
+++ b/config.toml
@@ -141,4 +141,22 @@ pluralizeListTitles = false
name = "Resources"
url = "/resources"
pre = "<i class=\"fa fa-caret-right fa-fw\"></i>"
- weight = 6
\ No newline at end of file
+ weight = 6
+
+[[menu.sidebar]]
+ identifier = "contribute"
+ name= "Development Program"
+ url = "/contribute/dev-program"
+ weight = 1
+
+[[menu.sidebar]]
+ parent = "contribute"
+ name = "Work Items"
+ url = "https://projects.eclipse.org/development-efforts"
+ weight = 1
+
+[[menu.sidebar]]
+ parent = "contribute"
+ name = "FAQ"
+ url = "/contribute/dev-program/faq"
+ weight = 2
\ No newline at end of file
diff --git a/config/nginx/default.conf b/config/nginx/default.conf
index 9b296c955ba621c88b19c01cbfd03d1e7ef87125..74e3212754cdecdf9a41d7c02d263787ec0599a9 100644
--- a/config/nginx/default.conf
+++ b/config/nginx/default.conf
@@ -71,6 +71,15 @@ server {
# https://git.eclipse.org/c/www.eclipse.org/ide.git/tree/
rewrite /ide/index.php /ide redirect;
+ # www.eclipse.org/contribute
+ # https://git.eclipse.org/c/www.eclipse.org/contribute.git/tree/
+ rewrite /contribute/dev_program /contribute/dev-program redirect;
+ rewrite /contribute/dev_program.php /contribute/dev-program redirect;
+ rewrite /contribute/dev_program/index.php /contribute/dev-program redirect;
+ rewrite /contribute/dev_program/faq.php /contribute/dev-program/faq redirect;
+ rewrite /contribute/cla https://accounts.eclipse.org/user/eca redirect;
+ rewrite /contribute/cla/index.php https://accounts.eclipse.org/user/eca redirect;
+
root /usr/share/nginx/html/;
index index.html index.htm;
}
diff --git a/content/contribute/_index.md b/content/contribute/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..72f87fe4282957ff4baf87e7220aede7e4991abd
--- /dev/null
+++ b/content/contribute/_index.md
@@ -0,0 +1,17 @@
+---
+title: "Contribute"
+date: 2022-07-27T09:00:00-04:00
+description: "Contribute to Eclipse Foundation"
+categories: []
+keywords: ["eclipse contribute", "how can I help", "contributing to eclipse"]
+slug: ""
+aliases: []
+toc: false
+draft: false
+hide_page_title: true
+hide_sidebar: true
+container: container
+layout: single
+---
+
+{{< pages/contribute/landing-page >}}
diff --git a/content/contribute/assets/EclipseServicesAgreement.pdf b/content/contribute/assets/EclipseServicesAgreement.pdf
new file mode 100644
index 0000000000000000000000000000000000000000..f5daf70a70192d82186d3325746714107cc2139d
Binary files /dev/null and b/content/contribute/assets/EclipseServicesAgreement.pdf differ
diff --git a/content/contribute/assets/images/friends_badge.png b/content/contribute/assets/images/friends_badge.png
new file mode 100644
index 0000000000000000000000000000000000000000..be090a05576d1ee4897ba1e85ed860ad9b7590fe
Binary files /dev/null and b/content/contribute/assets/images/friends_badge.png differ
diff --git a/content/contribute/dev-program/_index.md b/content/contribute/dev-program/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..88876889d4b524325041c867903f9d151ea0e729
--- /dev/null
+++ b/content/contribute/dev-program/_index.md
@@ -0,0 +1,16 @@
+---
+title: "Friend of Eclipse Enhancement Program (FEEP)"
+date: 2022-07-27T10:00:00-04:00
+description: "Contribute to Eclipse Foundation"
+categories: []
+keywords: ["eclipse", "foundation", "development", "platform", "funding"]
+slug: ""
+aliases: []
+toc: false
+draft: false
+container: container
+layout: single
+is_deprecated: true
+---
+
+{{< pages/contribute/dev-program >}}
diff --git a/content/contribute/dev-program/faq/_index.md b/content/contribute/dev-program/faq/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1db27dedf7da8f6f85eb9604baba3d50c357c0a
--- /dev/null
+++ b/content/contribute/dev-program/faq/_index.md
@@ -0,0 +1,68 @@
+---
+title: FAQ
+date: 2022-07-27T10:00:00-04:00
+description: "Contribute to Eclipse Foundation"
+seo_title: FEEP Bidding Process FAQ
+categories: []
+keywords: ["eclipse", "foundation", "development", "platform", "funding", "faq", "feep"]
+slug: ""
+aliases: []
+toc: false
+draft: false
+hide_page_title: true
+container: container
+is_deprecated: true
+---
+
+# FEEP Bidding Process FAQ
+
+## How can I submit a bid for a development effort?
+
+Click on the link for any one of the [development efforts](https://projects.eclipse.org/development-efforts), and you will see a button allowing you to generate and submit a bid. Please note that you must be logged in to do so.
+
+## Must I be a committer to submit a bid? Must my company be a member to submit a bid?
+
+Technically, no – this is not mandatory. However, strong preference will be given to bids
+submitted by member companies and individual committers.
+
+## Can I propose an alternative solution to what is being requested in the description of the Development Effort?
+
+Yes. It is our goal to ensure we have the best possible outcome from these Development Efforts,
+and if you feel we should consider an alternative approach, please feel free to propose it. You
+will, however, have to make clear the impact to scope, and please recognize if the cost you are
+proposing is greater than what was originally allocated, the proposed solution may not be
+feasible.
+
+## Can I get clarification on a specific Development Effort?
+
+Yes. Please send email to [feep@eclipse.org](mailto:feep@eclipse.org). Please be aware
+that we may post updates to the specific Development Efforts based on the questions we receive.
+
+## Must my bid be a fixed price bid?
+
+No, you may propose an alternative pricing mechanism such as time and materials, but be aware
+that preference will be given to fixed price bids. If you wish to specify an alternative to fixed
+price, please indicate this clearly in your bid.
+
+## Can I bid on multiple development efforts?
+
+Yes, but please submit each bid as a separate proposal. Each development effort will be managed
+through a separate Statement of Work (SOW).
+
+## How should I indicate the impact to my delivery schedule if I am awarded multiple Development Efforts?
+
+If you are bidding on more than one development effort, please make clear the impact of the
+deliverable schedule should you be awarded multiple SOWs. This detail should be included in each
+bid impacted.
+
+## How are bids qualified? Who is making the final decision regarding bids?
+
+All bids will be evaluated by the FEEP-PM in consultation with the team that helped develop the
+original list of Development Efforts. Bids will be evaluated using the criteria specified in the
+FEEP Program Description.
+
+## When will I know whether my bid has won, and when can I begin working on the Development Effort?
+
+The FEEP-PM will contact you directly should your bid(s) be selected as a winning bid. You will
+be required to execute a services contract with Eclipse Foundation, if you have not already done
+so, and then to execute a work schedule to contract for the specific Development Effort.
diff --git a/layouts/shortcodes/pages/contribute/dev-program.html b/layouts/shortcodes/pages/contribute/dev-program.html
new file mode 100644
index 0000000000000000000000000000000000000000..026726fab0a9fd6f45bd3541bdb55130f038b221
--- /dev/null
+++ b/layouts/shortcodes/pages/contribute/dev-program.html
@@ -0,0 +1,203 @@
+<small><b>Draft</b> v05 - September 17th, 2015</small>
+<h2>Program Objective:</h2>
+<p>The Friend of Eclipse Enhancement Program, or FEEP, utilizes the funds donated through the
+ Friends of Eclipse program to make significant and meaningful improvements and enhancements to the
+ Eclipse IDE/Platform.</p>
+<h2>Program Summary:</h2>
+<p>The Eclipse Foundation (EF) is committed to directing the funds donated through the Friends of
+ Eclipse initiative directly to making improvements to the Eclipse IDE/Platform.</p>
+<p>EF will engage with key stakeholders in the community to determine the highest priority issues to
+ be addressed, convert these priorities into actionable development tasks, and then engage with
+ qualified resources to carry out these tasks.</p>
+<p>The guiding principles of the process are:</p>
+<ul>
+ <li>To adhere to the principle of transparency and openness.</li>
+ <li>To complement the existing development efforts already underway.</li>
+ <li>To encourage a “multiplying effect†where community participation is amplified by this funding
+ program’s undertakings.</li>
+</ul>
+<p>Development will be carried out in an on-going series of Development Cycles, which are described
+ below.</p>
+<p>The effectiveness of the Program is dependent on the funds available. The expectation is for
+ contributions to continue to grow, especially once positive results are demonstrated.</p>
+<blockquote>NOTE: FEEP utilizes the funds donated exclusively through the Friends of Eclipse
+ program. EF also accepts corporate donations, including directed donations. In the case of
+ directed donations, a corporation may request their donation be directed to priorities identified
+ by them. EF will ensure these donations are used for these exclusive purposes, regardless of
+ whether these corporate priorities differ from the priorities identified by FEEP. However, EF is
+ motivated to ensure the impact of the donations through both sources collectively, regardless of
+ corporate or individual donations, leads to the maximum positive impact.</blockquote>
+<h2>Program Governance:</h2>
+<p>FEEP will be managed exclusively by the Eclipse Foundation. The EF commits to a full disclosure
+ of the expenditures made related to this program, as well as disclosure of the priorities
+ established for selecting development efforts.</p>
+<p>The Eclipse Management Organization (EMO) will designate a FEEP Program Manager (“FEEP PMâ€) to
+ manage the various tasks and processes on its behalf. Initially, it is expected the role of FEEP
+ PM will be played by one of EF’s staff member, though this may change over time.</p>
+<p>As the Program grows, EF may decide to create an IDE/Platform Working Group. This would be done
+ primarily to broaden governance responsibilities to interested Members, and would establish
+ committees to, for example, oversee budgets, contribute corporate funding directly to the program,
+ expand the prioritization process, work more closely with contractors, etc.</p>
+<h2>Budget:</h2>
+<p>The amount of funds available for development will vary, depending on the amount of donations
+ received through the Friends of Eclipse initiative.</p>
+<p>Initially, EF will collect the funds received over the previous half year, and then use this
+ amount for the development efforts identified for the upcoming quarter. For example, if we receive
+ $75,000 in contributions in Q3, we will apply $75,000 to the development efforts in Q4. EF may
+ change this to a more or less frequent process, depending on the experience gained.</p>
+<p>As background, in 2014 the amount donated through the Friends of Eclipse totaled $120,000.</p>
+<h2>Expected Areas of Focus:</h2>
+<p>Initially, the primary areas of focus to be addressed by this Program are:</p>
+<ul>
+ <li>Resolve deep technical issues that are outstanding and not being addressed by the community
+ otherwise.</li>
+ <li>Accelerate work on areas deemed critical by key stakeholders, including the Architecture
+ Council, relevant PMCs and others, to aid in keeping the Eclipse IDE state of the art.
+ “Accelerate work†can take on many forms, from directly funding development to reviewing inbound
+ community contributions.</li>
+ <li>Make improvements to the IDE that make adoption within the community simpler and broader.</li>
+ <li>Improve the tools, processes, etc. related to directly improving the IDE.</li>
+</ul>
+<p>EF reserves the right, through its governance role, to modify these areas of focus.</p>
+<h2>FEEP Cycles:</h2>
+<p>To create a process that is easier to track, budget for, and measure success, development will be
+ done through a series of FEEP Cycles.</p>
+<p>At a glance, each FEEP Cycle involves a 5 step process:</p>
+<table class="table table-bordered">
+ <thead>
+ <tr>
+ <th><strong>EF FEEP Cycle Activity</strong></th>
+ <th><strong>Estimated Time Period</strong></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Collect Input on Priorities</td>
+ <td>Weeks 1-2</td>
+ </tr>
+ <tr>
+ <td>Establish Budget and Select Approved Development Efforts</td>
+ <td>Week 2-3</td>
+ </tr>
+ <tr>
+ <td>Solicit Bids For Development Efforts</td>
+ <td>Week 3-4</td>
+ </tr>
+ <tr>
+ <td>Award Contracts For Development Efforts</td>
+ <td>Week 5</td>
+ </tr>
+ <tr>
+ <td>Sign-Off On Completed Development Efforts</td>
+ <td>Week 13 [1]</td>
+ </tr>
+ </tbody>
+</table>
+<p>Each step in the FEEP Cycle process is described below.</p>
+<p>It is expected that FEEP Cycles will be done initially on a semi-annual basis, though the EF may
+ change the frequency at its sole discretion.</p>
+<h3>1. Collect Input on Priorities</h3>
+<p>The FEEP-PM will gather input from interested parties, including:</p>
+<ul>
+ <li>Respective PMC’s</li>
+ <li>Member corporations that have donated funds with specific requests for development.</li>
+ <li>The Eclipse Management Organization (EMO), which includes</li>
+ <ul>
+ <li>Architecture Council</li>
+ <li>Planning Council</li>
+ <li>Foundation staff</li>
+ </ul>
+</ul>
+<p>From this input and interaction, the FEEP-PM will produce a collection of Development Efforts.</p>
+<p>The description of each Development Effort is expected to include, as a minimum:</p>
+<ul>
+ <li>task name and Bugzilla id,</li>
+ <li>time estimate,</li>
+ <li>cost estimate,</li>
+ <li>expected deliverable(s)/outcome(s),</li>
+ <li>anticipated dependencies,</li>
+ <li>means of demonstration and/or verification of completion.</li>
+</ul>
+<p>The FEEP-PM is likely to engage with potential contractors at this stage to seek their input on
+ the Development Efforts to enable him/her to provide better estimates. This input from potential
+ contractors will be provided based strictly on a non-committal basis by both sides, and is used
+ for informational purposes only. No funding will be provided to potential contractors for this
+ input.</p>
+<h3>2. Establish Budget and Select Approved Development Efforts</h3>
+<p>The FEEP-PM will create a draft budget identifying which of the Development Efforts identified
+ will go to contract. This draft budget will be based on the funds available through donation, as
+ well as the relative priorities established.</p>
+<p>The EMO will review both the budget and list of prioritized Development Efforts, and will
+ generate a list of Approved Development Efforts.</p>
+<blockquote>Note: Any budgeted development funds that are not allocated for development, or any
+ funds not released due to non-completion of a development effort, will be added to the funds
+ available for the next Development Cycle.</blockquote>
+<p>Before soliciting bids for the Approved Development Efforts, the FEEP-PM will review with the
+ affected project or PMC the Approved Development Efforts targeted in their project. The project or
+ PMC must commit their support to the proposed work, including naming the project committer(s) that
+ will review, and commit the work if the contractor isn't a committer on that project.</p>
+<h3>3. Solicit Bids for Approved Development Efforts</h3>
+<p>The FEEP-PM will post the Approved Development Efforts to the EF website. During the open bidding
+ period, expected to be approximately 2 weeks, potential contractors may interact with the FEEP-PM
+ to seek additional information regarding the development efforts.</p>
+<p>Interested contractors may submit confidential bids for any or all of the Approved Development
+ Efforts.</p>
+<blockquote>Note: EMO reserves the right to solicit bids from specific Committers and/or contractors
+ should it feel particular expertise or experience is required to be successful. The EMO is not
+ obliged to disclose that it has chosen to carry out this solicitation.</blockquote>
+<p>In each bid, the contractor must identify, as a minimum:</p>
+<ul>
+ <li>Description of the approa ch to address the Development Effort.</li>
+ <li>Identification of who will perform the work (i.e., named developers).</li>
+ <li>The proposed timeframe for the development effort.</li>
+ <li>Any dependencies/caveats that exist that must be addressed.</li>
+ <li>Proposed outcome for the work, including how to demonstrate the work has been completed.</li>
+ <li>Explicit list of deliverables, including any interim deliverables.</li>
+ <li>A proposed price, including whether the bid is being made on a fixed price or time and
+ materials basis, and whether any interim milestones and associated and/or interim payments are
+ proposed.</li>
+</ul>
+<p>All bids should indicate any taxes to be charged in addition to the costs identified. It is
+ expected that no expenses shall be incurred as part of any bid, though exceptions may be proposed
+ by contractors. These exceptions must be clearly identified, and contractors may only bill for
+ such expenses if agreed to in writing by the FEEP-PM as part of the contract for the Approved
+ Development Effort, and if the expense is actually incurred.</p>
+<p>All bids submitted will be treated as confidential by EF. However, all contractors must agree to
+ EF posting the name and value of each contracted Development Effort.</p>
+<h3>4. Award Contracts For Successful Bids</h3>
+<p>The FEEP-PM will work with others within the EMO to evaluate the submitted bids. Winning bids
+ will be selected upon the following criteria:</p>
+<ul>
+ <li>Price</li>
+ <li>Quality of proposed development and deliverables</li>
+ <li>Skillset of proposed developers, with preference given to Committers in the relevant area.</li>
+ <li>Bidder’s relationship with EF, with preference given to either Solution Members with
+ Committers, or self-employed Committers with relevant expertise</li>
+ <li>Any additional relevant elements in the bid, including delivery date, whether fixed price vs.
+ time and materials basis, etc.</li>
+</ul>
+<p>EMO may decide, at its sole discretion, not to let a contract for any particular Approved
+ Development Effort, even if acceptable bids have been submitted.</p>
+<p>Contractors will be expected to execute a Statement of Work (SOW) for each winning bid. Each SOW
+ will be created against the standing Professional Services Agreement with the contractor, which
+ must have been previously executed by the contractor.</p>
+<p>Following the execution of each SOW, EMO will publish the name of the winning contractor and the
+ total contract value.</p>
+<h3>5. Sign-Off on Completed Development Efforts</h3>
+<p>For each Development Effort, the contractor is expected to provide:
+<ul>
+ <li>Source code. In most cases, it will be expected that the acceptance criteria for code is that
+ it has been committed by the Eclipse project. Other scenarios may be possible in exceptional
+ circumstances.</li>
+ <li>Test harness(es) for code</li>
+ <li>Documentation, including appropriate documentation related to IP</li>
+ <li>Any other appropriate deliverables, including those to which the contractor committed in the
+ original bid.</li>
+</ul>
+<p>Unless explicitly agreed to otherwise, payment will only be made at the completion of the
+ Development Effort, and once the FEEP-PM has signed-off on the deliverables. The FEEP-PM may seek
+ assistance and opinions from the relevant interested parties to evaluate the completeness of the
+ deliverables.</p>
+<p>Sign-off by FEEP-PM on a submitted completed Development Effort is expected to take up to 14
+ days.</p>
+<small>[1] Completion dates may vary, depending on the individual development efforts. </small>
\ No newline at end of file
diff --git a/layouts/shortcodes/pages/contribute/landing-page.html b/layouts/shortcodes/pages/contribute/landing-page.html
new file mode 100644
index 0000000000000000000000000000000000000000..3e230ee72fdb71fdf17c1ce498c887bd383e70b1
--- /dev/null
+++ b/layouts/shortcodes/pages/contribute/landing-page.html
@@ -0,0 +1,95 @@
+
+<h1>Get Involved!</h1>
+
+<div class="row">
+ <div class="col-md-16">
+ <h3>Report Bugs and Enhancements</h3>
+ <ul class="fa-ul">
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i>
+ Download one of the latest <a href="/downloads/index-developer.php">
+ Eclipse Package Milestone Builds</a>. Take it for a test drive
+ before the final release and <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi">
+ report any bugs</a> you find.
+ </li>
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i>
+ <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi">Report Enhancements</a> :
+ Got an idea for a killer feature? Or maybe something you use often could use some tweaking? Post an
+ enhancement request!
+ </li>
+ </ul>
+
+ <h3>Fix Bugs or Implement Enhancements</h3>
+
+ <ul class="fa-ul">
+ <li><i class="fa fa-li fa-chevron-circle-right orange"></i>
+ <a href="http://bugs.eclipse.org/bugs/query.cgi">Is there some bug</a>
+ that really bothers you? Instead of just reporting it, fix it. And there are
+ <a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=REOPENED&keywords=helpwanted%2C%20&list_id=9664295">
+ many bugs marked with helpwanted</a>.
+ <ul class="">
+ <li><i class="fa fa-li fa-chevron-circle-right orange"></i>
+ First sign an
+ <a href="https://accounts.eclipse.org/user/eca">
+ Eclipse Contributor Agreement</a>.
+ </li>
+ <li>
+ To learn how the bug-fixing process works, check out the
+ <a href="http://wiki.eclipse.org/Bug_Reporting_FAQ"> bug reporting FAQ</a>.
+ </li>
+ <li>
+ To learn about the lifecycle of bugzilla entries, check
+ out the <a href="http://wiki.eclipse.org/Development_Resources/HOWTO/Bugzilla_Use">development process</a>.
+ </li>
+ </ul>
+
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i>
+ Participate in our <a href="/contribute/dev-program">Friend of Eclipse Enhancements Program</a> either as a funded developer, or by
+ making a <a href="/donate/">donation</a>.
+ </li>
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i>
+ <a href="https://wiki.eclipse.org/Learn_About_Eclipse">Learn about Eclipse</a>.
+ </li>
+ <li>
+ Browse our <a href="https://git.eclipse.org/c/">source code repositories</a>.
+ </li>
+ </ul>
+
+ <h3>Become a Committer</h3>
+
+ <ul class="fa-ul">
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i> Start a
+ <a href='http://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project'>
+ new project</a> or become a committer on an
+ <a href="/membership/become_a_member/committer.php">existing project</a>.
+ </li>
+ </ul>
+
+ <h3>Promote Eclipse Technologies</h3>
+
+ <ul class="fa-ul">
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i> Let other people know that your application is
+ <a href="/artwork">Built on Eclipse or Eclipse Ready</a>.
+ </li>
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i> Do you
+ or your company have a success story about Eclipse? Send us a
+ <a href="mailto:news@eclipse.org?subject=Success%20story%20about%20Eclipse">story</a>
+ and we'll help you spread the word.
+ </li>
+ <li>
+ <i class="fa fa-li fa-chevron-circle-right orange"></i> Follow the Eclipse community on
+ <a href="http://wiki.eclipse.org/Twitter">Twitter</a>.
+ </li>
+ </ul>
+ </div>
+
+ <div class="col-md-7 col-md-offset-1">
+ <img src="/contribute/assets/images/friends_badge.png" alt="friend">
+ </div>
+</div>
\ No newline at end of file