Modified: incubator/public/trunk/site-publish/ip-clearance/servicemix.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/ip-clearance/servicemix.html?view=diff&rev=473601&r1=473600&r2=473601 ============================================================================== --- incubator/public/trunk/site-publish/ip-clearance/servicemix.html (original) +++ incubator/public/trunk/site-publish/ip-clearance/servicemix.html Fri Nov 10 16:43:27 2006 @@ -1,314 +1,314 @@ - - - - - - - ServiceMix Codebase Intellectual Property (IP) Clearance Status - Apache Incubator - - - - - - - -
-The Apache Software Foundation - -Apache Incubator -
- - - - - - - - - - - - - - -

-

- Codebase IP Clearance -

-
-
-

- ServiceMix Codebase Intellectual Property (IP) Clearance Status -

-
-
-

- Description -

-
-

Apache ServiceMix is an open source distributed Enterprise Service Bus (ESB) and SOA toolkit built from - the ground up on the semantics and APIs of the Java Business Integration (JBI) specification JSR - 208.

-
-

- Project info -

-
-
    -
  • Which PMC will be responsible for the code: Apache Geronimo PMC
  • -
-
    -
  • Into which existing project/module: ServiceMix will go into its own project
  • -
-
    -
  • Officer or member managing donation: James Strachan
  • -
-

- Completed tasks are shown by the completion date (YYYY-MM-dd). -

-

- Identify the codebase -

-
- - - - - - - - - -
dateitem
2006-02-18Trademark, ServiceMix, assigned to ASF
-

- Copyright -

-
- - - - - - - - - - - - - -
dateitem
2006-02-04Check 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-12-26Check and make sure that the files that have been donated - have been updated to reflect the new ASF copyright.
-

- Identify name recorded for software grant: - the name of the grant as record - in the grants.txt document so that the grant can be easily identified - DONE -

-
-

- Verify distribution rights -

-
-

- Corporations and individuals holding existing distribution rights: -

-
    -
  • - For individuals, use the name as recorded on the committers page -
  • -
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2006-01-20

Check that all active committers have a signed CLA on record.

- svn log https://svn.codehaus.org/activemq/branches/activemq-4-0 | grep "r[0-9][0-9]* | " | - sed "s/r[0-9][0-9]* | \(.*\) | .* | .*$/\1/" | sort | uniq -

All of the committers have a CLA on file at Apache. The following - table maps the unix user names to real names:

- - - - - - - - - - - - - - - - -
bsnyderBruce Snyder
chirinoHiram Chirino
dandiepDaniel Diephouse
foconerFrederick OConer
gastaldiGeorge Gastaldi
gntGuillaume Nodet
gregwGregory Wilkins
janbJan Bartel
jgapuzJoseph Gapuz
jlimJonas Lim
jstrachanJames Strachan
maguroAlan Cabrera
myapMerwin Yap
pdoddsPhilip Dodds
rajdaviesRobert Davies
-
....-..-..Remind active committers that they are responsible for - ensuring that a Corporate CLA is recorded if such is - required to authorize their contributions under their - individual CLA.
....-..-..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.
....-..-..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 - -

-
-

- Related VOTEs: -

-
    -
  • - The VOTE thread accepting the donation may happen either - before or after IP clearance. Adoption by lazy concensus is acceptable but - not recommended. -
  • -
-
-
-

- - + + + + + + + ServiceMix Codebase Intellectual Property (IP) Clearance Status - Apache Incubator + + + + + + + +
+The Apache Software Foundation + +Apache Incubator +
+ + + + + + + + + + + + + + +

+

+ Codebase IP Clearance +

+
+
+

+ ServiceMix Codebase Intellectual Property (IP) Clearance Status +

+
+
+

+ Description +

+
+

Apache ServiceMix is an open source distributed Enterprise Service Bus (ESB) and SOA toolkit built from + the ground up on the semantics and APIs of the Java Business Integration (JBI) specification JSR + 208.

+
+

+ Project info +

+
+
    +
  • Which PMC will be responsible for the code: Apache Geronimo PMC
  • +
+
    +
  • Into which existing project/module: ServiceMix will go into its own project
  • +
+
    +
  • Officer or member managing donation: James Strachan
  • +
+

+ Completed tasks are shown by the completion date (YYYY-MM-dd). +

+

+ Identify the codebase +

+
+ + + + + + + + + +
dateitem
2006-02-18Trademark, ServiceMix, assigned to ASF
+

+ Copyright +

+
+ + + + + + + + + + + + + +
dateitem
2006-02-04Check 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-12-26Check and make sure that the files that have been donated + have been updated to reflect the new ASF copyright.
+

