Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
+1 I think things look really good. Well done, after such a long time. Cheers On Sun, Jul 7, 2013 at 12:33 AM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi all, The Apache JSPWiki podling is a project which holds a feature-rich and extensible WikiWiki engine, built around the standard Java EE components Java, Servlets, and Java Server Pages. We've been incubating for a very long time (almost 6 years); we feel we are ready for graduation. Since Jan 2012, we've shipped 2 releases, added 1 committer, adhered to the Apache Way in deciding technical and non-technical issues and revamped our website. We've already done an internal VOTE on the proposal which passed with a big majority [#1], and we consider the podling namesearch task as completed [#2]. Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board. [+1] yes, go forward [+0] don't care [-1] nope, because [blocker_reason] The VOTE is open for at least 72h thanks br, juan pablo [#1] http://s.apache.org/654 (an additional vote was received off-list, cfr. with http://s.apache.org/tC7) [#2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 - Proposed Board Resolution Report X. Establish the Apache JSPWiki Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache JSPWiki Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is responsible for the creation and maintenance of software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages; and be it further RESOLVED, that the office of Vice President, Apache JSPWiki be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache JSPWiki Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache JSPWiki Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache JSPWiki Project: * Murray Altheim alth...@apache.org * Dirk Frederickx brus...@apache.org * Florian Holeczekflori...@apache.org * Andrew Jaquith ajaqu...@apache.org * Glen Mazza gma...@apache.org * Harry Metske mets...@apache.org * Craig L Russell c...@apache.org * Juan Pablo Santos juanpa...@apache.org * Christoph Sauer csa...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Juan Pablo Santos be appointed to the office of Vice President, Apache JSPWiki, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is tasked with the migration and rationalization of the Apache Incubator JSPWiki podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator JSPWiki podling encumbered upon the Apache Incubator Project are hereafter discharged. -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
+1 ...ant On Sat, Jul 6, 2013 at 11:33 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi all, The Apache JSPWiki podling is a project which holds a feature-rich and extensible WikiWiki engine, built around the standard Java EE components Java, Servlets, and Java Server Pages. We've been incubating for a very long time (almost 6 years); we feel we are ready for graduation. Since Jan 2012, we've shipped 2 releases, added 1 committer, adhered to the Apache Way in deciding technical and non-technical issues and revamped our website. We've already done an internal VOTE on the proposal which passed with a big majority [#1], and we consider the podling namesearch task as completed [#2]. Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board. [+1] yes, go forward [+0] don't care [-1] nope, because [blocker_reason] The VOTE is open for at least 72h thanks br, juan pablo [#1] http://s.apache.org/654 (an additional vote was received off-list, cfr. with http://s.apache.org/tC7) [#2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 - Proposed Board Resolution Report X. Establish the Apache JSPWiki Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache JSPWiki Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is responsible for the creation and maintenance of software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages; and be it further RESOLVED, that the office of Vice President, Apache JSPWiki be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache JSPWiki Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache JSPWiki Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache JSPWiki Project: * Murray Altheim alth...@apache.org * Dirk Frederickx brus...@apache.org * Florian Holeczekflori...@apache.org * Andrew Jaquith ajaqu...@apache.org * Glen Mazza gma...@apache.org * Harry Metske mets...@apache.org * Craig L Russell c...@apache.org * Juan Pablo Santos juanpa...@apache.org * Christoph Sauer csa...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Juan Pablo Santos be appointed to the office of Vice President, Apache JSPWiki, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is tasked with the migration and rationalization of the Apache Incubator JSPWiki podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator JSPWiki podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
+1 binding Regards, Alan On Jul 6, 2013, at 3:33 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi all, The Apache JSPWiki podling is a project which holds a feature-rich and extensible WikiWiki engine, built around the standard Java EE components Java, Servlets, and Java Server Pages. We've been incubating for a very long time (almost 6 years); we feel we are ready for graduation. Since Jan 2012, we've shipped 2 releases, added 1 committer, adhered to the Apache Way in deciding technical and non-technical issues and revamped our website. We've already done an internal VOTE on the proposal which passed with a big majority [#1], and we consider the podling namesearch task as completed [#2]. Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board. [+1] yes, go forward [+0] don't care [-1] nope, because [blocker_reason] The VOTE is open for at least 72h thanks br, juan pablo [#1] http://s.apache.org/654 (an additional vote was received off-list, cfr. with http://s.apache.org/tC7) [#2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 - Proposed Board Resolution Report X. Establish the Apache JSPWiki Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache JSPWiki Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is responsible for the creation and maintenance of software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages; and be it further RESOLVED, that the office of Vice President, Apache JSPWiki be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache JSPWiki Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache JSPWiki Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache JSPWiki Project: * Murray Altheim alth...@apache.org * Dirk Frederickx brus...@apache.org * Florian Holeczekflori...@apache.org * Andrew Jaquith ajaqu...@apache.org * Glen Mazza gma...@apache.org * Harry Metske mets...@apache.org * Craig L Russell c...@apache.org * Juan Pablo Santos juanpa...@apache.org * Christoph Sauer csa...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Juan Pablo Santos be appointed to the office of Vice President, Apache JSPWiki, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is tasked with the migration and rationalization of the Apache Incubator JSPWiki podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator JSPWiki podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
+1 (binding) - well done. A long and winding road to graduation. Regards, Dave On Jul 7, 2013, at 8:30 AM, Alan D. Cabrera wrote: +1 binding Regards, Alan On Jul 6, 2013, at 3:33 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi all, The Apache JSPWiki podling is a project which holds a feature-rich and extensible WikiWiki engine, built around the standard Java EE components Java, Servlets, and Java Server Pages. We've been incubating for a very long time (almost 6 years); we feel we are ready for graduation. Since Jan 2012, we've shipped 2 releases, added 1 committer, adhered to the Apache Way in deciding technical and non-technical issues and revamped our website. We've already done an internal VOTE on the proposal which passed with a big majority [#1], and we consider the podling namesearch task as completed [#2]. Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board. [+1] yes, go forward [+0] don't care [-1] nope, because [blocker_reason] The VOTE is open for at least 72h thanks br, juan pablo [#1] http://s.apache.org/654 (an additional vote was received off-list, cfr. with http://s.apache.org/tC7) [#2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 - Proposed Board Resolution Report X. Establish the Apache JSPWiki Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache JSPWiki Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is responsible for the creation and maintenance of software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages; and be it further RESOLVED, that the office of Vice President, Apache JSPWiki be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache JSPWiki Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache JSPWiki Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache JSPWiki Project: * Murray Altheim alth...@apache.org * Dirk Frederickx brus...@apache.org * Florian Holeczekflori...@apache.org * Andrew Jaquith ajaqu...@apache.org * Glen Mazza gma...@apache.org * Harry Metske mets...@apache.org * Craig L Russell c...@apache.org * Juan Pablo Santos juanpa...@apache.org * Christoph Sauer csa...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Juan Pablo Santos be appointed to the office of Vice President, Apache JSPWiki, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is tasked with the migration and rationalization of the Apache Incubator JSPWiki podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator JSPWiki podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OData Proposal for Incubator
Dear all, This is a very good initiative. We use OData in our integration projects as the standard protocol. Based on our experiences with OData as a standard and its exiting ecosystem, I have a few suggestions, 1. Please start by supporting OData v3 (not v2). v2 is relatively old, lacks some key features that are present in v3. Also, the ACCEPT header semantics for JSON format is compatible between v3 and v4 (the current in progress version) but not v2. This is critical from a consumer point of view. Another reason to start with v3 is that it is the version that was submitted to OASIS for standardizing which will come out very soon as v4. 2. Please evaluate odata4j which is designed very well despite some bugs and deficiencies. This allows this apache project to take the best of ideas from 2 of the available implementations of odata on java. Thanks Regards, Anny G -- View this message in context: http://apache-incubator-general.996316.n3.nabble.com/PROPOSAL-OData-Proposal-for-Incubator-tp35801p36019.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Olingo proposal as an incubating project
HI Alan, If you are on then I am +1. Thanks, Dave On Jul 7, 2013, at 10:06 AM, Alan D. Cabrera wrote: I can help here. Regards, Alan On Jul 7, 2013, at 9:59 AM, Dave Fisher dave2w...@comcast.net wrote: While excited by this technology and project, I have to be -1. Why? A project should start with at least 3 mentors. AFAIK I am the only Mentor other than Florian. If someone volunteers, my -1 will become a +1, instantly. Regards, Dave On Jul 1, 2013, at 3:38 AM, Florian Müller wrote: Hi all, I'd like to call a VOTE for acceptance of Olingo into the Apache incubator. The proposal is pasted at the bottom on this email. The corresponding wiki page is: http://wiki.apache.org/incubator/OlingoProposal [ ] +1 Accept Olingo into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Olingo into the incubator because... +1 from me (binding) I'll close the VOTE next Sunday. Thanks, Florian = Apache Olingo Proposal = === Abstract === Apache Olingo is a generic Java language implementation of the OData 2.0 specification which will serve as a code base for the upcoming OASIS OData specification. === Proposal === The Open Data Protocol (OData) [1] is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The Apache Olingo is a library which enables developers to implement OData producers and OData consumers. Basic principles of the library are to provide an OData 2.0 specification compliant OData Library, enhancements shall be possible in a compatible manner, have a clear separation between Core and API, to provide an option to build extensions on top. This library should be base for implementing future releases of the specification. === Background === OData was originally developed by Microsoft and is released in a version 2.0 under an Open Specification Promise [2]. A lot of companies did show interests in this protocol, used it in products and gave feedback back to Microsoft. This joined effort resulted in a new release OData 3.0 in 2012, this version became the basis for the OASIS technical committee [3] which is currently working on a new version of the specification. This OASIS standard release is expected this year. The initial Java code of this project was developed by a development team that had already experience with other OData 2.0 and 3.0 implementations at SAP AG. The current code base implements OData 2.0 and because of this version is widely used it is a good starting point to build an open source community for the OData standard. The current code also comes up with an implementation of an OData sample service. On the one side this is an example for users which want to use the library to expose their own data and on the other side it illustrates how implemented features work. Additionally, the code base includes an extension which is called JPA processor. With this extension it is easy to expose any JPA persistence model via OData protocol without a lot of coding. === Rationale === More software vendors moving to OData means more choice for customers who will be able to use different implementations. For the standard to succeed, however, ensuring interoperability is paramount: in order to manage an ever growing context and leverage the enormous portability and interoperability issues that a globally adopted standard brings, it is necessary to think about how to make the related ecosystem healthy and sustainable. Successful modern standards are driven by: Clear documentation, built iteratively with continuous feedback from stakeholders A clearly defined compatibility process, enforced by tools that allow to gauge how implementations can be compatible and interoperable Accurate compliance criteria, documented in writing as well as in actual testing code that measure how tools and libraries are able to interoperate A sample implementation to clear up potential doubts and ensure that the standard can actually be implemented in real life scenarios The above mentioned pieces are able to make the development activity, towards an OData implementation, easier and more successful. Having an healthy ecosystem will ensure a smoother implementation process, more compliant products, and ultimately, a wider adoption of the standard. The OData ecosystem has been successful in creating and documenting early versions of the standard, yet it might potentially lack two very important aspects, that is a exhaustive implementation of the complete protocol that can be used productively and to ensure interoperability. As much as such
[REPORT] Re: Shepherd assignments July 2013
On Jul 2, 2013, at 7:23 AM, Marvin Humphrey wrote: Greets, Here are shepherd assignments for the July 2013 report: SHEPHERD PODLING -- Alan Cabrera jclouds Alan Cabrera Open Climate Workbench Alan Cabrera ODF Toolkit Dave FisherJSPWiki Ready to graduate. A VOTE is in progress on general@. Still needs to file July board report. Dave FisherStratos Still getting started. Very active lists. I noted a slight impatience with Infrastructure. Is it worth establishing a timeline or SLA with Infra to keep podling expectations aligned to reality? Regards, Dave Matt Franklin Falcon Matt Franklin Tashi Matt Franklin VXQuery Ross Gardler DeviceMap Ross Gardler Marmotta Ross Gardler Ripple Matt Hogstrom Mesos Matt Hogstrom Provisionr Matt Hogstrom Spark Benson Marguilies Chukwa Benson Marguilies Kafka Benson Marguilies MetaModel Suresh Marru Celix Suresh Marru Helix Suresh Marru MRQL Roman Shaposhnik Knox Roman Shaposhnik Tajo Roman Shaposhnik Tez Matt Franklin: I interpreted (Happy to take any podling) as willing to handle any podlings (plural) and assigned you three. All: Please speak up if there are any issues. Thanks as always, shepherds. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Is an android framework good candidate for Apache Incubation?Hello there, Is an android framework good candidate for Apache Incubation? I have been working on an Android framework(library, service and
Hello there, Is an android framework good candidate for Apache Incubation? I have been working on an Android framework(library, service and app) for connecting android devices (phones and tablets) in a peer-to-peer fashion and enabling communications among them. Some use cases are media sharing and multi-player games. Devices can be connected over WiFi, WiFi Direct or mobile hotspot; and the connecting process can be initiated through multicast, NFC tap or using camera scanning QR code. The design doc can be found here: http://www.peerdevicenet.net/arch.html The source code can be found here: https://github.com/yigongliu/PeerDeviceNet_Src Some API user guide can be found here: http://www.peerdevicenet.net/api.html Is such android framework good candidate to submit for Apache? From incubation docs, i read advisors or champions will help bootstrapping candidate projects. Is there a list of champions who we can contact to see if they are interested? Thanks Yigong - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Is an android framework good candidate for Apache Incubation?
Sorry for the repost. My last email is messed up. Is an android framework good candidate for Apache Incubation? I have been working on an Android framework(library, service and app) for connecting android devices (phones and tablets) in a peer-to-peer fashion and enable communications among them. Some use cases are media sharing and multi-player games. Devices can be connected over WiFi, WiFi Direct or mobile hotspot; and the connecting process can be initiated through multicast, NFC tap or using camera scanning QR code. The design doc can be found here: http://www.peerdevicenet.net/arch.html The source code can be found here: https://github.com/yigongliu/PeerDeviceNet_Src Some API user guide can be found here: http://www.peerdevicenet.net/api.html Is such android framework good candidate to submit for Apache? From incubation docs, i read advisors or champions will help bootstrapping candidate projects. Is there a list of champions who we can contact to see if they are interested? Thanks Yigong - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
