Re: Finding a Champion
Emmanuel Lécharny wrote [...] If you don't find a more suitable champion, I'd be please to offer my support. There is definitively a need for some XACML related project at the ASF. I agree with Emmanuel: I don't have unfortunately enough spare cycles for more involvement in this proposal, but I'd say that any IAM project at the ASF (including Directory, Syncope and Shiro) would potentially benefit from this. Regards. - -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PPMC http://people.apache.org/~ilgrosso/ -- View this message in context: http://apache-incubator-general.996316.n3.nabble.com/Finding-a-Champion-tp38668p38672.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: 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
Re: Process question on release votes
what has been with the rule that an ipmc must forward the VOTE to the incubator pmc when it gets started, and those members can also cast a binding -1 ? LieGrue, strub On Tuesday, 18 March 2014, 4:10, David Nalley da...@gnsa.us wrote: On Mon, Mar 17, 2014 at 1:10 PM, John D. Ament john.d.am...@gmail.com wrote: Hi all, While not specifically incubator related, was wondering if someone at the incubator may provide me some insight. Right now, release votes cannot be veto'd. This seems like an oversight IMHO. If a release candidate is visibly wrong (e.g. bad licenses, or something else), surely the release candidate can be veto'd no? This is correct - release votes are not veto-able. In my opinion if you have a PMC whose members choose to ignore an obviously problematic release, especially from a licensing standpoint, then you have much bigger problems with the project. In my experience two factors come into play: 1. The release manager, even with a vote that technically passes, will not proceed with a vote where there are obvious major problems, especially from a legal perspective. They cancel the vote on their own accord. No one wants a majorly flawed release shipping. 2. Other PMC members heap on -1 votes if it remains open for any length of time, effectively causing the vote to fail to pass. If you can't get agreement on the obviously wrong candidate, perhaps it's not as obvious why its wrong. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Process question on release votes
On 19 March 2014 15:05, Mark Struberg strub...@yahoo.de wrote: what has been with the rule that an ipmc must forward the VOTE to the incubator pmc when it gets started, and those members can also cast a binding -1 ? IPMC votes are the only ones that are binding. However, even a binding -1 vote is not a veto - it is just a negative vote. But IMO it would be foolish for an RM to ignore a -1 vote. In PMCs that have been established some time, IME the expectation is that the RM will cancel the vote if the -1 appears to be justified. This means that PMC members who have already voted probably won't revote as a -1 even if they agree with the -1 (perhaps they overlooked that issue - not everyone can check every aspect of a release). If there is some doubt as to whether the -1 should really block the release, IMO the RM should follow up to explain why they think it is not a blocker. So either way, the -1 is resolved before the release proceeds. LieGrue, strub On Tuesday, 18 March 2014, 4:10, David Nalley da...@gnsa.us wrote: On Mon, Mar 17, 2014 at 1:10 PM, John D. Ament john.d.am...@gmail.com wrote: Hi all, While not specifically incubator related, was wondering if someone at the incubator may provide me some insight. Right now, release votes cannot be veto'd. This seems like an oversight IMHO. If a release candidate is visibly wrong (e.g. bad licenses, or something else), surely the release candidate can be veto'd no? This is correct - release votes are not veto-able. In my opinion if you have a PMC whose members choose to ignore an obviously problematic release, especially from a licensing standpoint, then you have much bigger problems with the project. In my experience two factors come into play: 1. The release manager, even with a vote that technically passes, will not proceed with a vote where there are obvious major problems, especially from a legal perspective. They cancel the vote on their own accord. No one wants a majorly flawed release shipping. 2. Other PMC members heap on -1 votes if it remains open for any length of time, effectively causing the vote to fail to pass. If you can't get agreement on the obviously wrong candidate, perhaps it's not as obvious why its wrong. --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
[ANNOUNCE] Apache Phoenix 2.2.3-incubating released
Hello, The Apache Phoenix team is pleased to announce the release of version 2.2.3-incubating from the Apache Incubator. Phoenix is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. The source and binaries for the release may be downloaded here: http://phoenix.incubator.apache.org/download.html Link to release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325748styleName=TextprojectId=12315120Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7Ca7a6d3045efbe3f42c7483fd29510c92a7227195%7Clout For general information on Apache Phoenix, please visit the project website: http://phoenix.incubator.apache.org/index.html Disclaimer: Apache Phoenix is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. Regards, The Apache Phoenix team
FWD:
Hey! http://ceciliafatta.com.ar/-redirect?lekozynjlyru15178219 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
