Re: svn commit: r1626888 - /incubator/public/trunk/content/podlings.xml
Thanks for clarifying sebb, The incubator docs aren't very clear in that respect. I will correct it. -Taylor > On Sep 23, 2014, at 6:28 PM, sebb wrote: > >> On 22 September 2014 21:13, wrote: >> Author: ptgoetz >> Date: Mon Sep 22 20:13:24 2014 >> New Revision: 1626888 >> >> URL: http://svn.apache.org/r1626888 >> Log: >> set storm status to graduating >> >> Modified: >>incubator/public/trunk/content/podlings.xml >> >> Modified: incubator/public/trunk/content/podlings.xml >> URL: >> http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1626888&r1=1626887&r2=1626888&view=diff >> == >> --- incubator/public/trunk/content/podlings.xml [utf-8] (original) >> +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Sep 22 20:13:24 >> 2014 >> @@ -1645,7 +1645,7 @@ and a set of useful extensions for this >> Paul Fremantle >> >> >> -> sponsor="Incubator" startdate="2013-09-18"> >> +> sponsor="Incubator" startdate="2013-09-18"> > > That is not a valid status; is a child element that can > be applied to status="current" > > Please refer to the DTD in the same directory as podling.xml > >> Storm is a distributed, fault-tolerant, and >> high-performance realtime computation system that provides strong guarantees >> on the processing of data. >> >> Doug Cutting >> >> >> >> - >> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org >> For additional commands, e-mail: cvs-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
Re: [Proposal] Taverna workflow
On 23 September 2014 13:43, Stian Soiland-Reyes wrote: > I hereby present the Apache Incubator proposal for the project Taverna. > > > Also available in rich text in the Taverna wiki (with more hyperlinks!): > > http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal > > (Could someone grant me access to edit the Incubator wiki pages? My > wiki username is soilandreyes) (this would have been better as a separate e-mail) Done - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache DeviceMap Data 1.0.1 incubating
On 23 September 2014 17:11, Reza wrote: > This is the second device data release for DeviceMap. This release contains > various new devices and generic device class additions: > https://issues.apache.org/jira/browse/DMAP/fixforversion/12327454/ > > The project vote is here: http://markmail.org/message/c2wvexsa7ed46n65 Please use an ASF link for this in future. 3rd party links may change or disappear. > It passed with +3 PPMC and +1 IPMC (Kevan Miller) > > The release tag is located here: > http://svn.apache.org/viewvc/incubator/devicemap/tags/releases/devicemap-data-1.0.1/ Tags are not immutable. Please include the revision. I assume it is 1623255 Is that correct? > Release artifacts: http://devicemap-vm.apache.org/releases/data-1.0.1/ This includes the KEYS file, but it would be clearer to show that as a separate URL in future please. > Please vote to approve this release. Voting will close in 72 hours (Friday > Sept 26 2014). > > [ ] +1 Approve the release > [ ] 0 No opinion > [ ] -1 Don't release, because ... > > Thanks! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1626888 - /incubator/public/trunk/content/podlings.xml
On 22 September 2014 21:13, wrote: > Author: ptgoetz > Date: Mon Sep 22 20:13:24 2014 > New Revision: 1626888 > > URL: http://svn.apache.org/r1626888 > Log: > set storm status to graduating > > Modified: > incubator/public/trunk/content/podlings.xml > > Modified: incubator/public/trunk/content/podlings.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1626888&r1=1626887&r2=1626888&view=diff > == > --- incubator/public/trunk/content/podlings.xml [utf-8] (original) > +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Sep 22 20:13:24 > 2014 > @@ -1645,7 +1645,7 @@ and a set of useful extensions for this > Paul Fremantle > > > - sponsor="Incubator" startdate="2013-09-18"> > + sponsor="Incubator" startdate="2013-09-18"> That is not a valid status; is a child element that can be applied to status="current" Please refer to the DTD in the same directory as podling.xml > Storm is a distributed, fault-tolerant, and > high-performance realtime computation system that provides strong guarantees > on the processing of data. > > Doug Cutting > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1626885 - /incubator/public/trunk/content/podlings.xml
On 22 September 2014 21:03, wrote: > Author: ptgoetz > Date: Mon Sep 22 20:03:55 2014 > New Revision: 1626885 > > URL: http://svn.apache.org/r1626885 > Log: > set storm status to graduated > > Modified: > incubator/public/trunk/content/podlings.xml > > Modified: incubator/public/trunk/content/podlings.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1626885&r1=1626884&r2=1626885&view=diff > == > --- incubator/public/trunk/content/podlings.xml [utf-8] (original) > +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Sep 22 20:03:55 > 2014 > @@ -1645,7 +1645,7 @@ and a set of useful extensions for this > Paul Fremantle > > > - sponsor="Incubator" startdate="2013-09-18"> > + sponsor="Incubator" startdate="2013-09-18"> graduated podlings need an end-date > Storm is a distributed, fault-tolerant, and > high-performance realtime computation system that provides strong guarantees > on the processing of data. > > Doug Cutting > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-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] Taverna workflow
Thanks, Stian, for submitting a well-developed proposal and for your interest in Apache. I have a few questions: * Can you say more about why you want to take Taverna to the ASF? * What is your strategy for increasing the diversity of your committer base? * Do you have any third party dependencies in the Taverna core that have incompatible licenses (like GPL)? * Would you like developer-contributed plugins to be covered within a future "Apache Taverna" project? My main goal here is to give the Incubator community a little more background and foster discussion, which will be useful in attracting mentors, so don't worry about "right" or "wrong" answers. Marlon On 9/23/14, 8:43 AM, Stian Soiland-Reyes wrote: I hereby present the Apache Incubator proposal for the project Taverna. Also available in rich text in the Taverna wiki (with more hyperlinks!): http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal (Could someone grant me access to edit the Incubator wiki pages? My wiki username is soilandreyes) # Abstract Taverna is an open source and domain-independent suite of tools used to design and execute data-driven workflows. # Proposal The Taverna suite includes: * Taverna Workbench, a Java-based desktop application for graphically composing, editing and executing workflows of distributed web services and local tools * Taverna Commandline Tool which allows repeated execution of parameterized workflow definitions * Taverna Server provides a REST and SOAP API for executing workflows * Taverna Player is a Ruby-based web interface towards the Server, providing a high-level view of workflow executions and their results, and allows further integrations with Ruby on Rails applications. Taverna can browse and combine different service types, allowing workflows to integrate steps of arbitrary REST and SOAP web services with command line tools (local and SSH), scripts (Beanshell, R, Jython) and finally visualize the results. The goal of the Taverna suite is to help researchers to access distributed datasets and processing capabilities by the construction of pipelines, and also to simplify the execution of these pipelines in various environments. The Taverna suite of products is already successful and in wide-use across different domains. The software is currently licensed as LGPL 2.1, with copyright owned by University of Manchester. External contributors have all signed Apache-like CLAs. # Background Taverna workflows coordinate inputs and outputs between computational processes and Web Services. The workflow is designed in a graphical interface which shows the workflow as a series of boxes and arrows; representing processes and their data connections. The different processes in a workflow can be command line tools, REST and WSDL Web Services; which are used for combining steps such as data acquisition, filtering, cleaning, integrating, analysis and visualization. Taverna calls these processes "services", as they generally are provided by remote (third-party) servers. These kind of computational workflows, also known as pipelines and dataflows, focus on the movement of data rather than the execution order of the underlying processes. Features such as implicit iterations (where an input list of values causes multiple process executions) and parallel invocations (independent processes are executed as soon as their data is available) are intrinsic to a dataflow system, not requiring any particular constructs by the workflow designer. As a visual programming environment, workflows aids collaboration and reuse of workflows. At the highest level, a workflow represents the conceptual level of an analysis, allowing understanding, discussion and communication of the overall analysis protocol. More detail can be revealed and modified for individual steps. At the individual process level, the workflow defines execution specifics such as operations, parameters and command line tools. Sharing of the workflow definitions allows re-use and re-purposing of the computational analysis. During workflow execution, provenance can be collected from every step, allowing deep inspection of intermediate values for the purpose of debugging and validation. # Rationale There is a strong need to lower the barrier of entry to datasets and computational resources widely available on the Internet, to increase their use by researchers who understand the computational steps needed to produce their results, but who are not necessarily expert programmers. Taverna has already shown its success and popularity in a wide range of scientific disciplines. # Initial Goals * Transition mailing lists to Apache (keep existing subscribers, but invite more) * Taverna developer workshop (2014-10-30) * Prepare git repositories for move: * Update headers/metadata to indicate Apache License 2.0 * Restructure git repositories * Rename Maven groupIds to org.apache.taverna.* * Rename packages to
Re: [VOTE] Graduate Apache Storm to a TLP
Congrats again for Apache Storm for being TLP, great work! =) - Henry On Tue, Sep 23, 2014 at 5:52 AM, P. Taylor Goetz wrote: > Hi Henry, > > I'm working with press@ to put together an official press release (currently > waiting on some quotes from PMC members). > > That process can take up to two weeks. I only learned of it recently by > reading some past board meeting minutes, so we're a little behind time wise. > > It might be worthwhile to add something to the graduation guide [1] so other > podlings don't make the same mistake. > > -Taylor > > [1] http://incubator.apache.org/guides/graduation.html > >> On Sep 22, 2014, at 9:20 PM, Henry Saputra wrote: >> >> Hi Guys, >> >> Question for Apache Storm PPMCs, with Apache Storm graduating, why is >> the announcement happening at HortonWorks website: >> >> http://hortonworks.com/blog/apache-storm-graduates-top-level-project/ >> >> rather than in https://blogs.apache.org ? >> >> - Henry >> >> >> >>> On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz wrote: >>> Apache Storm has been incubating since September 2014. Since then we have >>> added 3 additional committers (with another 2 approved and pending account >>> creation), and performed two releases. The Storm community recently voted >>> to graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members: >>> >>>- Arvind Prabhakar >>>- Suresh Srinivas >>> >>> I would now like to ask the IPMC to vote for the graduation of Apache Storm >>> to a top-level project. >>> >>> Please vote to indicate if Apache Storm is ready to graduate. The proposed >>> board resolution is included below. >>> >>> [ ] +1 Graduate Apache Storm as a TLP >>> [ ] +0 No opinion >>> [ ] -1 Do not graduate Apache Storm as a TLP because… >>> >>> This vote will be open for at least 72 hours. >>> >>> - Taylor >>> >>> [1] >>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e >>> >>> >>> >>> === Board Resolution === >>> >>>X. Establish the Apache Storm 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 distributed, fault-tolerant, >>> and high-performance realtime computation. >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>> Committee (PMC), to be known as the "Apache Storm Project", >>> be and hereby is established pursuant to Bylaws of the >>> Foundation; and be it further >>> >>> RESOLVED, that the Apache Storm Project be and hereby is >>> responsible for the creation and maintenance of software >>> related to distributed, fault-tolerant, and high- >>> performance realtime computation; and be it further >>> >>> RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility >>> for management of the projects within the scope of >>> responsibility of the Apache Storm 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 Storm Project: >>> >>> * Derek Dagit (da...@apache.org) >>> * Devaraj Das (d...@apache.org) >>> * Ted Dunning (tdunn...@apache.org) >>> * Robert Evans (bo...@apache.org) >>> * Andy Feng(af...@apache.org) >>> * P. Taylor Goetz (ptgo...@apache.org) >>> * Jason Jackson(jjack...@apache.org) >>> * Flip Kromer (mrf...@apache.org) >>> * David Lao(d...@apache.org) >>> * Nathan Marz (nathanm...@apache.org) >>> * Michael G. Noll (mig...@apache.org) >>> * Arvind Prabhakar (arv...@apache.org) >>> * James Xu (xumingm...@apache.org) >>> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that P. Taylor Goetz >>> be appointed to the office of Vice President, Apache Storm, 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 Storm 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 Storm Project; and be it
Re: [VOTE] Graduate Apache Storm to a TLP
Thanks for the update Taylor. Just to make sure you guys working with press@ for the official announcement. Incubator projects are little bit scrutinized when making announcements under ASF so I want to make sure HW understand about it. Thanks, Henry On Tue, Sep 23, 2014 at 5:52 AM, P. Taylor Goetz wrote: > Hi Henry, > > I'm working with press@ to put together an official press release (currently > waiting on some quotes from PMC members). > > That process can take up to two weeks. I only learned of it recently by > reading some past board meeting minutes, so we're a little behind time wise. > > It might be worthwhile to add something to the graduation guide [1] so other > podlings don't make the same mistake. > > -Taylor > > [1] http://incubator.apache.org/guides/graduation.html > >> On Sep 22, 2014, at 9:20 PM, Henry Saputra wrote: >> >> Hi Guys, >> >> Question for Apache Storm PPMCs, with Apache Storm graduating, why is >> the announcement happening at HortonWorks website: >> >> http://hortonworks.com/blog/apache-storm-graduates-top-level-project/ >> >> rather than in https://blogs.apache.org ? >> >> - Henry >> >> >> >>> On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz wrote: >>> Apache Storm has been incubating since September 2014. Since then we have >>> added 3 additional committers (with another 2 approved and pending account >>> creation), and performed two releases. The Storm community recently voted >>> to graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members: >>> >>>- Arvind Prabhakar >>>- Suresh Srinivas >>> >>> I would now like to ask the IPMC to vote for the graduation of Apache Storm >>> to a top-level project. >>> >>> Please vote to indicate if Apache Storm is ready to graduate. The proposed >>> board resolution is included below. >>> >>> [ ] +1 Graduate Apache Storm as a TLP >>> [ ] +0 No opinion >>> [ ] -1 Do not graduate Apache Storm as a TLP because… >>> >>> This vote will be open for at least 72 hours. >>> >>> - Taylor >>> >>> [1] >>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e >>> >>> >>> >>> === Board Resolution === >>> >>>X. Establish the Apache Storm 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 distributed, fault-tolerant, >>> and high-performance realtime computation. >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>> Committee (PMC), to be known as the "Apache Storm Project", >>> be and hereby is established pursuant to Bylaws of the >>> Foundation; and be it further >>> >>> RESOLVED, that the Apache Storm Project be and hereby is >>> responsible for the creation and maintenance of software >>> related to distributed, fault-tolerant, and high- >>> performance realtime computation; and be it further >>> >>> RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility >>> for management of the projects within the scope of >>> responsibility of the Apache Storm 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 Storm Project: >>> >>> * Derek Dagit (da...@apache.org) >>> * Devaraj Das (d...@apache.org) >>> * Ted Dunning (tdunn...@apache.org) >>> * Robert Evans (bo...@apache.org) >>> * Andy Feng(af...@apache.org) >>> * P. Taylor Goetz (ptgo...@apache.org) >>> * Jason Jackson(jjack...@apache.org) >>> * Flip Kromer (mrf...@apache.org) >>> * David Lao(d...@apache.org) >>> * Nathan Marz (nathanm...@apache.org) >>> * Michael G. Noll (mig...@apache.org) >>> * Arvind Prabhakar (arv...@apache.org) >>> * James Xu (xumingm...@apache.org) >>> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that P. Taylor Goetz >>> be appointed to the office of Vice President, Apache Storm, 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 Storm PMC be and hereby
Re: [PROPOSAL] Grill as new Incubator project
+1! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Ted Dunning Reply-To: "general@incubator.apache.org" Date: Tuesday, September 23, 2014 8:44 AM To: "general@incubator.apache.org" , "sha...@apache.org" Subject: Re: [PROPOSAL] Grill as new Incubator project >Awesome community-building attitude here! > >I foresee a successful incubation. :-) > > > >On Tue, Sep 23, 2014 at 1:24 AM, Sharad Agarwal wrote: > >> Thanks Ted. We have renamed the proposal to Lens. >> >> The proposal is pasted here -> >> https://wiki.apache.org/incubator/LensProposal >> >> Thanks >> Sharad >> >> On Tue, Sep 23, 2014 at 12:04 AM, Ted Dunning >> wrote: >> >> > Both Lens and Blend are nice names. Nice connotations as well. >> > >> > I am slightly stunned by a quick search on the name Lens. I only >>found >> one >> > software package with that name (and it was for lens calibration so >>far >> > from databases). A name like that is usually massively over used. >> > >> > This might be a really nice opportunity to get a nice one syllable >>name. >> > >> > >> > >> > >> > On Mon, Sep 22, 2014 at 2:59 AM, Sharad Agarwal >> wrote: >> > >> > > Based on the feedback, we are considering to rename the project. >> > > >> > > Please provide feedback on following names: >> > > Apache Lens >> > > Apache Blend >> > > >> > > Thanks, >> > > Sharad >> > > >> > >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] Taverna workflow
+1 this is really great news. Would happily help where I could as a mentor as well. On Tuesday, September 23, 2014, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > WOW that is so awesome guys! Taverna at Apache FTW!! > > Let me know if you need a mentor, I'm in! :) > > Cheers, > Chris > > ++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > > > > > -Original Message- > From: Stian Soiland-Reyes > > Reply-To: "general@incubator.apache.org " < > general@incubator.apache.org > > Date: Tuesday, September 23, 2014 5:43 AM > To: "general@incubator.apache.org " < > general@incubator.apache.org > > Cc: List for general discussion and hacking of the Taverna project > > > Subject: [Proposal] Taverna workflow > > >I hereby present the Apache Incubator proposal for the project Taverna. > > > > > >Also available in rich text in the Taverna wiki (with more hyperlinks!): > > > > > http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal > > > >(Could someone grant me access to edit the Incubator wiki pages? My > >wiki username is soilandreyes) > > > > > > > > > ># Abstract > > > >Taverna is an open source and domain-independent suite of tools used > >to design and execute data-driven workflows. > > > > > ># Proposal > > > >The Taverna suite includes: > > > >* Taverna Workbench, a Java-based desktop application for graphically > >composing, editing and executing workflows of distributed web services > >and local tools > >* Taverna Commandline Tool which allows repeated execution of > >parameterized workflow definitions > >* Taverna Server provides a REST and SOAP API for executing workflows > >* Taverna Player is a Ruby-based web interface towards the Server, > >providing a high-level view of workflow executions and their results, > >and allows further integrations with Ruby on Rails applications. > > > >Taverna can browse and combine different service types, allowing > >workflows to integrate steps of arbitrary REST and SOAP web services > >with command line tools (local and SSH), scripts (Beanshell, R, > >Jython) and finally visualize the results. > > > >The goal of the Taverna suite is to help researchers to access > >distributed datasets and processing capabilities by the construction > >of pipelines, and also to simplify the execution of these pipelines > >in various environments. > > > >The Taverna suite of products is already successful and in wide-use > >across different domains. The software is currently licensed as LGPL > >2.1, with copyright owned by University of Manchester. External > >contributors have all signed Apache-like CLAs. > > > > > ># Background > > > >Taverna workflows coordinate inputs and outputs between computational > >processes and Web Services. The workflow is designed in a graphical > >interface which shows the workflow as a series of boxes and arrows; > >representing processes and their data connections. The different > >processes in a workflow can be command line tools, REST and WSDL Web > >Services; which are used for combining steps such as data acquisition, > >filtering, cleaning, integrating, analysis and visualization. Taverna > >calls these processes "services", as they generally are provided by > >remote (third-party) servers. > > > >These kind of computational workflows, also known as pipelines and > >dataflows, focus on the movement of data rather than the execution > >order of the underlying processes. Features such as implicit > >iterations (where an input list of values causes multiple process > >executions) and parallel invocations (independent processes are > >executed as soon as their data is available) are intrinsic to a > >dataflow system, not requiring any particular constructs by the > >workflow designer. > > > >As a visual programming environment, workflows aids collaboration and > >reuse of workflows. At the highest level, a workflow represents the > >conceptual level of an analysis, allowing understanding, discussion > >and communication of the overall analysis protocol. More detail can be > >revealed and modified for individual steps. At the individual process > >level, the workflow defines execution specifics such as operations, > >parameters and command line tools. > > > >Sharing of the workflow definitions allows re-use and re-purposing of > >the computational analysis. During workflow execution, provenance can > >be collected from every step, allowing deep inspection of in
Re: [Proposal] Taverna workflow
WOW that is so awesome guys! Taverna at Apache FTW!! Let me know if you need a mentor, I'm in! :) Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Stian Soiland-Reyes Reply-To: "general@incubator.apache.org" Date: Tuesday, September 23, 2014 5:43 AM To: "general@incubator.apache.org" Cc: List for general discussion and hacking of the Taverna project Subject: [Proposal] Taverna workflow >I hereby present the Apache Incubator proposal for the project Taverna. > > >Also available in rich text in the Taverna wiki (with more hyperlinks!): > >http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal > >(Could someone grant me access to edit the Incubator wiki pages? My >wiki username is soilandreyes) > > > > ># Abstract > >Taverna is an open source and domain-independent suite of tools used >to design and execute data-driven workflows. > > ># Proposal > >The Taverna suite includes: > >* Taverna Workbench, a Java-based desktop application for graphically >composing, editing and executing workflows of distributed web services >and local tools >* Taverna Commandline Tool which allows repeated execution of >parameterized workflow definitions >* Taverna Server provides a REST and SOAP API for executing workflows >* Taverna Player is a Ruby-based web interface towards the Server, >providing a high-level view of workflow executions and their results, >and allows further integrations with Ruby on Rails applications. > >Taverna can browse and combine different service types, allowing >workflows to integrate steps of arbitrary REST and SOAP web services >with command line tools (local and SSH), scripts (Beanshell, R, >Jython) and finally visualize the results. > >The goal of the Taverna suite is to help researchers to access >distributed datasets and processing capabilities by the construction >of pipelines, and also to simplify the execution of these pipelines >in various environments. > >The Taverna suite of products is already successful and in wide-use >across different domains. The software is currently licensed as LGPL >2.1, with copyright owned by University of Manchester. External >contributors have all signed Apache-like CLAs. > > ># Background > >Taverna workflows coordinate inputs and outputs between computational >processes and Web Services. The workflow is designed in a graphical >interface which shows the workflow as a series of boxes and arrows; >representing processes and their data connections. The different >processes in a workflow can be command line tools, REST and WSDL Web >Services; which are used for combining steps such as data acquisition, >filtering, cleaning, integrating, analysis and visualization. Taverna >calls these processes "services", as they generally are provided by >remote (third-party) servers. > >These kind of computational workflows, also known as pipelines and >dataflows, focus on the movement of data rather than the execution >order of the underlying processes. Features such as implicit >iterations (where an input list of values causes multiple process >executions) and parallel invocations (independent processes are >executed as soon as their data is available) are intrinsic to a >dataflow system, not requiring any particular constructs by the >workflow designer. > >As a visual programming environment, workflows aids collaboration and >reuse of workflows. At the highest level, a workflow represents the >conceptual level of an analysis, allowing understanding, discussion >and communication of the overall analysis protocol. More detail can be >revealed and modified for individual steps. At the individual process >level, the workflow defines execution specifics such as operations, >parameters and command line tools. > >Sharing of the workflow definitions allows re-use and re-purposing of >the computational analysis. During workflow execution, provenance can >be collected from every step, allowing deep inspection of intermediate >values for the purpose of debugging and validation. > > ># Rationale > >There is a strong need to lower the barrier of entry to datasets and >computational resources widely available on the Internet, to increase >their use by researchers who understand the computational steps needed >to produce their results, but who are not necessarily expert >programmers. Taverna has already shown its success and popularity in a >wide range of scientific disciplines. > > ># Init
[VOTE] Apache DeviceMap Data 1.0.1 incubating
This is the second device data release for DeviceMap. This release contains various new devices and generic device class additions: https://issues.apache.org/jira/browse/DMAP/fixforversion/12327454/ The project vote is here: http://markmail.org/message/c2wvexsa7ed46n65 It passed with +3 PPMC and +1 IPMC (Kevan Miller) The release tag is located here: http://svn.apache.org/viewvc/incubator/devicemap/tags/releases/devicemap-data-1.0.1/ Release artifacts: http://devicemap-vm.apache.org/releases/data-1.0.1/ Please vote to approve this release. Voting will close in 72 hours (Friday Sept 26 2014). [ ] +1 Approve the release [ ] 0 No opinion [ ] -1 Don't release, because ... Thanks!
Re: [PROPOSAL] Grill as new Incubator project
Awesome community-building attitude here! I foresee a successful incubation. :-) On Tue, Sep 23, 2014 at 1:24 AM, Sharad Agarwal wrote: > Thanks Ted. We have renamed the proposal to Lens. > > The proposal is pasted here -> > https://wiki.apache.org/incubator/LensProposal > > Thanks > Sharad > > On Tue, Sep 23, 2014 at 12:04 AM, Ted Dunning > wrote: > > > Both Lens and Blend are nice names. Nice connotations as well. > > > > I am slightly stunned by a quick search on the name Lens. I only found > one > > software package with that name (and it was for lens calibration so far > > from databases). A name like that is usually massively over used. > > > > This might be a really nice opportunity to get a nice one syllable name. > > > > > > > > > > On Mon, Sep 22, 2014 at 2:59 AM, Sharad Agarwal > wrote: > > > > > Based on the feedback, we are considering to rename the project. > > > > > > Please provide feedback on following names: > > > Apache Lens > > > Apache Blend > > > > > > Thanks, > > > Sharad > > > > > >
Re: [PROPOSAL] Grill as new Incubator project
On 23.09.2014 14:37, Jean-Baptiste Onofré wrote: > I like Lens indeed. Sooo ... I suppose the PMC chair will be called the Grey Lensman then? :) -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Storm to a TLP
Hi Henry, I'm working with press@ to put together an official press release (currently waiting on some quotes from PMC members). That process can take up to two weeks. I only learned of it recently by reading some past board meeting minutes, so we're a little behind time wise. It might be worthwhile to add something to the graduation guide [1] so other podlings don't make the same mistake. -Taylor [1] http://incubator.apache.org/guides/graduation.html > On Sep 22, 2014, at 9:20 PM, Henry Saputra wrote: > > Hi Guys, > > Question for Apache Storm PPMCs, with Apache Storm graduating, why is > the announcement happening at HortonWorks website: > > http://hortonworks.com/blog/apache-storm-graduates-top-level-project/ > > rather than in https://blogs.apache.org ? > > - Henry > > > >> On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz wrote: >> Apache Storm has been incubating since September 2014. Since then we have >> added 3 additional committers (with another 2 approved and pending account >> creation), and performed two releases. The Storm community recently voted to >> graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members: >> >>- Arvind Prabhakar >>- Suresh Srinivas >> >> I would now like to ask the IPMC to vote for the graduation of Apache Storm >> to a top-level project. >> >> Please vote to indicate if Apache Storm is ready to graduate. The proposed >> board resolution is included below. >> >> [ ] +1 Graduate Apache Storm as a TLP >> [ ] +0 No opinion >> [ ] -1 Do not graduate Apache Storm as a TLP because… >> >> This vote will be open for at least 72 hours. >> >> - Taylor >> >> [1] >> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e >> >> >> >> === Board Resolution === >> >>X. Establish the Apache Storm 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 distributed, fault-tolerant, >> and high-performance realtime computation. >> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >> Committee (PMC), to be known as the "Apache Storm Project", >> be and hereby is established pursuant to Bylaws of the >> Foundation; and be it further >> >> RESOLVED, that the Apache Storm Project be and hereby is >> responsible for the creation and maintenance of software >> related to distributed, fault-tolerant, and high- >> performance realtime computation; and be it further >> >> RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility >> for management of the projects within the scope of >> responsibility of the Apache Storm 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 Storm Project: >> >> * Derek Dagit (da...@apache.org) >> * Devaraj Das (d...@apache.org) >> * Ted Dunning (tdunn...@apache.org) >> * Robert Evans (bo...@apache.org) >> * Andy Feng(af...@apache.org) >> * P. Taylor Goetz (ptgo...@apache.org) >> * Jason Jackson(jjack...@apache.org) >> * Flip Kromer (mrf...@apache.org) >> * David Lao(d...@apache.org) >> * Nathan Marz (nathanm...@apache.org) >> * Michael G. Noll (mig...@apache.org) >> * Arvind Prabhakar (arv...@apache.org) >> * James Xu (xumingm...@apache.org) >> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that P. Taylor Goetz >> be appointed to the office of Vice President, Apache Storm, 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 Storm 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 Storm Project; and be it further >> >> RESOLVED, that the Apache Storm Project be and hereby >> is tasked with the migration and rationalization of the Apache >> Incubator Storm podling; and be it further >> >> RESOLVED, that a
[Proposal] Taverna workflow
I hereby present the Apache Incubator proposal for the project Taverna. Also available in rich text in the Taverna wiki (with more hyperlinks!): http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal (Could someone grant me access to edit the Incubator wiki pages? My wiki username is soilandreyes) # Abstract Taverna is an open source and domain-independent suite of tools used to design and execute data-driven workflows. # Proposal The Taverna suite includes: * Taverna Workbench, a Java-based desktop application for graphically composing, editing and executing workflows of distributed web services and local tools * Taverna Commandline Tool which allows repeated execution of parameterized workflow definitions * Taverna Server provides a REST and SOAP API for executing workflows * Taverna Player is a Ruby-based web interface towards the Server, providing a high-level view of workflow executions and their results, and allows further integrations with Ruby on Rails applications. Taverna can browse and combine different service types, allowing workflows to integrate steps of arbitrary REST and SOAP web services with command line tools (local and SSH), scripts (Beanshell, R, Jython) and finally visualize the results. The goal of the Taverna suite is to help researchers to access distributed datasets and processing capabilities by the construction of pipelines, and also to simplify the execution of these pipelines in various environments. The Taverna suite of products is already successful and in wide-use across different domains. The software is currently licensed as LGPL 2.1, with copyright owned by University of Manchester. External contributors have all signed Apache-like CLAs. # Background Taverna workflows coordinate inputs and outputs between computational processes and Web Services. The workflow is designed in a graphical interface which shows the workflow as a series of boxes and arrows; representing processes and their data connections. The different processes in a workflow can be command line tools, REST and WSDL Web Services; which are used for combining steps such as data acquisition, filtering, cleaning, integrating, analysis and visualization. Taverna calls these processes "services", as they generally are provided by remote (third-party) servers. These kind of computational workflows, also known as pipelines and dataflows, focus on the movement of data rather than the execution order of the underlying processes. Features such as implicit iterations (where an input list of values causes multiple process executions) and parallel invocations (independent processes are executed as soon as their data is available) are intrinsic to a dataflow system, not requiring any particular constructs by the workflow designer. As a visual programming environment, workflows aids collaboration and reuse of workflows. At the highest level, a workflow represents the conceptual level of an analysis, allowing understanding, discussion and communication of the overall analysis protocol. More detail can be revealed and modified for individual steps. At the individual process level, the workflow defines execution specifics such as operations, parameters and command line tools. Sharing of the workflow definitions allows re-use and re-purposing of the computational analysis. During workflow execution, provenance can be collected from every step, allowing deep inspection of intermediate values for the purpose of debugging and validation. # Rationale There is a strong need to lower the barrier of entry to datasets and computational resources widely available on the Internet, to increase their use by researchers who understand the computational steps needed to produce their results, but who are not necessarily expert programmers. Taverna has already shown its success and popularity in a wide range of scientific disciplines. # Initial Goals * Transition mailing lists to Apache (keep existing subscribers, but invite more) * Taverna developer workshop (2014-10-30) * Prepare git repositories for move: * Update headers/metadata to indicate Apache License 2.0 * Restructure git repositories * Rename Maven groupIds to org.apache.taverna.* * Rename packages to org.apache.taverna.* * Move Github repositories to Apache git * Automated builds in Apache's Jenkins * Update to latest releases of Apache dependencies * Propose updated release & testing procedure under Apache * Moved Website and documentation We intend to only release the current development version Taverna 3.x http://www.taverna.org.uk/developers/work-in-progress/taverna-3/ under the Apache umbrella (). 3.0 is not yet officially released - however the Taverna 3.0 Command Line can be released almost "as-is" after migration. The Taverna 3.0 Server is at beta quality, while the Taverna 3.0 Workbench is at alpha stage and would need to be stabilized to an initial beta release. * Before first release: Maven Central releases o
Re: [PROPOSAL] Grill as new Incubator project
I like Lens indeed. Thanks for the update Sharad. Regards JB On 09/23/2014 10:24 AM, Sharad Agarwal wrote: Thanks Ted. We have renamed the proposal to Lens. The proposal is pasted here -> https://wiki.apache.org/incubator/LensProposal Thanks Sharad On Tue, Sep 23, 2014 at 12:04 AM, Ted Dunning wrote: Both Lens and Blend are nice names. Nice connotations as well. I am slightly stunned by a quick search on the name Lens. I only found one software package with that name (and it was for lens calibration so far from databases). A name like that is usually massively over used. This might be a really nice opportunity to get a nice one syllable name. On Mon, Sep 22, 2014 at 2:59 AM, Sharad Agarwal wrote: Based on the feedback, we are considering to rename the project. Please provide feedback on following names: Apache Lens Apache Blend Thanks, Sharad -- 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
Re: [PROPOSAL] Grill as new Incubator project
Thanks Ted. We have renamed the proposal to Lens. The proposal is pasted here -> https://wiki.apache.org/incubator/LensProposal Thanks Sharad On Tue, Sep 23, 2014 at 12:04 AM, Ted Dunning wrote: > Both Lens and Blend are nice names. Nice connotations as well. > > I am slightly stunned by a quick search on the name Lens. I only found one > software package with that name (and it was for lens calibration so far > from databases). A name like that is usually massively over used. > > This might be a really nice opportunity to get a nice one syllable name. > > > > > On Mon, Sep 22, 2014 at 2:59 AM, Sharad Agarwal wrote: > > > Based on the feedback, we are considering to rename the project. > > > > Please provide feedback on following names: > > Apache Lens > > Apache Blend > > > > Thanks, > > Sharad > > >
