Modified: incubator/public/trunk/site-publish/projects/kabuki.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/projects/kabuki.html?view=diff&rev=469371&r1=469370&r2=469371 ============================================================================== --- incubator/public/trunk/site-publish/projects/kabuki.html (original) +++ incubator/public/trunk/site-publish/projects/kabuki.html Mon Oct 30 21:01:24 2006 @@ -1,598 +1,598 @@ - - - - - - - Kabuki Project Incubation Status - Apache Incubator - - - - - - - -
-The Apache Software Foundation - -Apache Incubator -
- - - - - - - - - - - - - - -

-

- Kabuki Project Incubation Status -

-
-

- This page tracks the project status, incubator-wise. For more - general project status, look on the - project - website. -

-
-

- Description -

-
-

- The Kabuki project is a toolkit for building rich browser-based - clients using AJAX technology. The framework will consist of - user interface widgets as well as infrastructure to enable - communication with server-side logic. -

-
-

- News -

-
-
    -
  • 2006-06-24 Project requested to be withdrawn from incubation.
  • -
  • 2006-01-26 Project accepted for incubation in Apache.
  • -
  • 2006-01-23 Project proposal updated for final vote.
  • -
  • 2006-01-16 Call for vote.
  • -
  • 2006-01-11 Project proposal updated.
  • -
  • 2005-12-20 Project announced publicly.
  • -
-
-

- Project info -

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemTypeReference
Websitewww - http://incubator.apache.org/kabuki/ - to be created -
Websitewikito be created
Mailing listppmckabuki-ppmc@incubator.apache.org
Mailing listdev - kabuki-dev@incubator.apache.org - [Subscribe | Unsubscribe] -
Mailing listuser - kabuki-user@incubator.apache.org - [Subscribe | Unsubscribe] -
Mailing listcommits - kabuki-commits@incubator.apache.org - [Subscribe | Unsubscribe] -
Bug trackingbugzillaKABUKI to be created
Source codesvn - https://svn.apache.org/repos/asf/incubator/kabuki/ -
-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
RoleApache IdName (Given Surname)
ChampionrubysSam Ruby
MentorandycAndy Clark
MentorrubysSam Ruby
MentorpzfPaul Fremantle
MentorsanjivaSanjiva Weerawarana
CommitterandycAndy Clark
CommittertbdConrad Damon
CommittertbdRoss Dargahi
CommittertbdRoland Schemers
CommittertbdParag Shah
CommittertbdGreg Solovyev
CommittermmarinschekMartin Marinschek
-

-

- Incubation status reports -

-
-
    -
  • none yet
  • -
-
-

- Incubation work items -

-
-

- Project Setup -

-
-

- This is the first phase on incubation, needed to start the - project at Apache. DONE. -

-

- Interim responsibility -

-
- - - - - - - - - - - - - - - - - - - - - -
DateItem
2006-01-26 - 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 SVN modules. (to be - done by PMC chair) -
....-..-.. - Tell Mentors to track progress in the file - 'incubator/projects/kabuki.html' which is generated - from the XML status file. -
-
-

- Copyright -

-
- - - - - - - - - - - - - -
DateItem
....-..-.. - 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 -

-
- - - - - - - - - - - - - -
DateItem
....-..-.. - Check and make sure that for all code included with the - distribution that is not under the Apache license have the - right to combine with Apache-licensed code and redistribute. -
2006-02-13 - 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 -

-
- - - - - - - - - - - - - - - - - -
DateItem
....-..-.. - 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 - people.apache.org. -
-
-

- Infrastructure -

-
- - - - - - - - - - - - - - - - - - - - - -
DateItem
2006-02-20 - Ask infrastructure to create source repository modules and - grant the committers karma. Done. -
2006-02-18 - Ask infrastructure to set up and archive Mailing lists. - Done. -
....-..-.. - Decide about and then ask infrastructure to setup an issue - tracking 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? -
  • -
-
-
-
-

- - + + + + + + + Kabuki Project Incubation Status - Apache Incubator + + + + + + + +
+The Apache Software Foundation + +Apache Incubator +
+ + + + + + + + + + + + + + +

+

+ Kabuki Project Incubation Status +

+
+

+ This page tracks the project status, incubator-wise. For more + general project status, look on the + project + website. +

+
+

+ Description +

+
+

+ The Kabuki project is a toolkit for building rich browser-based + clients using AJAX technology. The framework will consist of + user interface widgets as well as infrastructure to enable + communication with server-side logic. +

