From cvsjulie93@example.com Mon Dec 01 08:28:39 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 45481 invoked from network); 1 Dec 2003 08:28:38 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:28:38 -0000 Received: (qmail 64481 invoked by uid 500); 1 Dec 2003 08:27:37 -0000 Delivered-To: julie93@example.com Received: (qmail 64411 invoked by uid 500); 1 Dec 2003 08:27:36 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 64083 invoked from network); 1 Dec 2003 08:27:34 -0000 Date: 1 Dec 2003 08:27:57 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/projects directory.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:27:57 Modified: site/projects directory.cwiki Log: Remove ids, with the same reason held for @author tags in code. Incubation is of all. If someone really needs to see who did it, it's all in the CVS records. Revision Changes Path 1.5 +28 -28 incubator/site/projects/directory.cwiki Index: directory.cwiki =================================================================== RCS file: /home/cvs/incubator/site/projects/directory.cwiki,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- directory.cwiki 28 Nov 2003 15:07:20 -0000 1.4 +++ directory.cwiki 1 Dec 2003 08:27:57 -0000 1.5 @@ -18,12 +18,12 @@ | . | wiki | . | Mailing list | dev | julie93@example.com | . | cvs | julie93@example.com -| Bug tracking | . | . +| Bug tracking | . | Source code | CVS | incubator-directory | Mentors | noel | Noel Bergman | . | nicolaken | Nicola Ken Barozzi -| Committers | . | . -| Extra | . | . +| Committers | . +| Extra | . !!! Incubation status reports @@ -40,46 +40,46 @@ '' Completed tasks are shown by the completion date (YYYY-MM-dd). '' ! Identify the project to be incubated -|| id || date || item -| . | . | Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. -| . | . | If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. -| . | . | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. -| . | . | If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted. +|| date || item +| ....-..-.. | Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. +| ....-..-.. | If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. +| ....-..-.. | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. +| ....-..-.. | If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted. ! Interim responsibility -|| id || date || item -| . | . | Identify all the Mentors for the incubation, by asking all that can be Mentors. -| . | . | Subscribe all Mentors on the pmc and general lists. -| . | . | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) -| . | . | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki' +|| date || item +| ....-..-.. | Identify all the Mentors for the incubation, by asking all that can be Mentors. +| ....-..-.. | Subscribe all Mentors on the pmc and general lists. +| ....-..-.. | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) +| ....-..-.. | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki' ! Copyright -|| id || date || item -| . | . | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. -| . | . | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. +|| date || item +| ....-..-.. | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. +| ....-..-.. | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. ! Verify distribution rights -|| id || date || item -| . | . | Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute. -| . | . | Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. +|| date || item +| ....-..-.. | Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute. +| ....-..-.. | Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. ! Establish a list of active committers ! -|| id || date || item -| . | . | Check that all active committers have submitted a contributors agreement. -| . | . | Add all active committers in the STATUS file. -| . | . | Ask root for the creation of committers' accounts on cvs.apache.org. +|| date || item +| ....-..-.. | Check that all active committers have submitted a contributors agreement. +| ....-..-.. | Add all active committers in the STATUS file. +| ....-..-.. | Ask root for the creation of committers' accounts on cvs.apache.org. ! Infrastructure ! -|| id || date || item -| . | . | Ask infrastructure to create source repository modules and add thecommitters to the avail file. -| . | . | Ask infrastructure to set up and archive Mailing lists. -| . | . | Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). -| . | . | Migrate the project to our infrastructure. +|| date || item +| ....-..-.. | Ask infrastructure to create source repository modules and add thecommitters to the avail file. +| ....-..-.. | Ask infrastructure to set up and archive Mailing lists. +| ....-..-.. | Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). +| ....-..-.. | Migrate the project to our infrastructure. ! Project specific --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:38:13 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 49100 invoked from network); 1 Dec 2003 08:38:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:38:13 -0000 Received: (qmail 78719 invoked by uid 500); 1 Dec 2003 08:37:47 -0000 Delivered-To: julie93@example.com Received: (qmail 78675 invoked by uid 500); 1 Dec 2003 08:37:47 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 78644 invoked from network); 1 Dec 2003 08:37:47 -0000 Date: 1 Dec 2003 08:38:10 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/projects incubation-status-template.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:38:10 Added: site/projects incubation-status-template.cwiki Log: Add the template for project incubation status. This is our live document. Revision Changes Path 1.1 incubator/site/projects/incubation-status-template.cwiki Index: incubation-status-template.cwiki =================================================================== !!! X Project Incubation Status This page tracks the project status, incubator-wise. For more general project status, look on the project website. !!! Description The X Project is a wonderful project that does things and goes places. !!! News * none yet !!! Project info || item || type || reference | Website | www | [http://incubator.apache.org/X/|http://incubator.apache.org/X/] | . | wiki | . | Mailing list | dev | julie93@example.com | . | cvs | julie93@example.com | Bug tracking | . | Source code | CVS | incubator-X | Mentors | id1 | Name1 Surname1 | . | id2 | Name2 Surname2 | Committers | . | Extra | . !!! Incubation status reports * none yet !!! Incubation work items !! Project Setup This is the first phase on incubation, needed to start the julie93@example.com. '' Item assignment is shown by the Apache id.'' '' Completed tasks are shown by the completion date (YYYY-MM-dd). '' ! Identify the project to be incubated || date || item | ....-..-.. | Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. | ....-..-.. | If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. | ....-..-.. | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. | ....-..-.. | If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted. ! Interim responsibility || date || item | ....-..-.. | Identify all the Mentors for the incubation, by asking all that can be Mentors. | ....-..-.. | Subscribe all Mentors on the pmc and general lists. | ....-..-.. | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) | ....-..-.. | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki' ! Copyright || date || item | ....-..-.. | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. | ....-..-.. | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. ! Verify distribution rights || date || item | ....-..-.. | Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute. | ....-..-.. | Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. ! Establish a list of active committers ! || date || item | ....-..-.. | Check that all active committers have submitted a contributors agreement. | ....-..-.. | Add all active committers in the STATUS file. | ....-..-.. | Ask root for the creation of committers' accounts on cvs.apache.org. ! Infrastructure ! || date || item | ....-..-.. | Ask infrastructure to create source repository modules and add thecommitters to the avail file. | ....-..-.. | Ask infrastructure to set up and archive Mailing lists. | ....-..-.. | Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). | ....-..-.. | Migrate the project to our infrastructure. ! Project specific ''Add project specific tasks here.'' !! Incubation These action items have to be checked for during the whole incubation process. '' These items are not to be signed as done during incubation, as they may change during incubation. '' '' They are to be looked into and described in the status reports and completed in the request for incubation signoff. '' ! Collaborative Development * Have all of the active long-term volunteers been identified and acknowledged as committers on the project? * Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.) * Are project decisions being made in public by the committers? * Are the decision-making guidelines published and agreed to by all of the committers? ! Licensing awareness * Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers? ! Project Specific ''Add project specific tasks here.'' !! Exit ''Things to check for before voting the project out.'' ! Organizational acceptance of responsibility for the project * If graduating to an existing PMC, has the PMC voted to accept it? * If graduating to a new PMC, has the board voted to accept it? ! Incubator sign-off * Has the Incubator decided that the project has accomplished all of the above tasks? --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:40:41 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 50305 invoked from network); 1 Dec 2003 08:40:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:40:41 -0000 Received: (qmail 82884 invoked by uid 500); 1 Dec 2003 08:40:17 -0000 Delivered-To: julie93@example.com Received: (qmail 82833 invoked by uid 500); 1 Dec 2003 08:40:16 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 82820 invoked from network); 1 Dec 2003 08:40:16 -0000 From: julie93@example.com To: julie93@example.com Subject: [Incubator Wiki] Updated: NewProjectStatusTemplate X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Date: 2003-12-01T00:40:40 Editor: NicolaKen <julie93@example.com> Wiki: Incubator Wiki Page: NewProjectStatusTemplate This page has moved to the incubator CVS. Change Log: ------------------------------------------------------------------------------ @@ -1,130 +1,5 @@ -= Project X = - -Project X is a wonderful X Project that does things and goes places. - -= News = - -== YYYY-MM-DD One thing that happened Part II == - -This is what has happened on YYYY-MM-DD... blah... blah... - -== YYYY-MM-D2 One thing that happened == - -This is what has happened on YYYY-MM-D2... blah... blah... - -= Project info = - -|| '''item''' || type || '''reference''' || -|| Website || www || http://x.apache.org/ || -|| || wiki || http://wiki.apache.org/x/ || -|| Mailing list || dev || julie93@example.com || -|| || user || julie93@example.com || -|| || cvs || julie93@example.com || -|| Bug tracking || scarab || [link] || -|| Source code || CVS || incubator-x || -|| Mentors || name <id> || Mentor1 || -|| || name <id> || Mentor2 || -|| Committers || name <id> || Committer1 || -|| || name <id> || Committer2 || -|| Extra || x vote || [link] || - -= Incubation status reports = - -== YYYY-MM-DD == - -This is what has happeded about incubation till YYYY-MM-DD... blah... blah... - -= Incubation work items = - -== Project Setup == - -This is the first phase on incubation, needed to start the julie93@example.com. - -'' Item assignment is shown by the Apache id.'' -'' Completed tasks are shown by the completion date (YYYY-MM-dd). '' - -=== Identify the project to be incubated === -|| id || date || item || -|| || || Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product.|| -|| || || If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names.|| -|| || || If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.|| -|| || || If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.|| - -=== Interim responsibility === - -|| id || date || item || -|| || || Identify all the Mentors for the incubation, by asking all that can be Mentors. || -|| || || Subscribe all Mentors on the pmc and general lists. || -|| || || Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) || -|| || || Tell Mentors to track progress in the file 'incubator/projects/{project_name}.cwiki' || - -=== Copyright === - -|| id || date || item || -|| || || Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. || -|| || || Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. || - -=== Verify distribution rights === - -|| id || date || item || -|| || || Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute. || -|| || || Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.|| - -=== Establish a list of active committers === - -|| id || date || item || -|| || || Check that all active committers have submitted a contributors agreement. || -|| || || Add all active committers in the STATUS file. || -|| || || Ask root for the creation of committers' accounts on cvs.apache.org. || - -=== Infrastructure === - -|| id || date || item || -|| || || Ask infrastructure to create source repository modules and add thecommitters to the avail file. || -|| || || Ask infrastructure to set up and archive Mailing lists. || -|| || || Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). || -|| || || Migrate the project to our infrastructure. || - -=== Project specific === - -''Add project specific tasks here.'' - -== Incubation == - -These action items have to be checked for during the whole incubation process. - -'' These items are not to be signed as done during incubation, as they may change during incubation. '' -'' They are to be looked into and described in the status reports and completed in the request for incubation signoff. '' - -=== Collaborative Development === - - * Have all of the active long-term volunteers been identified and acknowledged as committers on the project? - - * Are there three or more independent committers? - -(The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.) - - *Are project decisions being made in public by the committers? - - *Are the decision-making guidelines published and agreed to by all of the committers? - -=== Licensing awareness === - - *Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers? - -=== Project Specific === - -''Add project specific tasks here.'' - -== Exit == - -'' Things to check for before voting the project out. '' - -=== Organizational acceptance of responsibility for the project === - - *If graduating to an existing PMC, has the PMC voted to accept it? - *If graduating to a new PMC, has the board voted to accept it? - -=== Incubator sign-off === - - *Has the Incubator decided that the project has accomplished all of the above tasks? +This page has moved to the incubator CVS, under +{{{ + incubator/site/projects/incubation-status-template.cwiki +}}} +[http://cvs.apache.org/viewcvs/incubator/site/projects/incubation-status-template.cwiki?rev=HEAD&content-type=text/vnd.viewcvs-markup] --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:41:09 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 50522 invoked from network); 1 Dec 2003 08:41:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:41:09 -0000 Received: (qmail 83225 invoked by uid 500); 1 Dec 2003 08:40:45 -0000 Delivered-To: julie93@example.com Received: (qmail 83179 invoked by uid 500); 1 Dec 2003 08:40:44 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 83166 invoked from network); 1 Dec 2003 08:40:44 -0000 From: julie93@example.com To: julie93@example.com Subject: [Incubator Wiki] Updated: FrontPage X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Date: 2003-12-01T00:41:08 Editor: NicolaKen <julie93@example.com> Wiki: Incubator Wiki Page: FrontPage This page has moved to the incubator CVS Change Log: ------------------------------------------------------------------------------ @@ -18,7 +18,6 @@ = Draft docs = * IncubatorCharterDraft - draft charter under development - * NewProjectStatusTemplate - draft of a new status boilerplate doc = Resources = --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:42:59 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 51258 invoked from network); 1 Dec 2003 08:42:59 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:42:59 -0000 Received: (qmail 84377 invoked by uid 500); 1 Dec 2003 08:42:34 -0000 Delivered-To: julie93@example.com Received: (qmail 84326 invoked by uid 500); 1 Dec 2003 08:42:34 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 84313 invoked from network); 1 Dec 2003 08:42:34 -0000 Date: 1 Dec 2003 08:42:57 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/projects directory.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:42:57 Modified: site/projects directory.cwiki Log: Fix table. Revision Changes Path 1.6 +3 -3 incubator/site/projects/directory.cwiki Index: directory.cwiki =================================================================== RCS file: /home/cvs/incubator/site/projects/directory.cwiki,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- directory.cwiki 1 Dec 2003 08:27:57 -0000 1.5 +++ directory.cwiki 1 Dec 2003 08:42:57 -0000 1.6 @@ -18,12 +18,12 @@ | . | wiki | . | Mailing list | dev | julie93@example.com | . | cvs | julie93@example.com -| Bug tracking | . +| Bug tracking | . | . | Source code | CVS | incubator-directory | Mentors | noel | Noel Bergman | . | nicolaken | Nicola Ken Barozzi -| Committers | . -| Extra | . +| Committers | . | . +| Extra | . | . !!! Incubation status reports --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:43:18 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 51499 invoked from network); 1 Dec 2003 08:43:18 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:43:18 -0000 Received: (qmail 84544 invoked by uid 500); 1 Dec 2003 08:42:53 -0000 Delivered-To: julie93@example.com Received: (qmail 84490 invoked by uid 500); 1 Dec 2003 08:42:53 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 84474 invoked from network); 1 Dec 2003 08:42:53 -0000 Date: 1 Dec 2003 08:43:17 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/projects incubation-status-template.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:43:17 Modified: site/projects incubation-status-template.cwiki Log: Fix table. Revision Changes Path 1.2 +3 -3 incubator/site/projects/incubation-status-template.cwiki Index: incubation-status-template.cwiki =================================================================== RCS file: /home/cvs/incubator/site/projects/incubation-status-template.cwiki,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- incubation-status-template.cwiki 1 Dec 2003 08:38:10 -0000 1.1 +++ incubation-status-template.cwiki 1 Dec 2003 08:43:16 -0000 1.2 @@ -18,12 +18,12 @@ | . | wiki | . | Mailing list | dev | julie93@example.com | . | cvs | julie93@example.com -| Bug tracking | . +| Bug tracking | . | . | Source code | CVS | incubator-X | Mentors | id1 | Name1 Surname1 | . | id2 | Name2 Surname2 -| Committers | . -| Extra | . +| Committers | . | . +| Extra | . | . !!! Incubation status reports --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:44:20 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 51903 invoked from network); 1 Dec 2003 08:44:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:44:20 -0000 Received: (qmail 84910 invoked by uid 500); 1 Dec 2003 08:43:56 -0000 Delivered-To: julie93@example.com Received: (qmail 84850 invoked by uid 500); 1 Dec 2003 08:43:55 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 84832 invoked from network); 1 Dec 2003 08:43:55 -0000 Date: 1 Dec 2003 08:44:19 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/projects geronimo.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:44:19 Modified: site/projects geronimo.cwiki Log: Fixed in Forrest the link bug -> restoring relative links. Revision Changes Path 1.12 +2 -2 incubator/site/projects/geronimo.cwiki Index: geronimo.cwiki =================================================================== RCS file: /home/cvs/incubator/site/projects/geronimo.cwiki,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- geronimo.cwiki 28 Nov 2003 15:04:43 -0000 1.11 +++ geronimo.cwiki 1 Dec 2003 08:44:19 -0000 1.12 @@ -8,7 +8,7 @@ !!2003-11-11 We have recieved a mail [a letter on behalf of -the JBoss Group, LCC dated October 31, 2003|http://incubator.apache.org/projects/geronimo/20031031_jboss.pdf] that asks for +the JBoss Group, LCC dated October 31, 2003|geronimo/20031031_jboss.pdf] that asks for clarifiations regarding similarity between parts of the Geronimo codebase and the JBoss codebase. @@ -70,7 +70,7 @@ of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms? *Check all clarification requests from the JBoss group, and in - particular check that [this letter dated 2003-10-31|http://incubator.apache.org/projects/geronimo/20031031_jboss.pdf] + particular check that [this letter dated 2003-10-31|geronimo/20031031_jboss.pdf] has been properly addressed. !!!Establish a list of active committers --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:49:52 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 53959 invoked from network); 1 Dec 2003 08:49:51 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:49:51 -0000 Received: (qmail 89132 invoked by uid 500); 1 Dec 2003 08:49:27 -0000 Delivered-To: julie93@example.com Received: (qmail 89070 invoked by uid 500); 1 Dec 2003 08:49:26 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 89056 invoked from network); 1 Dec 2003 08:49:26 -0000 Date: 1 Dec 2003 08:49:50 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site site.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:49:50 Modified: site site.xml Log: Add other links to external resources. Revision Changes Path 1.17 +2 -0 incubator/site/site.xml Index: site.xml =================================================================== RCS file: /home/cvs/incubator/site/site.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- site.xml 19 Nov 2003 13:38:26 -0000 1.16 +++ site.xml 1 Dec 2003 08:49:50 -0000 1.17 @@ -71,6 +71,8 @@ <apache href="http://www.apache.org/"> <foundation href="foundation/"> <roles href="roles.html"/> + <members href="members.html"/> + <officers href="index.html"/> </foundation> <licenses href="licenses"> <license href="LICENSE"/> --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 08:50:09 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 54102 invoked from network); 1 Dec 2003 08:50:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 08:50:09 -0000 Received: (qmail 89305 invoked by uid 500); 1 Dec 2003 08:49:44 -0000 Delivered-To: julie93@example.com Received: (qmail 89245 invoked by uid 500); 1 Dec 2003 08:49:44 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 89232 invoked from network); 1 Dec 2003 08:49:43 -0000 Date: 1 Dec 2003 08:50:07 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator/site/incubation Process_Description.cwiki X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 00:50:07 Modified: site/incubation Process_Description.cwiki Log: Use site: links Revision Changes Path 1.5 +2 -2 incubator/site/incubation/Process_Description.cwiki Index: Process_Description.cwiki =================================================================== RCS file: /home/cvs/incubator/site/incubation/Process_Description.cwiki,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- Process_Description.cwiki 29 Nov 2003 15:44:40 -0000 1.4 +++ Process_Description.cwiki 1 Dec 2003 08:50:07 -0000 1.5 @@ -4,11 +4,11 @@ [incubation-process.png] -Readers should also review the [Roles and Responsibilities |Roles_and_Responsibilities] document for a description of the various parties involved in the Incubation process. +Readers should also review the [Roles and Responsibilities |site:incubation/rolesandersponsibilities] document for a description of the various parties involved in the Incubation process. !!Establishment -The first thing you will want to do is find a __Champion __ for your project. One way to do this is to explore the Apache site to find similar projects. Spend some time reading both the projects' web pages and mailing lists. By simply lurking on the mailing lists (see Mailing Lists section in this document), you may get ideas about who you would like to ask to help you with your project proposal. However, Champions must either be ASF [members |http://www.apache.org/foundation/members.html] or [officers |http://www.apache.org/foundation/index.html] (see the Champion section later in this document for more on Champion criteria and responsibilities). 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 complement the ASF. 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 first thing you will want to do is find a __Champion __ for your project. One way to do this is to explore the Apache site to find similar projects. Spend some time reading both the projects' web pages and mailing lists. By simply lurking on the mailing lists (see Mailing Lists section in this document), you may get ideas about who you would like to ask to help you with your project proposal. However, Champions must either be ASF [members |ext:apache/foundation/members] or [officers |ext:apache/foundation/officers] (see the Champion section later in this document for more on Champion criteria and responsibilities). 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 complement the ASF. 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 description (consistent with the candidate description detailed below) endorsed by a __Champion__. --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 09:25:11 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 69501 invoked from network); 1 Dec 2003 09:25:11 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 09:25:11 -0000 Received: (qmail 16831 invoked by uid 500); 1 Dec 2003 09:24:46 -0000 Delivered-To: julie93@example.com Received: (qmail 16751 invoked by uid 500); 1 Dec 2003 09:24:46 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 16738 invoked from network); 1 Dec 2003 09:24:45 -0000 From: julie93@example.com To: julie93@example.com Subject: [Incubator Wiki] Updated: FrontPage X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Date: 2003-12-01T01:25:10 Editor: NicolaKen <julie93@example.com> Wiki: Incubator Wiki Page: FrontPage Add project proposals section Change Log: ------------------------------------------------------------------------------ @@ -15,6 +15,12 @@ * [http://wiki.apache.org/geronimo Geronimo] += Project proposals = + +''add proposals here'' + + * [http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages old wiki proposals page] (please don't use the old page for new proposals or changes to the old docs) + = Draft docs = * IncubatorCharterDraft - draft charter under development --------------------------------------------------------------------- To unsubscribe, e-mail: julie93@example.com For additional commands, e-mail: julie93@example.com From cvsjulie93@example.com Mon Dec 01 10:18:48 2003 Return-Path: <cvsjulie93@example.com> Delivered-To: julie93@example.com Received: (qmail 96566 invoked from network); 1 Dec 2003 10:18:48 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur-2.apache.org with SMTP; 1 Dec 2003 10:18:48 -0000 Received: (qmail 75042 invoked by uid 500); 1 Dec 2003 10:18:22 -0000 Delivered-To: julie93@example.com Received: (qmail 74989 invoked by uid 500); 1 Dec 2003 10:18:22 -0000 Mailing-List: contact julie93@example.com; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: <mailto:julie93@example.com> List-Help: <mailto:julie93@example.com> List-Unsubscribe: <mailto:julie93@example.com> List-Subscribe: <mailto:julie93@example.com> Reply-To: julie93@example.com Delivered-To: mailing list julie93@example.com Received: (qmail 74976 invoked by uid 500); 1 Dec 2003 10:18:22 -0000 Delivered-To: julie93@example.com Date: 1 Dec 2003 10:18:47 -0000 Message-ID: <julie93@example.com> From: julie93@example.com To: julie93@example.com Subject: cvs commit: incubator-site/build/site/incubation incubation-process.png Incubation_Policy.html Incubation_Policy.pdf Process_Description.html Process_Description.pdf Roles_and_Responsibilities.html Roles_and_Responsibilities.pdf X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N nicolaken 2003/12/01 02:18:47 Modified: build/site/incubation Incubation_Policy.html Incubation_Policy.pdf Process_Description.html Process_Description.pdf Roles_and_Responsibilities.html Roles_and_Responsibilities.pdf Added: build/site/incubation incubation-process.png Log: Update the incubation docs without draft status and new process image. Revision Changes Path 1.7 +30 -42 incubator-site/build/site/incubation/Incubation_Policy.html Index: Incubation_Policy.html =================================================================== RCS file: /home/cvs/incubator-site/build/site/incubation/Incubation_Policy.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- Incubation_Policy.html 28 Nov 2003 15:49:54 -0000 1.6 +++ Incubation_Policy.html 1 Dec 2003 10:18:47 -0000 1.7 @@ -413,28 +413,16 @@ </h4> <div style="margin-left: 0 ; border: 2px"> <p>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. </p> -<pre class="code">&#13; -&#13; -&#13; - establishment |------------| acceptance |----------| engagement |----------|&#13; ----------------&gt; | Candidate |-------------&gt; | Podling |---------------&gt;| Project |&#13; - |------------| |----------|--| |----------|&#13; - | | ^ |&#13; - | | | | continuation&#13; - V | |--------|&#13; - rejection | &#13; - V&#13; - termination&#13; - &#13; -</pre> +<p> +<img alt="incubation-process.png" src="incubation-process.png"></p> </div> </div> -<a name="N1004D"></a><a name="Entry+to+Incubation%0D%0A"></a> +<a name="N1004F"></a><a name="Entry+to+Incubation%0D%0A"></a> <h3>Entry to Incubation&#13; </h3> <div style="margin-left: 0 ; border: 2px"> <p>Entry to Incubation requires a number of hurdles be passed. </p> -<a name="N10053"></a><a name="Proposal%0D%0A"></a> +<a name="N10055"></a><a name="Proposal%0D%0A"></a> <h4>Proposal&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -454,7 +442,7 @@ <strong>Need to provide a short list</strong> </p> </div> -<a name="N1006D"></a><a name="Acceptance+of+Proposal+by+Sponsor%0D%0A"></a> +<a name="N1006F"></a><a name="Acceptance+of+Proposal+by+Sponsor%0D%0A"></a> <h4>Acceptance of Proposal by Sponsor&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -468,7 +456,7 @@ <p>The Incubator PMC MAY immediately accept the Candidate, or may (at the discretion of the Incubator PMC) require a successful VOTE by the Incubator PMC. </p> <p>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. </p> </div> -<a name="N10080"></a><a name="Creation+of+Podling%0D%0A"></a> +<a name="N10082"></a><a name="Creation+of+Podling%0D%0A"></a> <h4>Creation of Podling&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -476,12 +464,12 @@ <p>Upon acceptance by the Incubator PMC, the Podling's Mentor becomes a member of the Incubator PMC (should they not already be one). </p> </div> </div> -<a name="N10088"></a><a name="Incubation+Activities%0D%0A"></a> +<a name="N1008A"></a><a name="Incubation+Activities%0D%0A"></a> <h3>Incubation Activities&#13; </h3> <div style="margin-left: 0 ; border: 2px"> <p>The following sections detail the minimum activities that must be undertaken by the various parties during an Incuabation process. </p> -<a name="N1008E"></a><a name="Setting+Up+a+New+Podling%0D%0A"></a> +<a name="N10090"></a><a name="Setting+Up+a+New+Podling%0D%0A"></a> <h4>Setting Up a New Podling&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -494,7 +482,7 @@ <li>Incubator PMC mandating a helper Mentor </li> </ul> </div> -<a name="N1009C"></a><a name="Ongoing+Activities%0D%0A"></a> +<a name="N1009E"></a><a name="Ongoing+Activities%0D%0A"></a> <h4>Ongoing Activities&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -511,7 +499,7 @@ </ul> <p>The Mentor MUST ensure that the STATUS file is up to date at all times. </p> </div> -<a name="N100B5"></a><a name="Review+of+Activity"></a> +<a name="N100B7"></a><a name="Review+of+Activity"></a> <h4>Review of Activity</h4> <div style="margin-left: 0 ; border: 2px"> <p>Each Podling in Incubation SHALL undergo a regular review of progress by the Incubator PMC. Such reviews SHALL occur at least quaterly. 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. </p> @@ -524,7 +512,7 @@ </ul> <p>Termination and Escalation are discussed in more detail in section "Exitting the Incubator". </p> </div> -<a name="N100C8"></a><a name="Disputing+an+Assessment%0D%0A"></a> +<a name="N100CA"></a><a name="Disputing+an+Assessment%0D%0A"></a> <h4>Disputing an Assessment&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -545,7 +533,7 @@ </ul> <p>The decision of the Board of the Apache Software Foundation is final. </p> </div> -<a name="N100E6"></a><a name="Continuation%0D%0A"></a> +<a name="N100E8"></a><a name="Continuation%0D%0A"></a> <h4>Continuation&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -553,12 +541,12 @@ <p>The Mentor SHALL review the contents of the continuation recommendation and ensure that the development recommendations are carried out over the following review period. </p> </div> </div> -<a name="N100EE"></a><a name="Podling+Constraints%0D%0A"></a> +<a name="N100F0"></a><a name="Podling+Constraints%0D%0A"></a> <h3>Podling Constraints&#13; </h3> <div style="margin-left: 0 ; border: 2px"> <p>While in Incubation, Podlings are constrained in the actions they can undertake. </p> -<a name="N100F4"></a><a name="Branding%0D%0A"></a> +<a name="N100F6"></a><a name="Branding%0D%0A"></a> <h4>Branding&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -570,7 +558,7 @@ <p>Podlings wishing to use a different disclaimer message MUST have the disclaimer approved by the Incubator PMC prior to use. </p> <p>Podlings websites SHOULD contain the Apache Incubator Project logo as sign of affiliation. </p> </div> -<a name="N10104"></a><a name="Releases%0D%0A"></a> +<a name="N10106"></a><a name="Releases%0D%0A"></a> <h4>Releases&#13; </h4> <div style="margin-left: 0 ; border: 2px"> @@ -584,11 +572,11 @@ <li>the release archive MUST contain an Incubation disclaimer (as described in the previous section), clearly visible in the main documentation or README file. </li> </ul> </div> -<a name="N10117"></a><a name="Use+of+Apache+Resources"></a> +<a name="N10119"></a><a name="Use+of+Apache+Resources"></a> <h4>Use of Apache Resources</h4> <div style="margin-left: 0 ; border: 2px"> <p>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. </p> -<a name="N1011D"></a><a name="Website"></a> +<a name="N1011F"></a><a name="Website"></a> <h5>Website</h5> <div style="margin-left: 0 ; border: 2px"> <ul> @@ -625,11 +613,11 @@ </div> </div> </div> -<a name="N10149"></a><a name="Exitting+the+Incubator"></a> +<a name="N1014B"></a><a name="Exitting+the+Incubator"></a> <h3>Exitting the Incubator</h3> <div style="margin-left: 0 ; border: 2px"> <p>This section describes the requirements and process for exitting the Incubator. </p> -<a name="N1014F"></a><a name="Minimum+Exit+Requirements"></a> +<a name="N10151"></a><a name="Minimum+Exit+Requirements"></a> <h4>Minimum Exit Requirements</h4> <div style="margin-left: 0 ; border: 2px"> <p>Prior to escalation to the ASF, a Podling needs to show that : </p> @@ -693,27 +681,27 @@ <li>Developers tied into ASF PGP web of trust </li> </ul> </div> -<a name="N101B1"></a><a name="Termination+of+a+Podling"></a> +<a name="N101B3"></a><a name="Termination+of+a+Podling"></a> <h4>Termination of a Podling</h4> <div style="margin-left: 0 ; border: 2px"> <p>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. </p> </div> -<a name="N101B7"></a><a name="Migration+as+a+Top+Level+Project"></a> +<a name="N101B9"></a><a name="Migration+as+a+Top+Level+Project"></a> <h4>Migration as a Top Level Project</h4> <div style="margin-left: 0 ; border: 2px"> <p>In cases where a Podling has successfully completed Incubation, and is exitting the Incubator to become a Top Level Project, the Incubator PMC SHALL provide a recommendation to the board that the Podling is ready to escalate. The recommendation SHALL include a draft resolution for the board to vote on. </p> </div> -<a name="N101BD"></a><a name="Migration+as+a+sub-project"></a> +<a name="N101BF"></a><a name="Migration+as+a+sub-project"></a> <h4>Migration as a sub-project</h4> <div style="margin-left: 0 ; border: 2px"> <p>In cases where a Podling has successfully completed Incubation, and is exitting 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 escalate. </p> </div> </div> -<a name="N101C3"></a><a name="Roles+in+the+Incubation+Process"></a> +<a name="N101C5"></a><a name="Roles+in+the+Incubation+Process"></a> <h3>Roles in the Incubation Process</h3> <div style="margin-left: 0 ; border: 2px"> <p>This section describes the roles involved in the Incubation process. </p> -<a name="N101C9"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a> +<a name="N101CB"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a> <h4>Incubator Project Management Committee (PMC)</h4> <div style="margin-left: 0 ; border: 2px"> <p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html) </p> @@ -729,22 +717,22 @@ <li>be terminated. </li> </ul> </div> -<a name="N101E2"></a><a name="Chair+of+the+Incubator+PMC"></a> +<a name="N101E4"></a><a name="Chair+of+the+Incubator+PMC"></a> <h4>Chair of the Incubator PMC</h4> <div style="margin-left: 0 ; border: 2px"> <p>The person appointed by the Board of Directors to have primary responsibility for oversight of the Incubator Project, its policies, and policy implementation. </p> </div> -<a name="N101E8"></a><a name="Candidate"></a> +<a name="N101EA"></a><a name="Candidate"></a> <h4>Candidate</h4> <div style="margin-left: 0 ; border: 2px"> <p>A project that is proposed for incubation. </p> </div> -<a name="N101EE"></a><a name="Champion"></a> +<a name="N101F0"></a><a name="Champion"></a> <h4>Champion</h4> <div style="margin-left: 0 ; border: 2px"> <p>A Member of the Apache Software Foundation who supports a Candidate's application for Incubation and who supports and assists the Podling through the Incubation process. </p> </div> -<a name="N101F4"></a><a name="Sponsor"></a> +<a name="N101F6"></a><a name="Sponsor"></a> <h4>Sponsor</h4> <div style="margin-left: 0 ; border: 2px"> <p>The Sponsor is the entity within the ASF that makes the determination that a candidate would make a worthy addition to the ASF, and agrees to take on the candidate in question (or in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation process. </p> @@ -755,12 +743,12 @@ <li>The Incubator PMC. In this case, the Incubator PMC agrees that the project in question will make a good addition to the ASF, but there is no clear "owner" of the candidate should it successfully complete incubation. An incubation exit requirement for such candidates will be the identification (and successfuly lobbying) of an "owner" entity - either the board (and the candidate will be a TLP) or another project. </li> </ul> </div> -<a name="N10203"></a><a name="Mentor"></a> +<a name="N10205"></a><a name="Mentor"></a> <h4>Mentor</h4> <div style="margin-left: 0 ; border: 2px"> <p>A Mentor is a role undertaken by a permanent member of the Apache Software Foundation and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above). Upon acceptance by the Incubator PMC, the Mentor automatically becomes a member of the Incubator PMC. A Mentor has specific responsibilities towards the Incubator PMC, the Sponsor and towards the members of the assigned Podling. </p> </div> -<a name="N10209"></a><a name="Committers"></a> +<a name="N1020B"></a><a name="Committers"></a> <h4>Committers</h4> <div style="margin-left: 0 ; border: 2px"> <p>The candidate shall declare an initial set of committers. On acceptance of a candidate project, the assigned Mentor shall be given access to the Podling's cvs repository for the duration of the incubation process. This is to allow the Mentor to perform their incubation duties, and is for administrative purposes only. To be given full committer privileges, such as the right to add new code to the repository, the Mentor must earn them as would any other potential new committer. In some cases, the Mentor may be part of the initial set of declared committers, but this is not a requirement of the Incubation process. </p> 1.6 +148 -148 incubator-site/build/site/incubation/Incubation_Policy.pdf <<Binary file>> 1.7 +9 -20 incubator-site/build/site/incubation/Process_Description.html Index: Process_Description.html =================================================================== RCS file: /home/cvs/incubator-site/build/site/incubation/Process_Description.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- Process_Description.html 28 Nov 2003 15:49:54 -0000 1.6 +++ Process_Description.html 1 Dec 2003 10:18:47 -0000 1.7 @@ -276,21 +276,10 @@ <h3>The Process of Incubation</h3> <div style="margin-left: 0 ; border: 2px"> <p>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. </p> -<pre class="code">&#13; -&#13; - establishment |------------| acceptance |----------| engagement |----------|&#13; ----------------&gt; | Candidate |-------------&gt; | Podling |---------------&gt;| Project |&#13; - |------------| |----------|--| |----------|&#13; - | | ^ |&#13; - | | | | continuation&#13; - V | |--------|&#13; - rejection | &#13; - V&#13; - termination&#13; - &#13; -</pre> -<p>Readers should also review the <a href="Roles_and_Responsibilities.html">Roles and Responsibilities </a>document for a description of the various parties involved in the Incubation process. </p> -<a name="N10015"></a><a name="Establishment"></a> +<p> +<img alt="incubation-process.png" src="incubation-process.png"></p> +<p>Readers should also review the <a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities </a>document for a description of the various parties involved in the Incubation process. </p> +<a name="N10017"></a><a name="Establishment"></a> <h4>Establishment</h4> <div style="margin-left: 0 ; border: 2px"> <p>The first thing you will want to do is find a <strong>Champion </strong> for your project. One way to do this is to explore the Apache site to find similar projects. Spend some time reading both the projects' web pages and mailing lists. By simply lurking on the mailing lists (see Mailing Lists section in this document), you may get ideas about who you would like to ask to help you with your project proposal. However, Champions must either be ASF <a href="http://www.apache.org/foundation/members.html">members </a>or <a href="http://www.apache.org/foundation/index.html">officers </a>(see the Champion section later in this document for more on Champion criteria and responsibilities). 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 complement the ASF. 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. </p> @@ -298,7 +287,7 @@ <p>A <strong>Candidate </strong> project description should be submitted to the relevant mailing list(s) of a <strong>Sponsor </strong> (see the Mailing Lists section in this document). See the <a href="http://jakarta.apache.org/site/newproject.html">Jakarta Guidelines for New Projects </a>for a list of issues that should be addressed in your proposal; also see <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF Proposal Pages </a>for other examples. Typically a <strong>Candidate </strong> 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. </p> <p>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 you proposal - however, if you feel that your candidate project is not being addresed you may want to specifically request a decision on the Candidate by the Sponsor by posting a request to the decision making list (either pmc@{project-name}.apache.org or julie93@example.com; see Mailing List section for more details). 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. </p> </div> -<a name="N10040"></a><a name="Acceptance"></a> +<a name="N10042"></a><a name="Acceptance"></a> <h4>Acceptance</h4> <div style="margin-left: 0 ; border: 2px"> <p>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. </p> @@ -307,7 +296,7 @@ <p>One of the roles of the Mentor 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 Mentor can help you by guiding and protecting you from much of this based on his/her experience in the process and familiarity with the policy and procedures of incubation. In performing their role, the Mentor is representing the Sponsor. </p> <p>Your Sponsor, represented by your Mentor, has specific responsibilities towards you and the Incubator PMC. There are a bunch of administrative and technical actions to take care of. Your Mentor is responsible for ensuring that these things happen quickly and efficiently. Also, your Mentor is 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. </p> </div> -<a name="N10057"></a><a name="Review"></a> +<a name="N10059"></a><a name="Review"></a> <h4>Review</h4> <div style="margin-left: 0 ; border: 2px"> <p>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 things and bad thing. Exit via escalation 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
{'source': 'Apache Software Foundation Public Mail Archives'}