Updating HTrace podling page with retirement status
Hi all, Unless I'm missing something, the HTrace podling page ( http://htrace.incubator.apache.org/) has no indication that the project has been retired (http://incubator.apache.org/projects/htrace.html). The website should be updated to make the status clear. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Gobblin to enter Apache Incubator
+1 (binding) Colm. On Fri, Feb 17, 2017 at 7:43 AM, Ross Gardler <r...@gardler.org> wrote: > +1 (binding) > > Not signing up to mentor, but I will be watching and hopefully helping > from the sidelines. > > -Original Message- > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Sent: Thursday, February 16, 2017 11:27 PM > To: general@incubator.apache.org > Subject: Re: [VOTE] Gobblin to enter Apache Incubator > > +1 (binding) > > Happy to be mentor on it ! > > Regards > JB > > On 02/17/2017 06:33 AM, Olivier Lamy wrote: > > Hello Everyone, > > I would like to call a vote for accepting "Gobblin" for incubation in > > the Apache Incubator. > > The full proposal is available below, and is also available in the wiki: > > https://wiki.apache.org/incubator/GobblinProposal > > > > Please cast your vote: > > > > [ ] +1, bring Gobblin into Incubator > > [ ] +0, I don't care either way, > > [ ] -1, do not bring Gobblin into Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding. > > > > I start with my vote: > > +1 (binding) > > > > Cheers > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > - > 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 > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Release Apache Ranger 0.6.3 (incubating) - rc1
I've raised a JIRA so that these concerns will get fixed: https://issues.apache.org/jira/browse/RANGER-1326 Colm. On Sat, Jan 21, 2017 at 4:37 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > I'll point out that Ranger has graduated to a TLP, so the IPMC's votes > are > > non-binding (unless you're on the Ranger PMC as well) > > I was wondering why they put something up to vote just before becoming a > TLP. > > So I guess they should cancel that vote here? > > They probably should still look into those issue particularly are they > have been outstanding for several releases, but up to them I guess. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] OpenAZ retirement
+1 to retire. Colm. On Wed, Aug 17, 2016 at 12:59 PM, John D. Ament <johndam...@apache.org> wrote: > Copying mine from the dev list. +1 > > On Aug 13, 2016 02:29, "Emmanuel Lécharny" <elecha...@gmail.com> wrote: > > > Hi ! > > > > > > Despite an effort to reboot the project in april, we weren't successful > > in keeping the existing committers active. At this point, a decision to > > retire the podling was taken, and a vote was don eon the PPMC : > > https://lists.apache.org/thread.html/e87c384315966c81c523fad94326d8 > > c72e312b3025d2e7b86b50e377@%3Cdev.openaz.apache.org%3E > > > > > > Per http://incubator.apache.org/guides/retirement.html, I'm starting a > > vote on the incubator mailing list. > > > > > > [ ] +1 : retire OpenAZ > > > > [ ] +/-0 : No opinion > > > > [ ] -1 : Don't retire OpenAZ. > > > > > > Thanks ! > > > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Release Apache Ranger 0.5.3 (incubating)
Hi Alan/Justin, Just so that we get it right the next time, can you verify that the current NOTICE is acceptable or does it require further changes? https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=blob;f=NOTICE.txt;h=3130ce2dd60bd148aa74e13610a218704dc3e1a7;hb=refs/heads/ranger-0.5 I'll look into the licensing changes. Colm. On Thu, May 12, 2016 at 7:49 PM, Alan Gates <alanfga...@gmail.com> wrote: > -1 for now. Justin has brought up some issues with the LICENSE and NOTICE > files that have note been addressed. Specifically: > > > - LICENSE is still missing a few things (same issues as previous release) > - NOTICE year is wrong and contains far too much text. There is not need > to mention any permissive MIT licenses here. > > > The copyright year was fixed in the NOTICE file. LICENSE has not been > changed and the MIT license has not been removed from NOTICE. > > You should either make these changes or make an argument for why they are > not necessary. “We’ll do them next time” is not a good answer as that was > said in the 0.5.2 release. > > Alan. > > > On May 7, 2016, at 08:09, Velmurugan Periasamy <v...@apache.org> wrote: > > > > Incubator PMC: > > > > The Apache Ranger community has voted on and approved a proposal to > release Apache Ranger 0.5.3 (incubating) after addressing comments raised > in IPMC review for ranger-0.5.3-rc1 vote. > > > > The ranger-0.5.3-rc2 release candidate is now available with the > following artifacts up for a project vote : > > > > Git tag for the release: > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=log;h=refs/tags/ranger-0.5.3-rc2 > > > > Source release: > > > https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz > > > > Source release verification: > > PGP signature: > https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz.asc > > MD5/SHA Hash: > https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating/apache-ranger-incubating-0.5.3.tar.gz.mds > > Keys to verify the signature of the release artifact are available at: > https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS > > > > Release Notes: > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62694969 > > > > Build verification steps can be found at: > http://ranger.incubator.apache.org/quick_start_guide.html > > > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here is my +1 (non binding) > > > > Thanks, > > Vel > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Adding a podling committer
Thanks for the quick reply. Colm. On Fri, Apr 22, 2016 at 9:42 AM, Daniel Gruno <humbed...@apache.org> wrote: > depends on whether it's git or svn. > for git, if you're in the incubator ldap group, all is well. > if not, get someone from the IPMC to add you. > > for svn, you'll need to add the user to the svn auth file in the > infrastructure-puppet repository. > > With regards, > Daniel. > > On 04/22/2016 10:36 AM, Colm O hEigeartaigh wrote: > > Hi all, > > > > How should a PMC add a podling committer? The Incubator documentation > > points to: > > > > http://incubator.apache.org/guides/ppmc.html > > > > which in turn refers to: > > > > http://www.apache.org/dev/pmc.html#SVNaccess > > > > However this is out of date, the ASF Authorization template does not > exist > > in SVN any more: > > > > > https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template > > > > I've queried the infrastructure list about the docs being out of date but > > have got no response. > > > > Colm. > > > > > > > ----- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Adding a podling committer
Hi all, How should a PMC add a podling committer? The Incubator documentation points to: http://incubator.apache.org/guides/ppmc.html which in turn refers to: http://www.apache.org/dev/pmc.html#SVNaccess However this is out of date, the ASF Authorization template does not exist in SVN any more: https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template I've queried the infrastructure list about the docs being out of date but have got no response. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Graduate Sentry
>* Tuong Truong <tuongtru...@apache.org> > > > >* Vamsee Yarlagadda <vam...@apache.org> > > > >* Xiaomeng Huang <xi...@apache.org> > > > >* Xuefu Zhang <xu...@apache.org> > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur > > be appointed to the office of Vice President, Apache Sentry, 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 Sentry 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 Sentry Project; and be it further > > > > RESOLVED, that the Apache Sentry Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator Sentry podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator Sentry podling encumbered upon the Apache Incubator > > Project are hereafter discharged. > > > > == > > > > > > Regards, > > Sravya Tirukkovalur > > > > - > > 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 > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Accept Milagro into the Incubator
nd Japan. Prospective developers (whose companies are >> interested in Milagro) are located in other countries, and we anticipate >> a global community. >> >> === Reliance on Salaried Developers === >> Most of the initial committers are salaried developers from the core >> corporate teams. Github activity, including 29 forks of the Miracl >> library, indicates wider community interest, and it is hoped that the >> developer community will grow substantially at Apache. >> >> === Apache Brand === >> The Apache brand is of course seen as an advantage. However, the >> project is more directly concerned with the Apache platform and >> environment to unite diverse teams. >> >> == Relationships with Other Apache Products == >> See Alignment above. >> >> == Documentation == >> Milagro derives from Certivox's existing M-Pin, MIRACL and associated >> tools at github.com/Certivox/ Documentation at http://docs.certivox.com/ >> may also inform and feed into the Milagro project. >> >> == Initial Source and Intellectual Property == >> As soon as Milagro is accepted into the Incubator, Certivox (now MIRACL) >> will transfer the source code and trademark to the ASF with a Software >> Grant, and licensed under the Apache License 2.0. Certivox/MIRACL >> retains rights to its existing MIRACL mark. >> >> == External Dependencies == >> There are no external dependencies and all software is under the sole >> ownership of Certivox/MIRACL. >> >> == Cryptography == >> This is advanced cryptographic software, and as such may be subject to >> government interest and red tape in some countries. However, the >> architecture by which SD-DSM / Crypto Apps are distributed, via open >> source freely available code repositories, is intentional to exploit the >> near universal interpretation of the Wassenar agreement to permit export >> of open source cryptography without restriction (in most cases). >> >> == Required Resources == >> Mailinglists: >> >> * private >> * dev >> * users >> >> Git repository (to mirror existing github repo) >> >> * https://git-wip-us.apache.org/repos/asf/incubator-milagro.git >> >> Issue Tracking >> >> * JIRA repository to be requested >> >> Trust Authority Service >> The podling would like to request a VM at >> "ta.milagro[.incubator].apache.org" with which to run a Community Trust >> Authority. It is anticipated that this will serve as a test facility >> for developers and may become a Trust Authority for the community of ASF >> committers. >> >> == Initial Committers == >> * Akira Nagai (NTT) >> * Brian Spector (Certivox/MIRACL) >> * Fuji Hitoshi(NTT) >> * Genoveffa Pagano(Certivox/MIRACL) >> * Go Yamamoto (NTT) >> * Jordan Katserov (Certivox/MIRACL) >> * Kealan Mccusker (Certivox/MIRACL) >> * Kenji Takahishi (NTT) >> * Michael Scott (Certivox/MIRACL) >> * Milen Rangelove (Certivox/MIRACL) >> * Mitko Yugovski (Certivox/MIRACL) >> * Michael Scott (Certivox/MIRACL) >> * Nick Kew(Apache) >> * Nick Pateman(Certivox/MIRACL) >> * Patrick Hilt(Certivox/MIRACL) >> * Simeon Aladhem (Certivox/MIRACL) >> * Stanislav Mihaylov (Certivox/MIRACL) >> * Tetsutaro Kobayashi (NTT) >> >> == Sponsors == >> === Champion === >> . Nick Kew >> >> === Mentors === >> * Sterling Hughes >> * Jan Willem Janssen >> * Nick Kew >> >> === Sponsoring Entity === >> . The Apache Incubator >> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE][Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
://wiki.apache.org/incubator/TinkerPop will use subversion for it’s website and requests: * https://svn.apache.org/repos/asf/incubator/tinkerpop Y. Git Repository TinkerPop https://wiki.apache.org/incubator/TinkerPop wishes to have the following created: * https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git And to have all of these mirrored to Github with integration taken care of. Z. Issue Tracking Please help us setup a JIRA instance for both issue tracking and code review (TINKERPOP). AA. Initial Committers and Affiliations Marko A. Rodriguez (2009) Aurelius Stephen Mallette (2011) Nidomics James Thornton (2013) Electric Speed BB. Sponsors * Champion: David Nalley * Mentors: Rich Bowen, Matt Franklin, Daniel Gruno, David Nalley, Hadrian Zbarcea * Sponsoring Entity: We request the Incubator to sponsor this project. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] [PROPOSAL] Accept OpenAz (Access Control Tools) into the Apache Incubator
+1. Colm. On Tue, Jan 6, 2015 at 3:27 AM, Hadrian Zbarcea hzbar...@gmail.com wrote: +1. I made some cosmetic changes to the list of committers and mentors. It should be clear now. Hadrian On 01/05/2015 02:04 PM, Hal Lockhart wrote: I added a comma and the word and to the Mentors section. The Mentors are: Emmanuel Lécharny, Colm O hEigeartaigh and Hadrian Zbarcea Do you see any other formatting errors? Hal -Original Message- From: Roman Shaposhnik [mailto:ro...@shaposhnik.org] Sent: Monday, January 05, 2015 1:24 PM To: general@incubator.apache.org Subject: Re: [VOTE] [PROPOSAL] Accept OpenAz (Access Control Tools) into the Apache Incubator Hi! can you please fix the formatting issues? For example, I can't even tell the exact list of mentors you're proposing. Thanks, Roman. On Mon, Jan 5, 2015 at 10:15 AM, Hal Lockhart hal.lockh...@oracle.com wrote: I call a vote to accept OpenAz as a new Incubator project. The proposal can be found here: https://wiki.apache.org/incubator/OpenAZProposal and is included below in this email. Voting will remain open until at least January 20, 2015 23:00 ET. Hal Lockhart - - - Abstract OpenAz is a project to create tools and libraries to enable the development of Attribute-based Access Control (ABAC) Systems in a variety of languages. In general the work is at least consistent with or actually conformant to the OASIS XACML Standard. Proposal Generally the work falls into two categories: ready to use tools which implement standardized or well understood components of an ABAC system and design proposals and proof of concept code relating to less well understood or experimental aspects of the problem. Much of the work to date has revolved around defining interfaces enabling a PEP to request an access control decision from a PDP. The XACML standard defines an abstract request format in xml and protocol wire formats in xaml and json, but it does not specify programmatic interfaces in any language. The standard says that the use of XML (or JSON) is not required only the semantic equivalent. The first Interface, AzAPI is modeled closely on the XACML defined interface, expressed in Java. One of the goals was to support calls to both a PDP local to the same process and a PDP in a remote server. AzAPI includes the interface, reference code to handle things like the many supported datatypes in XACML and glue code to mate it to the open source Sun XACML implementation. Because of the dependence on Sun XACML (which is XACML 2.0) the interface was missing some XACML 3.0 features. More recently this was corrected and WSo2 has mated it to their XACML 3.0 PDP. Some work was done by the JPMC team to support calling a remote PDP. WSo2 is also pursuing this capability. A second, higher level interface, PEPAPI was also defined. PEPAPI is more intended for application developers with little knowledge of XACML. It allows Java objects which contain attribute information to be passed in. Conversion methods, called mappers extract information from the objects and present it in the format expected by XACML. Some implementers have chosen to implement PEPAPI directly against their PDP, omitting the use of AzAPI. Naomaru Itoi defined a C++ interface which closely matches the Java one. Examples of more speculative work include: proposals for registration and dispatch of Obligation and Advice handlers, a scheme called AMF to tell PIPs how to retrieve attributes and PIP code to implement it, discussion of PoC code to demonstrate the use of XACML policies to drive OAuth interations and a proposal to use XACML policies to express OAuth scope. ATT has recently contributed their extensive XACML framework to the project. The ATT framework represents the entire XACML 3.0 object set as a collection of Java interfaces and standard implementations of those interfaces. The ATT PDP engine is built on top of this framework and represents a complete implementation of a XACML 3.0 PDP, including all of the multi-decision profiles. In addition, the framework also contains an implementation of the OASIS XACML 3.0 RESTful API v1.0 and XACML JSON Profile v1.0 WD 14. The PEP API includes annotation functionality, allowing application developers to simply annotate a Java class to provide attributes for a request. The annotation support removes the need for application developers to learn much of the API. The ATT framework also includes interfaces and implementations to standardize development of PIP engines that are used by the ATT PDP implementation, and can be used by other implementations built on top of the ATT framework. The framework also includes interfaces and implementations for a PAP distributed cloud infrastructure of PDP nodes that includes support for policy distribution and pip
Re: [PROPOSAL] OpenAZ as new Incubator project
It will be cool to see a XACML project at Apache, especially one that looks certain to be the main open source implementation. One minor correction: Colm MacCárthaigh You have the wrong Apache Colm there :-) Colm (O hEigeartaigh) On Fri, Nov 14, 2014 at 1:55 PM, Hal Lockhart hal.lockh...@oracle.com wrote: I was not questioning whether to initiate discussion. That was what I was trying to do. I was asking how to go about it. Thanks for the comments, they are noted. Hal -Original Message- From: John D. Ament [mailto:john.d.am...@gmail.com] Sent: Thursday, November 13, 2014 8:59 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] OpenAZ as new Incubator project I think so. There's a few things that you want to iron out first, before people start voting on this. - 3 is generally the minimum number of mentors. - I can't find a Paul Freemantle on the apache committers list. There's a Paul Fremantle, minor spelling difference. - You may want to review this section to get a better understanding of the goals: http://incubator.apache.org/guides/proposal.html#formulating the Discuss option just helps everyone look at your proposal a little bit better and determine if there's any gotchas. For example, I'm surprised to see a new incubator project using SVN. - Can you list out your issue tracking preference (should probably be JIRA unless you need something else) - Please also explicitly list the mailing lists your want. John On Thu, Nov 13, 2014 at 8:43 PM, Hal Lockhart hal.lockh...@oracle.com wrote: So you want me to repost the proposal with the Subject changed to start with [DISCUSS]? Or should I simply reference the wiki page? Hal -Original Message- From: John D. Ament [mailto:john.d.am...@gmail.com] Sent: Thursday, November 13, 2014 5:03 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] OpenAZ as new Incubator project Hal, Per customs, would you mind if we cancel this and start with a [DISCUSS] thread about OpenAZ? It's unclear if you meant this to be a vote or something. John On Thu, Nov 13, 2014 at 4:14 PM, Hal Lockhart hal.lockh...@oracle.com wrote: Abstract OpenAz is a project to create tools and libraries to enable the development of Attribute-based Access Control (ABAC) Systems in a variety of languages. In general the work is at least consistent with or actually conformant to the OASIS XACML Standard. Proposal Generally the work falls into two categories: ready to use tools which implement standardized or well understood components of an ABAC system and design proposals and proof of concept code relating to less well understood or experimental aspects of the problem. Much of the work to date has revolved around defining interfaces enabling a PEP to request an access control decision from a PDP. The XACML standard defines an abstract request format in xml and protocol wire formats in xaml and json, but it does not specify programmatic interfaces in any language. The standard says that the use of XML (or JSON) is not required only the semantics equivalent. The first Interface, AzAPI is modeled closely on the XACML defined interface, expressed in Java. One of the goals was to support calls to both a PDP local to the same process and a PDP in a remote server. AzAPI includes the interface, reference code to handle things like the many supported datatypes in XACML and glue code to mate it to the open source Sun XACML implementation. Because of the dependence on Sun XACML (which is XACML 2.0) the interface was missing some XACML 3.0 features. More recently this was corrected and WSo2 has mated it to their XACML 3.0 PDP. Some work was done by the JPMC team to support calling a remote PDP. WSo2 is also pursuing this capability. A second, higher level interface, PEPAPI was also defined. PEPAPI is more intended for application developers with little knowledge of XACML. It allows Java objects which contain attribute information to be passed in. Conversion methods, called mappers extract information from the objects and present it in the format expected by XACML. Some implementers have chosen to implement PEPAPI directly against their PDP, omitting the use of AzAPI. Naomaru Itoi defined a C++ interface which closely matches the Java one. Examples of more speculative work include: proposals for registration and dispatch of Obligation and Advice handlers, a scheme called AMF to tell PIPs how to retrieve attributes and PIP code to implement it, discussion of PoC code to demonstrate the use of XACML policies
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: [VOTE] Graduate Syncope podling from Apache Incubator
+1. Colm. On Fri, Nov 2, 2012 at 10:50 AM, Andrus Adamchik and...@objectstyle.orgwrote: +1 Looking forward to actually using Syncope soon. On Nov 2, 2012, at 1:43 PM, Emmanuel Lécharny elecha...@gmail.com wrote: a big +1 ! Excellent work, guys ! Le 11/2/12 10:00 AM, Francesco Chicchiriccò a écrit : Hi all, this is a call for vote to graduate the Syncope podling from Apache Incubator. Syncope entered the Incubator in Feb 2012. Since then it has added two new committers and PPMC members, picked up a couple of new contributors, and made some releases following the ASF policies and guidelines. The community of Syncope is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. The Syncope community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Syncope podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Syncope podling [ ] -1 Reject graduation of Syncope podling from Apache Incubator because ... This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/up [2] http://s.apache.org/A8u Regards. Resolution: X. Establish the Apache Syncope 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 managing digital identities in enterprise environments. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Syncope Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Syncope Project be and hereby is responsible for the creation and maintenance of software related to the Identity Management and be it further RESOLVED, that the office of Vice President, Apache Syncope 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 Syncope Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Syncope 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 Syncope Project: * Colm O Heigeartaigh cohei...@apache.org * Emmanuel Lécharny elecha...@apache.org * Fabio Martelli fmarte...@apache.org * Francesco Chicchiriccò ilgro...@apache.org * Jan Bernhardt jbernha...@apache.org * Jean-Baptiste Onofré jbono...@apache.org * Massimiliano Perrone ma...@apache.org * Marco Di Sabatino Di Diodoro mdisabat...@apache.org * Simone Tripodi simonetrip...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Francesco Chicchiriccò be appointed to the office of Vice President, Apache Syncope 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 Syncope Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Amber podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Amber podling encumbered upon the Apache Incubator Project are hereafter discharged. -- 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Incubator Wiki write access
I need access as well to sign off on Syncope: cohei...@apache.org. Colm. On Wed, May 2, 2012 at 4:19 PM, Nick Burch nick.bu...@alfresco.com wrote: On Wed, 2 May 2012, Raymond Feng wrote: I need write access too to copy and sign off the Amber report. RaymondFeng rf...@apache.org Should be granted now Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- 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: [VOTE][PROPOSAL] Syncope join the Incubator
committers are geographically distributed across the Europe with no one company being associated with a majority of the developers. Some of these initial developers are experienced Apache committers already and all are experienced with working in distributed development communities. == Reliance on Salaried Developers == To the best of our knowledge, Tirasa[5] is the only entity sponsoring Syncope development. == Relationships with Other Apache Products == Syncope fits naturally in the ASF because it naturally completes a whole set of ASF projects dedicated to enterprise environments like as Geronimo, Directory, CXF, ActiveMQ and so on. Moreover, Syncope could complete ASF coverage of middleware technologies by adding identity management to current ASF portfolio. == A Excessive Fascination with the Apache Brand == While the Apache Software Foundation would be a good home for the Syncope project, it already has some traction and it could live on its own - however we see reciprocal benefits for both the ASF and the project in adopting the brand to attract more people and enlarge users and developers communities. = Documentation = * The Syncope project page[6] * The Syncope project on Google Code[7] * The Syncope Wiki[8] * The public dev ML[9] * The public users ML[10] * The Syncope Issue Tracker[11] * The Syncope Continuous Integration system[12] = Initial Source = The intial source comprises code developed on Google Code[7] = Source and Intellectual Property Submission Plan = Source code will be moved from Google Code[7] space inside the SVN space of the podling. = External Dependencies = * Spring[13] - Apache License 2.0 * Apache OpenJPA[14] - Apache License 2.0 * Apache Bean Validation[15] - Apache License 2.0 * Apache Commons[16] - Apache License 2.0 * Activiti BPM[17] - Apache License 2.0 * AspectJ[18] - Eclipse Public License (Category B, used only in binary form) * Apache Wicket[19] - Apache License 2.0 * ConnId[20] - CDDL 1.0 (Category B, used only in binary form) * SLF4J[21] - MIT License (Category A) * Logback[22] - dual licensed under EPL v1.0 and LGPL 2.1 (Category B, but not really a dependency as it is astracted by the SLF4j facade) == Build/Test time dependencies == * Apache Maven[23] - Apache License 2.0 * JUnit[24] - CPL License v1.0 - (Category B, used only in binary form) * H2[25] - dual licensed under EPL v1.0 and MPL 1.1 (Category B, used only in binary form) * Cargo[26] - Apache License 2.0 * Apache Tomcat[27] - Apache License 2.0 * Apache DS[28] - Apache License 2.0 = Cryptography = The project does not handle cryptography in any way but standard mechanism available at JDK level. = Required Resources = * Mailing lists * syncope-private (with moderated subscriptions) * syncope-dev * syncope-user * syncope-commits * Subversion directory * https://svn.apache.org/repos/asf/incubator/syncope * Website * Wiki (Syncope) * Issue Tracking * JIRA (SYNCOPE) * Continuous Integration * Jenkins (Syncope) = Initial Committers = Names of initial committers - in alphabetical order - with current ASF status: * Dino Anzellotti dino.anzellotti at gmail dot com (ICLA Signed) * Francesco Chicchiriccò ilgrosso at apache dot org (PMC member) * Maurizio Cucchiara mcucchiara at apache dot org (PMC member) * Marco Di Sabatino Di Diodoro mdisabatinodidiodoro at gmail dot com (ICLA Signed) * Colm O Heigeartaigh coheigea at apache dot org (ASF Member) * Emmanuel Lecharny elecharny at apache dot org (ASF Member) * Fabio Martelli fabio.martelli at gmail dot com (ICLA Signed) * Rene Mulder rene.mulder at gmail dot com (ICLA Signed) * Massimiliano Perrone !MassimilianoPerrone at gmail dot com (ICLA Signed) * Nicola Scendoni scendoni at gmail dot com (ICLA Signed) * Simone Tripodi simonetripodi at apache dot org (ASF Member) * Geert van der Ploeg geertpl at gmail dot com (ICLA Signed) = Sponsors = == Champion == * Simone Tripodi simonetripodi at apache dot org == Nominated Mentors == * Colm O Heigeartaigh coheigea at apache dot org * Emmanuel Lecharny elecharny at apache dot org * Simone Tripodi simonetripodi at apache dot org == Sponsoring Entity == * The Apache Incubator = Other interested people (in alphabetical order) = * none [ 1] http://wiki.syncope-idm.org/index.php?title=Releases [ 2] http://www.syncope-idm.org/wordpress/?cat=12 [ 3] http://wiki.syncope-idm.org/index.php?title=Roadmap [ 4] http://www.syncope-idm.org/wordpress/?cat=12 [ 5] http://www.tirasa.net/ [ 6] http://www.syncope-idm.org/wordpress/ [ 7] http://code.google.com/p/syncope/ [ 8] http://wiki.syncope-idm.org/index.php [ 9] https://groups.google.com/group/syncope-dev [10] https://groups.google.com/group/syncope-dev [11] http://code.google.com/p/syncope/issues/list [12] http://jenkins.syncope-idm.org [13] http://www.springsource.org/ [14] http
Re: [DISCUSS] Syncope to Join the Apache Incubator
Great thanks! Could you add me to the initial committer list as well? Colm. 2012/2/3 Francesco Chicchiriccò ilgro...@apache.org: Hi Colm, this sounds great: I've just added your details to Syncope proposal [1]: please check if everything is correct. Regards. [1]http://wiki.apache.org/incubator/SyncopeProposal -- Francesco Chicchiriccò Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/ -- 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: [DISCUSS] Syncope to Join the Apache Incubator
Hi, Syncope proposal [1] is still looking for more mentors: who is interested in Identity Management and wants to get involved in one of first Open Source projects in this field? I am interested in this project and would like to come on board as a mentor if possible. I'm an ASF member and work on XML Security (Apache Santuario), WS-Security (Apache WSS4J) as well as Apache CXF. Colm. -- 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