+
+

+ News +

+
+
    +
  • 2006-06-24 Project requested to be withdrawn from incubation.
  • +
  • 2006-01-26 Project accepted for incubation in Apache.
  • +
  • 2006-01-23 Project proposal updated for final vote.
  • +
  • 2006-01-16 Call for vote.
  • +
  • 2006-01-11 Project proposal updated.
  • +
  • 2005-12-20 Project announced publicly.
  • +
+
+

+ Project info +

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ItemTypeReference
Websitewww + http://incubator.apache.org/kabuki/ + to be created +
Websitewikito be created
Mailing listppmckabuki-ppmc@incubator.apache.org
Mailing listdev + kabuki-dev@incubator.apache.org + [Subscribe | Unsubscribe] +
Mailing listuser + kabuki-user@incubator.apache.org + [Subscribe | Unsubscribe] +
Mailing listcommits + kabuki-commits@incubator.apache.org + [Subscribe | Unsubscribe] +
Bug trackingbugzillaKABUKI to be created
Source codesvn + https://svn.apache.org/repos/asf/incubator/kabuki/ +
+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
RoleApache IdName (Given Surname)
ChampionrubysSam Ruby
MentorandycAndy Clark
MentorrubysSam Ruby
MentorpzfPaul Fremantle
MentorsanjivaSanjiva Weerawarana
CommitterandycAndy Clark
CommittertbdConrad Damon
CommittertbdRoss Dargahi
CommittertbdRoland Schemers
CommittertbdParag Shah
CommittertbdGreg Solovyev
CommittermmarinschekMartin Marinschek
+

+

+ Incubation status reports +

+
+
    +
  • none yet
  • +
+
+

+ Incubation work items +

+
+

+ Project Setup +

+
+

+ This is the first phase on incubation, needed to start the + project at Apache. DONE. +

+

+ Interim responsibility +

+
+ + + + + + + + + + + + + + + + + + + + + +
DateItem
2006-01-26 + 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 SVN modules. (to be + done by PMC chair) +
....-..-.. + Tell Mentors to track progress in the file + 'incubator/projects/kabuki.html' which is generated + from the XML status file. +
+
+

+ Copyright +

+
+ + + + + + + + + + + + + +
DateItem
....-..-.. + 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 +

+
+ + + + + + + + + + + + + +
DateItem
....-..-.. + Check and make sure that for all code included with the + distribution that is not under the Apache license have the + right to combine with Apache-licensed code and redistribute. +
2006-02-13 + 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 +

+
+ + + + + + + + + + + + + + + + + +
DateItem
....-..-.. + 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 + people.apache.org. +
+
+

+ Infrastructure +

+
+ + + + + + + + + + + + + + + + + + + + + +
DateItem
2006-02-20 + Ask infrastructure to create source repository modules and + grant the committers karma. Done. +
2006-02-18 + Ask infrastructure to set up and archive Mailing lists. + Done. +
....-..-.. + Decide about and then ask infrastructure to setup an issue + tracking 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? +
  • +
+
+
+
+

+ + Modified: incubator/public/trunk/site-publish/projects/lucene.net.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/projects/lucene.net.html?view=diff&rev=469371&r1=469370&r2=469371 ============================================================================== --- incubator/public/trunk/site-publish/projects/lucene.net.html (original) +++ incubator/public/trunk/site-publish/projects/lucene.net.html Mon Oct 30 21:01:24 2006 @@ -1,630 +1,630 @@ - - - - - - - Lucene.Net Incubation Status - - Apache Incubator - - - - - - - -
-The Apache Software Foundation - -Apache Incubator -
- - - - - - - - - - - - - - -

-

- Lucene.Net Project Incubation Status -

-
-
-

- Description - -

-
-

Lucene.Net is a source code, class-per-class, API-per-API and algorithmatic port of the Java Lucene search engine to the C# and .NET platform utilizing Microsoft .NET Framework.

-

Lucene.Net sticks to the APIs and classes used in the original Java implementation of Lucene. The API names as well as class names are preserved with the intention of giving Lucene.Net the look and feel of the C# language and the .NET Framework. For example, the method Hits.length() in the Java implementation now reads Hits.Length() in the C# port.

-

In addition to the APIs and classes port to C#, the algorithm of Java Lucene is ported to C# Lucene. This means an index created with Java Lucene is back-and-forth compatible with the C# Lucene; both at reading, writing and updating. In fact a Lucene index can be concurrently searched and updated using Java Lucene and C# Lucene processes.

