Modified: portals/site-live/mission.html URL: http://svn.apache.org/viewvc/portals/site-live/mission.html?rev=1901427&r1=1901426&r2=1901427&view=diff ============================================================================== --- portals/site-live/mission.html (original) +++ portals/site-live/mission.html Tue May 31 02:08:01 2022 @@ -1,238 +1,170 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<!-- Generated by Apache Maven Doxia Site Renderer 1.4 at 16 July 2015 --> -<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>The Apache Portals Site - - Apache Portals Mission</title> - <style type="text/css" media="all"> - @import url("./css/maven-base.css"); - @import url("./css/maven-theme.css"); - @import url("./css/site.css"); - </style> - <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" /> - <meta name="author" content="David Sean Taylor" /> - <meta name="Date-Revision-yyyymmdd" content="20150716" /> - <meta http-equiv="Content-Language" content="en" /> - - </head> - <body class="composite"> - <div id="banner"> - <a href="http://www.apache.org/" id="bannerLeft"> - <img src="images/apache.gif" alt="Apache Software Foundation" /> - </a> - <a href="http://portals.apache.org/" id="bannerRight"> - <img src="images/apache-portals.gif" alt="Apache Portals Site" /> - </a> - <div class="clear"> - <hr/> - </div> - </div> - <div id="breadcrumbs"> - - - <div class="xleft"> - <span id="publishDate">Last Published: 16 July 2015</span> - | <span id="projectVersion">Version: 1.0</span> - </div> - <div class="xright"> <a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> - | - <a href="bridges/" title="Bridges">Bridges</a> - | - <a href="pluto/" title="Pluto">Pluto</a> - | - <a href="applications/" title="Applications">Applications</a> - | - <a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> - - - </div> - <div class="clear"> - <hr/> - </div> - </div> - <div id="leftColumn"> - <div id="navcolumn"> - - - <h5>About Apache Portals</h5> - <ul> - <li class="none"> - <a href="index.html" title="Overview">Overview</a> - </li> - <li class="none"> - <strong>Our Mission</strong> - </li> - <li class="none"> - <a href="news.html" title="News and Status">News and Status</a> - </li> - <li class="none"> - <a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink" title="How the ASF Works">How the ASF Works</a> - </li> - <li class="none"> - <a href="guidelines.html" title="Project Guidelines">Project Guidelines</a> - </li> - <li class="none"> - <a href="whoweare.html" title="Who We Are">Who We Are</a> - </li> - <li class="none"> - <a href="supporting.html" title="Supporting Organizations">Supporting Organizations</a> - </li> - <li class="none"> - <a href="license.html" title="License">License</a> - </li> - </ul> - <h5>Resources</h5> - <ul> - <li class="none"> - <a href="download.html" title="Downloads">Downloads</a> - </li> - <li class="none"> - <a href="javadocs.html" title="JavaDocs">JavaDocs</a> - </li> - <li class="none"> - <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a> - </li> - <li class="none"> - <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a> - </li> - <li class="none"> - <a href="wiki.html" title="Wikis">Wikis</a> - </li> - </ul> - <h5>Portals Sub projects</h5> - <ul> - <li class="none"> - <a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> - </li> - <li class="none"> - <a href="pluto/" title="Pluto">Pluto</a> - </li> - <li class="none"> - <a href="applications/" title="Applications">Applications</a> - </li> - <li class="none"> - <a href="bridges/" title="Bridges">Bridges</a> - </li> - <li class="none"> - <a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> - </li> - </ul> - <h5>Development</h5> - <ul> - <li class="none"> - <a href="http://www.apache.org/dev/" class="externalLink" title="Developer Resources">Developer Resources</a> - </li> - <li class="none"> - <a href="development/code-standards.html" title="Coding Standards">Coding Standards</a> - </li> - <li class="none"> - <a href="development/documentation.html" title="Documentation Standards">Documentation Standards</a> - </li> - <li class="none"> - <a href="development/developer-links.html" title="Developer Resources">Developer Resources</a> - </li> - <li class="none"> - <a href="development/further-reading.html" title="Further Reading">Further Reading</a> - </li> - </ul> - <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy"> - <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" /> - </a> - - - </div> - </div> - <div id="bodyColumn"> - <div id="contentBox"> - - - -<div class="section"> -<h2>Mission<a name="Mission"></a></h2> - -<p> - <b>Apache Portals</b> exists to promote the use of open source portal technology. - We view portals as an important technology in in the growing portal and web application environments. - We intend to build freely available portal software in order to promote the use of this technology. - </p> - -<p> - To provide reference implementations Java and W3C Standards such as the - </p> -<ul> - -<li>Java Portlet Standard (Pluto)</li> - -<li>WSRP Portlet Standard (WSRP-4J)</li> - </ul> - To provide portal implementations including: - -<ul> - -<li>Cocoon Portal</li> - -<li>Jetspeed-1</li> - -<li>Jetspeed-2</li> - -<li>PHP Portals (TBD)</li> - </ul> - To provide fully working and standardized portlet applications: - -<ul> - -<li>Jetspeed Content Replication Engine</li> - -<li>Jetspeed Portal Administration Application</li> - -<li>(TBD)</li> - </ul> - To provide common frameworks and tools for developing portal software - -<ul> - -<li>CPS (Cornerstone Portlet Services)</li> - -<li>Struts Portlet Application Framework</li> - -<li>Python Portlet Application Framework</li> - -<li>Turbine Portlet Application Framework</li> - </ul> - To provide portal interoperability frameworks and tools for programming languages including - -<ul> - -<li>Java</li> - -<li>Perl</li> - -<li>PHP</li> - -<li>Python</li> - -<li>...</li> - </ul> - -</div> - - - </div> - </div> - <div class="clear"> - <hr/> - </div> - <div id="footer"> - <div class="xright"> - Copyright © 2004-2015 - <a href="http://www.apache.org/">Apache Software Foundation</a>. - All Rights Reserved. - - </div> - <div class="clear"> - <hr/> - </div> - </div> - </body> -</html> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<!-- Generated by Apache Maven Doxia Site Renderer 1.8.1 from src\site\xdoc/mission.xml at 26 May 2022 --> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>The Apache Portals Site – Apache Portals Mission</title> + <style type="text/css" media="all"> + @import url("./css/maven-base.css"); + @import url("./css/maven-theme.css"); + @import url("./css/site.css"); + </style> + <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" /> + <meta name="author" content="David Sean Taylor" /> + <meta http-equiv="Content-Language" content="en" /> + + </head> + <body class="composite"> + <div id="banner"> +<a href="http://www.apache.org/" id="bannerLeft"><img src="images/apache.gif" alt="Apache Software Foundation"/></a> +<a href="http://portals.apache.org/" id="bannerRight"><img src="images/apache-portals.gif" alt="Apache Portals Site"/></a> + <div class="clear"> + <hr/> + </div> + </div> + <div id="breadcrumbs"> + <div class="xleft"> + <span id="publishDate">Last Published: 26 May 2022</span> + | <span id="projectVersion">Version: 1.0</span> + </div> + <div class="xright"><a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> | +<a href="bridges/" title="Bridges">Bridges</a> | +<a href="pluto/" title="Pluto">Pluto</a> | +<a href="applications/" title="Applications">Applications</a> | +<a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> </div> + <div class="clear"> + <hr/> + </div> + </div> + <div id="leftColumn"> + <div id="navcolumn"> + <h5>About Apache Portals</h5> + <ul> + <li class="none"><a href="index.html" title="Overview">Overview</a></li> + <li class="none"><strong>Our Mission</strong></li> + <li class="none"><a href="news.html" title="News and Status">News and Status</a></li> + <li class="none"><a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink" title="How the ASF Works">How the ASF Works</a></li> + <li class="none"><a href="guidelines.html" title="Project Guidelines">Project Guidelines</a></li> + <li class="none"><a href="whoweare.html" title="Who We Are">Who We Are</a></li> + <li class="none"><a href="supporting.html" title="Supporting Organizations">Supporting Organizations</a></li> + <li class="none"><a href="license.html" title="License">License</a></li> + </ul> + <h5>Resources</h5> + <ul> + <li class="none"><a href="download.html" title="Downloads">Downloads</a></li> + <li class="none"><a href="javadocs.html" title="JavaDocs">JavaDocs</a></li> + <li class="none"><a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a></li> + <li class="none"><a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a></li> + <li class="none"><a href="wiki.html" title="Wikis">Wikis</a></li> + </ul> + <h5>Portals Sub projects</h5> + <ul> + <li class="none"><a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a></li> + <li class="none"><a href="pluto/" title="Pluto">Pluto</a></li> + <li class="none"><a href="applications/" title="Applications">Applications</a></li> + <li class="none"><a href="bridges/" title="Bridges">Bridges</a></li> + <li class="none"><a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a></li> + </ul> + <h5>Development</h5> + <ul> + <li class="none"><a href="http://www.apache.org/dev/" class="externalLink" title="Developer Resources">Developer Resources</a></li> + <li class="none"><a href="development/code-standards.html" title="Coding Standards">Coding Standards</a></li> + <li class="none"><a href="development/documentation.html" title="Documentation Standards">Documentation Standards</a></li> + <li class="none"><a href="development/developer-links.html" title="Developer Resources">Developer Resources</a></li> + <li class="none"><a href="development/further-reading.html" title="Further Reading">Further Reading</a></li> + </ul> + <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy"> + <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" /> + </a> + </div> + </div> + <div id="bodyColumn"> + <div id="contentBox"> + + + +<div class="section"> +<h2><a name="Mission"></a>Mission</h2> + +<p> + <b>Apache Portals</b> exists to promote the use of open source portal technology. + We view portals as an important technology in in the growing portal and web application environments. + We intend to build freely available portal software in order to promote the use of this technology. + </p> + +<p> + To provide reference implementations Java and W3C Standards such as the + </p> +<ul> + +<li>Java Portlet Standard (Pluto)</li> + +<li>WSRP Portlet Standard (WSRP-4J)</li> + </ul> + To provide portal implementations including: + +<ul> + +<li>Cocoon Portal</li> + +<li>Jetspeed-1</li> + +<li>Jetspeed-2</li> + +<li>PHP Portals (TBD)</li> + </ul> + To provide fully working and standardized portlet applications: + +<ul> + +<li>Jetspeed Content Replication Engine</li> + +<li>Jetspeed Portal Administration Application</li> + +<li>(TBD)</li> + </ul> + To provide common frameworks and tools for developing portal software + +<ul> + +<li>CPS (Cornerstone Portlet Services)</li> + +<li>Struts Portlet Application Framework</li> + +<li>Python Portlet Application Framework</li> + +<li>Turbine Portlet Application Framework</li> + </ul> + To provide portal interoperability frameworks and tools for programming languages including + +<ul> + +<li>Java</li> + +<li>Perl</li> + +<li>PHP</li> + +<li>Python</li> + +<li>...</li> + </ul> + +</div> + + + </div> + </div> + <div class="clear"> + <hr/> + </div> + <div id="footer"> + <div class="xright"> + Copyright © 2004–2022 <a href="http://www.apache.org/">Apache Software Foundation</a>. +All rights reserved. </div> + <div class="clear"> + <hr/> + </div> + </div> + </body> +</html>
Modified: portals/site-live/newproject.html URL: http://svn.apache.org/viewvc/portals/site-live/newproject.html?rev=1901427&r1=1901426&r2=1901427&view=diff ============================================================================== --- portals/site-live/newproject.html (original) +++ portals/site-live/newproject.html Tue May 31 02:08:01 2022 @@ -1,466 +1,387 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<!-- Generated by Apache Maven Doxia Site Renderer 1.4 at 16 July 2015 --> -<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> - <title>The Apache Portals Site - - New Project Proposals</title> - <style type="text/css" media="all"> - @import url("./css/maven-base.css"); - @import url("./css/maven-theme.css"); - @import url("./css/site.css"); - </style> - <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" /> - <meta name="author" content="Apache Portals Project" /> - <meta name="Date-Revision-yyyymmdd" content="20150716" /> - <meta http-equiv="Content-Language" content="en" /> - - </head> - <body class="composite"> - <div id="banner"> - <a href="http://www.apache.org/" id="bannerLeft"> - <img src="images/apache.gif" alt="Apache Software Foundation" /> - </a> - <a href="http://portals.apache.org/" id="bannerRight"> - <img src="images/apache-portals.gif" alt="Apache Portals Site" /> - </a> - <div class="clear"> - <hr/> - </div> - </div> - <div id="breadcrumbs"> - - - <div class="xleft"> - <span id="publishDate">Last Published: 16 July 2015</span> - | <span id="projectVersion">Version: 1.0</span> - </div> - <div class="xright"> <a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> - | - <a href="bridges/" title="Bridges">Bridges</a> - | - <a href="pluto/" title="Pluto">Pluto</a> - | - <a href="applications/" title="Applications">Applications</a> - | - <a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> - - - </div> - <div class="clear"> - <hr/> - </div> - </div> - <div id="leftColumn"> - <div id="navcolumn"> - - - <h5>About Apache Portals</h5> - <ul> - <li class="none"> - <a href="index.html" title="Overview">Overview</a> - </li> - <li class="none"> - <a href="mission.html" title="Our Mission">Our Mission</a> - </li> - <li class="none"> - <a href="news.html" title="News and Status">News and Status</a> - </li> - <li class="none"> - <a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink" title="How the ASF Works">How the ASF Works</a> - </li> - <li class="none"> - <a href="guidelines.html" title="Project Guidelines">Project Guidelines</a> - </li> - <li class="none"> - <a href="whoweare.html" title="Who We Are">Who We Are</a> - </li> - <li class="none"> - <a href="supporting.html" title="Supporting Organizations">Supporting Organizations</a> - </li> - <li class="none"> - <a href="license.html" title="License">License</a> - </li> - </ul> - <h5>Resources</h5> - <ul> - <li class="none"> - <a href="download.html" title="Downloads">Downloads</a> - </li> - <li class="none"> - <a href="javadocs.html" title="JavaDocs">JavaDocs</a> - </li> - <li class="none"> - <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a> - </li> - <li class="none"> - <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a> - </li> - <li class="none"> - <a href="wiki.html" title="Wikis">Wikis</a> - </li> - </ul> - <h5>Portals Sub projects</h5> - <ul> - <li class="none"> - <a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> - </li> - <li class="none"> - <a href="pluto/" title="Pluto">Pluto</a> - </li> - <li class="none"> - <a href="applications/" title="Applications">Applications</a> - </li> - <li class="none"> - <a href="bridges/" title="Bridges">Bridges</a> - </li> - <li class="none"> - <a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> - </li> - </ul> - <h5>Development</h5> - <ul> - <li class="none"> - <a href="http://www.apache.org/dev/" class="externalLink" title="Developer Resources">Developer Resources</a> - </li> - <li class="none"> - <a href="development/code-standards.html" title="Coding Standards">Coding Standards</a> - </li> - <li class="none"> - <a href="development/documentation.html" title="Documentation Standards">Documentation Standards</a> - </li> - <li class="none"> - <a href="development/developer-links.html" title="Developer Resources">Developer Resources</a> - </li> - <li class="none"> - <a href="development/further-reading.html" title="Further Reading">Further Reading</a> - </li> - </ul> - <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy"> - <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" /> - </a> - - - </div> - </div> - <div id="bodyColumn"> - <div id="contentBox"> - <!-- Copyright 1999-2004 The Apache Software Foundation -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - -http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. --> - - - -<div class="section"> -<h2>Subproject Proposals<a name="Subproject_Proposals"></a></h2> - - -<p> -Not every software product is suited for life at Portals. Before proposing -a new subproject, it is important to read this document carefully and determine -whether your product is a good fit. -</p> - -</div> - - -<div class="section"> -<h2>Before Reading...<a name="Before_Reading..."></a></h2> - - -<p> -<a class="externalLink" href="http://www.apache.org/">The Apache Software Foundation</a> has established a -project for the acceptance of new codebases and for the incubation, named -<a class="externalLink" href="http://incubator.apache.org/">Apache Incubator Project</a> on October, 2002. -</p> - -<p> -If you, who are thinking of donating code and starting a project, have some contributions -to make for an existing <a class="externalLink" href="http://portals.apache.org/">Portals</a> sub-project, -work with that community via the <a href="./mail-lists.html">mailing lists</a>. -</p> - -</div> - - -<div class="section"> -<h2>Criteria<a name="Criteria"></a></h2> - - -<p> -Here are some best practices that we will expect to find in a successful -proposal. This is not a checklist, but guidelines to help communicate what -is expected of a Portals subproject. -</p> - - -<p> -<b>Meritocracy.</b> Before submitting a proposal, be sure to study -the guidelines that <a href="guidelines.html">govern Portals subprojects</a>. -These guidelines explain our system of Meritocracy, which is the core -of the Portals Project. If the product developers do not wish to adopt -this system, then they should <b>not</b> donate their code -to the Project, and should look elsewhere for hosting. -</p> - - -<p> -<b>Community.</b> Portals is a Project of the -<a class="externalLink" href="http://www.apache.org/">Apache Software Foundation</a>. A prime purpose of -the ASF is to ensure that the Apache projects continue to exist beyond the -participation of individual volunteers. Accordingly, a prime criteria required -of any new subproject is that it already enjoys -- or has a high potential for -attracting -- an active community of developers and users. -</p> - - -<p> -Proposals for non-established products have been accepted, most often when -the proposal was tendered by experienced open source developers, who understand -what it means to build a community. -</p> - - -<p> -A design document, developer and user documentation, example code, and a -working implementation all help to increase the likelihood of acceptance. -Well-documented products tend to build stronger communities than -products that rely source code and JavaDocs alone. -</p> - - -<p> -<b>Core Developers.</b> To considered, a product must have -at least 3 active developers who are already involved with the codebase. -This is an absolute minimum, and it is helpful for there to more than -three developers. It is <b>very</b> helpful for at least one of the -developers making the proposal to already be active in a Portals subproject or -other open source initiative. -</p> - - -<p> -At Portals, the core developers of a product (the -<a href="roles.html">Committers</a>) manage the codebases and make the -day-to-day development decisions. We are only interested in products -that can guided by their own development communities. Portals provides -the infrastructure, and some essential guidelines, but the Committers -must take responsibility for developing and releasing their own product. -</p> - - -<p> -<b>Alignment with existing Apache subprojects.</b> Products that -are already used by existing subprojects make attractive candidates, since -bringing such a codebase into the Apache fold tends to benefit both -communities. Products with dependancies on existing Apache products are also -attractive for the same reason. -</p> - - -<p> -<b>Scope.</b> Portals products are generally related to the -development of portlets, portals and portal-related frameworks, independant -of the implementation language. Most of the current efforts evolve around -the JSR-168 Java Portlet Specification and the OASIS WSRP4J standard. Proposals -for products outside this venue will have greater difficulty in being accepted. -</p> - -</div> - - -<div class="section"> -<h2>Warning Signs<a name="Warning_Signs"></a></h2> - - -<p> -These are anti-patterns that we have found detrimental to the success of -a proposal. Some of these are lesson learned from the school of -hard-knocks, others are taken from proposals which have been rejected in -the past. All will raise a red flag, making it unlikely that a proposal -will be accepted. -</p> - - -<p> -<b>Orphaned products.</b> Products which have lost their -corporate sponsor (for whatever reason) do <b>not</b> make good candidates. -These products will lack a development community and won't -have the support needed to succeed under the Portals umbrella. -</p> - - -<p> -For example, we have seen proposals that contain paragraphs like this: -</p> - - -<div class="source"> -<pre> -FooProduct is currently a production quality product, and in -fact is being used a live website. It was developed as a -product by FooCompany, with the intention that we would sell -it. However, due to various economic factors such as the -decline in FooProduct's intended market and the -recent difficulties in obtaining venture capital, we have -decided that at this time it is not feasible for us to -continue in that direction. -</pre></div> - - - -<p> -The alleged quality of a product is not the prime criteria. To be -accepted, we must believe that a product will attract volunteers to -extend and maintain it over the long term. A product like this, -arriving with no volunteer developers or open source community, does -not further <a href="mission.html">Portals' mission</a>, and would -not be accepted. -</p> - - -<p> -We generally recommend that an orphaned product start with an -independent host, and consider making a proposal after it has started -to build a community. -</p> - - -<p> -<b>Inexperience with open source.</b> We often receive -proposals that start with "We will open our software if you -choose to accept it." This is the wrong way to approach the proposal -process. A closed source project does not have an open community, and -so we have no way to tell if the developers can work in an open source -environment. Products that have lived on their own and have started -to develop their own community, have a much better chance of being -accepted. -</p> - - -<p> -If the product's developers have not worked with open source before, -it is recommended that they spend some time contributing to an existing -open source project before trying to manage one of their own. Since -Portals subprojects are managed by their own Committers, it is -important that a new product supported by people who understand -how open source works. -</p> - - -<p> -<b>Homogenous developers.</b> Apache communities attract -developers with diverse backgrounds. Products with a tightly-knit -team of developers may have difficulty shepherding new developers -into the fold. It is vital that we believe the developers will -discuss development issues openly with the community, and -<b>not</b> make decisions behind closed doors. We are -especially wary of products with developers who all share a -common employer or geographic location. -</p> - - -<p> -<b>Reliance on salaried developers.</b> Portals has strong ties -to the business community. Many of our developers are encouraged by their -employers to work open source projects as part of their regular job. -We feel that this is a Good Thing, and corporations should be entitled to -contribute to open source, same as anyone else. However, we are wary of -products which rely strongly on developers who only work on open source -products when they are paid to do so. A product at Portals must continue -to exist beyond the participation of individual volunteers. We believe the -best indicator of success is when developers volunteer their own time to -work open source projects. -</p> - - -<p> -<b>No ties to other Apache products</b>. Products -<b>without</b> a tie to any existing Apache product, and that have -strong dependencies on alternatives to Apache products, do not make good -candidates. Many Apache products are related through common licenses, -technologies, and through their volunteers. Products without licensing, -technology, or volunteers in common will have trouble attracting a -strong community. -</p> - - -<p> -<b>A fascination with the Apache brand.</b> The -<a class="externalLink" href="http://www.apache.org/LICENSE">Apache Software License</a> is quite -liberal and allows for the code to used in commercial products. This -can induce people to donate a commercial codebase to the ASF, allow it -developed as open source for a time, and then convert it back to -commercial use. While this would legal under the Apache Software -License, we are wary of proposals that seem to be more interested in -exposure than community. -</p> - -</div> - - -<div class="section"> -<h2>Subproject Alternatives<a name="Subproject_Alternatives"></a></h2> - - -<p> -If your product is a server-side java product, be sure to also -visit the <a class="externalLink" href="http://jakarta.apache.org/">Apache Jakarta Project</a> -to see if it would be a good fit there. - -If your product is XML related, be sure to also visit the -<a class="externalLink" href="http://xml.apache.org/">Apache XML Project</a> or -<a class="externalLink" href="http://cocoon.apache.org/">Apache Cocoon Project</a> to see if it -would be a good fit there. - -If your product is Web Service related, be sure to also visit -the <a class="externalLink" href="http://ws.apache.org/">Apache WebService Project</a> to see -if it would be a good fit there. -</p> - -</div> - - -<div class="section"> -<h2>Who Decides<a name="Who_Decides"></a></h2> - - -<p> -Final acceptance is based the rules defined in the <a href="management.html">Project Management Committee Bylaws</a> which -state that "Creation of a new subproject requires approval by 3/4 vote -of the PMC." The proposal for a new subproject must submitted to the -<a href="mail-lists.html#general">Portals General mailing list</a>, where the PMC -conducts business. All discussion regarding the proposal will occur -the General list, including the final vote. -</p> - -</div> - - - </div> - </div> - <div class="clear"> - <hr/> - </div> - <div id="footer"> - <div class="xright"> - Copyright © 2004-2015 - <a href="http://www.apache.org/">Apache Software Foundation</a>. - All Rights Reserved. - - </div> - <div class="clear"> - <hr/> - </div> - </div> - </body> -</html> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<!-- Generated by Apache Maven Doxia Site Renderer 1.8.1 from src\site\xdoc/newproject.xml at 26 May 2022 --> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> + <title>The Apache Portals Site – New Project Proposals</title> + <style type="text/css" media="all"> + @import url("./css/maven-base.css"); + @import url("./css/maven-theme.css"); + @import url("./css/site.css"); + </style> + <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" /> + <meta name="author" content="Apache Portals Project" /> + <meta http-equiv="Content-Language" content="en" /> + + </head> + <body class="composite"> + <div id="banner"> +<a href="http://www.apache.org/" id="bannerLeft"><img src="images/apache.gif" alt="Apache Software Foundation"/></a> +<a href="http://portals.apache.org/" id="bannerRight"><img src="images/apache-portals.gif" alt="Apache Portals Site"/></a> + <div class="clear"> + <hr/> + </div> + </div> + <div id="breadcrumbs"> + <div class="xleft"> + <span id="publishDate">Last Published: 26 May 2022</span> + | <span id="projectVersion">Version: 1.0</span> + </div> + <div class="xright"><a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a> | +<a href="bridges/" title="Bridges">Bridges</a> | +<a href="pluto/" title="Pluto">Pluto</a> | +<a href="applications/" title="Applications">Applications</a> | +<a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a> </div> + <div class="clear"> + <hr/> + </div> + </div> + <div id="leftColumn"> + <div id="navcolumn"> + <h5>About Apache Portals</h5> + <ul> + <li class="none"><a href="index.html" title="Overview">Overview</a></li> + <li class="none"><a href="mission.html" title="Our Mission">Our Mission</a></li> + <li class="none"><a href="news.html" title="News and Status">News and Status</a></li> + <li class="none"><a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink" title="How the ASF Works">How the ASF Works</a></li> + <li class="none"><a href="guidelines.html" title="Project Guidelines">Project Guidelines</a></li> + <li class="none"><a href="whoweare.html" title="Who We Are">Who We Are</a></li> + <li class="none"><a href="supporting.html" title="Supporting Organizations">Supporting Organizations</a></li> + <li class="none"><a href="license.html" title="License">License</a></li> + </ul> + <h5>Resources</h5> + <ul> + <li class="none"><a href="download.html" title="Downloads">Downloads</a></li> + <li class="none"><a href="javadocs.html" title="JavaDocs">JavaDocs</a></li> + <li class="none"><a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a></li> + <li class="none"><a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a></li> + <li class="none"><a href="wiki.html" title="Wikis">Wikis</a></li> + </ul> + <h5>Portals Sub projects</h5> + <ul> + <li class="none"><a href="jetspeed-2/" title="Jetspeed-2">Jetspeed-2</a></li> + <li class="none"><a href="pluto/" title="Pluto">Pluto</a></li> + <li class="none"><a href="applications/" title="Applications">Applications</a></li> + <li class="none"><a href="bridges/" title="Bridges">Bridges</a></li> + <li class="none"><a href="jetspeed-1/" title="Jetspeed-1">Jetspeed-1</a></li> + </ul> + <h5>Development</h5> + <ul> + <li class="none"><a href="http://www.apache.org/dev/" class="externalLink" title="Developer Resources">Developer Resources</a></li> + <li class="none"><a href="development/code-standards.html" title="Coding Standards">Coding Standards</a></li> + <li class="none"><a href="development/documentation.html" title="Documentation Standards">Documentation Standards</a></li> + <li class="none"><a href="development/developer-links.html" title="Developer Resources">Developer Resources</a></li> + <li class="none"><a href="development/further-reading.html" title="Further Reading">Further Reading</a></li> + </ul> + <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy"> + <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" /> + </a> + </div> + </div> + <div id="bodyColumn"> + <div id="contentBox"> + + + + +<div class="section"> +<h2><a name="Subproject_Proposals"></a>Subproject Proposals</h2> + + +<p> +Not every software product is suited for life at Portals. Before proposing +a new subproject, it is important to read this document carefully and determine +whether your product is a good fit. +</p> + +</div> + + +<div class="section"> +<h2><a name="Before_Reading..."></a>Before Reading...</h2> + + +<p> +<a class="externalLink" href="http://www.apache.org/">The Apache Software Foundation</a> has established a +project for the acceptance of new codebases and for the incubation, named +<a class="externalLink" href="http://incubator.apache.org/">Apache Incubator Project</a> on October, 2002. +</p> + +<p> +If you, who are thinking of donating code and starting a project, have some contributions +to make for an existing <a class="externalLink" href="http://portals.apache.org/">Portals</a> sub-project, +work with that community via the <a href="./mail-lists.html">mailing lists</a>. +</p> + +</div> + + +<div class="section"> +<h2><a name="Criteria"></a>Criteria</h2> + + +<p> +Here are some best practices that we will expect to find in a successful +proposal. This is not a checklist, but guidelines to help communicate what +is expected of a Portals subproject. +</p> + + +<p> +<b>Meritocracy.</b> Before submitting a proposal, be sure to study +the guidelines that <a href="guidelines.html">govern Portals subprojects</a>. +These guidelines explain our system of Meritocracy, which is the core +of the Portals Project. If the product developers do not wish to adopt +this system, then they should <b>not</b> donate their code +to the Project, and should look elsewhere for hosting. +</p> + + +<p> +<b>Community.</b> Portals is a Project of the +<a class="externalLink" href="http://www.apache.org/">Apache Software Foundation</a>. A prime purpose of +the ASF is to ensure that the Apache projects continue to exist beyond the +participation of individual volunteers. Accordingly, a prime criteria required +of any new subproject is that it already enjoys -- or has a high potential for +attracting -- an active community of developers and users. +</p> + + +<p> +Proposals for non-established products have been accepted, most often when +the proposal was tendered by experienced open source developers, who understand +what it means to build a community. +</p> + + +<p> +A design document, developer and user documentation, example code, and a +working implementation all help to increase the likelihood of acceptance. +Well-documented products tend to build stronger communities than +products that rely source code and JavaDocs alone. +</p> + + +<p> +<b>Core Developers.</b> To considered, a product must have +at least 3 active developers who are already involved with the codebase. +This is an absolute minimum, and it is helpful for there to more than +three developers. It is <b>very</b> helpful for at least one of the +developers making the proposal to already be active in a Portals subproject or +other open source initiative. +</p> + + +<p> +At Portals, the core developers of a product (the +<a href="roles.html">Committers</a>) manage the codebases and make the +day-to-day development decisions. We are only interested in products +that can guided by their own development communities. Portals provides +the infrastructure, and some essential guidelines, but the Committers +must take responsibility for developing and releasing their own product. +</p> + + +<p> +<b>Alignment with existing Apache subprojects.</b> Products that +are already used by existing subprojects make attractive candidates, since +bringing such a codebase into the Apache fold tends to benefit both +communities. Products with dependancies on existing Apache products are also +attractive for the same reason. +</p> + + +<p> +<b>Scope.</b> Portals products are generally related to the +development of portlets, portals and portal-related frameworks, independant +of the implementation language. Most of the current efforts evolve around +the JSR-168 Java Portlet Specification and the OASIS WSRP4J standard. Proposals +for products outside this venue will have greater difficulty in being accepted. +</p> + +</div> + + +<div class="section"> +<h2><a name="Warning_Signs"></a>Warning Signs</h2> + + +<p> +These are anti-patterns that we have found detrimental to the success of +a proposal. Some of these are lesson learned from the school of +hard-knocks, others are taken from proposals which have been rejected in +the past. All will raise a red flag, making it unlikely that a proposal +will be accepted. +</p> + + +<p> +<b>Orphaned products.</b> Products which have lost their +corporate sponsor (for whatever reason) do <b>not</b> make good candidates. +These products will lack a development community and won't +have the support needed to succeed under the Portals umbrella. +</p> + + +<p> +For example, we have seen proposals that contain paragraphs like this: +</p> + + +<div class="source"> +<pre> +FooProduct is currently a production quality product, and in +fact is being used a live website. It was developed as a +product by FooCompany, with the intention that we would sell +it. However, due to various economic factors such as the +decline in FooProduct's intended market and the +recent difficulties in obtaining venture capital, we have +decided that at this time it is not feasible for us to +continue in that direction. +</pre></div> + + + +<p> +The alleged quality of a product is not the prime criteria. To be +accepted, we must believe that a product will attract volunteers to +extend and maintain it over the long term. A product like this, +arriving with no volunteer developers or open source community, does +not further <a href="mission.html">Portals' mission</a>, and would +not be accepted. +</p> + + +<p> +We generally recommend that an orphaned product start with an +independent host, and consider making a proposal after it has started +to build a community. +</p> + + +<p> +<b>Inexperience with open source.</b> We often receive +proposals that start with "We will open our software if you +choose to accept it." This is the wrong way to approach the proposal +process. A closed source project does not have an open community, and +so we have no way to tell if the developers can work in an open source +environment. Products that have lived on their own and have started +to develop their own community, have a much better chance of being +accepted. +</p> + + +<p> +If the product's developers have not worked with open source before, +it is recommended that they spend some time contributing to an existing +open source project before trying to manage one of their own. Since +Portals subprojects are managed by their own Committers, it is +important that a new product supported by people who understand +how open source works. +</p> + + +<p> +<b>Homogenous developers.</b> Apache communities attract +developers with diverse backgrounds. Products with a tightly-knit +team of developers may have difficulty shepherding new developers +into the fold. It is vital that we believe the developers will +discuss development issues openly with the community, and +<b>not</b> make decisions behind closed doors. We are +especially wary of products with developers who all share a +common employer or geographic location. +</p> + + +<p> +<b>Reliance on salaried developers.</b> Portals has strong ties +to the business community. Many of our developers are encouraged by their +employers to work open source projects as part of their regular job. +We feel that this is a Good Thing, and corporations should be entitled to +contribute to open source, same as anyone else. However, we are wary of +products which rely strongly on developers who only work on open source +products when they are paid to do so. A product at Portals must continue +to exist beyond the participation of individual volunteers. We believe the +best indicator of success is when developers volunteer their own time to +work open source projects. +</p> + + +<p> +<b>No ties to other Apache products</b>. Products +<b>without</b> a tie to any existing Apache product, and that have +strong dependencies on alternatives to Apache products, do not make good +candidates. Many Apache products are related through common licenses, +technologies, and through their volunteers. Products without licensing, +technology, or volunteers in common will have trouble attracting a +strong community. +</p> + + +<p> +<b>A fascination with the Apache brand.</b> The +<a class="externalLink" href="http://www.apache.org/LICENSE">Apache Software License</a> is quite +liberal and allows for the code to used in commercial products. This +can induce people to donate a commercial codebase to the ASF, allow it +developed as open source for a time, and then convert it back to +commercial use. While this would legal under the Apache Software +License, we are wary of proposals that seem to be more interested in +exposure than community. +</p> + +</div> + + +<div class="section"> +<h2><a name="Subproject_Alternatives"></a>Subproject Alternatives</h2> + + +<p> +If your product is a server-side java product, be sure to also +visit the <a class="externalLink" href="http://jakarta.apache.org/">Apache Jakarta Project</a> +to see if it would be a good fit there. + +If your product is XML related, be sure to also visit the +<a class="externalLink" href="http://xml.apache.org/">Apache XML Project</a> or +<a class="externalLink" href="http://cocoon.apache.org/">Apache Cocoon Project</a> to see if it +would be a good fit there. + +If your product is Web Service related, be sure to also visit +the <a class="externalLink" href="http://ws.apache.org/">Apache WebService Project</a> to see +if it would be a good fit there. +</p> + +</div> + + +<div class="section"> +<h2><a name="Who_Decides"></a>Who Decides</h2> + + +<p> +Final acceptance is based the rules defined in the <a href="management.html">Project Management Committee Bylaws</a> which +state that "Creation of a new subproject requires approval by 3/4 vote +of the PMC." The proposal for a new subproject must submitted to the +<a href="mail-lists.html#general">Portals General mailing list</a>, where the PMC +conducts business. All discussion regarding the proposal will occur +the General list, including the final vote. +</p> + +</div> + + + </div> + </div> + <div class="clear"> + <hr/> + </div> + <div id="footer"> + <div class="xright"> + Copyright © 2004–2022 <a href="http://www.apache.org/">Apache Software Foundation</a>. +All rights reserved. </div> + <div class="clear"> + <hr/> + </div> + </div> + </body> +</html>