+ Identify name recorded for software grant: + the name of the grant as record + in the grants.txt document so that the grant can be easily identified + DONE +

+
+

+ Verify distribution rights +

+
+

+ Corporations and individuals holding existing distribution rights: +

+
    +
  • + For individuals, use the name as recorded on the committers page +
  • +
+ + + + + + + + + + + + + + + + + + + + + +
dateitem
2006-01-20

Check that all active committers have a signed CLA on record.

+ svn log https://svn.codehaus.org/activemq/branches/activemq-4-0 | grep "r[0-9][0-9]* | " | + sed "s/r[0-9][0-9]* | \(.*\) | .* | .*$/\1/" | sort | uniq +

All of the committers have a CLA on file at Apache. The following + table maps the unix user names to real names:

+ + + + + + + + + + + + + + + + +
bsnyderBruce Snyder
chirinoHiram Chirino
dandiepDaniel Diephouse
foconerFrederick OConer
gastaldiGeorge Gastaldi
gntGuillaume Nodet
gregwGregory Wilkins
janbJan Bartel
jgapuzJoseph Gapuz
jlimJonas Lim
jstrachanJames Strachan
maguroAlan Cabrera
myapMerwin Yap
pdoddsPhilip Dodds
rajdaviesRobert Davies
+
....-..-..Remind active committers that they are responsible for + ensuring that a Corporate CLA is recorded if such is + required to authorize their contributions under their + individual CLA.
....-..-..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.
....-..-..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 + +

+
+

+ Related VOTEs: +

+
    +
  • + The VOTE thread accepting the donation may happen either + before or after IP clearance. Adoption by lazy concensus is acceptable but + not recommended. +
  • +
+
+
+

+ + Propchange: incubator/public/trunk/site-publish/ip-clearance/servicemix.html ------------------------------------------------------------------------------ svn:eol-style = native Modified: incubator/public/trunk/site-publish/ip-clearance/ws-jaxws.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/ip-clearance/ws-jaxws.html?view=diff&rev=473601&r1=473600&r2=473601 ============================================================================== --- incubator/public/trunk/site-publish/ip-clearance/ws-jaxws.html (original) +++ incubator/public/trunk/site-publish/ip-clearance/ws-jaxws.html Fri Nov 10 16:43:27 2006 @@ -1,290 +1,290 @@ - - - - - - - JAXWS - - Apache Incubator - - - - - - - -
-The Apache Software Foundation - -Apache Incubator -
- - - - - - - - - - - - - - -

-

- JAXWS Codebase IP Clearance Status - -

-
-
-

- Description - -

-
-

