RE: [VOTE] JSPWiki Incubation
+1 to incubation. Go JSPWiki! On Wed, 2007-09-12 at 13:16 -0400, Noel J. Bergman wrote: Are we ready to incubate? Seems as if we have: Dave Johnson Sam Ruby Henning Schmiedehausen Craig L Russell as Mentors. Given that there was no [VOTE] explicitly posted, and at least one person comented that I thought this was just the disussion and the vote would start afterwards, I am posting this as a formal vote. So far we have: Binding: +1 Craig Russell +1 Noel Bergman +1 Nicolas Hedman +1 Ted Husted Other: +1 Dave Johnson (retroactively binding?) Barring any changes, it will be as of Thursday, so yes. +1 Alexey Petrenko +1 Martijn Dashorst Run this until Friday, then post (and act on) the results. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person Open Source Consulting, Development, Design| Velocity - Turbine guy INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen It's good to be a lunatic... -- 10th doctor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve release CXF 2.0.2-incubator
Kevan, Two notes: 1) Section 4(d) of the apache license says that any derivative work of an apache licensed product must include a readable copy of the attribution notices contained within the NOTICE file of the product. I guess there is a question of whether including a products jar is creating a derivative work.We use xbean, but we haven't made a derivative work. That said, probably not something worth arguing about IANAL. 2) Of the list you listed, the only two that would apply is the BEA copyright and the W3C suff. We already have w3c stuff in the NOTICE. Dan D. and myself will try to go through things more in the next couple days (we've both been traveling this week) and add them to the appended stuff. Dan On Wednesday 12 September 2007, Kevan Miller wrote: On Sep 11, 2007, at 6:34 AM, Dan Diephouse wrote: We held a vote on cxf-dev to release a new version of CXF. This version includes mosltly bug fixes since the 2.0.1 release. For a full list of the issues, see: https://issues.apache.org/jira/secure/ReleaseNote.jspa? version=12312672styleName=HtmlprojectId=12310511Create=Create The vote thread is at: http://www.nabble.com/-VOTE--Release- CXF-2.0.2-incubator-tf4403518.html In summary, we have 11 +1 votes, no 0 or -1 votes. One of these is an IPMC vote from Jeff Genender. The staging area is at: http://people.apache.org/~dkulp/stage_cxf/2.0.2-incubator-take1/ The distributions are in the dist directory. The m2_repo directory contains the stuff that will by pushed to the m2-incubating-repository. This release is tagged at: http://svn.apache.org/repos/asf/ incubator/cxf/tags/cxf-2.0.2-incubator/ We and our users appreciate you taking the time to look over this release! Looks like I should have asked this question for your 2.0 and 2.0.1 releases. Apologies for bringing it up now... I'm guessing that you're using the maven-remote-resources-plugin to help generate your NOTICE files. I've noticed other projects using the plugin and their notice files follow a similar form. I've just started looking at the plugin for possible use in Geronimo and OpenEJB, probably the reason I noticed... My question is: is your NOTICE file correct? I don't think it is. I don't think that it follows the requirements of the licenses of the artifacts which you are redistributing... Section 4(d) of the apache license says that any derivative work of an apache licensed product must include a readable copy of the attribution notices contained within the NOTICE file of the product. You are redistributing multiple apache licensed artifacts. However, you aren't reproducing their attribution notices. Instead, attributions of the following form have been generated: This product includes/uses software, name of software, developed by name of project License: name of license Case in point (taken at random from your lib directory) is lib/ xbean-2.2.0.jar. This is your XMLBeans attribution in your NOTICE file: This product includes/uses software, XMLBeans main classes (http:// xmlbeans.apache.org), developed by Apache Software Foundation (http://www.apache.org/) License: The Apache Software License, Version 2.0 (http:// www.apache.org/licenses/LICENSE-2.0.txt) However, this is the NOTICE.txt file contained within xbean-2.2.0.jar: This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Portions of this software were originally based on the following: - software copyright (c) 2000-2003, BEA Systems, http:// www.bea.com/. Aside from contributions to the Apache XMLBeans project, this software also includes: - one or more source files from the Apache Xerces-J and Apache Axis products, Copyright (c) 1999-2003 Apache Software Foundation - W3C XML Schema documents Copyright 2001-2003 (c) World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University) - resolver.jar from Apache Xml Commons project, Copyright (c) 2001-2003 Apache Software Foundation - Piccolo XML Parser for Java from http://piccolo.sourceforge.net/, Copyright 2002 Yuval Oren under the terms of the Apache Software License 2.0 - JSR-173 Streaming API for XML from http://sourceforge.net/ projects/xmlpullparser/, Copyright 2005 BEA under the terms of the Apache Software License 2.0 You can decide that some of these attributions do not apply to CXF. However, IMO some of them do. And these need to be reproduced in your NOTICE file. I suspect this applies to other artifacts that your are including. NB: this is my understanding of the requirements for the handling of NOTICE files. Suggest you draw on the expertise of incubating experts, before acting... --kevan
Re: [VOTE] Approve release CXF 2.0.2-incubator
On Sep 14, 2007, at 11:34 AM, Daniel Kulp wrote: Kevan, Two notes: 1) Section 4(d) of the apache license says that any derivative work of an apache licensed product must include a readable copy of the attribution notices contained within the NOTICE file of the product. I guess there is a question of whether including a products jar is creating a derivative work.We use xbean, but we haven't made a derivative work. That said, probably not something worth arguing about IANAL. Neither am I. ;-) Ultimately, it's a decision for your PMC (and, for the moment, the incubator PMC). 2) Of the list you listed, the only two that would apply is the BEA copyright and the W3C suff. We already have w3c stuff in the NOTICE. Dan D. and myself will try to go through things more in the next couple days (we've both been traveling this week) and add them to the appended stuff. Sounds good. I know it's painful -- I'm reminded every release... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Incubator Proposal: SPL
All, Developers at IBM and Sun, with assistance from Bill Stoddard, have developed the proposal appended below. We ask that the ASF consider forming an incubator according to the proposal. As this is our first incubator request, we would appreciate any suggestions, and we're happy to answer any questions that you have. Cheers, David David L. Kaminsky [EMAIL PROTECTED] Abstract - Policy systems allow administrators to define policies that guide the automated administration of resources. Such automation saves time and effort by simplifying resource-management. We proposed to develop a policy-based management infrastructure that automates administrative tasks by executing policies written in the Simplified Policy Language (SPL), a standards-based policy language. Proposal This proposal seeks to create a project within the Apache Software Foundation to (1) develop a policy evaluator for the SPL policy language, and (2) develop bindings between the policy evaluator and projects such as Apache Geronimo. Background --- As computer systems become more complicated, they continue to become increasingly complex and costly to manage. Various studies have shown that the cost of managing systems often exceeds the cost of purchasing them. The goal of the SPL project is to reduce management burden by allowing administrators to specify policies that replace manual administrative actions. Rationale Policy-based management is one approach to reducing the cost of systems administration. Administrators define policies that express a management intent, and the policy-based management system executes the policy, thereby reducing the burden on the administrator. For example, a policy might state backup the database daily at 1am. A policy management system would interpret the policy, and trigger the database to perform a backup at the assigned time, offloading that task from the administrator. To allow more flexible semantics, such policies are often expressed as If-Then (also called Condition-Action) rules. For example, If the packet comes from subnet 6.7.8.*, Then place it on the high-priority outgoing queue or If the data in the database have changed by 10%, Then perform an incremental backup. Such policies allow for more complex automation. To implement these kinds of rule-based policies, the policy system must interact with the system's APIs. In the second example above, the system relies on the ability to measure the percentage of data that have changed since the last backup (or to compute that value from measurable data). Similarly, to execute the then clause, the policy system must be able to start an incremental backup on the database using the database's API. Expressed generally, a policy system must have a binding to the instrumentation layer or API for the system under management. Thus, policy systems consist of two major components: an evaluation engine and a binding to an instrumentation environment. The evaluation engine (1) accepts policies expressed according to a well-defined grammar, (2) collects the data needed to evaluate the policies, and (3) actuates the Then section as appropriate. This project would build an SPL evaluation engine and bindings to various Apache and non-Apache APIs. The design of SPL, a Preliminary DMTF standard, is inspired by existing policy languages and models including PDL (policy definition language) from Bell Laboratories, the Ponder policy language from Imperial College, and other policy languages. The basic unit of a SPL policy is a policy rule. A SPL policy rule consists of a condition, an action, and other fields. Multiple policy rules can be grouped into a policy group. Policy groups can be nested -- i.e., a policy group can contain another policy group. For the specification of the policy condition, SPL provides a rich set of operators that act on the following types: signed and unsigned short, regular and long integers, float and long float, character, string, Boolean, and calendar. We expect the community to develop a number of bindings between the evaluation engine and APIs. Examples include the API for Geronimo, and standard interfaces such as WSDM and CIM. The community may choose to develop a wide range of bindings, all leveraging the common SPL engine and policy syntax. The SPL Policy Engine will be implemented in the form of a Java application. The SPL application will provide the following functionality: 1. PolicyManager - The PolicyManager acts as an orchestrator delegating tasks to its subcomponents. 2. PolicyDataStore - The PolicyDataStore is responsible for two major tasks: Policy Storage and the creation of Internal Policy Objects: a. Policy Storage: This involves persisting of the policies into a repository along with caching of the Internal Policy Objects for use in evaluation b. Internal Policy Object Creation: This involves
Re: Incubator Proposal: SPL
Hi, A few comments on this proposal. On Sep 14, 2007, at 11:11 AM, David L Kaminsky wrote: The design of SPL, a Preliminary DMTF standard, is inspired by existing policy languages and models including PDL (policy definition language) from Bell Laboratories, the Ponder policy language from Imperial College, and other policy languages. Are there any IP issues with these standards? Under what licenses are these languages and models released? Relationships with other Apache Products Might be good to discuss here (or elsewhere with a list here) how an integration with the previously listed Apache projects would work. (3.1) mailing list(s) -cimspl-private (with moderated subscriptions) As a project name, cimspl doesn't grab me. Since email aliases are long-lived, it might be well to discuss a suitable project name before entering incubation. How about mordac after the Scott Adams IT manager ;-) Champion -Bill Stoddard([EMAIL PROTECTED]) Nominated Mentors -Bill Stoddard([EMAIL PROTECTED]) I'll volunteer to help mentor this project. Regards, Craig Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
[PROPOSAL] JVending
Hi, I have a proposal to bring over JVending to the Apache incubator. I have put a good deal of work into this project over the last few years, but it is languishing on Sourceforge due to lack of community interest. I've seen what the incubator has done for the NMaven podling; I would like to breathe similar life into JVending by using the incubator to generate interest, build a community and recruit good developers. I'd like to see if there is any interest from the Apache community in getting JVending fully compliant with JSR-124 and passing the TCK, as well as subsequent work on the portal and various adaptors. I have also been reading about some of the new work with Product Line Architectures coming out using JVending: this could be an important area of growth for social networks and the delivery of content, and another area of focus for JVending. Currently, there are no other developers; I am in need of mentors and committers. Proposal Link: http://wiki.apache.org/incubator/JVendingProposal Thanks, Shane Isbell = JVending Proposal Abstract JVending is a content provisioning system that implements most of the J2EE Client Provisioning Specification (JSR-124). Proposal JVending is a content provisioning system that implements most of the J2EE Client Provisioning Specification (JSR-124). It provides catalog management, device detection and Web/WAP based browsing. It is designed to run on embedded servers and DBs, as well as within more traditional carrier systems and deployments. Background The mobile application space deals with numerous handheld devices, each with different capabilities. It's a challenge to match content requirements - such as screen size, MIDP version, and memory - to an appropriate device. The JSR-124 expert group addressed these issues by creating a specification that defined how to match content requirements to device capabilities. The specification also covers discovery of content, stocking of content and delivery adapters for provisioning. While the specification arose to address pain points within the mobile industry, the specification covers all content and all devices (including PCs). JVending initially arose from a desire to demonstrate the basics of DRM and OTA provisioning, but later developed into a fully functional provisioning server based on the JSR-124 spec. An early goal, maintained throughout the life of the project, has been to build a provisioning server that is light enough to deploy on PCs so that the individual can participate in the sharing and publishing of content. Rationale JVending is the only open-source version of JSR-124. While there are a number of other content repositories, JVending is the only one specialized for general capability matching and custom interactions to the device, making it highly extensible. For example, users can easily create custom interfaces - SOAP, RDF, HTTP, OTA - that sit on top of a common repository with advanced device capability matching. In my case, I recently developed a Maven adapter to deliver artifacts to the build machine. There is also exciting, new work in Product Line Architectures that integrates JVending with Scatter for matching devices and applications across millions of variants. This has important implications for social and location aware content delivery. ASF would be a good home for JVending due to the ASF's emphasis on community building, which is an area that has been enormously difficult to do on sourceforge. Initial Goals - Change code base to ASLv2 - Import code base to incubator SVN - Remove LGPL Hibernate dependencies - Recruit developers Current Status JVending implements most of the JSR-124 spec but has not been tested with the TCK. The last release of JVending provisioning J2EE component was April 2006. There has been subsequent work related to integrating with WURFL and adapters for provisioning of Maven artifacts. No active work is going on at this time. Meritocracy There is currently only one developer on the project. Additional developers will be added by following the Apache meritocracy process. Community Various companies have expressed interest in deploying JVending but no active community has involved in its development or use. Given the current trends in self-publishing of content, there is a large potential base of users and developers, particularly those wanting to deliver personal content to mobile devices. Also, since JVending is implementing a JSR spec, I expect there to be interest in commercial developers wanting to leverage open standards in the provisioning space. The goal is to attract 3-5 developers from different companies/organizations to sustain the project. Core Developers Shane Isbell, who is the only developer on the project, founded JVending. Alignment JVending currently has dependencies on Apache projects jaxme for processing of configuration files and Lucene for content search. It is packaged as a WAR file and runs on Tomcat. It also
RE: Incubator Proposal: SPL
We proposed to develop a policy-based management infrastructure that automates administrative tasks by executing policies Sounds good. I will be curious to see the reaction from the HTTP Server folks, but this sort of thing is very much needed in real-world deployments of app servers. The initial goals are to develop an SPL evaluation engine and bindings to the APIs for [...] What about Tomcat? Nominated Mentors -Bill Stoddard([EMAIL PROTECTED]) Glad to see that Bill will have cycles for this. :-) Would you please take a look at lokahi (http://incubator.apache.org/lokahi) and comment on any synergies that you see? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] JVending
Have you approached Geronimo to see if they are interested, and would participate? Are there other projects with which it aligns well? Just looking for natural allies to help build your community. :-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: SPL
On Saturday 15 September 2007 02:11, David L Kaminsky wrote: Simplified Policy Language (SPL), a standards-based policy language. Incubator has been discouraging naming projects after domains or standards. Once you come with a suitable name, you'll have my +1 for Incubation. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] JVending
On Saturday 15 September 2007 06:01, Shane Isbell wrote: - JSR-124 Specification: http://jcp.org/aboutJava/communityprocess/final/jsr124/ There has been some debate over Sun led JSRs in general. Is this particular one to the ASF's satisfaction? Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
