[VOTE] Accept Taverna into the Apache Incubator
Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Taverna into the Apache Incubator
+ 1 (binding). Suresh @Andy a typo, +1 accept Lens in the Incubator” - “+1 accept taverna in the Incubator”. On Oct 16, 2014, at 11:54 AM, Andy Seaborne a...@apache.org wrote: Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - 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: [VOTE] Accept Taverna into the Apache Incubator
+1 - binding I assume that you mean Taverna instead of Lens. Regards, Alan On Oct 16, 2014, at 8:54 AM, Andy Seaborne a...@apache.org wrote: Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - 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
I would love to join and listen in if the time zone differences don't make it too difficult. -- Joyce On Wed, Oct 15, 2014 at 5:45 PM, Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov wrote: Great I would be happy to participate and to receive the remote dial in instructions. Thanks Stian! ++ 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 soiland-re...@cs.manchester.ac.uk Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, October 15, 2014 at 4:52 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [Proposal] Taverna workflow Would any of the Taverna mentors be interested in joining the Taverna Development Workshop at the end of the month? http://taverna2014.eventbrite.co.uk/ http://dev.mygrid.org.uk/wiki/display/developer/Taverna+Open+Development+W orkshop I know most of you are not really based near Manchester - but we are already arranging for remoting in for another participant, so that is always an option if the time-zones allow. On 15 October 2014 10:02, Andy Seaborne a...@apache.org wrote: On 14/10/14 16:51, Marlon Pierce wrote: Hi all-- I'm a bit late on this but I would also like to serve as a mentor. I'm a PMC member of Apache Airavata and Apache Rave, and I've also served as a mentor for Apache Stratos. Marlon Marlon, Thank you for the offer - I've added you to the the mentor list on the proposal. Andy On 9/26/14, 10:18 AM, Andy Seaborne wrote: On 25/09/14 19:19, Suresh Marru wrote: If you need a mentor, count me in. I actively contribute to Apache Airavata, and will be happy to bring our experiences from a similar journey. Infact Ross queried on airavata lists few years ago about potential taverna move to airavata/apache(Ross mentioned it further in this thread), good to see finally its happening. Integrating plugin community into the apache project (once its voted in) seems to be a low hanging fruit to diversify. On 25/09/14 17:36, Suresh Srinivas wrote: If you you need a volunteer, I am available. Hi there, It being Friday, and Stian is about to be away, I've added you both to the mentors list. Taverna has a long history so getting as much experience from mentors will be very valuable. Thanks Andy PS I put Michael in as Not formally a mentor - 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 -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/-0001-9842-9718 - 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: [VOTE] Accept Taverna into the Apache Incubator
+1 binding (assuming its Taverna, and there has been a simple copy/paste error). have fun. jan I. On 16 October 2014 18:48, Alan D. Cabrera l...@toolazydogs.com wrote: +1 - binding I assume that you mean Taverna instead of Lens. Regards, Alan On Oct 16, 2014, at 8:54 AM, Andy Seaborne a...@apache.org wrote: Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - 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: [VOTE] Accept Taverna into the Apache Incubator
Apart from the typo, I thought it was necessary for the VOTE thread to contain the full text of the proposal. This has been the case for (almost) all previous acceptance votes. I assume the text is required so the mail archives have a full record of what was actually voted on. The Wiki page might subsequently change or be deleted. On 16 October 2014 18:27, jan i j...@apache.org wrote: +1 binding (assuming its Taverna, and there has been a simple copy/paste error). have fun. jan I. On 16 October 2014 18:48, Alan D. Cabrera l...@toolazydogs.com wrote: +1 - binding I assume that you mean Taverna instead of Lens. Regards, Alan On Oct 16, 2014, at 8:54 AM, Andy Seaborne a...@apache.org wrote: Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - 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
Re: [VOTE] Accept Taverna into the Apache Incubator
On 16/10/14 18:47, sebb wrote: Apart from the typo, I thought it was necessary for the VOTE thread to contain the full text of the proposal. This has been the case for (almost) all previous acceptance votes. The Lens one I copied from didn't :-) Version static link: https://wiki.apache.org/incubator/TavernaProposal?rev=10 and copied below. Andy I assume the text is required so the mail archives have a full record of what was actually voted on. The Wiki page might subsequently change or be deleted. 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 desktop application written in Java for graphically composing, editing and executing workflows composed of distributed Web services and local tools * Taverna Command Line Tool, which allows execution of workflows from a command line * Taverna Server, which provides a REST and SOAP API for executing workflows * Taverna Player, a Web interface the Taverna Server written in Ruby towards, providing a high-level view of workflow executions and their results and allowing further integrations with other Ruby on Rails applications Taverna allows browsing through and combining different service types in workflows, allowing them to integrate steps of arbitrary REST and SOAP Web services with command line tools (local and via SSH), scripts (Beanshell, R, Jython), and finally to visualize the results. The goal of the Taverna suite is to help researchers to access distributed datasets and processing capabilities by the construction of (data) 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 the 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 connected with arrows representing processes (i.e. executable services) and their data connections. 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 or 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) Fully investigate/resolve incompatibly licensed dependencies Stage git repositories for move at https://github.com/taverna-incubator : Update headers/metadata to indicate Apache License 2.0 Restructure git repositories (to ~ 10 repos?) Rename Maven groupIds to org.apache.taverna.* Rename packages to org.apache.taverna.* Move staged Github repositories to Apache git Automated builds in Apache's Jenkins Update to latest releases of Apache dependencies Propose updated release and testing procedure under Apache Moved Website and documentation We intend to only release
Re: [VOTE] Accept Taverna into the Apache Incubator
[ ] +1 accept Taverna in the Incubator [ ] ±0 [ ] -1 because... +1 (binding) Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [] Accept Taverna into the Apache Incubator
yes - s/Lens/Taverna/ (sigh) On 16/10/14 18:27, jan i wrote: +1 binding (assuming its Taverna, and there has been a simple copy/paste error). have fun. jan I. On 16 October 2014 18:48, Alan D. Cabrera l...@toolazydogs.com wrote: +1 - binding I assume that you mean Taverna instead of Lens. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Flink 0.7.0-incubating release
Hi all, The Flink incubator community has successfully voted for releasing version 0.7.0-incubating. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201410.mbox/%3CCAGr9p8DeNoa0R0%3DyFjmr4hbBwJP%2BvFJdeCFsh8ozjcQ8z7Ds9Q%40mail.gmail.com%3E The vote passed with +6 binding votes from the PPMC. - The commit to be voted on is in the branch release-0.7.0-rc1 (commit 17185a0b): http://git-wip-us.apache.org/repos/asf/incubator-flink/commit/17185a0b The release artifacts to be voted on can be found at: http://people.apache.org/~rmetzger/flink-0.7.0-incubating-rc1/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/rmetzger.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapacheflink-1015 - Please vote to approve this release. The vote is open for 72 hours or until the necessary number of votes is reached (+3). [ ] +1 Release this package as Apache Flink 0.7.0-incubating [ ] -1 Do not release this package because ... Thanks!
Re: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)
It looks like the version [1] of the Wiki page that was active at the time of the vote was: https://wiki.apache.org/incubator/LensProposal?rev=4 [1] https://wiki.apache.org/incubator/LensProposal?action=info For the record, the current contents of that version are appended below: -- cut here Lens Abstract Lens is a platform that enables multi-dimensional queries in a unified way over datasets stored in multiple warehouses. Lens integrates Apache Hive with other data warehouses by tiering them together to form logical data cubes. Proposal Lens provides a unified Cube abstraction for data stored in different stores. Lens tiers multiple data warehouses for unified representation and efficient access. It provides SQL-like Cube query language to query and describe data sets organized in data cubes. It enables users to run queries against Facts and Dimensions that can span multiple physical tables stored in different stores. The primary use cases that Lens aims to solve: Facilitate analytical queries by providing the OLAP like Cube abstraction Data Discovery by providing single metadata layer for data stored in different stores Unified access to data by integrating Hive with other traditional data warehouses Background Apache Hive is a data warehouse that facilitates querying and managing large datasets stored in distributed storage systems like HDFS. It provides SQL like language called HiveQL aka HQL. Apache Hive is a widely used platform in various organizations for doing adhoc analytical queries. In a typical Data warehouse scenario, the data is multi-dimensional and organized into Facts and Dimensions to form Data Cubes. Lens provides this logical layer to enable querying and manage data as Cubes. The Lens project is actively being developed at InMobi to provide the higher level of analytical abstraction to query data stored in different storages including Hive and beyond seamlessly. Rationale The Lens project aims to ease the analytical querying capabilities and cut the data-silos by providing a single view of data across multiple data stores. Conceiving data as a cube with hierarchical dimensions leads to conceptually straightforward operations to facilitate analysis. Integrating Apache Hive with other traditional warehouses provides the opportunity to optimize on the query execution cost by tiering the data across multiple warehouses. Lens provides Access to data Cubes via Cube Query language similar to HiveQL. Driver based architecture to allow for plugging systems like Hive and other warehouses such as columnar data RDBMS. Cost based engine selection that provides optimal use of resources by selecting the best execution engine for a given query. In a typical Data warehouse, data is organized in Cubes with multiple dimensions and measures. This facilitates the analysis by conceiving the data in terms of Facts and Dimensions instead of physical tables. Lens aims to provide this logical Cube abstraction on Data warehouses like Hive and other traditional warehouses. Initial Goals Donate the Lens source code and documentation to Apache Software Foundation Build a user and developer community Support Hive and other Columnar data warehouses Support full query life cycle management Add authentication for querying cubes Provide detailed query statistics Long Term Goals Here are some longer-term capabilities that would be added to Lens Add authorization for managing and querying Cubes Provide REST and CLI for full Admin controls Capability to schedule queries Query caching Integrate with Apache Spark. Creating Spark RDD from Lens query Integrate with Apache Optiq Current Status The project is actively developed at InMobi. The first version is deployed at InMobi 4 months back. This version allows querying dimension and fact data stored in Hive over CLI. The source code and documentation is hosted at GitHub. Meritocracy We intend to build a diverse developer and user community for the project following the Apache meritocracy model. We want to encourage contributors from multiple organizations, provide plenty of support to new developers and welcome them to be committers. Community Currently the project is being developed at InMobi. We hope to extend our contributor and user base significantly in the future and build a solid open source community around Lens. Core Developers Lens is currently being developed by Amareshwari Sriramadasu, Sharad Agarwal and Jaideep Dhok from InMobi, and Sreekanth Ramakrishnan who is currently employed by SoftwareAG. Raghavendra Singh from InMobi has built the QA automation for Lens. Alignment The ASF is a natural home to Lens as it is for Apache Hadoop, Apache Hive, Apache Spark and other emerging projects in Big Data space. We believe in any enterprise, multiple data warehouses will co-exist, as not all workloads are cost effective to run on single one. Apache Hive is one of the crucial data warehouse along with upcoming
Re: FW: [Proposal] Taverna workflow
Hi Stain, Great, I will continue the discussion there then. Thanks, Shameera. On Wed, Oct 15, 2014 at 7:46 AM, Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk wrote: Thanks, I have signed up to the Airavata Architecture mailing list to follow the discussion. If you could Reply to the existing thread I can chip in with a description of SCUFL2. On 30 September 2014 17:31, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Devs, Apache Airavata http://airavata.apache.org/ is a software framework for executing and managing computational jobs and workflows on distributed computing resources. Taverna's concern is not as much job coordination, but more of a data flow between services. Airavata's XBaya Workflow Suite can export workflows in Taverna 1 format SCUFL, but could be updated to work with Taverna 3's SCUFL2 format. I am a committer of Apache Airavata project and interesting to contribute for Airavata-SCUFL2 integrations. I already have started a mail [1] thread in apache Airavata architecture mailing list to explore the next generation workflow description language for Airavata which best support and suit for Scientific domains. [1] http://markmail.org/thread/tkpbj3sr4jhg6o6z Thanks, Shameera. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/-0001-9842-9718 -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
Re: [VOTE] Accept Taverna into the Apache Incubator
+1 (binding) Ralph On Oct 16, 2014, at 12:42 PM, Andy Seaborne a...@apache.org wrote: On 16/10/14 18:47, sebb wrote: Apart from the typo, I thought it was necessary for the VOTE thread to contain the full text of the proposal. This has been the case for (almost) all previous acceptance votes. The Lens one I copied from didn't :-) Version static link: https://wiki.apache.org/incubator/TavernaProposal?rev=10 and copied below. Andy I assume the text is required so the mail archives have a full record of what was actually voted on. The Wiki page might subsequently change or be deleted. 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 desktop application written in Java for graphically composing, editing and executing workflows composed of distributed Web services and local tools * Taverna Command Line Tool, which allows execution of workflows from a command line * Taverna Server, which provides a REST and SOAP API for executing workflows * Taverna Player, a Web interface the Taverna Server written in Ruby towards, providing a high-level view of workflow executions and their results and allowing further integrations with other Ruby on Rails applications Taverna allows browsing through and combining different service types in workflows, allowing them to integrate steps of arbitrary REST and SOAP Web services with command line tools (local and via SSH), scripts (Beanshell, R, Jython), and finally to visualize the results. The goal of the Taverna suite is to help researchers to access distributed datasets and processing capabilities by the construction of (data) 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 the 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 connected with arrows representing processes (i.e. executable services) and their data connections. 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 or 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) Fully investigate/resolve incompatibly licensed dependencies Stage git repositories for move at https://github.com/taverna-incubator : Update headers/metadata to indicate Apache License 2.0 Restructure git repositories (to ~ 10 repos?) Rename Maven groupIds to org.apache.taverna.* Rename packages to org.apache.taverna.* Move staged Github repositories to Apache git Automated builds in Apache's Jenkins
Re: [VOTE] Accept Taverna into the Apache Incubator
+1 binding Sent from my iPhone On Oct 16, 2014, at 8:54 AM, Andy Seaborne a...@apache.org wrote: Following the discussion earlier in the thread: https://www.mail-archive.com/general@incubator.apache.org/msg45241.html I would like to call a Vote for accepting Taverna as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/TavernaProposal Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... Only Votes from Incubator PMC members are binding, but everyone is welcome to contribute to the process. Andy - 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
