Re: [ANNOUNCE] Apache Phoenix 2.2.3-incubating released
Hi, I may just be missing something but I don't see any MD5 or signed files in the release area from the mirror the download page took me to. [1] they do seem to be in RC4 [2] so it may be they just not been copied over or perhaps all the mirrors haven't caught up yet? Having the README, RELEASE_NOTES and KEYS files in the dist area (outside the tar) is also helpful. Looks like the src release is missing a DISCLAIMER file. [4] Thanks, Justin 1. http://apache.mirror.uber.com.au/incubator/phoenix/phoenix-2.2.3-incubating/src/ 2. https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/src/ 3. http://phoenix.incubator.apache.org/download.html 4. http://incubator.apache.org/guides/branding.html#disclaimers - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Phoenix 2.2.3-incubating released
Hi, Looks like the src release is missing a DISCLAIMER file. [4] Ah sorry - ignore that as it already been discussed on this list. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Phoenix 2.2.3-incubating released
On 20 March 2014 01:12, Justin Mclean jus...@classsoftware.com wrote: Hi, I may just be missing something but I don't see any MD5 or signed files in the release area from the mirror the download page took me to. [1] they do seem to be in RC4 [2] so it may be they just not been copied over or perhaps all the mirrors haven't caught up yet? KEYS, hashes and sigs are explicitly excluded from synching with 3rd party mirrors. They must be downloaded from an ASF host. Having the README, RELEASE_NOTES and KEYS files in the dist area (outside the tar) is also helpful. Looks like the src release is missing a DISCLAIMER file. [4] Thanks, Justin 1. http://apache.mirror.uber.com.au/incubator/phoenix/phoenix-2.2.3-incubating/src/ 2. https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/src/ 3. http://phoenix.incubator.apache.org/download.html 4. http://incubator.apache.org/guides/branding.html#disclaimers - 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: [RESULT][VOTE] Graduation of Apache Olingo from the Incubator
Dear all, Maybe you have received Apache board meeting report already. Apache Olingo now a TLP :-) Thank you all for the great support from Apaches incubator. That Olingo is now a TLP is also your result. Olingo has learned a lot from incubation and is now happy to continue on the Apache Way as TLP Greetings, Stephan (VP Apache Olingo) On 17.03.14 10:27, Florian Müller f...@apache.org wrote: Hi all, The vote has passed with three binding +1 votes, no +0, and no -1 votes. +1 votes: * Dave Fisher * Alan Cabrera * Florian Müller I will ask the board to add the resolution to the agenda of the next board meeting. Thanks! Florian Hi all, The Apache Olingo community has VOTEd to graduate from the incubator [1][2]. Apache Olingo entered the Incubator in July 2013, has done two releases, has added new contributors, received code contributions, and has an active community. Please find the proposed board resolution below. Please VOTE below on the graduation of Apache Olingo from the Incubator. The graduation resolution is pasted below. I'll leave the VOTE open for at least 72 hours: [ ] +1 Graduate Apache Olingo podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Olingo podling [ ] -1 Reject graduation of Apache Olingo podling from Apache Incubator because ... My vote is +1 (binding). Thanks, Florian [1] http://s.apache.org/olingo-graduation-vote [2] http://s.apache.org/olingo-graduation-vote-result Resolution: Establish the Apache Olingo 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, for distribution at no charge to the public, related to providing an implemention of the OASIS OData (Open Data Protocol) specifications, in server and client form. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Olingo Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Olingo Project be and hereby is responsible for the creation and maintenance of software related to providing an implemention of the OASIS OData (Open Data Protocol) specifications, in server and client form; and be it further RESOLVED, that the office of Vice President, Olingo 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 Olingo Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Olingo 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 Olingo Project: * Florian Mueller f...@apache.org * Dave Fisher w...@apache.org * Christian Amend chri...@apache.org * Francesco Chicchiriccòilgro...@apache.org * Jens Huesken jhues...@apache.org * Michael Bolz m...@apache.org * Stephan Klevenz sklev...@apache.org * Tamara Boehm tbo...@apache.org * Challen Hechall...@apache.org * Chandan V A chanda...@apache.com * Eduard Koller edua...@apache.com NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Klevenz be appointed to the office of Vice President, Olingo, 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 initial Apache Olingo PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Olingo Project; and be it further RESOLVED, that the Apache Olingo Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Olingo podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Olingo 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: Finding a Champion
Thanks to everyone for the encouraging comments. I will report back to OpenAz and begin drafting a proposal. I suspect we will want Paul to act as our Champion, since WSO2 is already active in the project. I think the group will be glad to have Emmanuel and Colm help us as Mentors. Hal -Original Message- From: Colm O hEigeartaigh [mailto:cohei...@apache.org] Sent: Wednesday, March 19, 2014 5:03 AM To: general@incubator.apache.org Subject: Re: Finding a Champion I'm also willing to help out (as a mentor). Apache CXF has a PEP that uses a interface to convert a service request to a XACML request, and ships with an implementation that uses OpenSAML to create the request. I was planning to dedicate some time to switching to use OpenAZ instead. Colm. On Wed, Mar 19, 2014 at 3:00 AM, Paul Fremantle pzf...@gmail.com wrote: I'm also willing to champion this. Paul On Tue, Mar 18, 2014 at 9:57 PM, Emmanuel Lécharny elecha...@gmail.com wrote: Le 3/18/14 7:47 PM, Rich Bowen a écrit : On 03/18/2014 02:40 PM, Hal Lockhart wrote: I am a newbie here. I am involved in an open source project called OpenAz. It is focus is to provide tools and components for developing authorization and access control systems. Our web page (and wiki) is here: http://www.openliberty.org/wiki/index.php/OpenAz_Main_Page We are using SourceForge for the code. We use the Apache license throughout. The project was started in 2009 and was very small initially. More recently we have been gaining more momentum and participants. We intend to propose to become an Incubator project. I have looked at the documents and lists and I believe I understand how to write the first draft of a Proposal. However, how does one go about recruiting a Champion. Does it make sense to draft a proposal and then try to attract a Champion to it or is there a better way to proceed? This email was a good start. Also, finding an existing Apache member who's either active in your community, or is a user of your stuff, would be a good thing to investigate. I see from your website that WSO2 is somehow involved. There's several ASF members there. Failing that, tell us why your project is awesome and why we'd want to be involved. If you don't find a more suitable champion, I'd be please to offer my support. There is defintively a need for some XACML related project at the ASF. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com --- - - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Paul Fremantle Co-Founder and CTO, WSO2 Member of the Apache Software Foundation OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org twitter: @pzfreo -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Marking retired podlings in SVN
On Tue, 18 Mar 2014, at 07:09 AM, sebb wrote: Just wondering whether it might be useful to add a RETIRED marker file to the top-level SVN directory of podlings that have retired? Good idea. Add that as another step to: http://incubator.apache.org/guides/retirement.html Ideally it would be the last thing done to SVN. In that way the last log message seen via 'viewvc' web interface also makes it clear. It could just be an empty file, or it could contain a link to the retired summary status, for example: http://incubator.apache.org/projects/index.html#agila The link would be good. I'm happy to make a start on that if it's thought useful. Yes, i think so. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Marking retired podlings in SVN
On 21 March 2014 00:03, David Crossley cross...@apache.org wrote: On Tue, 18 Mar 2014, at 07:09 AM, sebb wrote: Just wondering whether it might be useful to add a RETIRED marker file to the top-level SVN directory of podlings that have retired? Good idea. Add that as another step to: http://incubator.apache.org/guides/retirement.html Done. Ideally it would be the last thing done to SVN. In that way the last log message seen via 'viewvc' web interface also makes it clear. Yes, just _before_ marking the SVN tree read-only! It could just be an empty file, or it could contain a link to the retired summary status, for example: http://incubator.apache.org/projects/index.html#agila The link would be good. I'm happy to make a start on that if it's thought useful. Yes, i think so. -David - 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