The incoming code was contributed by IBM. The code -is currently in JIRA (http://issues.apache.org/jira/browse/AXIS2-826). It implements -JAX-WS standard for use with Apache Axis2. -

-
-

- Project info - -

-
-
    -
  • Which PMC will be responsible for the code -
  • -
-

Apache Web Services PMC -

-
    -
  • Into which existing project/module -
  • -
-

/webservices/axis2/trunk/java/modules/jaxws -

-

- Completed tasks are shown by the completion date (YYYY-MM-dd). - -

-

- Identify the codebase - -

-
- - - - - - - - - -
date -item -
2006-16-06 -Codebase has been uploaded into JIRA. -
-
-

- Copyright - -

-
- - - - - - - - - -
date -item -
2006-06-16 -Software Grant form received by Jim -
-
-

- Verify distribution rights - -

-
- - - - - - - - - - - - - - - - - - - - - -
date -item -
2006-06-16 -Software Grant form received by Jim -
2006-06-19 -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. -
2006-06-19 -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. -
2006-06-19 -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? -
  • -
-

Started an explicit VOTE on 2006-06-19 -

-
-

- - + + + + + + + JAXWS + - Apache Incubator + + + + + + + +
+The Apache Software Foundation + +Apache Incubator +
+ + + + + + + + + + + + + + +

+

+ JAXWS Codebase IP Clearance Status + +

+
+
+

+ Description + +

+
+

The incoming code was contributed by IBM. The code +is currently in JIRA (http://issues.apache.org/jira/browse/AXIS2-826). It implements +JAX-WS standard for use with Apache Axis2. +

+
+

+ Project info + +

+
+
    +
  • Which PMC will be responsible for the code +
  • +
+

Apache Web Services PMC +

+
    +
  • Into which existing project/module +
  • +
+

/webservices/axis2/trunk/java/modules/jaxws +

+

+ Completed tasks are shown by the completion date (YYYY-MM-dd). + +

+

+ Identify the codebase + +

+
+ + + + + + + + + +
date +item +
2006-16-06 +Codebase has been uploaded into JIRA. +
+
+

+ Copyright + +

+
+ + + + + + + + + +
date +item +
2006-06-16 +Software Grant form received by Jim +
+
+

+ Verify distribution rights + +

+
+ + + + + + + + + + + + + + + + + + + + + +
date +item +
2006-06-16 +Software Grant form received by Jim +
2006-06-19 +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. +
2006-06-19 +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. +
2006-06-19 +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? +
  • +
+

Started an explicit VOTE on 2006-06-19 +

+
+

+ + Propchange: incubator/public/trunk/site-publish/ip-clearance/ws-jaxws.html ------------------------------------------------------------------------------ svn:eol-style = native Modified: incubator/public/trunk/site-publish/official/mailing-lists.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/official/mailing-lists.html?view=diff&rev=473601&r1=473600&r2=473601 ============================================================================== --- incubator/public/trunk/site-publish/official/mailing-lists.html (original) +++ incubator/public/trunk/site-publish/official/mailing-lists.html Fri Nov 10 16:43:27 2006 @@ -1,191 +1,191 @@ - - - - - - - Mailing List Resolutions - Apache Incubator - - - - - - - -
-The Apache Software Foundation - -Apache Incubator -
- - - - - - - - - - - - - - -

-

- Resolution Of July 2005 -

-
-

Reproduced below is - the -text of the ASF Board resolution that was adopted in July 2005 which pertains to mailing lists: -

-
-

WHEREAS, Project Management Committees (PMCs) within - The Apache Software Foundation are required to conduct their - normal business on public mailing lists for their project; and -

-

WHEREAS, the Foundation provides each PMC with a private list - called "pmc" for sensitive discussions for which a public - discussion is prevented by statute or contractual restraints - on the Foundation; and -

-

WHEREAS, mailing list names are standardized to make it easier - for project oversight and administration; and -

-

WHEREAS, volunteers on Foundation projects frequently make the - mistake of misdirecting public discussion to the "pmc" lists - because the name implies a group of people rather than a type - of discussion. -

-

NOW, THEREFORE, BE IT RESOLVED, that the Infrastructure - Committee be and hereby is directed to rename all "pmc" lists - to private@project and to use the name "private" for all such - future lists; and let it further be -

-

RESOLVED, that all Project Management Committees within The - Apache Software Foundation shall restrict their communication - on private mailing lists to issues that cannot be discussed in - public, such as discussion of pre-disclosure security problems, - pre-agreement discussions with third parties that require - confidentiality, discussion of nominees for project or - Foundation membership, and personal conflicts among project - personnel. -

-
-
-

- - + + + + + + + Mailing List Resolutions - Apache Incubator + + + + + + + +
+The Apache Software Foundation + +Apache Incubator +
+ + + + + + + + + + + + + + +

+

+ Resolution Of July 2005 +

+
+

Reproduced below is + the +text of the ASF Board resolution that was adopted in July 2005 which pertains to mailing lists: +

+
+

WHEREAS, Project Management Committees (PMCs) within + The Apache Software Foundation are required to conduct their + normal business on public mailing lists for their project; and +

+

WHEREAS, the Foundation provides each PMC with a private list + called "pmc" for sensitive discussions for which a public + discussion is prevented by statute or contractual restraints + on the Foundation; and +

+

WHEREAS, mailing list names are standardized to make it easier + for project oversight and administration; and +

+

WHEREAS, volunteers on Foundation projects frequently make the + mistake of misdirecting public discussion to the "pmc" lists + because the name implies a group of people rather than a type + of discussion. +

+

NOW, THEREFORE, BE IT RESOLVED, that the Infrastructure + Committee be and hereby is directed to rename all "pmc" lists + to private@project and to use the name "private" for all such + future lists; and let it further be +

+

RESOLVED, that all Project Management Committees within The + Apache Software Foundation shall restrict their communication + on private mailing lists to issues that cannot be discussed in + public, such as discussion of pre-disclosure security problems, + pre-agreement discussions with third parties that require + confidentiality, discussion of nominees for project or + Foundation membership, and personal conflicts among project + personnel. +

+
+
+

+ + Propchange: incubator/public/trunk/site-publish/official/mailing-lists.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: incubator/public/trunk/site-publish/projects/abdera.html ------------------------------------------------------------------------------ svn:eol-style = native --------------------------------------------------------------------- To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org For additional commands, e-mail: cvs-help@incubator.apache.org