[STATUS] (Derby) Wed Mar 9 23:45:28 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
ApacheCon presentation proposals
-BEGIN PGP SIGNED MESSAGE- Just a reminder.. ApacheCon 2005 Europe is being held in Stuttgart, Germany, in July of this year. Proposals for presentations are being accepted through 12 March 2005 (tomorrow), although that date will probably move out a couple of days to make up for system downtime. Presentations about Derby are, obviously, welcome. If you're interested in giving a presentation on Derby, please submit a proposal by logging on to the http://ApacheCon.Com/2005/EU/ system (when it comes back up) and filling out the form. (Follow the link from the left sidebar.) Major speaker expenses are covered by the conference. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQjGU6prNPMCpn3XdAQGlYQQAlNQNXyzJJRLYK0dzaIgq3ZlsGfXYe7ur p70C9bX2rrGbnW0E8m5f9lGnddbiYymHcpbI+jSqSGyASwoFo0sQrq0r9gtleOiw WkH/7CmBZGlUoeG7gt6EGSFABV7v582Q1uuxx1mzwfYWO3jbNfPD4UN4RHf3tk2i u/s7TsFtOpc= =x32A -END PGP SIGNATURE-
[STATUS] (Derby) Wed Mar 16 23:45:49 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
Proposing Derby for graduation
-BEGIN PGP SIGNED MESSAGE- As mentor, I feel comfortable proposing that Derby graduate from the incubator and take up its place in the DB project. Doea anyone feel UNcomfortable about that? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQkCgeJrNPMCpn3XdAQFiAwQAhuUafq4H9R6RgIKboC2r4O2DhS+UYrx9 6vpI1Cj62nSGXViwCTdra+KWYvj8maQMc8CFZnnHrsfPGFnr64V/EfNorNZjbdjq Vswv1SZvNSqwCLW0PPslACEcS0QOoAxe4Ysm1rb+4Hm+ubrUrMgbdFZ8bp+UR+Am HFO24MAs604= =VcrC -END PGP SIGNATURE-
Re: Proposing Derby for graduation
-BEGIN PGP SIGNED MESSAGE- Shreyas Kaushik wrote: > Wouldn't it be nice if we have a wider cross-section of committers? Do you mean, 'wouldn't it be nice if we haa a broader and more diverse set of committers?' If so, then yes, it would. However, in my view the delay in adding committers is not due to insularity, which would be an issue, but the usual 'prove your merit' caution of Apache projects. And since Derby is slated to go to the DB project rather than becoming a TLP, I feel comfortable that the DB project will take up the task of seeing that the committer base grows. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQkFufprNPMCpn3XdAQH/twQAuD2GGfYiqxe2X+aa3LF7KetUr/U88LRM 1nL4GIbODzbCNxiTA9tvTEJ9S9MRzS95VLG9CoDFvCah2vJXQMjaupIZySxuGBuW QNbpmss+G1UsO0jOSkshtwGD7OMBDTC0WFanxEwS71VciwWQvKP2k87kooqKDtsr gx6ODed+H0E= =YnLI -END PGP SIGNATURE-
[STATUS] (Derby) Wed Mar 23 23:45:18 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
Re: Proposing Derby for graduation
-BEGIN PGP SIGNED MESSAGE- I proposed Derby for graduation yesterday. Discussion takes place on [EMAIL PROTECTED] - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQkmNy5rNPMCpn3XdAQHoYQP9Ft8N6JG+1H/zwxWiq5OvaHo4TRbR60sC DXfVLtRGWVotE4aGvVKVYR3XRtCDwy8NId2p9DlOFb4G41uUoUAaQ8O3IfMDfhPu +kyAghi1moxrasaXAQzAqzV4LKfhWc4ZHb1PP5bhAIgM2NJczoFc1aGKPOYA1CoC tmQmYTgcG2U= =NAJm -END PGP SIGNATURE-
[STATUS] (Derby) Wed Mar 30 23:45:22 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Apr 6 23:45:26 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Apr 13 23:45:57 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
Re: Availability of Derby client ...
-BEGIN PGP SIGNED MESSAGE- Geir Magnusson Jr. wrote: > You will need to get an additional CCLA or Software Grant for this. My > recollection is that IBM prefers the new adjusted CCLA (with > incorporated SG). Do we actually? By whose requirement, Apache's or IBM's? If IBM feels that the client code drop is covered by the initial Derby CCLA, isn't that sufficient? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQmUx1prNPMCpn3XdAQFEeAQA0zzJ1qQxQgR5Yp2dGVfr5hGVGLgcN+yD xo62rXt28fMmWHcp9VpXSJt/pqrs4msd4Y1GwJV/Ze91TuinbG+SpHsFsTwuiNWb ewszetVcPBmY7h4+aAOtpXfSoFipbHfaZTxtxV3moNmEqtwfdb78Y81c9VjzqZjw ifhy/cjHWHQ= =Kssz -END PGP SIGNATURE-
[STATUS] (Derby) Wed Apr 20 23:45:29 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
Podling status reports
-BEGIN PGP SIGNED MESSAGE- Every month, a subset of the Apache top-level projects are required to submit status reports to the ASF board. The incubator project is a little different, since it's a project of projects, and reports every single month. For a normal top-level project, the project chair assembles and submits the report. For the incubator, the incubator chair pulls together reports from all of the active podlings and rolls that up. So once a month each podling needs to submit a status report to the general@incubator.apache.org list. The incubator chair typically sends a reminder to that list a few days before the reports are due. All the report really needs to be is a few paragraphs describing significant activities and accomplishments since the last report. There's no specific individual responsible for doing this; the report should be assembled on the dev discussion list. Examples from other podlings can be seen on the general@incubator.apache.org list as an aid to building our own. Something as simple as: "Since our last report, the Derby podling has accepted an additional committer and made another interim software release. The mailing lists continue active, and high-energy discussions have included X, Y, and Z. We decided that Y was worth pursuing. "We feel that Derby is essentially ready to graduate from the incubator, lacking only a sufficient diversity of committers. The progress on that front is blah blah blah. "" And that's basically it. Basing this at least in part on the STATUS file is typical. Posting a draft to the dev list a few days before it's due allows everyone a chance to offer suggestions or note things that got missed. Who does all this is a self-selecting thing. It is preferable for someone to take the initiative rather than everyone expecting someone else to do it. That, too, is a sign of a healthy community. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQm5wJJrNPMCpn3XdAQFaHwP9EC8XhuOfrinu3RJ+OqElYDbcki10FLPN 9veBkOHsM7r48xUgQnYNVhsBv7QHRnvuTrm9UtKUQbhvcSQgJKX4jWsbxRd71bLv rHGJdYqBJvkEOAtA18Oc/3/FCTD/Dz6gBzpBE2qYaUuR4SRfj5J4xCYcUAF9vn2s JbGTh4qfuyo= =9gKT -END PGP SIGNATURE-
[STATUS] (Derby) Wed Apr 27 23:45:27 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed May 4 23:45:27 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed May 11 23:46:09 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed May 18 23:45:28 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed May 25 23:45:27 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Jun 1 23:45:59 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Jun 8 23:45:37 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Jun 15 23:45:30 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-06-09 01:55:07 -0400 (Thu, 09 Jun 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAsk infrastructure to create source repository modules and grant the committers karma. DONEAsk infrastructure to set up and archive Mailing lists. DONEDecide about and then ask infrastructure to setup an issuetrac
Podling status report
-BEGIN PGP SIGNED MESSAGE- The Incubator report to the board isn't due this month, but a podling report to the Incubator covering the last month's challenges and accomplishments would be a good thing to prepare. If this *were* the Incubator's month to report, Noel would have sent a reminder to [EMAIL PROTECTED], since tomorrow is the June board meeting. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQrgvXprNPMCpn3XdAQEMEQP8CMibJ8qJ7ffmB7rfdHzJj3rcU1Ks1CG2 X9D8pqIrhy+Sb32WEPTO7FTFs9RXLbpTTy4OrSgpRxNAvs6CbImezkEYmx8QudSS kf+JPfOztqXjzV5BN9LGlO3j4XhpOVR/jSh5ndW7QrtWyImUwcwqKXAbVd3j9PKh ofIjwIPPrgk= =nWhf -END PGP SIGNATURE-
Re: Podling status report
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > Who should prepare this report -- you :-) ? and by when? The developers should prepare it. Each project provides a report to the board quarterly, so at the very least the habit should be formed of rolling things up every three months. If the habit is made of doing it monthly, then all that's necessary when the report comes due is to hand over the current contents and empty the file to start for the next cycle. For this I'm envisioning a cumulative file in which accomplishments are collected and challenges/problems/issues are listed (until they are addressed, at which point they get removed). The report should probably be kept in svn so multiple people can contribute to it. The STATUS file is a good place to collect the salient points. As for when.. Reports are due a few days before the board meeting so the directors have a chance to read them. While Derby is in the incubator, Noel will give a few days notice (on [EMAIL PROTECTED]) so the podlings can give *him* their reports so he can roll them up into the incubator report. If the report file is maintained on a pretty regular basis, then very little work should be necessary when the 'reports due in a few days' alert comes out. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCUAwUBQrkmCprNPMCpn3XdAQGuzQP3SNxECpM/nFTAi3RXjmZRyd5FajWqy681 ougSF7P03G+pg3EA79JDr64ATjjaZ36Mtenc9CElaO4zhgM+4P797UC7W6619Hz2 XnBfZrQ+q5RiMqiQjG4BjMp7dq6bAPMIJSp3IEgtuqSDc0cb8k+7RP6jb0LdCQhD xz7L/hY++Q== =4Bh4 -END PGP SIGNATURE-
[STATUS] (Derby) Wed Jun 22 23:45:32 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-06-16 00:08:03 -0400 (Thu, 16 Jun 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) CommittersTomohito Nakayama (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAsk infrastructure to create source repository modules and grant the committers karma. DONEAsk infrastructure to set up and archive Mailing lists. DONEDecide
[STATUS] (Derby) Wed Jun 29 23:45:28 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-06-16 00:08:03 -0400 (Thu, 16 Jun 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) CommittersTomohito Nakayama (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAsk infrastructure to create source repository modules and grant the committers karma. DONEAsk infrastructure to set up and archive Mailing lists. DONEDecide
[STATUS] (Derby) Wed Jul 6 23:45:27 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-06-16 00:08:03 -0400 (Thu, 16 Jun 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) CommittersTomohito Nakayama (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAsk infrastructure to create source repository modules and grant the committers karma. DONEAsk infrastructure to set up and archive Mailing lists. DONEDecide
[Fwd: **** QUARTERLY REPORTS DUE ****]
-BEGIN PGP SIGNED MESSAGE- This means us.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQtPFRprNPMCpn3XdAQE3egP/c1Tx9SQM1NMbZWxGVZyn6ugAatf+86mB Nx5g32YQvVD0r9bhA6lq7NygzzKHpUUqpJtzSgAbd4Rxl/QW/bfAs8BjwxIVq5b4 tnbmjfp8JjYPK5JCPqrQUbwGt8JFwGwNVJmnWEkRrjH9Fyn9Qb3Y/IzwBfW5UlVN 4HNi4GYm1Ak= =xGrV -END PGP SIGNATURE- --- Begin Message --- Just a reminder: quarterly reports are due from all incubating projects by Friday. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- End Message ---
[STATUS] (Derby) Wed Jul 13 23:45:30 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-07-08 16:07:03 -0400 (Fri, 08 Jul 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Committers tmnk Tomohito Nakayama (CLA on file) CommittersBernt M. Johnsen (CLA on file) CommittersØyvind Bakksjø (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAsk infrastructure to create source repository modules and gra
[STATUS] (Derby) Wed Jul 20 23:45:26 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-07-16 10:35:08 -0400 (Sat, 16 Jul 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Committers tmnk Tomohito Nakayama (CLA on file) CommittersBernt M. Johnsen (CLA on file) CommittersØyvind Bakksjø (CLA on file) CommittersDavid Van Couvering (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAs
[STATUS] (Derby) Wed Jul 27 23:45:25 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-07-16 10:35:08 -0400 (Sat, 16 Jul 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Committers tmnk Tomohito Nakayama (CLA on file) CommittersBernt M. Johnsen (CLA on file) CommittersØyvind Bakksjø (CLA on file) CommittersDavid Van Couvering (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. DONEIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. N/A 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. Copyright dateitem 2004-08-26 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. 2005-01-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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 ! status item DONECheck that all active committers have submitted a contributors agreement. DONEAdd all active committers in the STATUS file. DONEAsk root for the creation of committers' accounts on cvs.apache.org. Infrastructure ! status item DONEAs
Re: Call for Papers for the Open Source Database Conference
--- Begin Message --- Sorry for the generic message - many people to write to and a high risk of someone accidentally hitting "reply all" I am writing to make you aware of the CfP for the upcoming Open Source Database Conference that is happening November 2005 in Frankfurt, Germany (and to request your help in spreading the CfP via blogs and mailing lists). Cheers! --zak Software & Support Verlag, the producer of internationally renowned conferences such as JAX, International PHP Conference, ApacheCon Europe and others, announces a new conference for the international Free Software/Open Source community: Open Source Database Conference 05 November 7 to 9, 2005 Frankfurt, Germany It is our pleasure to invite you to become part of this new conference by sending you the official Call for Paper. Your submissions would be very much appreciated. Please find further information on the conference and on the submission proceeding below. ++ THE CONFERENCE AT A GLANCE * Open Source Database Conference 05: November 7 to 9, 2005 * Event location: NH-Hotel Frankfurt-Mörfelden * Main conference: November 8 and 9, 2005 * Power workshops (tutorials): November 7, 2005 * Duration of a session: 75 minutes * Duration of a power workshop (whole day): ~ 6 hours * Duration of a power workshop (half-day): ~ 3 hours * Entry form: http://input.entwickler.com * Closing date: August 19, 2005 ++ The main conference is divided into the following tracks: - Database Fundamentals - Database Development - Database Administration - Business Intelligence - Free Software/Open Source Database Business Conference topics to be covered are: - Database Administration - Migration to Free Software/Open Source Databases - Performance tuning and optimization - APIs/Connectors - New Technologies - Lowering TCO with Free Software and Open Source RDBMS - Case studies - Community-related topics Languages, technologies: all (Java, PHP…) We are looking forward to your submission and wish you all the best! --- End Message ---
derby-dev@db.apache.org set up
-BEGIN PGP SIGNED MESSAGE- the development discussion list for derby has been set up and the initial set of committers subscribed. [EMAIL PROTECTED] to get on it. i dunno if db.apache.org has a 'general@' list; go ahead and forward/disseminate this freely.. :-) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQQ8gy5rNPMCpn3XdAQEwJQQAquOl51NL6A+aTwS3SRdmdF4+/x0DAuPu bDkBfXO+YkZqrhgkfaMU/SgERRF49aHDBDY0OrSjUQiwxIjJ7CkBlvboHoPZQqlI Gbp428t4xBgTYekU8OSRzVj5Wpg0H5+J3F9pH3k9DvYYrHlDZcOEvp/zbSpp840c qjO5CT+rwEw= =Eum3 -END PGP SIGNATURE- - Derby is a project of the Apache Incubator (http://incubator.apache.org) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: http://incubator.apache.org/derby is live
-BEGIN PGP SIGNED MESSAGE- Ian Holsman wrote: > > this might help (from when I did it for httpd-cli) > > 1. get the lastest SVN version of forrest, the current one won't work apache-forrest 0.6-dev from trunk > 3. make your mod's in: > site/site.xml -- add your project under 'projects' > (shouldn't have to do that again) > site/projects/index.xml -- add the 1-liner of the project in > > site/projects/httpd-cli.cwiki -- (the meat) all done. > 4. in ./incubator run > > $ forrest -- generates the HTML pages 'skin forrest-site no longer exists, using crust; update forrest.properties' warning: incubator/site/content not found warning: incubator/build/webapp/resources not found warning: incubator/site/skins/common/images not found warning: incubator/site/skins/crust/images not found warning: incubator/site/skins/common not found warning: incubator/site/skins/crust not found and then it throws an exception during cocoon: exception in thread "main" java.lang.NoClassDefFoundError: com/ibm/crypto/provider/IBMJCE (wrong name: org/apache/cocoon/Main) > $ forrest run -- which brings up a web-server on port > to view the it and this throws an exception about InvalidJarIndexException > 5. if your happy (or as close as happy as you can get) *not* happy. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSKFv5rNPMCpn3XdAQHNAQQAyW5Ux57CmpQrlEB/Q20/p6+yiIadiyJE 70yijRPQoJ5Fi1z9kziayngWFBUDxa6T8Cawh0ZhgTF4DtAUZFe4m6Xi1yjx9g7Q HcRhVu5SVh6tLIUIIOVwjxTQ+2nVMbYAdZt77jw0pHj7amlyphcHAkaE2yCITk9H R582xZh4WvM= =lg0d -END PGP SIGNATURE-
Re: http://incubator.apache.org/derby is live
-BEGIN PGP SIGNED MESSAGE- Ian Holsman wrote: > >> all done. > nup > you missed site.xml & projects/index.xml > I added them for you. no, i didn't miss them. they're here in my working directory. >> and this throws an exception about InvalidJarIndexException > > ok.. > I got it to run and build the derby.html/pdf files > I checked them in, and updated the site > >>5. if your happy (or as close as happy as you can get) >> >> *not* happy. > > happy now I hope? i really appreciate your helping out. however, we need to be able to do this ourselves without having to ask another project to do it for us as things change. :-/ which means figuring out/fixing the forrest crap. thanks! - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSNNAJrNPMCpn3XdAQG8xQP/fQGeG1e8D4ibo4liSlMT/FhzaBWDF+0h M79DirikEhnxIDU6uBgWkbuaJ59s22Q+nF6F0taYsel8rgypOGFojea5ox7gaQLc kVM2C3WH6JbGv+MPbs8DjlL0mpKe+yllJwX6x8LKmBpUZnbGnDqqSdlzok5rQL7F 3XVPHaKty10= =fdr9 -END PGP SIGNATURE-
derby repository structure
-BEGIN PGP SIGNED MESSAGE- the svn repository for the derby project has been prepared, but it might not have an optimal structure. no code has been imported yet, just pages for the web site. according to the svn people, 'best practice' is for there to be three areas in each versionable module; one for the main-line development (called 'trunk'), one for branches (called, curiously enough, 'branches'), and one for tagged versions. so for module foo, with a single file 'file.name' and a single branch 'B1', the module layout would look something like: /repos/foo/tags /repos/foo/branches/B1/file.name /repos/foo/trunk/file.name the derby project has at least two discrete parts: derby itself, and the site web pages. currently the module is set up (with prefix '/repos/asf/incubator/') as: derby/code/{trunk,tags,branches} derby/site/{trunk,tags,branches} some questions have been raised about whether this is the best structure; an alternative would be: derby/{trunk,tags,branches}/ derby/{trunk,tags,branches}/site making the site just another piece of the overall project. which layout do you think is better? everything *can* be rearranged after the code upload, but it would be a lot simpler if any structural changes were made before then. :-) the only thing that would need to be moved about would be the existing site docco, and it's simply a matter of moving a directory (essentially). - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSSVxprNPMCpn3XdAQEsOAP/VKI5XzMrM16H0GRwAuncFIECmSQrqAGK gOo2vS8iwVNU523k8J5tTiahjBRkNjPthStneA29GM3V9Ay1AcyG4Rap/ripxr+Q Cz+yPhqktvx14x8F1dCfYNwIPDT6IkVw/pQkDAVZtDGDCl9KjpcPSLL2n+VbthYA gkWgPRyqIvo= =RhxF -END PGP SIGNATURE-
Re: derby repository structure
-BEGIN PGP SIGNED MESSAGE- Rodney Waldhoff wrote: > On Thu, 19 Aug 2004, Rodent of Unusual Size wrote: > >> some questions have been raised about whether this is the best >> structure; > > With a mentor hat on, it's better to raise these questions on the list > than off. which is *exactly* why i'm bringing it up here. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSSsXZrNPMCpn3XdAQEp5wP6AgonSUpCctRS0TkMskqxuiwGqHuVwMgn SsojPNWTpXBatn1R9bceMMlHm29Anof/QToxa7wih2Nb8+c0wgJesDmX5AwyiVvw 44vIIbgcApMbtJnoqn3lSGnEIhkX83DttuwfXqihShn4AUKPMz45XP1yt1/M1Whu obx9rPEGOUI= =fLj+ -END PGP SIGNATURE-
Re: derby repository structure
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > derby/code/{trunk,tags,branches} > derby/site/{trunk,tags,branches} > > I believe this is a good setup because it would seem to me that > branching of the code would typically be independent of branching > of the site. Though I'm not sure what it would mean to branch the > site, would that ever occur? maybe. something like that happened for the http server, for instance; both 1.3 and 2.0 are supported and deployed, and the docco is distinctly different. separate modules were created for them, but they use cvs rather than svn. branching is simpler/easier in svn, i believe. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSSsvJrNPMCpn3XdAQHypAP+NsPgP+ATrULmrxTbP1BoDwaqW53YGF4u byAmgA3rLYondRp6Warr4kDf8nV7Y7MhnEWgQiHGnhGV+4md7kRudY3kzAhg11fK fpOFiSbQMr26tL0vQSKlNDd4rySwbg9dXrsVEwdxNmICx/3/Z8cVPDqVEtNHWgPB kCpev28Rd8Q= =zh9s -END PGP SIGNATURE-
Re: [VOTE] on repository layout
-BEGIN PGP SIGNED MESSAGE- Cloudscape Testing wrote: > > That means though, that I would include the user documentation in the > code part of the repository, since we would want to keep that in sync > with the code that it documents. The developer would also then have the > current doc set in their build tree for reference, and a person could > build a full binary distribution from the source distribution. as only a mentor for the derby podling, i don't feel qualified to have a vote on this issue. however, i'd like to suggest that *if* the decision is to keep the docco and the code separate, then developers who are keeping up with the bleeding edge of svn aren't forced to have it, and it can always be included in any release tarballs when they're built. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSntYprNPMCpn3XdAQFVJwP9G0vrFuz4tStvipZJocEYQ/a9wOmQvq5u FQf5ZKB9nnvPDYfi2Wkspq19tCXkO56UAazeJ1K9nOIEW0HAhT6dRt1dv1BMWROY Cuv3ErHPvG3Q8XFhaCfPr7BWv1TPdGJck7MgrIsS6gaJhpBorZlowrVTzTsvPAQA fBWMJjUukAo= =6Vhw -END PGP SIGNATURE-
derby source code has been uploaded!
-BEGIN PGP SIGNED MESSAGE- okey, the necesary paperwork has been executed, so i just uploaded the derby source code into the subversion repository. whee! http://svn.apache.org/repos/asf/incubator/derby/code/trunk/ - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQS3w4JrNPMCpn3XdAQF0mQP/fZcXy3jURjsviFUsUmKOG/5OgT1DqehU ZMNCmrl6El4uNos0IRNB4kZnrjTIEvtifNLgpi8kcXvQMnObVDygGGzKT9TzOOnJ PIhurNu35EWbErnlxdHNYbtprhUOpWSwBaokm72rop8O4itU2OYH1YaVQEX1WL3Y kd+5GeZkbwE= =TC+v -END PGP SIGNATURE-
Re: derby source code has been uploaded!
-BEGIN PGP SIGNED MESSAGE- dan, i can't find your gpg key in any of the key servers. have you uploaded it? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQS4/qZrNPMCpn3XdAQEH2AQAgTzEPDWxwCmFuYHy7RqTiFk9pbNbzSof Efiw1hxCEwlPPtYPTpdfY0OdFS+FTgELr5zPY74BuCBYOys2jHTKDUMGr1nf3LMV ThybW54IJQPviqs3ctiqPD5G217LHSxh8HhiZXV83c8FwKPgS1aTEnn+LeA7JukF oiC0yyeVAq0= =wL6N -END PGP SIGNATURE-
Re: Derby commit records are posted to derby-commits@db.apache.org
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > Originally I thought commit records were supposed to go to > derby-dev@db.apache.org, but they are in fact going to > [EMAIL PROTECTED] (you can find it at > http://nagoya.apache.org/eyebrowse/). > > So, any thoughts on this? Should they continue to go to the separate > list? Or would people prefer they go to derby-dev? they were supposed to be redirected to the -dev list. i guess that got dropped. they were originally set up to be on their own list, but it was decided to put them on -dev instead. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTTcS5rNPMCpn3XdAQHwhgP/Zpj0M09ssTasF697G1OT0vR7kpQ6uvgp 4EzidGVUSkIkphS8KDZMuB5eUZ2H3J4tacQ+uaOOLydQ579MKE74RLoND55BNbXC DTg4zU5UnbIwflH16yP+riUDjDhkAwlJ9Hs3hNbIFmfrA0yritPPr5rlk5tAle5S +084Dd6o5CM= =CSfu -END PGP SIGNATURE-
Re: Derby commit records are posted to derby-commits@db.apache.org
-BEGIN PGP SIGNED MESSAGE- Rodney Waldhoff wrote: > On Tue, 31 Aug 2004, Rodent of Unusual Size wrote: > >> they were supposed to be redirected to the -dev list. i guess >> that got dropped. they were originally set up to be on their >> own list, but it was decided to put them on -dev instead. > > Where? amongst the initial set of committers from ibm when the infrastructure was being set up. if you think it should be revisited now in a more open forum, i have absolutely no problem whatsoever with that. :-) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTXdsZrNPMCpn3XdAQHi9QP8DmEmXo5CfkM5OW/VEhE/RuoHN6pRRvWu Pr86VdYOmdImLGP0O9N18agOjIobVQLwSfzPoUcQr7bMMuhLvvpjDGMXngH5b8/n 3qNdDGhXI7QuA+WueVODrMcTnSC46mDwJzHmY4nDl9fCgcy/TJOLtoV4/0qpNZLP qCNahruSsbI= =b09n -END PGP SIGNATURE-
reminder: #apache-derby irc channel on irc.freenode.net
-BEGIN PGP SIGNED MESSAGE- i don't think this got documented anywhere.. there's an #apache-derby irc channel on the freenode network for people wanting to have real-time discussions. just remember that any discussions that lead to action on the code need to be summarised on the list here, and any necessary go/no-go decision needs to be made here too. (for archival and audit purposes.) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTXfXprNPMCpn3XdAQEJrwQAvNM1ff2TCriJ9NQ25B0y5xaNSeiu5AdB lwSvNv7JVCla5kSOx1OMvyzfv4EcbBwhG/SZeNR8rZMiLl7n6bqSenOXCXCcWeWK NC3q0bNALlWfA+WMZEtKPxRW3at8XtKbCM1dNN4ctlURytO8WLJ8JfwWXSFT4pwN q0VnUoie3Qc= =cfJF -END PGP SIGNATURE-
Re: [VOTE] Establish development model based on Apache DB guidelines
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > Ken, obviously as you know I'm new to Apache voting and so I'm not > really understanding your post. > > The first question is are you starting a new vote or trying to add an > item to the vote I started? neither, actually. :-) as podling mentor, i'm providing advice based on my experience. the db project has a documented and designed disparity between the pmc and the committer list. during incubation, podlings emulate pmc operation and become familiar with it via a 'ppmc' list. i am suggesting that the derby podling adopt a policy that all committers are automatically on the ppmc. i bring this up because i think the db project pages could be viewed as recommending that the members of the ppmc be a subset of the committer list. > The second is, are you voting on your issue only, or voting for the > issue I started the vote on? The URL after your vote is confusing me as > I would guess the appropriate URL for "my" vote would be > http://db.apache.org/guidelines.html. i am not voting; i am a mentor only, and a committer only by courtesy during incubation. if/when derby graduates, i expect i will no longer be a committer, which is appropriate since i don't know java and certainly not a db in java. the podling needs to be self-defining; it's part of my function to help that happen. i *don't* think it's part of my job to try to steer it by voting. the point i raise may not be considered directly relevant to the issue being voted, but i mention it because it's related. i don't think emulating *all* of the db project procedures is necessarily appropriate during incubation, since subsetting for the ppmc could be a barrier to community building. > Sorry if these are dumb questions. no dumb questions. ignorance is curable. i only hope i have some appropriate medicine. :-) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTYfCZrNPMCpn3XdAQFtbQQAoekwE1VJgbuU/c8o1r183hI4Yl6d1uU6 NLow+yY2Fb72LFOTnHbpCWkXnzkXHJiMWyYkcc29a7bkBxZ/6qTzGliB3j1KxNX4 VmX+z+gWPfmRaj2VxFGx4jNRurpEMBWHdE0/TKU/Dv6vDEz6i9OPBC8b+2SG2IB6 AHb1foyFo74= =Tms5 -END PGP SIGNATURE-
Re: derby source code has been uploaded!
-BEGIN PGP SIGNED MESSAGE- Andrew McIntyre wrote: > > On Aug 26, 2004, at 1:00 PM, Jan Hlavatý wrote: >> >> Can we have the official committer's PGP keys posted somewhere please? > > You can find my public key at either http://www.pgp.net or > http://pgp.mit.edu it's a valid and appropriate request to have committers' keys directly associated with the project. i suggest the creation of a derby/code/trunk/KEYS file into which committers can put their extracted ascii-armoured keys. this serves two purposes: all of the committers' keys can be inloaded in a single operation, and the fact that they keys are part of the apache infrastructure adds a small amount of additional verification. while i'm on the subject, would every person who is signing its email please see that its key is uploaded to the servers? canonical servers include pgpkeys.mit.edu and wwwkeys.pgp.com. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTYhBJrNPMCpn3XdAQHIcgP/Uxxl05YeTW9GYWbiFji0Ojyu21j5DJrV 2repNh2NBbq2XtaUzr5Yw+CHI7NwaN0BkKOWwECI8DdmST6iAeK2EdCFZzddSOf4 kDNRYOjPMBbfzx1+JzDCw6mn0RvnNFfp+nZQroJhDbfwobSpfeydE+/zGRIB451a /0amGV2GTes= =9gZP -END PGP SIGNATURE-
accounts for committers
-BEGIN PGP SIGNED MESSAGE- the necessary forms for the initial set of committers have been submitted afaik; the accounts have not yet materialised because the foundation secretary (to whom they were sent) has been on holiday. as soon as he logs them in, the accounts can be created. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTYjy5rNPMCpn3XdAQHvKAP/SsRCyLtvtih48oPZhsfDOUISGmM54ULV orR9cNgdwI4Ck0QtZQSBma53upga7hAyZRRJ/KOB1Iqm4PKpuLy+Q2tSg/rjSVq5 JnX16+e2pka/VqrdtH6fk99ATwmxUcXrXdMNBtetrs5XJWe8aYrWZq6w0xn9cV/m ba8g1h0MK70= =8f/B -END PGP SIGNATURE-
Re: Derby web site updates [Ken, please 'svn update' to make visible]
-BEGIN PGP SIGNED MESSAGE- done. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTdD+prNPMCpn3XdAQFCyQP9Gj/ENIZi2FZhneMU95G/qsgGocB5B/W0 5eZpSss72tP094zfSSCaRyCQG8+vOHcv+cEHUvIy6IBPvP0lOAFjnmwF37x+DW33 bdgbSSQkGiN924kVhjQcDFes9AGWf8xRbGH7dy+IY6kwTpgsIxogII70JlDQofA7 AwEypUimPrw= =8C1Q -END PGP SIGNATURE-
Re: Derby web site updates [Ken, please 'svn update' to make visible]
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > Can someone explain the web-site process? A Derby committer can make > changes to the source pages for the web-site but does not have the > permissions to make them visible on the actual site. Hence the requests > to Ken to 'svn update to make visible'. Is Ken in a committer++ role or > ~ as a committer on the incubator project or something else? more or less, yes. there are four different kinds of access involved: a) access to the derby site module (svn incubator/derby/site/trunk/) b) access to the incubator module (cvs incubator/) c) access to the incubator site module (cvs incubator-site/) d) access to the web server filesystems there are two places on the incubator site where the derby project has pages: 1. http://incubator.apache.org/derby/ 2. http://incubator.apache.org/projects/derby.html #1 comes from the derby site module, and is quite straightforward: any time someone with [a] access changes the derby site module, someone with [d] access needs to propagate those changes to the web server. #2 is much more complex. someone with [b] access needs to change the derby.cwiki file and generate the pages from it. then someone with [c] access needs to import the generated pages into the incubator-site module. then someone with [d] access needs to update the web server from the incubator-site module. access types [b] and [c] are mostly granted to the members of the incubator project. access type [a] is granted to whomever needs to keep the derby site pages updated. and access type [d] is granted to a less well-defined set of people, such as the infrastructure team and others who need to and are trusted to safely update the web server pages. i have all of these access types: [d] primarily because i've been around a long time at apache and have worn many hats; [b] and [c] because i'm part of the incubator project; and [a] because i'm one of the mentors of the derby project and imported the code and pages before any other derby committers were set up. when derby exits incubation, i expect i will lose access [a] because i will not need it. i hope that description helps.. by the way, i encourage everyone involved with the derby podling to subscribe to the general@incubator.apache.org list for the duration of the incubation; just send an empty message to [EMAIL PROTECTED] - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTdc1prNPMCpn3XdAQHdqQP/VMpGq/zYqKclNitapwYOLRNdeNdSPIsp WiZUH15cl2HtgOM4PPvrNyPJIuUEtOVzyF8XbARtyFlrcxoa+qiPBMk23kFJ/JbM gTCLe9ACKeCyWF6/m8+3pHstFl7y5wMcC4ez/QhXB0L9rQ4YjZA0Za4/jdRObwLJ hZWrAqab1lM= =wVBk -END PGP SIGNATURE-
Re: Derby web site updates [Ken, please 'svn update' to make visible]
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > Does the #1 process ever become automated, e.g. once out of incubation, > or is there always a manual step asking someone with d) to perform the > magic? it depends on the project. some projects have their sites automatically updated from the respository on a regular basis, some don't keep the pages in a repository but generate them in situ regularly, and some require the manual intervention. i'm not sure what process the db project uses, but people with [d] access to the db web site are/will be on the derby committer list (such as rodney waldhoff), so if it's a manual process it will be within the family. plus, the db project has the say about who has [d] access to their site, so there shouldn't be a problem getting derby people that capability after graduation. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTfHcJrNPMCpn3XdAQEmQwQAmjUCThWqiknxtnisLc11MKBOAPoMyAvq SjfoATAaY+SRZDzSpILMrSU196vzz5wqqAyyN8iMxs5voIwXHdrirSYvpNKjJNUI vvT2LcrnY4+D+Hd/Air7e17gK2XpsT40iVBMZQ9bVpdzd8EgdKtrZNRBI6pEzDuU jaC0cUjc5ps= =noAT -END PGP SIGNATURE-
Re: version scheme
-BEGIN PGP SIGNED MESSAGE- there's also the special substitutable keyword $LastChangedRevision$, but that only tells you the revision of the file in which the keyword is located. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTyoJZrNPMCpn3XdAQGtWAP8DYUxc3PwfzZYAOu8sWtl70aAzmI7umje seohXUKs+C6LV2ODq+5SQ8EGTI5NM7ZMBnqn7QutoC2EezxU34VbHB0vlh9rgHQg JknRfIhwEyNKkMA4VUDFdPnIsotHiikgnweMkczJhpQkf6qqn3PF1DjtsPTUuZhq urqqAHOojdM= =qp0F -END PGP SIGNATURE-
Re: accounts for committers
-BEGIN PGP SIGNED MESSAGE- Rodent of Unusual Size wrote: > > the necessary forms for the initial set of committers have > been submitted afaik; the accounts have not yet materialised > because the foundation secretary (to whom they were sent) > has been on holiday. as soon as he logs them in, the accounts > can be created. jim has returned, and has been processing the cla forms in his stack. unfortunately, he hasn't gotten to ours yet -- but he will. it occurs to me.. is the presence of the names on the corporate cla sufficient to serve to grant commit access? i don't think that question has been asked before, so let me go ask it. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQT9N8ZrNPMCpn3XdAQGbfgQAwVPtKScVMc4iqBOvusESKyu3y0QvX8wa s+ZPrQEBbVaD0A0dRBdjZLrZDbwFl/c1F1oRhAWnE3PqY6gQl9iIEAVC8Jn3vCsl vwZjckj+Qop3KUWkbU0DXOXaJkiSQfJYK7IwLLb3wFz9Ry36XKAbVdTpxcd4KkZp pkpd3P22qJw= =A14E -END PGP SIGNATURE-
Re: accounts for committers
-BEGIN PGP SIGNED MESSAGE- Rodent of Unusual Size wrote: > > it occurs to me.. is the presence of the names on the corporate cla > sufficient to serve to grant commit access? i don't think that > question has been asked before, so let me go ask it. alas, the answer appears to be 'no.' - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUA4o5rNPMCpn3XdAQHTjQQAsUGzC27DdAZuu4VLh8kOzyBPrNcf9u6V X9dfH2zOmmcbPlhylur0mfsnglBQ6V0FugvydfFlKAVM5b+qqo7+vjCkuBtfTqUx PiqOOwxsv8Y9jHeXAaIEIBZCy72SmtFVfMexFr9UK/XWrio4iuo1fYBpb8ahP25I C0tMQFZN5Cg= =arjO -END PGP SIGNATURE-
Re: [WEB] Ken, please 'svn update' to make changes visible
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > Changes include: > - derby_resources : updated URL for IBM DB2 JDBC Universal Driver download. > - derby__comm: reorganized, added info on the process voted in > (http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=258) > and tips for producing patches and for sending/saving them using Enigmail. done. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUA5LJrNPMCpn3XdAQGGrAQAhM7nkgZeOaxQH9+bFGX1daoUpQi/hSVO zhwJ/BUvdmlm3kjqFGcw7qO33yr2gmFCToy18r/n6BexHuZpqCqtEJpfPBTUigVT Y5FEn/Q/6YLKBRN0kll2+4mwlxHzkVQTZa9LtGI/S/OE+iQlHt0oCxrAATsvny7G 6j28/lShL7k= =jOng -END PGP SIGNATURE-
Re: [DEFECT] Network Server Protocol error when select fails and "order by" is specified
-BEGIN PGP SIGNED MESSAGE- just for those who might not be aware, 'defect' is ibm terminology for 'bug.' being less formal, apache projects tend to call them 'bugs.' :-) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUGDFJrNPMCpn3XdAQH28gQAun1SVs5hirKn3h2TFYzuNcwYXw4Qy0Va 52vpfkshNLPsBQurrggoTB5R124C2kuv9lgIBVuj2/wDxYO6vh/LpB50h0HhOoQp E9kReeDYaYtZw2qWGj/9Znx+suPsv71/382pk23mtrlnBsPSUyNIq1tYmJZJP7Nr uK8d6PK1g0s= =qCpU -END PGP SIGNATURE-
Re: Clarification of Apache DB Project guideline for submitting docs and patches
-BEGIN PGP SIGNED MESSAGE- another hint for those coming from the realm of lotus notes: please trim the message to which you're replying so that only the parts specifically relevant are included. who wrote them should also be included. if large amounts of text are removed sometimes an indication is given somehow, such as being replaced with a line like [snippage] this makes it clear that you're aware that there's context, and are trying to address a specific item within its framework rather than in isolation. for example, the entire previous exchange included in the last message could have been trimmed to: - --- John McNally wrote: > > The two sentences would appear to have little to do with each other. If > the last sentence has any place in that section I think it would be more > appropriate within the first paragraph. Location aside, does that mean that before submitting a change from a contributor, a committer should verify that the contributor has a CLA on file? If so, how would I do that? Thanks Kathey - --- sometimes quoting the entire message is appropriate, but usually not. a reasonable rule of thumb is that the quoted port *shouldn't* be much larger than the text you're adding. it's just a guideline/sanity check, though. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUGFdJrNPMCpn3XdAQE2NQQApakAAcwHzZrn6GREkSTYsn88HbjPElUO KOoux1+wbknQhSePZQo8UqK97g5RiePx3uIVDxIfm53MEcXhBMevPZv4w7UcFICY UbuNRvdhKR5uJlcWy+42vKPDbTGoFfOIZoOuQmEvW6Q46hc3mFQ8TWs4XAdjho3v bredVllv5+o= =cqIM -END PGP SIGNATURE-
Re: Thoughts on a release?
-BEGIN PGP SIGNED MESSAGE- if we do a release now, bear in mind that we'll probably need to do another one. at this point, unless i'm mistaken we'd just be covering mostly beaten ground, since no changes have been made to derby. it would be a good exercise for everyone to get familiar with the release process, but i'd think we'd need to do another after we've actually made some changes and tested them. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUHvyprNPMCpn3XdAQE6ugQAuSPTZgKic3IjHZXa4ogeBU0Iakdkw174 uze3deqVHfy1ovqnl0hZrvCMCoBQlhjbEAKsH8JSDr3FKQyol8BATn5RJBVn6DUQ Nz4sHaH1b81CAKoLj0GUPfmrEwCo6atamoYkrSzLBAwqN5xL1CVerlsr8l7AXwK9 6aWKrWt8vHg= =6zGZ -END PGP SIGNATURE-
Re: [WEB] Please 'svn update' for new Papers tab
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > > So, Ken, please do an 'svn update'. done. other people here, like sam ruby and rodney, can do this as well.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUWfzprNPMCpn3XdAQHAmgQAxW1QR0QzZhiGECylA1JCPhhncglxRX0s 3enjoOYXeIuTe7CtkM8cHzCz1Mm1TpZgbb7F4QUGHsfJOk518jj+3PDuXGw9jBHH QybVhsV7smsKxkZSfknMEHkoDak+PjbvYchOEWoRdr+OjpAPAo+BdluiwpDjdWUh YZvXDzx1gp0= =6YL6 -END PGP SIGNATURE-
Account creation requests
-BEGIN PGP SIGNED MESSAGE- for all of these, Requested karma: incubator/derby Full name:Satheesh Bandaram Preferred userid: satheesh Forwarding email address: [EMAIL PROTECTED] Full name:Daniel Debrunner Preferred userid: djd Forwarding email address: [EMAIL PROTECTED] Full name:Katherine Marsden Preferred userid: kmarsden Forwarding email address: [EMAIL PROTECTED] Full name:Mike Matrigali Preferred userid: mikem Forwarding email address: [EMAIL PROTECTED] Full name:Samuel McIntyre Preferred userid: fuzzylogic Forwarding email address: [EMAIL PROTECTED] - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUdzkJrNPMCpn3XdAQFaAAQA1dop5tEhUpD5tjmlSDmE3D8NXspfwdrX AWOGKyW+szKQFhxCDLXCtpsHLkObF3pXP6+RjHqfjZN3/VMgJrVchPbXTufr0S73 IgzkK7nlSivAM6XW0bTsXoxB28R/lm7eAqgdcQPFJEb6NymBJ+18ufjvkei1sgkx Tk/3yDqvWD4= =8L0D -END PGP SIGNATURE-
Re: [PATCH] Change Copyright notice to ASF
-BEGIN PGP SIGNED MESSAGE- nd.. the answer is: replace the ibm notices with asf ones. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUd0cprNPMCpn3XdAQEtbAP/QZWlUe2k+8tO/ai1x+MiqvnZceBbacuF zgErPCiMv5kZWcbtemyQ2kXDtGNTF/WiWCqNfbVp8eExDZ+j9hlH9gkspsEPaAlt L8F7uBK6GpQ3kXDjfNG+n2/0G0K3H1jYXrDmkQAu21ky3foolGTaOrd1IM9RXy6R IxME0hYs/B4= =e3+G -END PGP SIGNATURE-
Re: [VOTE] Change Copyright notice to ASF
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > For this specific vote, I'm still not sure if a vote is the correct > approach. If we need to retain copyright notices then option 2) is the > only choice. I think "retain" could only mean leave as-is, not 'keep a > modified version'. It may be more a legal decision than a community one. no, a vote isn't the way to go. since getting the files cleaned up is one of the graduation criteria, it would essentially be a vote on whether to ever graduate or not. :-) see the bottom of http://www.apache.org/licenses/LICENSE-2.0.txt note that the 'fill in the copyright owner' aspect is directed to non-apache groups that are using the licence to protect *their* code, not to apache's own code. the copyright notice in the files needs to change to: Copyright 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. information about ibm's involvement needs to go into a NOTICE file; see http://www.apache.org/licenses/example-NOTICE.txt for an example. both a LICENCE and a NOTICE file should be at the top level of the source code repository, *and* in any binary distributions. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUgaIJrNPMCpn3XdAQE0HgP9G2I0q/OFc+7tPyt3Wu3gY9YnOZx8zWTf BHXSSs5CfqqsUQIDpwpIcSlr/d+wW0OgNJ2gEvM7eGb9uwMejaMud18NBluOkyDe FL6aQYSTj+jqKxVcfQd21jwMPImU22VmVD2IhJnBGXY/i1WS+8Awo/JnyEcgQw0P 8P0VBz1E6lQ= =OaDc -END PGP SIGNATURE-
Re: [PATCH] Change Copyright notice to ASF
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > Rodent of Unusual Size wrote: > >> nd.. the answer is: replace the ibm notices with asf ones. > > nd this is > > a) your opinion > b) a fact based upon ??? > c) a decision made elsewhere? > d) something else a determination from reviewing archives, the derby grant, and double-checking with the incubator chair. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUgpeZrNPMCpn3XdAQHxeQQA07qf1+5kmIBsWVCyn6it9tDUnwv6odZK SmoiZwrRmo7oxY92/SuSZFdMAFtCTEQa3Y68MuUmFjxEMyV3I69RmTCPeCT41Ebi 4LRbGkAyGcviylFluyTdBOV9LVG32aDrmdjOv5mhnqj7FBp1T4y6fQThO7AgtgL3 DOjucpvaTKs= =Ykub -END PGP SIGNATURE-
Re: [PATCH] Change Copyright notice to ASF
-BEGIN PGP SIGNED MESSAGE- Geir Magnusson Jr. wrote: > Just for the record, Ken is an ASF founder, an ASF director, and the > project champion as well as mentor, I think... his opinion counts for > quite a bit here. > > I don't always agree with him, but I certainly pay attention to what he > says. ;) skepticism when it comes to ip issues is a mark of our times, and in order. besides, paying attention to what someone says doesn't mean he's right. i pay attention to what shrub says, but mostly in order to be horrified and get my adrenaline running. :-) republicans as therapy. hmm.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUgp9ZrNPMCpn3XdAQHIbQQA0vTub3GbOdU6Zp8cpKb37315pCBZcJmu QwGP3V3bZgsTWZX5aBJnsuMizkE8ErKN6T3Ttq9ol4hwmKU6WPINAktvlGEaC2E+ Op45Mbm9JXKs4jw6g+8IoReuzNNgQbmRGKexARv5UxyIDDR5mESnHSxcJEepPyeq YjMtiFGiHGI= =4TL1 -END PGP SIGNATURE-
logo for derby
-BEGIN PGP SIGNED MESSAGE- logos can be focal points for identity and community pride. (and fun, too.) how would people feel about having a contest to pick the best one? and maybe announcing a decision at apachecon? it's possible i know of someone who'd be willing to handle the logistics of running such a thing, in case it's something too involved for us to get running quickly. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUgqwZrNPMCpn3XdAQFkUgP+Jel0bz63eU15PcdDmaUe4NLV7xVWAjs1 YnRFQMEWLXnJhbrtKZWznvrS61vbvpM6B85mLMgdlbWbLW17FCtzsU5oQICF5UkY 1N1uEntp7FDuGuyUvtbjg/pYRTpNm7ZdzJhCciptkw5eB5NhkMLRX5gkxoHL75Hk Ve+89rFwF6M= =qKIE -END PGP SIGNATURE-
'live' documentation
-BEGIN PGP SIGNED MESSAGE- i've heard a few comments/suggestions about maybe having the docco be user-annotatable, so i thought i'd bring it up. to see what i mean, take a look at the php documentation, say at http://us4.php.net/manual/en/function.strstr.php -- search down for 'user contributed notes'. the php project has a lot of success with this. the comments are backed by a database (!), and static versions are generated for mirroring. so the amount of dynamicness is limited and performance maintained. does this sound like something it would be worthwhile to investigate? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUgr35rNPMCpn3XdAQGYoQP7Bk32kSpaLVZbgFpLN/z+SJO/b/G+Nwb5 YnvIcU/hOAZrXo5iK1ENNdIXCgtwRu/YcwnmhuYMLar/vFxHbo2B8ph6gk1eUsWE Bgong2T+lE1sY+x2NEIWLKaRS3fflvIYoUsZI5u96qFAu3v14tSOpaHJqItyDcXX SzQc1Md38C8= =H4rp -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- Jonas S Karlsson wrote: > > Noel J. Bergman wrote: >> As Ken explained in >> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]& >> msgNo=362, the copyright holder would be The Apache Software Foundation, >> having received a copyright grant from IBM. The purpose for having the >> copyright holder pluggable is to allow other entities to re-use the Apache >> License. > > That is not clear from the referred pages. so i'm clarifying it. > In this case, according to Jennifer the "copyright owner" is still > IBM, and she doesn't want the IBM copyright notices to be removed or > replaced since that could imply Apache copyright ownership. um, where is this 'according to jennifer' source you're citing? i was intimately involved in the grant discussions and i remember nothing of the sort. > She also states that ASF copyright notices can be *added* to > intellectual property created (i.e. modified code) or owned by ASF. > Adding an embedded copy of the ASF v2.0 licence is OK according to > her. ditto. > Whether the copyright notices can be removed/replaced or not I cannot > find any support for directly in the apache documentation. But IANAL > and this is an issue for ASF lawyers to look into. two officers and a director of the asf have provided clarification and instructions. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUiNaZrNPMCpn3XdAQGMIAP/Si6jw1b1SULS32cgV3NJ8hRjAL/z3mdO ngCwdRbChXHxVVeQ2jdNQDK7PdbjkPcMXQVwEOvLLN3sWLML0eHl1+XTCWTVihMn 3pJf6cZcI1fO5ak0/cMkPCMjbYTvk4m082udPcRyRjXQJhTwSuHqoBXs3W21LemG IFybqbEpNMk= =qZpX -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- Roy T. Fielding wrote: > > That is not correct: CLAs and software grants are licenses, > not assignments. Larry Lessig says that the code should retain > each contributor's copyright. Apache has traditionally used the > Apache copyright alone to make it clear that everyone is contributing > to a joint work, and to avoid issues with ego and territory building. > Nevertheless, copyright remains with the original contributor and > only the copyright owner can change the notice. okey, which for derby means.. what? move the ibm copyright into NOTICES, and replace it in all source files with the asf licence application text? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUir+JrNPMCpn3XdAQFb0gP/bhVsPJ61fV3vI+ngFBDyQ/WqYSrzf+g7 3heDUscHNHOjB2LKu0GRoPUag9LMwn3pI8TGZc+yHPkVq+eBmH0S7gzuVaIro36/ Ox32Uhh3CWMj5X2JykG186JZL1yvAiBXh/2i3FYpZOVeMSjUxYPaPJcemOyCJRsA F+LWfeFIo3o= =ylvr -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > > I'll ensure it will get done by an committer from IBM, > once commit access has actually been granted :-) access has been requested; individuals should be receiving email as it is granted for them. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUnZUZrNPMCpn3XdAQFP8QP/TyYIoh9RApEBjFcN3UTdGDaCWgUjlmK2 hqEw3TYyHaqkVTNlvdhYivIuxWam6Ic0RhBUJkk0V30AOOFfkUcf3rulg+HnWKV9 +ssHmiV8vBKfUrAykxjmG5NAJtHBivjC5xR/Of0PwZKYSCiiiamL1WKTLW6b0Bqk AhWL5fXkQwI= =8lHS -END PGP SIGNATURE-
Re: [WEB] Derby Mentors, please 'svn update' to make DOTS writeup visible
-BEGIN PGP SIGNED MESSAGE- updated. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQUogh5rNPMCpn3XdAQH7PwP/flCitQU+6UupKbmTyf06/d1lpDm61Sb8 KgJz+p5b67FMH5aDBqsWS8gH/YXR/xGNJz9A12c2ieQo5JWW6+mliY66SP1S05GU 5TRiatbUyV4j/KPCOHZHfbAzHrXbjTq4o25xAMQF833VbJvEQBbtvbtrL6R/9xV7 rbXAJcQSbR8= =xy4E -END PGP SIGNATURE-
commit access finally enabled
-BEGIN PGP SIGNED MESSAGE- commit access enabled! clas having been received from the following people, the infrastructure team has created their accounts and i have just granted them commit access (called 'karma') to the /repos/asf/incubator/derby module: dan debrunner (djd) satheesh bandaram (bandaram) kathy marsden (kmarsden) samuel mcintyre (fuzzylogic) mike matrigali (mikem) each of these individuals should have received a message from the infrastructure team including their credentials and instructions. hurrah! - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQVFqsJrNPMCpn3XdAQH/fwP/YZGPkWM7mUzKFj5MoD2BN8adwj5MBMI+ Gh5qpilWx9esQTBJJEYD9gdtdiXdifadA59wydBpFfrRi7rQKMFxG/PZ0SNsZMj7 fm9pfqEp+HAn6CdHs6FllglLkRsBSUIGjhozm2N6WnkTXv6Ki1hxhCSH8j83yg77 htls6MvYh5M= =834S -END PGP SIGNATURE-
Re: [WEB] Derby Mentors, please 'svn update' to make web changes visible
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > > So if a mentor will 'svn update' to make the web site changes visible, > I'd appreciate it. done. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQVMzhZrNPMCpn3XdAQE0ZgP+M7M8CVAoAfM/jNySjC/+B1ZCevFFaP2i E8ClJNlSqwo8cARymgI4e7snWlu5EN+SxVJIk04TPwQz/mEHaXiJpMrno1y3cQfE 1T/CAQNZiHeDxdiQKdwB6bk3LTinasf33FGPGamFACd2viglbpzbhwgx7wUwfTAT nn/7/Gyzp2Y= =o6Uk -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- okey, after discussing this in seven different directions, we have a clear conclusion, which i'll summarise here: 1. the NOTICE file (or NOTICE.txt) gets created if it doesn't already exist, and this gets added to it: Portions of Apache Derby are © Copyright 2004 International Business Machines Corporation. All rights reserved. if there are earlier copyright years in any any of the main files, the earliest one of all should be taken and used to change the notice to 'Copyright , 2004 International ..'. in other words, the range of copyright years in the NOTICE file should be the earliest one with IBM's name on it in the sources, followed by ', 2004'. 2. the ibm copyright in the individual files gets replaced with Apache Derby © Copyright 2004 The Apache Software Foundation. All rights reserved. and reference to the apache licence added as described in http://www.apache.org/licenses/LICENSE-2.0.html#apply et vóilà! that item can then get checked off the incubation goal list and we can focus on *real* code issues. :-) see also http://www.apache.org/dev/apply-license.html for common questions about this stuff. the procedure above, which has finally been clarified, should be used by the incubator folks to update that file at some point. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQVQEoprNPMCpn3XdAQFadwP9GvqVgzI6tUffUeJh80QofQ5kmQr4hq7K NKDjnZHzjbMH5aGrximoeXSly9L/a96/7r0ESfBRI+xoy4NQZ0C9ebuj41qeO0DU jAxE4tE0bLZx+kvZ0VwyjbBI095I9hy3b2D7hOMuUTBTJGvaYztlQYiZjqr+d5HT tuj9tNE4Xj8= =Lg7h -END PGP SIGNATURE-
Re: Code changes going forward
-BEGIN PGP SIGNED MESSAGE- John McNally wrote: > All committers should be watching svn commit emails whether they go to > the dev list or a separate list and that is enough notice for changes > initiated by a committer. It's a good policy to respond to a > contributed patch by a non-committer in the original thread and is > especially necessary if the dev list is not the svn list. one possibly helpful tweak would be for the commit email list to have a reply-to set to derby-dev. that way any discussion of commits is directed to where it properly belongs. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQVV6fprNPMCpn3XdAQEm6wQAu6OIciexTWzqfJoYquThRTpxrlYhJDp7 er8slyg5Lw+EHD4Ad+1Q3TzMS09mxc7g++PFZCb+TirPOZ77Gjgvr42NhIWk1TG/ elryqguaMzeq/os+OtepRyu+LGCmWIAm4+sk5brFVeIEtGdzlfVSPxD5o9nek9zc kf6CYS1QVpM= =Z1J1 -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- all right, since roy has thrown yet another spanner in the works, Don't Anybody Do Anything. Roy T. Fielding wrote: > >> 1. the NOTICE file (or NOTICE.txt) gets created if it doesn't >>already exist, and this gets added to it: >> >> Portions of Apache Derby are © Copyright 2004 International >> Business Machines Corporation. All rights reserved. > > -1 The NOTICE file cannot contain restrictions on the license. > "All rights reserved" is a restriction -- it is contradicting > the irrevocable copyright license. i asked jennifer about that before posting this, and she disagrees with you. i'll let her explain it. >> et vóilà! that item can then get checked off the incubation goal list >> and we can focus on *real* code issues. :-) > > No, it does not. It means the code in the individual files is not > licensed under the AL2. It means that if someone wants to take an > individual function out of an individual file and add it to their > wizz-bang programmable dog, they have to ask permission from IBM. > > In short, their is no F*ing way this is going into code at the ASF. > > The copyright notice in the file has to say THIS FILE MAY BE COPIED > under the terms of the Apache License. It cannot just say "Apache > Derby" may be copied, since that name is not bound to any specific > expression, and copyright notices that are not bound to an expression > are null and void. okey, it's clear that this has to be resolved by lawyers, and specifically to a resolution acceptable to the asf counsel, since the advice we're getting from ibm's lawyers isn't universally satisfactory. so, everybody on the derby code team: forget the frickin' copyright issue and just work on the code while we get the legal bunfight settled. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQVVd0JrNPMCpn3XdAQHiMwP/U4xB/PRwz/D+yNbMKr/aS2a3sawp4HSL 2JIjFB6jzjGyRHxD4VP7Mhu9fo2MHyIXrSJEbIdMwz619RDLIoJ2Jg3GOyHKYL8e jxikVnjrVVSucbhIi1I4b4WB8yHUk4eGWlzcD3Z+s0/BcNJLEZ+2d/QLhObGzF3p jamaWGqEmLU= =X4mL -END PGP SIGNATURE-
Re: [VOTE] Establish development model based on Apache DB guidelines
-BEGIN PGP SIGNED MESSAGE- Daniel John Debrunner wrote: > Derby is being sponsored by the Apache DB project and the Derby status > page states 'The Apache DB project will own the Derby subproject, and > the subproject will follow the Apache DB PMC's direction'. I assume the > 'will own' means if Derby graduates from incubation. > (http://incubator.apache.org/projects/derby.html) > > I propose a consensus approval vote that the Derby development model > follows the guidelines defined by the Apache DB project. This will set > the initial rules for development, changes to the model could > subsequently be called for and voted on using the Derby developer > mailing list. i personally would recommend that all committers also be part of the ppmc (podling pmc) whilst in the incubator. after a successful exit and adoption into the db project, the db project's fixed-seat five-person pmc[1] will ultimately have total control of all non-technical issues and decisions. i don't recommend that any such subsetting is either appropriate or advisable while still incubating. so i would recommend the adoption of a 'the ppmc shall consist of all derby committers' policy for the duration of the incubation. [1] http://db.apache.org/management.html - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQTXdPZrNPMCpn3XdAQEbqQQAqVyHTQzKV+6+8DeFjWrfDm4UGgPofvV+ 192e+PISl7Qskk1If3+1j9B1HLu/IhPjBClACWhwdFIU2MRUxTJBSrq0FHPr/V17 7odarkTJbM4P8unlQkw58M8Tx4Po6SSmSjgQwxN2KGMode5iTW52omA60rBBj1QW Cmh9xSPyBa0= =3GrK -END PGP SIGNATURE-
Re: Derby code copyright question
-BEGIN PGP SIGNED MESSAGE- Jennifer B Machovec wrote: > I thought it might be helpful to give some background on the "all rights > reserved" phrase. The requirement for this phrase originated in the > Buenos Aires Convention of 1910, which provided that a copyright owner had > to make an express statement of the reservation of property rights in > order to have copyright protection in all countries that were party to the > convention. Because of subsequent changes in copyright law that I won't > bore you with (but can if you really want), this phrase essentially > became useless for works first published in the United States and most > other North and South American countries. However, there are still a few > countries in which this is a meaningful declaration, and for that reason > IBM (and many other copyright owners, including ASF in its standard > notice) retain this phrase to avoid such an exposure. It does not in any > way change or restrict license grants that are made by the copyright > owner. > > As far as the copyright notice in the individual files, while I'm not > certain that there is a problem regarding the Apache Derby reference, it > would be consistent with the ASL v.2.0 instructions to add a notice > stating: "Licensed under the Apache License, Version 2.0 (the "License"); > you may not use this file except in compliance with the License." That > should remove any ambiguity. roy, does that answer your concerns or not? - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQWFcw5rNPMCpn3XdAQEm2gQAyeunX6B3ZD9Wh3y0GXGco9xEUPAUZNCZ ri4x1x9/Hh7zyMV0e9gRBlDdW46sgJOT/BmKbq2NzQgq7873eLuwoDtcRofg7/Ku kWqw/Gp2+fmCBpUQC2yRu5NynyQb3tq6q15OXdSf91PuU5znaWnFs2FSBr8U+r3T u9aVlmNOtic= =YJD5 -END PGP SIGNATURE-
Re: Resend: [WEB] Derby Mentors, please 'svn update' to make web changes visible
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > > So, any mentor, please 'svn update' to make the web site changes visible. Done. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQXbgpJrNPMCpn3XdAQGjMwP+MbAuf8OR/Jrn6CzkTOt0PzqpFWYRAMWp wCidn6hY6tCnsEwbPcBZlBG1s6cDDJ2PnAi1K2HRr/QKczP29KvxaOJhvVMsLis0 IGcxWI/lIUPiZhsTVaiw3weWpVjeIMaENUE2boQkpsSg7n4Ioo4kD/kI2+oSHCw6 3b5kbhN5vqg= =5f1U -END PGP SIGNATURE-
Reolution of the copyright question
-BEGIN PGP SIGNED MESSAGE- Based upon advice for our counsel, the ASF has today adopted a policy governing how copyright notices on contributed files should be handled. Here's what happens: The following notice gets added to the top of each source file: Copyright [] The Apache Software Foundation or its licensors, as applicable. 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. The contributor may a) remove any copyright notice it may currently have in the file(s); OR b) move it to a package-wide COPYRIGHT file, changing 'Copyright []' to 'Portions Copyright []'; OR c) provide permission in writing to the ASF to do one or the other of the above. If the contributor doesn't have a copyright notice in the files, that's fine; nothing needs be done beyond the adding of the section above. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQYp9BJrNPMCpn3XdAQFKAAP/fSc0cyW5HooCNZQtlj0MLPnAGRSYTr0o 6YCB8LNRLhQw32qW1OgZ/mLFuD794UTxxblaHOFu8S4fqc9Zr5p0W68uvQqCVTWo 4AXG5uAWams1A1jupd1xoiF0aGlZrBsGijoc2VUuN+15kdLamZiOLl4XgZn7MJxX 9CMsfgGYpgc= =rtyY -END PGP SIGNATURE-
Re: Reolution of the copyright question
-BEGIN PGP SIGNED MESSAGE- Samuel Andrew McIntyre wrote: > > On Nov 4, 2004, at 11:53 AM, Daniel John Debrunner wrote: > >> 1) Create COPYRIGHT file > > Is this in addition to or in place of the NOTICE file? In addition to it. Furthermore, the format of the COPYRIGHT file should be: The following copyright notice(s) were affixed to portions of code with which this file is now or was at one time distributed and are placed here unaltered. followed by the _verbatim_ notices, moved without change. This has been approved by the ASF general counsel, and by the IBM counsel who has been tracking this issue. (And in record time, too!) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQZE6yZrNPMCpn3XdAQHnsQQAmokjd4QYuVSf72rpXQcUjkk0s6SNHsz+ NCbdGOoQ1fjfPv1aIUEx3DpR+F7apDNB+fXOWYro7kDBF1uq3ZSTQBykDdiU79QN aXehFIB2HuwVfJAmZErH8msTnOluezSHGnGD7zmS5Wjzy36qKR6KyfCk7Z/G1PZM Fr6jWnpzs1g= =efwy -END PGP SIGNATURE-
Note for committers
-BEGIN PGP SIGNED MESSAGE- Mentor hat on.. One of the aspects of being a committer that I suspect is less well publicised than it should be is the MailAlias.txt file in the Apache committers CVS module. Committers should each have a line in that file listing all valid email addresses that identify them; for instance, mine includes [EMAIL PROTECTED], [EMAIL PROTECTED], and [EMAIL PROTECTED] as\ well as [EMAIL PROTECTED] Of course, if this has already been mentioned, ignore me. Carry on.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQaR3B5rNPMCpn3XdAQGrswP8DZUFQTYjSxd5Ifpv1uGsYVP88pNgaA84 NrOPmThDNUeMdlmAhbq6VQ2rOC4thGR2Qn4h3fTyY3pT+U+ACvQd3d0xaNSAlxJg r0HVwlp8pd25tu+lP1OpWlMq2lLUnM7P163h13GeUPwo31ApYIcAmWBuvID3vAb4 NJfg3cZmggo= =SQOF -END PGP SIGNATURE-
[STATUS] (Derby) Fri 07 Jan 2005 04:09:10 PM EST
APACHE DERBY STATUS: Last modified at [$Date$] by $Author$. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t,b} ) [ One vote ] Option 2: Put all things Derby into a single tree ( derby/{trunk,tag
Re: [STATUS] (Derby) Fri 07 Jan 2005 04:09:10 PM EST
-BEGIN PGP SIGNED MESSAGE- Rodent of Unusual Size wrote: > APACHE DERBY STATUS: > Last modified at [$Date$] by $Author$. I can set this up to be automailed every Wednesday, as I do for several other projects. Shall I? This was a sample/test run. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQd9iv5rNPMCpn3XdAQGMMQQAgpvJZivo7T4la5bctDofv/LHOvTIzqmB 1WOfqBo0A86bJFahbmWw1HyvUTRoQ5WXPjFl9B+qto5rer3WaOoqNMbkXmv994ja 6+g0vZaQowh9CegPAWF6t7MggOc3RujX2X+ONcDmrYTc2G0iAKPx0YIkKEzNSoxm jDHO49CoNbc= =aZx5 -END PGP SIGNATURE-
Re: [STATUS] (Derby) Fri 07 Jan 2005 04:09:10 PM EST
-BEGIN PGP SIGNED MESSAGE- Jean T. Anderson wrote: > Rodent of Unusual Size wrote: >> >> I can set this up to be automailed every Wednesday, as I do for several >> other projects. Shall I? This was a sample/test run. > > Yes! Please do! Done. It should come out on Wednesdays. Someone might want to change the $Author$ and $Date$ tags to be something svn knows how to substitute.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQeQXaprNPMCpn3XdAQFa3gP+KKyVDkQ8sm89OLlJ9P//IORIG5pZNPG5 c0mdug2tteubiycrZfmqVk50HwQBclGeewJAr36gjevn3MG2z/gyiarCcbpG5xNF Bwdef5rzi1LVntrAK1e0hZ9pQI+/GuGMjJUv8RKvgQngKo2ai7AQqWVAQO1mDOXT UarYVt7GDb0= =dnPB -END PGP SIGNATURE-
Versioning, contents of STATUS and CHANGES files
-BEGIN PGP SIGNED MESSAGE- Is there anything in the code that tells someone using a copy built from Subversion that it isn't a formally released version? If there isn't, there needs to be one. As an example, the HTTP Server project sets the server version to something like "2.0.54-dev" while 2.0.54 is in development, then sets that to "2.0.54" and builds the release, and then sets the version in the code to "2.0.55-dev". This allows people to know from *exactly* where in the release sequence their version came, and whether it was released or something still in alpha/beta status. In looking through the sources for Derby, I don't see anything like that. I recall that there's an issue with the version being embedded in the database (or something like that), but the *code* version and the *database* version aren't identical, just related. If I'm missing something, just ignore me. Have there been no changes to the code since the release of 10.0.2.1? If there have been, they should be getting recorded in the trunk/CHANGES file, at the top, under a heading such as Changes in Derby 10.0.2.2-dev (or whatever version number is being used/embedded to identify the code as alpha/beta). At the 10.0.2.2 release, that gets altered to 'Changes with 10.0.2.2' and a new 'Changes with 10.0.2.3-dev' heading is started above it. Otherwise the CHANGES file won't change except at releases, which is a disservice to people observing or getting involved in the development mid-stream. When I took a look at the trunk/STATUS file this morning, I noticed two things. Firstly, that the formatting and wrapping was a bit off; I fixed that. Secondly, that the file appears to contain a lot of unnecessary or redundant info. It's intended to touch the high points, detailing what currently needs work and what items are under discussion (or have been committed/vetoed after being discussed) since the last release. Once the next release goes out the door, a lot of that gets cleaned up so that the file refers strictly to the current state of the code. The STATUS file's purpose in not to provide exhaustive status nor to include all past history. It's appropriate to include *some* environmental status while we're in the incubator, but if/when we graduate it should be reduced to just development/technical status, and project meta-data (guidelines, history, et cetera) should be moved elsewhere. I've attached a patch to reduce the STATUS file to what I think it should be; please 'test' the patch (apply it to your own copy) and see whether there's general agreement. Since there's no indication in the STATUS or CHANGES files that there have been any commits since the 10.0.2.1 release, I elided all the 'patches applied' paragraphs. If any of those have actually been applied since 10.0.2.1, they should be added back in. Oh, and when there are patches available, a link to the submission message should be included (ref. the RetrieveMessages patch). What the STATUS file contains *is* up to the developers, but this message is a mentor-guidance suggestion thing. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQe5cQprNPMCpn3XdAQGe2QQAynLV+mOOAyGclOWEFuLV/1xbsB09rnrU Y8zQGXiQ3Mrg5+xC6pHhujO6NQ6CoivtGx0zN5u7Xatq0a0K1GIxbMYk5oz3opma vTSMjqUwLCX7APzC8Pg1x4YGzVzZsKP7wYeDZo7GzPz3teVwqWzKwj6S8xnUzX8G ixoEYv855JI= =lNtt -END PGP SIGNATURE- Index: STATUS === --- STATUS (revision 125620) +++ STATUS (working copy) @@ -2,399 +2,68 @@ Last modified at [$Date$] by $Author$. -Web site: http://incubator.apache.org/derby/ +Web site: http://incubator.apache.org/derby/ +Incubator status: http://incubator.apache.org/projects/derby.html +Status file: http://incubator.apache.org/repos/asf/code/trunk/STATUS +Mailing lists:derby-dev@db.apache.org + derby-user@db.apache.org + [EMAIL PROTECTED] +Source code: http://svn.apache.org/repos/asf/incubator/derby/code/trunk/ + (in Subversion) +Bug database: http://issues.apache.org/jira/browse/DERBY +Mentors: Ken Coar + Sam Ruby + Geir Magnusson + Rodney Waldhoff +Guidelines: http://db.apache.org/guidelines.html + http://db.apache.org/source.html + http://tinyurl.com/4um2v + http://tinyurl.com/6c2pc -Incubator Status +Releases: 10.0.2.1 (8 December 2004) +In development: 10.0.2.2-dev - Description +DESCRIPTION +=== + "Derby" is the source code of IBM's Cloudscape Java relational + database, which was contributed to The Apache Software Foundation + in 2004. The IB
[STATUS] (Derby) Thu 27 Jan 2005 12:21:04 AM EST
APACHE DERBY STATUS: Last modified at [$Date: 2005-01-20 02:09:11 -0500 (Thu, 20 Jan 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: * 10.0.2.1 released on December 8, 2005. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. The Getting Started and Reference Manual were converted to DITA and are available for review from http://incubator.apache.org/derby/manuals/index.html RESOLVED ISSUES SINCE LAST STATUS = [VOTE] Network Server XAMGR Level Support Kathey Marsden submitted a patch for adding XA Support to
[STATUS] (Derby) Thu Feb 10 06:04:36 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-01-20 02:09:11 -0500 (Thu, 20 Jan 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem 2004-08-30 If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: * 10.0.2.1 released on December 8, 2005. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. The Getting Started and Reference Manual were converted to DITA and are available for review from http://incubator.apache.org/derby/manuals/index.html RESOLVED ISSUES SINCE LAST STATUS = [VOTE] Network Server XAMGR Level Support Kathey Marsden submitted a patch for adding XA Support to
[STATUS] (Derby) Wed Feb 16 23:45:28 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
[STATUS] (Derby) Wed Feb 23 23:45:27 2005
APACHE DERBY STATUS: Last modified at [$Date: 2005-02-10 15:37:41 -0500 (Thu, 10 Feb 2005) $] by $Author: fuzzylogic $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code by contributing it to The Apache Software Foundation and basing future versions of IBM Cloudscape on the Apache-managed code. To participate in the Derby podling, you should join the mailing list. Just send an empty message to [EMAIL PROTECTED] . The initial goal of the project while in incubation is to build a viable developer community around the codebase. The second goal of Derby-in-incubation is to successfully produce a release. Since Derby is in incubation, such a release would not have formal standing; it will serve as a proof-of-concept to demonstrate to the developers' and incubator's satisfaction that this aspect of the project is health and understood. Project info * The Apache DB project will own the Derby subproject, and the subproject will follow the Apache DB PMC's direction. Significant contributors to this sub- project (for example, after a significant interval of sustained contribution) will be proposed for commit access to the codebase. * The Derby sub-project's modules will be available as distinct and discrete downloads. Detailed References: itemtype reference Status file www http://incubator.apache.org/projects/derby.html Website www http://incubator.apache.org/derby/ Mailing listdev derby-dev@db.apache.org Mailing listusers derby-user@db.apache.org Source code SVN /repos/asf/incubator/derby/code/trunk/ Mentor coar Ken Coar (CLA on file) Committers jta Jean Anderson (CLA on file) Committers satheesh Satheesh Bandaram (CLA on file) Committers jboynes Jeremy Boynes (CLA on file) Committers djd Daniel Debrunner (CLA on file) Committers kmarsden Katherine Marsden (CLA on file) Committers mikem Mike Matrigali (CLA on file) Committers mcintyre Samuel McIntyre (CLA on file) Committers coar Ken Coar (CLA on file) Completed tasks are shown by the completion date (-MM-dd). Incubation status reports * none yet Incubation work items Project Setup Identify the codebase dateitem ...-..-.. If applicable, make sure that any associated 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. Copyright dateitem 2004-08-26 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. 2004-11-04 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Verify distribution rights dateitem 2004-10-12 Check that all active committers have a signed CLA on record. 2004-10-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. 2004-10-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2004-10-12 Check and make sure that all items depended upon 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. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project * Has the receiving PMC voted to accept it? **YES** Releases: None so far. A first release is in progress. This first release will be versioned 10.0.2.1. PENDING ISSUES == Derby documentation in PDF format: A request was made for PDF documentation, however, the source files for the current HTML documentation for Derby are not in a form useful for creating PDF documentation with Forrest. A proposal was made by Jeff Levitt <[EMAIL PROTECTED]> to convert the documentation into XML DITA format. RESOLVED ISSUES SINCE LAST STATUS = [VOTE] on repository layout: [ Ten votes ] Option 1: Keep the code and site pages in separately-versionable trees ( derby/site/{trunk,tags,branches}/ and derby/code/{t,t
Re: Case Sensitivity
-BEGIN PGP SIGNED MESSAGE- I don't actually use Derby, not being a Java person, but I *have* used MySQL for years. The case-sensitivity issue has bitten me before as well, but in the other direction: Satheesh Bandaram wrote: > I don't think Derby has a property to create a database case > insensitive. Why exactly do you need the database to be case > insensitive? Derby has string functions to convert data to upper case or > lower case, so it is possible for the application to store data in one > case. (Either upper only or lower only by converting at the input time) > All the searches after the database is created can then happen in that case. There's case-sensitive, case-aware/case-preserving, and case-insensitive. Is it actually the data that should be regarded as case-insensitive, or search operations? Case sensitivity makes a difference in collation results, and I think that can be compounded in some non-ISO-8859-1 character sets. For comparison, MySQL stores all data verbatim -- that is, case-sensitive. By default, stringish search operations (WHERE foo LIKE 'bar%') are case insensitive. They can be made case-sensitive by labelling one of the comparison operands as binary, either in the column definition (if appropriate) or in the search expression (WHERE foo LIKE BINARY 'bar%'). See http://dev.mysql.com/doc/mysql/en/case-sensitivity.html For what it's worth.. - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQh8G55rNPMCpn3XdAQEPjgQA3gEcRky+K1qqLf8SmFAjfbh7ORBYrsKY MYOVS9r1H2U617wKGQFOUquVKWsN4DdN8PlslzVaXNjYV1ppvDquk4Yl4prH6OV+ VuSGnecTHRVhRT//QhhimPTXZrk/r1q32VTEK4kDQSfuuDkrHYSFJkrH+f7UZGA8 OqxsQ4QUZJs= =Yla1 -END PGP SIGNATURE-