-
-
-

- News - -

-
-
    -
  • The old project website is at SourceForge.Net
  • -
  • Lucene.Net is also known as DotLucene on SourceForge.Net
  • -
-
-

- Project info - -

-
- -

If the project website and code repository are not yet setup, use the -following table: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
item -type -reference -
Website -www - - http://incubator.apache.org/lucene.net - -
Wiki -wiki - - http://wiki.apache.org/lucene.net - -
Mailing list -dev -lucene-net-dev@incubator.apache.org -
- user -lucene-net-user@incubator.apache.org -
- commits -lucene-net-commits@incubator.apache.org -
Bug tracking -Jira - - http://issues.apache.org/jira/browse/LUCENENET - -
Source code -SVN - - https://svn.apache.org/repos/asf/incubator/lucene.net/ - -
Mentors -ehatcher -Erik Hatcher -
Committers -aroush -George Aroush -
-
-

- Incubation status reports - -

-
-
    -
  • none yet -
  • -
-
-

- Incubation work items - -

-
-

- Project Setup - -

-
-

This is the first phase on incubation, needed to start the project at -Apache. -

-

- 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 SVN 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}.html' -
-
-

- 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 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 -people.apache.org. -
-
-

- Infrastructure - -

-
- - - - - - - - - - - - - - - - - - - - - -
date -item -
... -Ask infrastructure to create source repository modules and grant the -committers karma. -
... -Ask infrastructure to set up and archive Mailing lists. -
... -Decide about and then ask infrastructure to setup an issue tracking -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? -
  • -
-
-
-
-

- - + + + + + + + Lucene.Net Incubation Status + - Apache Incubator + + + + + + + +
+The Apache Software Foundation + +Apache Incubator +
+ + + + + + + + + + + + + + +

+

+ Lucene.Net Project Incubation Status +

+
+
+

+ Description + +

+
+

Lucene.Net is a source code, class-per-class, API-per-API and algorithmatic port of the Java Lucene search engine to the C# and .NET platform utilizing Microsoft .NET Framework.

+

Lucene.Net sticks to the APIs and classes used in the original Java implementation of Lucene. The API names as well as class names are preserved with the intention of giving Lucene.Net the look and feel of the C# language and the .NET Framework. For example, the method Hits.length() in the Java implementation now reads Hits.Length() in the C# port.

+

In addition to the APIs and classes port to C#, the algorithm of Java Lucene is ported to C# Lucene. This means an index created with Java Lucene is back-and-forth compatible with the C# Lucene; both at reading, writing and updating. In fact a Lucene index can be concurrently searched and updated using Java Lucene and C# Lucene processes.

+
+
+

+ News + +

+
+
    +
  • The old project website is at SourceForge.Net
  • +
  • Lucene.Net is also known as DotLucene on SourceForge.Net
  • +
+
+

+ Project info + +

+
+ +

If the project website and code repository are not yet setup, use the +following table: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
item +type +reference +
Website +www + + http://incubator.apache.org/lucene.net + +
Wiki +wiki + + http://wiki.apache.org/lucene.net + +
Mailing list +dev +lucene-net-dev@incubator.apache.org +
+ user +lucene-net-user@incubator.apache.org +
+ commits +lucene-net-commits@incubator.apache.org +
Bug tracking +Jira + + http://issues.apache.org/jira/browse/LUCENENET + +
Source code +SVN + + https://svn.apache.org/repos/asf/incubator/lucene.net/ + +
Mentors +ehatcher +Erik Hatcher +
Committers +aroush +George Aroush +
+
+

+ Incubation status reports + +

+
+
    +
  • none yet +
  • +
+
+

+ Incubation work items + +

+
+

+ Project Setup + +

+
+

This is the first phase on incubation, needed to start the project at +Apache. +

+

+ 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 SVN 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}.html' +
+
+

+ 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 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 +people.apache.org. +
+
+

+ Infrastructure + +

+
+ + + + + + + + + + + + + + + + + + + + + +
date +item +
... +Ask infrastructure to create source repository modules and grant the +committers karma. +
... +Ask infrastructure to set up and archive Mailing lists. +
... +Decide about and then ask infrastructure to setup an issue tracking +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: cvs-unsubscribe@incubator.apache.org For additional commands, e-mail: cvs-help@incubator.apache.org