Re: November Incubator Reports ARE LATE!
Done On Nov 11, 2007, at 11:02 PM, Noel J. Bergman wrote: Bruce Snyder wrote: ServiceMix graduated from the Incubator, is it still required to report? It is required to clean up http://incubator.apache.org/projects. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: [PROPOSAL] Shindig, an OpenSocial Container
+1 On Nov 9, 2007, at 1:03 PM, Brian McCallister wrote: Shindig Proposal -- = Abstract = Shindig will develop the container and backend server components for hosting OpenSocial applications. = Proposal = Shindig will develop a JavaScript container and implementations of the backend APIs and proxy required for hosting OpenSocial applications. = Background = OpenSocial provides a common set of APIs for social applications across multiple websites. With standard JavaScript and HTML, developers can create social applications that use a social network's friends and update feeds. A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server. More information can be found about OpenSocial at http://code.google.com/apis/opensocial/ == Rationale == Shindig is an implementation of an emerging set of APIs for client- side composited web applications. The Apache Software Foundation has proven to have developed a strong system and set of mores for building community-centric, open standards based systems with a wide variety of participants. A robust, community-developed implementation of these APIs will encourage compatibility between service providers, ensure an excellent implementation is available to everyone, and enable faster and easier application development for users. The Apache Software Foundation has proven it is the best place for this type of open development. = Current Status = This is a new project. = Meritocracy = The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project. === Community === Shindig seeks to develop developer and user communities during incubation. = Core Developers = The initial core developers are all Ning employees. We hope to expand this very quickly. = Alignment = The developers of Shindig want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components. = Known Risks = == Orphaned products == Shindig is new development of an emerging set of APIs. == Inexperience with Open Source == The initial developers include long-time open source developers, including Apache Members. == Homogenous Developers == The initial group of developers is quite homogenous. Remedying this is a large part of why we want to bring the project to Apache. == Reliance on Salaried Developers == The initial group of developers are employed by a potential consumer of the project. Remedying this is a large part of why we want to bring the project to Apache. == Relationships with Other Apache Products == None in particular, except that Apache HTTPD is the best place to run PHP, which the server-side components Ning intends to donate have been implemented in. == A Excessive Fascination with the Apache Brand == We believe in the processes, systems, and framework Apache has put in place. The brand is nice, but is not why we wish to come to Apache. = Documentation = Google's OpenSocial Documentation: http://code.google.com/apis/opensocial/ Ning's OpenSocial Documentation: http://tinyurl.com/3y5ckx = Initial Source = Ning, Inc. intends to donate code based on their implementation of OpenSocial. The backend systems will be replaced with more generic equivalents in order to not bind the implementation to specifics of the Ning platform. This code will be extracted from Ning's internal development, and has not been expanded on past the extraction. It will be provided primarily as a starting place for a much more robust, community- developed implementation. = External Dependencies = The initial codebase relies on a library created by Google, Inc., and licensed under the Apache Software License, Version 2.0. = Required Resources = Developer and user mailing lists A subversion repository A JIRA issue tracker = Initial Committers = Thomas Baker[EMAIL PROTECTED] Tim Williamson [EMAIL PROTECTED] Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Martin Traverso [EMAIL PROTECTED] = Sponsors = == Champion == Brian McCallister [EMAIL PROTECTED] == Nominated Mentors == Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Santiago Gala [EMAIL PROTECTED] Upayavira [EMAIL PROTECTED] == Sponsoring Entity == The Apache Incubator. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: [PROPOSAL] Shindig, an OpenSocial Container
+1 I have no explanation why the social networks are experiencing such growth these days, but it is certainly another fun area for developers :-) Andrus Brian McCallister wrote: Shindig Proposal -- = Abstract = Shindig will develop the container and backend server components for hosting OpenSocial applications. = Proposal = Shindig will develop a JavaScript container and implementations of the backend APIs and proxy required for hosting OpenSocial applications. = Background = OpenSocial provides a common set of APIs for social applications across multiple websites. With standard JavaScript and HTML, developers can create social applications that use a social network's friends and update feeds. A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server. More information can be found about OpenSocial at http://code.google.com/apis/opensocial/ == Rationale == Shindig is an implementation of an emerging set of APIs for client- side composited web applications. The Apache Software Foundation has proven to have developed a strong system and set of mores for building community-centric, open standards based systems with a wide variety of participants. A robust, community-developed implementation of these APIs will encourage compatibility between service providers, ensure an excellent implementation is available to everyone, and enable faster and easier application development for users. The Apache Software Foundation has proven it is the best place for this type of open development. = Current Status = This is a new project. = Meritocracy = The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project. === Community === Shindig seeks to develop developer and user communities during incubation. = Core Developers = The initial core developers are all Ning employees. We hope to expand this very quickly. = Alignment = The developers of Shindig want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components. = Known Risks = == Orphaned products == Shindig is new development of an emerging set of APIs. == Inexperience with Open Source == The initial developers include long-time open source developers, including Apache Members. == Homogenous Developers == The initial group of developers is quite homogenous. Remedying this is a large part of why we want to bring the project to Apache. == Reliance on Salaried Developers == The initial group of developers are employed by a potential consumer of the project. Remedying this is a large part of why we want to bring the project to Apache. == Relationships with Other Apache Products == None in particular, except that Apache HTTPD is the best place to run PHP, which the server-side components Ning intends to donate have been implemented in. == A Excessive Fascination with the Apache Brand == We believe in the processes, systems, and framework Apache has put in place. The brand is nice, but is not why we wish to come to Apache. = Documentation = Google's OpenSocial Documentation: http://code.google.com/apis/opensocial/ Ning's OpenSocial Documentation: http://tinyurl.com/3y5ckx = Initial Source = Ning, Inc. intends to donate code based on their implementation of OpenSocial. The backend systems will be replaced with more generic equivalents in order to not bind the implementation to specifics of the Ning platform. This code will be extracted from Ning's internal development, and has not been expanded on past the extraction. It will be provided primarily as a starting place for a much more robust, community- developed implementation. = External Dependencies = The initial codebase relies on a library created by Google, Inc., and licensed under the Apache Software License, Version 2.0. = Required Resources = Developer and user mailing lists A subversion repository A JIRA issue tracker = Initial Committers = Thomas Baker[EMAIL PROTECTED] Tim Williamson [EMAIL PROTECTED] Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Martin Traverso [EMAIL PROTECTED] = Sponsors = == Champion == Brian McCallister [EMAIL PROTECTED] == Nominated Mentors == Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Santiago Gala [EMAIL PROTECTED] Upayavira [EMAIL PROTECTED] == Sponsoring Entity == The Apache Incubator. -
Re: Projects in trouble or otherwise needing help
Noel J. Bergman wrote: It appears that we have a number of projects to discuss: NMaven - mailing list shows steady activity. XAP - mailing lists show almost no discussion, mostly JIRA issues and commits WSRP4J - burst of activity during the Summer, nothing since. The issues do not appear to be the same in all cases. I had to review the archives, since there were no board reports. I still think we should close WSRP4J and afaik it's an open issue at the portals project. Carsten -- Carsten Ziegeler [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve release CXF 2.0.3-incubator
Looks good. +1 --kevan On Nov 9, 2007, at 9:23 PM, Daniel Kulp wrote: We held a vote on [EMAIL PROTECTED] to publish a new patch release of Apache CXF.This release is mostly a patch release to fix problems and issues (82 JIRA items resolved) that users have encountered in the 2.0.2-incubator release. From an IPMC review standpoint, the major changes are: 1) Upgraded to newer versions of a couple libs. No license changes or anything. 2) The NOTICE file has a new format. We upgraded to newer versions of the remote-resources stuff that allows a much more organized and easier to follow NOTICE files. The information is all the same, just clearer. For a full list of the issues, see: http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312800styleName=TextprojectId=12310511Create=Create The staging area is at: http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/ The distributions are in the dist directory. The maven 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.3- incubator/ I've also created a list of the ! files from rat and categoriezed them. This is checked into SVN along with the tag: http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.3-incubator/etc/rat.unknowns.txt The vote on cxf-dev resulting in 15 +1 votes: +1 IPMC: 2 (jim, jgenender) +1 committers: 12 (dkulp, bmargulies, wjiang, gmazza, blin, ffang, jmao, jliu, jma, ubhole, gnodet, apaibir, ddiephouse) No 0 or -1 votes. Vote thread: http://www.nabble.com/-VOTE--Release-CXF-2.0.3-incubator- tf4760901.html This vote will remain open for at least 72 hours. (probably longer due to travelling to ApacheCon, see you all there!) -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Shindig, an OpenSocial Container
+1 --kevan On Nov 9, 2007 1:03 PM, Brian McCallister [EMAIL PROTECTED] wrote: Shindig Proposal
[RESULT] [VOTE] Approve release CXF 2.0.3-incubator
We have 4 IPMC +1 votes from jstrachan, jim, jgenender, and kevan to go along with the 13 committer votes. No -1 votes or 0 votes were cast. Thus, I'm closing this vote as Passed and will start the releasing the artifacts. Thanks to everyone for taking the time to look at it! Dan On Friday 09 November 2007, Daniel Kulp wrote: We held a vote on [EMAIL PROTECTED] to publish a new patch release of Apache CXF.This release is mostly a patch release to fix problems and issues (82 JIRA items resolved) that users have encountered in the 2.0.2-incubator release. From an IPMC review standpoint, the major changes are: 1) Upgraded to newer versions of a couple libs. No license changes or anything. 2) The NOTICE file has a new format. We upgraded to newer versions of the remote-resources stuff that allows a much more organized and easier to follow NOTICE files. The information is all the same, just clearer. For a full list of the issues, see: http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312800 styleName=TextprojectId=12310511Create=Create The staging area is at: http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/ The distributions are in the dist directory. The maven 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.3-incubator / I've also created a list of the ! files from rat and categoriezed them. This is checked into SVN along with the tag: http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.3-incubator /etc/rat.unknowns.txt The vote on cxf-dev resulting in 15 +1 votes: +1 IPMC: 2 (jim, jgenender) +1 committers: 12 (dkulp, bmargulies, wjiang, gmazza, blin, ffang, jmao, jliu, jma, ubhole, gnodet, apaibir, ddiephouse) No 0 or -1 votes. Vote thread: http://www.nabble.com/-VOTE--Release-CXF-2.0.3-incubator-tf4760901.htm l This vote will remain open for at least 72 hours. (probably longer due to travelling to ApacheCon, see you all there!) -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][ANN] Qpid M2 Release
Can the IPMC members cast their vote, as we are very keen to do the release during Apache Con. We already have 3 mentor votes. Is that good enough? Regards, Rajith On Nov 12, 2007 12:33 PM, Rajith Attapattu [EMAIL PROTECTED] wrote: Folks, The Qpid PPMC is happy to notify the completion of the vote for the Qpid M2 release. We would appreciate if the incubator PMC could ratify the release. There were 12 binding votes in total, including 3 mentor votes. The following is the vote thread. http://mail-archives.apache.org/mod_mbox/incubator-qpid-dev/200711.mbox/browser Here are the details pertaining to the vote. The signed artifacts for the M2 final release is available at http://people.apache.org/~rajith/qpid-release/M2/Final/ The keys are located at, https://svn.apache.org/repos/asf/incubator/qpid/tags/M2/Final/java/KEYS All artifacts can be downloaded as a single tar file at, http://people.apache.org/~rajith/qpid-release/M2/Final/final.tar.gz The release artifacts can be built using the following tag, https://svn.apache.org/repos/asf/incubator/qpid/tags/M2/Final/ Regards, Rajith Attapattu Red Hat Blog http://mutlix.blogspot.com/ -- Rajith Attapattu Red Hat Blog http://mutlix.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][ANN] Qpid M2 Release
On Nov 13, 2007 6:17 PM, Rajith Attapattu [EMAIL PROTECTED] wrote: Can the IPMC members cast their vote, as we are very keen to do the release during Apache Con. We already have 3 mentor votes. Is that good enough? Hi Rajith, Well, here's my interpretation... According to http://incubator.apache.org/incubation/Incubation_Policy.html#Releases you must hold a vote. Convention for votes is a minimum 72 hours. So, I would say you must wait 72 hours. At the end of that time, barring any -1 votes, your vote will pass... --kevan
Re: [VOTE][ANN] Qpid M2 Release
Hi Kevan, Thanks a lot. Since we started the vote on monday noon, we can hopefully close the vote (barring any -1s) by thursday noon. Regards, Rajith On Nov 13, 2007 6:38 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Nov 13, 2007 6:17 PM, Rajith Attapattu [EMAIL PROTECTED] wrote: Can the IPMC members cast their vote, as we are very keen to do the release during Apache Con. We already have 3 mentor votes. Is that good enough? Hi Rajith, Well, here's my interpretation... According to http://incubator.apache.org/incubation/Incubation_Policy.html#Releases you must hold a vote. Convention for votes is a minimum 72 hours. So, I would say you must wait 72 hours. At the end of that time, barring any -1 votes, your vote will pass... --kevan -- Rajith Attapattu Red Hat Blog http://mutlix.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
