Re: [PROPOSAL] Stonehenge
+1, this seems to be interesting Thanks, Ruwan On Tue, Nov 4, 2008 at 10:04 PM, Paul Fremantle [EMAIL PROTECTED] wrote: I'd like to propose Stonehenge as an incubator proposal. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. The full proposal is here: http://wiki.apache.org/incubator/StonehengeProposal As ever, all feedback, positive or negative is welcome. Also, any further mentors are more than welcome! Paul -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ruwan Linton http://wso2.org - Oxygenating the Web Services Platform http://ruwansblog.blogspot.com/
Re: Donations Repo
On Tue, Nov 4, 2008 at 6:23 PM, David Crossley [EMAIL PROTECTED] wrote: Greg, as a PMC chair you will now have access. The Subversion authorisation is fixed. Thank you very much! I'll test it here in a bit. Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Stonehenge
Robert sounds like a worthwhile initiative Thanks for the feedback! i like the idea but i do wonder a little whether the practical scope of the project needs some more rounding out I agree it would make sense to help tie down what would make this a successful project, release, etc. Any thoughts on how to make this more concrete? AFAICT (hopefully the committers will jump in and correct any misunderstandings) the project seems likely to consist of independent products, each (ideally) corresponding to a suite of applications target described by a sort-of-specification. Yes. the scope's really pretty broad so i think a little more detail about scaling out would be useful: how would stonehenge approach adding new suites especially when donated from outside the developers group? I guess I imagined that there would be two approaches. One is that someone might develop this outside of Stonehenge and then do a grant. However, I would expect a more likely approach is that someone would contribute via the normal JIRA / patch process. Do you see any issues with either of these? Thanks Paul -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
On Tue, Nov 4, 2008 at 12:22 AM, Darren Hague [EMAIL PROTECTED] wrote: I would like to propose ESME as a project for the Apache Incubator. Uber-cool. I signed up as a mentor as well. Ciao, -- Gianugo Rabellino Sourcesense, making sense of Open Source: http://www.sourcesense.com (blogging at http://www.rabellino.it/blog/) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
Darren Hague wrote: I would like to propose ESME as a project for the Apache Incubator. Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME is written in Scala and uses the Lift web framework. I've been looking at Scala and Lift while I was searching ways to apply Erlang's lightweight process approach to Java. So this is a very cool proposal and I'm willing to help as a mentor, so that it can finally force me to get my hands dirty on Scala! However, this proposal could be made way more interesting and potentially disrupting if it were to include the Lift framework itself, and also consider not only enterprise micro-blogging, but also open federated microblogging [1] that was initiated by Identi.ca [2]. Micro blogging has become part of the daily activity of many people, and a scalable open source solution to run federated microblogging would be really nice, rather than wondering when will be Twitter's next downtime ;-) Sylvain [1] http://openmicroblogging.org/ [2] http://identi.ca/ -- Sylvain Wallez - http://bluxte.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Stonehenge
Paul Fremantle wrote: the scope's really pretty broad so i think a little more detail about scaling out would be useful: how would stonehenge approach adding new suites especially when donated from outside the developers group? I guess I imagined that there would be two approaches. One is that someone might develop this outside of Stonehenge and then do a grant. However, I would expect a more likely approach is that someone would contribute via the normal JIRA / patch process. Do you see any issues with either of these? I actually expect that the way a true community will form around this project is when the next application is something that is born out of Stonehenge itself .. that is, someone proposes an idea and then we discuss it, refine it, develop an architecture, document it and implement it in 17 different ways. In that case there could be external contribs and JIRA/patch contribs too but most would be by project committers directly writing the code. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
On Wed, Nov 5, 2008 at 8:18 AM, Sylvain Wallez [EMAIL PROTECTED] wrote: Darren Hague wrote: I would like to propose ESME as a project for the Apache Incubator. Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME is written in Scala and uses the Lift web framework. I've been looking at Scala and Lift while I was searching ways to apply Erlang's lightweight process approach to Java. So this is a very cool proposal and I'm willing to help as a mentor, so that it can finally force me to get my hands dirty on Scala! However, this proposal could be made way more interesting and potentially disrupting if it were to include the Lift framework itself, and also consider not only enterprise micro-blogging, but also open federated microblogging [1] that was initiated by Identi.ca [2]. Speaking for Lift (I'm the BDFL of Lift), I'm very very happy with how we've been hosting Lift. I don't see a compelling reason to move Lift to the Apache foundation. ESME will support a variety of standard-ish APIs including Twitter's APIs, open federated micro blogging APIs, etc. It will also have a set of secure federation APIs. Micro blogging has become part of the daily activity of many people, and a scalable open source solution to run federated microblogging would be really nice, rather than wondering when will be Twitter's next downtime ;-) Sylvain [1] http://openmicroblogging.org/ [2] http://identi.ca/ -- Sylvain Wallez - http://bluxte.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp
Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
David Pollak wrote: On Wed, Nov 5, 2008 at 8:18 AM, Sylvain Wallez [EMAIL PROTECTED] wrote: Darren Hague wrote: I would like to propose ESME as a project for the Apache Incubator. Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME is written in Scala and uses the Lift web framework. I've been looking at Scala and Lift while I was searching ways to apply Erlang's lightweight process approach to Java. So this is a very cool proposal and I'm willing to help as a mentor, so that it can finally force me to get my hands dirty on Scala! However, this proposal could be made way more interesting and potentially disrupting if it were to include the Lift framework itself, and also consider not only enterprise micro-blogging, but also open federated microblogging [1] that was initiated by Identi.ca [2]. Speaking for Lift (I'm the BDFL of Lift), I'm very very happy with how we've been hosting Lift. I don't see a compelling reason to move Lift to the Apache foundation. It's not just about hosting, but about getting more exposure to grow a larger community, which could be beneficial not only for Lift, but also more generally for Scala. ESME will support a variety of standard-ish APIs including Twitter's APIs, open federated micro blogging APIs, etc. It will also have a set of secure federation APIs. Sounds good! Sylvain -- Sylvain Wallez - http://bluxte.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OpenWebBeans status page (Was: svn commit: r711682)
Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OpenWebBeans status page (Was: svn commit: r711682)
also... did we already ping infra for the mailing lists? If not, let me do that. @mail to request the accounts. We only have CLA from Conny, but not from Gurkan. Gurkan, did you already fax it? (Or is Sam just busy w/ ACon ;)) -M On Wed, Nov 5, 2008 at 11:06 PM, David Crossley [EMAIL PROTECTED] wrote: Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Podling board reports are due November 12
David Crossley wrote: See http://wiki.apache.org/incubator/November2008 There is one other project that is recently accepted: OpenWebBeans You can still report this month if you want to. Otherwise, please add your project to the ReportingSchedule page, ready for next month. I see that OpenWebBeans instead chose to report in November and added themselves to the ReportingSchedule, but not to this month's list: http://wiki.apache.org/incubator/November2008 So i just did it for you. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: [VOTE] Release Apache UIMACPP-2.2.2-incubating
Hi, The UIMA-CPP 2.2.2-incubating release, which is the first release of the part of UIMA that supports C++ components, is waiting for a couple of more IPMC votes to approve its release. The original email to this list (attached below and also here: http://markmail.org/message/meropdoa4vmsmeut) asking for review and voting is dated Sept 16, so it's been awhile. Could a couple of other IPMC members please vote on this release? Thanks, Eddie -- Forwarded message -- From: Eddie Epstein [EMAIL PROTECTED] Date: Tue, Sep 16, 2008 at 8:05 AM Subject: Re: [VOTE] Release Apache UIMACPP-2.2.2-incubating To: general@incubator.apache.org The voting template was inadvertently omitted from this vote request. Adding it here: [ ] +1 Yes, release Apache UIMACPP-2.2.2-incubating [ ] -1 No, do not release, there are issues to be resolved Thanks for your attention to this request, Eddie On Thu, Sep 11, 2008 at 6:42 PM, Eddie Epstein [EMAIL PROTECTED] wrote: Hi Everyone, Please review and vote on approving the first release of Apache UIMACPP, the C++ version of the UIMA framework. The release artifacts and the annotated RAT reports can be found here: http://people.apache.org/~eae/uimacpp-release-candidates/2.2.2/03/ UIMACPP makes it easy to create UIMA-compliant component from C++ analytics. This is extremely important for multimodal analytics such as speech-to-text, machine translation, image analysis, and many others. As a C++ library, UIMACPP also enables creating UIMA compliant components in other programming languages which easily link to C++. Included in this release is support for Perl, Python and Tcl via a common SWIG wrapper. UIMACPP utilizes several other Apache projects: APR, Xerces-c and ActiveMQ-CPP. Another, and final dependency, is ICU4C from icu-project.org. An official release of UIMACPP was delayed until a mechanism was in place to run C++ analytics as native processes; UIMA-AS has finally provided that mechanism. Previously, UIMACPP analytics had to be run under a JVM process through the JNI, which put many restrictions on operability. The UIMA project dev-list vote to release UIMACPP was 6 +1's, and no other votes; see the vote here: http://markmail.org/message/dmf2wk6zzq7dlsft Many thanks for your support, Eddie Epstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Next steps for droids
On Fri, 2008-10-31 at 11:50 +1100, David Crossley wrote: Grant Ingersoll wrote: Thorsten Scherler wrote: One more thing we need is: ssh people.apache.org cd /www/incubator.apache.org/ mkdir droids chown droids:droids droids However if I am doing groups on people I do not get the droids group but I remembered that you said you have set it up. I don't have that Karma. That would have to be a JIRA infra request, I think. I set up a Droids group in the SVN auth. However, I don't think we need an explicit Droids UNIX group (just look at all the others there) I presume that anyone on your project who wants to update your website, needs to ask to be added to the incubator UNIX group. http://apache.org/dev/reporting-issues.html#perms Thanks for pointing t out David. What we need is someone in the incubator group to add the directory. I _think_ all Incubator committers can be in that group, judging by the people who are already in that group. Maybe that's just an INFRA request? I just added the droids directory. Thanks very much I just deployed the documentation. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Qpid Graduation - for top level (resolution)
It is with the support of our mentors and a community vote on our dev list that Qpid would like to proceed to graduation. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise). Qpid also continues to attract more contributors, so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Attached is the graduation resolution, which was critiqued (/bashed :-) on the general list on our last graduation attempt with updated would be PMC... Please review our resolution, and provide any feedback or questions before a vote is started on the general list to graduate Qpid as a top level project many thanks. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid 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 Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Andrew Stitcher * Carl Trieloff * Craig Russell * Gordon Sim * John O'Hara * Kim van der Riet * Lahiru Gunathilake * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Rupert Smith * Steve Huston * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
[IP CLEARANCE] Check clearance for Velocity-Tiles plugin
Hi, I am Antonio Petrelli, PMC member of Apache Tiles. Can you check the IP clearance for Velocity-Tiles plugin? The IP clearance form is: http://incubator.apache.org/ip-clearance/velocity-tiles.html The vote thread is: http://www.nabble.com/-VOTE--Accept-Velocity-Tiles-plugin-donation-td20189659.html The donation is in this JIRA issue: https://issues.apache.org/struts/browse/TILES-170 The donation has been committed into the donations repo. Thanks in advance Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
