Re: [RESTART] [VOTE] Graduate Apache Beam

[Sandeep Deshmukh]

+1 (non-binding)

Regards,
Sandeep

On Tue, Dec 6, 2016 at 6:24 PM, Stian Soiland-Reyes 
wrote:

> +1 (binding)
>
> On 5 December 2016 at 23:30, Davor Bonaci  wrote:
> > Hi everyone,
> > Please vote on the draft resolution proposed by the Apache Beam PPMC
> below,
> > which establishes Apache Beam as a new top-level project at the Apache
> > Software Foundation, as follows:
> >
> > [ ] +1, Graduate Apache Beam from the Incubator.
> > [ ] +0, Don't care.
> > [ ] -1, Don't graduate Apache Beam from the Incubator because...
> >
> > Please note that this is a restarted vote, per John's request, to clarify
> > the alternatives. The old voting thread is archived [1].
> >
> > Before voting, please see the full text of the draft resolution below and
> > the corresponding discussion thread [2], and vote only after you feel
> ready
> > to do so. The vote will be open for at least 72 hours. This is a
> procedural
> > vote [3]; it is adopted by a simple majority of qualified votes (with no
> > minimum).
> >
> > If approved by the Apache Incubator, the proposed resolution will be
> > submitted to the Board of Directors for their consideration.
> >
> > Thank you!
> >
> > Davor
> >
> > [1]
> > https://lists.apache.org/thread.html/a8e9cecfe93f0e464cc7c1774d2761
> ca14326df1101b7670ca8b1dc3@%3Cgeneral.incubator.apache.org%3E
> > [2]
> > https://lists.apache.org/thread.html/b9c1071b35558846836814575ada3c
> dca61c72dc1e672ab994a9c936@%3Cgeneral.incubator.apache.org%3E
> > [3] http://apache.org/foundation/voting.html
> >
> > The full-text of the draft resolution proposed by the Apache Beam PPMC:
> >
> > X. Establish the Apache Beam 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 a unified programming model for both
> >batch and streaming data processing, enabling efficient
> >execution across diverse distributed execution engines
> >and providing extensibility points for connecting to different
> >technologies and user communities.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >Committee (PMC), to be known as the "Apache Beam Project",
> >be and hereby is established pursuant to Bylaws of the
> >Foundation; and be it further
> >
> >RESOLVED, that the Apache Beam Project be and hereby is
> >responsible for the creation and maintenance of software
> >related to a unified programming model for both batch and
> >streaming data processing, enabling efficient execution across
> >diverse distributed execution engines and providing extensibility
> >points for connecting to different technologies and user
> >communities; and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache Beam" 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 Beam Project, and to have primary responsibility
> >for management of the projects within the scope of
> >responsibility of the Apache Beam 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 Beam Project:
> >
> >  * Tyler Akidau 
> >  * Davor Bonaci 
> >  * Robert Bradshaw 
> >  * Ben Chambers 
> >  * Luke Cwik 
> >  * Stephan Ewen 
> >  * Dan Halperin 
> >  * Kenneth Knowles 
> >  * Aljoscha Krettek 
> >  * Maximilian Michels 
> >  * Jean-Baptiste Onofré 
> >  * Frances Perry 
> >  * Amit Sela 
> >  * Josh Wills 
> >
> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci
> >be appointed to the office of Vice President, Apache Beam, 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 Beam PMC be and hereby is
> >tasked with the creation of a set of bylaws intended to
> >encourage open development and increased 

Re: [VOTE] Accept CarbonData into the Apache Incubator

[Sandeep Deshmukh]

+1 (non-binding)

Regards,
Sandeep

On Mon, May 30, 2016 at 7:04 PM, lidong  wrote:

> +1 (non-binding)
>
>
> Thanks,
> Dong
> ---
> Apache Kylin - http://kylin.apache.org
> Kyligence Inc. - http://kyligence.io
>
>
> Original Message
> Sender:Jean-Baptiste Onofréj...@nanthrax.net
> Recipient:generalgene...@incubator.apache.org
> Date:Monday, May 30, 2016 14:07
> Subject:Re: [VOTE] Accept CarbonData into the Apache Incubator
>
>
> My own +1 (binding) ;) Regards JB On 05/25/2016 10:24 PM, Jean-Baptiste
> Onofré wrote:  Hi all,   following the discussion thread, I'm now calling a
> vote to accept  CarbonData into the Incubator.   ​[ ] +1 Accept CarbonData
> into the Apache Incubator  [ ] +0 Abstain  [ ] -1 Do not accept CarbonData
> into the Apache Incubator, because ...   This vote is open for 72 hours.
>  The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/CarbonDataProposal   Thanks !  Regards
> JB   = Apache CarbonData =   == Abstract ==   Apache CarbonData is a new
> Apache Hadoop native file format for faster  interactive  query using
> advanced columnar storage, index, compression and encoding  techniques  to
> improve computing efficiency, in turn it will help speedup queries an
> order of  magnitude faster over PetaBytes of data.   CarbonData github
> address: https://github.com/HuaweiBigData/carbondata   == Background ==
>  Huawei is an ICT solution provider, we are committed to enhancing
> customer experiences for telecom carriers, enterprises, and consumers on
> big data, In order to satisfy the following customer requirements, we
> created a new Hadoop native file format:   * Support interactive OLAP-style
> query over big data in seconds.  * Support fast query on individual record
> which require touching all  fields.  * Fast data loading speed and support
> incremental load in period of  minutes.  * Support HDFS so that customer
> can leverage existing Hadoop cluster.  * Support time based data
> retention.   Based on these requirements, we investigated existing file
> formats in  the Hadoop eco-system, but we could not find a suitable
> solution that  satisfying requirements all at the same time, so we start
> designing  CarbonData.   == Rationale ==   CarbonData contains multiple
> modules, which are classified into two  categories:   1. CarbonData File
> Format: which contains core implementation for file  format such as
> columnar,index,dictionary,encoding+compression,API for  reading/writing
> etc.  2. CarbonData integration with big data processing framework such as
> Apache Spark, Apache Hive etc. Apache Beam is also planned to abstract  the
> execution runtime.   === CarbonData File Format ===   CarbonData file
> format is a columnar store in HDFS, it has many features  that a modern
> columnar format has, such as splittable, compression  schema ,complex data
> type etc. And CarbonData has following unique  features:    Indexing
>    In order to support fast interactive query, CarbonData leverage
> indexing  technology to reduce I/O scans. CarbonData files stores data
> along with  index, the index is not stored separately but the CarbonData
> file itself  contains the index. In current implementation, CarbonData
> supports 3  types of indexing:   1. Multi-dimensional Key (B+ Tree index)
> The Data block are written in sequence to the disk and within each  data
> blocks each column block is written in sequence. Finally, the  metadata
> block for the file is written with information about byte  positions of
> each block in the file, Min-Max statistics index and the  start and end MDK
> of each data block. Since, the entire data in the file  is in sorted order,
> the start and end MDK of each data block can be used  to construct a B+Tree
> and the file can be logically represented as a  B+Tree with the data blocks
> as leaf nodes (on disk) and the remaining  non-leaf nodes in memory.  2.
> Inverted index  Inverted index is widely used in search engine. By using
> this index,  it helps processing/query engine to do filtering inside one
> HDFS block.  Furthermore, query acceleration for count distinct like
> operation is  made possible when combining bitmap and inverted index in
> query time.  3. MinMax index  For all columns, minmax index is created so
> that processing/query  engine can skip scan that is not required.   
> Global Dictionary    Besides I/O reduction, CarbonData accelerates
> computation by using  global dictionary, which enables processing/query
> engines to perform all  processing on encoded data without having to
> convert the data (Late  Materialization). We have observed dramatic
> performance improvement for  OLAP analytic scenario where table contains
> many columns in string data  type. The data is converted back to the user
> readable form just before  processing/query engine returning results to
> user.    Column Group    Sometimes users want to perform
> processing/query on 

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Sandeep Deshmukh]

+ 1 (non-binding)

Regards,
Sandeep

On Wed, May 25, 2016 at 10:38 AM, Paul Fremantle  wrote:

> +1 (binding)
> Paul
>
> On Wed, May 25, 2016 at 5:12 AM, Tsuyoshi Ozawa  wrote:
>
> > +1 (non-binding)
> > - Tsuyoshi
> >
> > On Wed, May 25, 2016 at 1:00 PM, Reynold Xin 
> wrote:
> > > +1 (binding)
> > >
> > >
> > > On Mon, May 23, 2016 at 3:22 PM, Andrew Purtell 
> > wrote:
> > >
> > >> Since discussion on the matter of PredictionIO has died down, I would
> > like
> > >> to call a VOTE
> > >> on accepting PredictionIO into the Apache Incubator.
> > >>
> > >> Proposal: https://wiki.apache.org/incubator/PredictionIO
> > >>
> > >> [ ] +1 Accept PredictionIO into the Apache Incubator
> > >> [ ] +0 Abstain
> > >> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because
> ...
> > >>
> > >> This vote will be open for at least 72 hours.
> > >>
> > >> My vote is +1 (binding)
> > >>
> > >> --
> > >>
> > >> PredictionIO Proposal
> > >>
> > >> Abstract
> > >>
> > >> PredictionIO is an open source Machine Learning Server built on top of
> > >> state-of-the-art open source stack, that enables developers to manage
> > and
> > >> deploy production-ready predictive services for various kinds of
> machine
> > >> learning tasks.
> > >>
> > >> Proposal
> > >>
> > >> The PredictionIO platform consists of the following components:
> > >>
> > >>* PredictionIO framework - provides the machine learning stack for
> > >>  building, evaluating and deploying engines with machine learning
> > >>  algorithms. It uses Apache Spark for processing.
> > >>
> > >>* Event Server - the machine learning analytics layer for unifying
> > >> events
> > >>  from multiple platforms. It can use Apache HBase or any JDBC
> > backends
> > >>  as its data store.
> > >>
> > >> The PredictionIO community also maintains a Template Gallery, a place
> to
> > >> publish and download (free or proprietary) engine templates for
> > different
> > >> types of machine learning applications, and is a complemental part of
> > the
> > >> project. At this point we exclude the Template Gallery from the
> > proposal,
> > >> as it has a separate set of contributors and we’re not familiar with
> an
> > >> Apache approved mechanism to maintain such a gallery.
> > >>
> > >> Background
> > >>
> > >> PredictionIO was started with a mission to democratize and bring
> machine
> > >> learning to the masses.
> > >>
> > >> Machine learning has traditionally been a luxury for big companies
> like
> > >> Google, Facebook, and Netflix. There are ML libraries and tools lying
> > >> around the internet but the effort of putting them all together as a
> > >> production-ready infrastructure is a very resource-intensive task that
> > is
> > >> remotely reachable by individuals or small businesses.
> > >>
> > >> PredictionIO is a production-ready, full stack machine learning system
> > that
> > >> allows organizations of any scale to quickly deploy machine learning
> > >> capabilities. It comes with official and community-contributed machine
> > >> learning engine templates that are easy to customize.
> > >>
> > >> Rationale
> > >>
> > >> As usage and number of contributors to PredictionIO has grown bigger
> and
> > >> more diverse, we have sought for an independent framework for the
> > project
> > >> to keep thriving. We believe the Apache foundation is a great fit.
> > Joining
> > >> Apache would ensure that tried and true processes and procedures are
> in
> > >> place for the growing number of organizations interested in
> contributing
> > >> to PredictionIO. PredictionIO is also a good fit for the Apache
> > foundation.
> > >> PredictionIO was built on top of several Apache projects (HBase,
> Spark,
> > >> Hadoop). We are familiar with the Apache process and believe that the
> > >> democratic and meritocratic nature of the foundation aligns with the
> > >> project goals.
> > >>
> > >> Initial Goals
> > >>
> > >> The initial milestones will be to move the existing codebase to Apache
> > and
> > >> integrate with the Apache development process. Once this is
> > accomplished,
> > >> we plan for incremental development and releases that follow the
> Apache
> > >> guidelines, as well as growing our developer and user communities.
> > >>
> > >> Current Status
> > >>
> > >> PredictionIO has undergone nine minor releases and many patches.
> > >> PredictionIO is being used in production by Salesforce.com as well as
> > many
> > >> other organizations and apps. The PredictionIO codebase is currently
> > >> hosted at GitHub, which will form the basis of the Apache git
> > repository.
> > >>
> > >> Meritocracy
> > >>
> > >> We plan to invest in supporting a meritocracy. We will discuss the
> > >> requirements in an open forum. We intend to invite additional
> developers
> > >> to participate. We will encourage and monitor community participation
> so
> > >> that privileges can be 

Re: [VOTE] Graduate Apex from the Incubator

[Sandeep Deshmukh]

+1

On Wed, Mar 30, 2016 at 6:52 AM, P. Taylor Goetz  wrote:

> +1 (binding) (Though my vote from dev@ can carry over)
>
> Nice work by the Apex community.
>
> -Taylor
>
> > On Mar 28, 2016, at 5:20 PM, Pramod Immaneni  wrote:
> >
> > The Apache Apex community has discussed and voted on graduation to top
> > level project.
> > The vote passed with 42 +1 votes (12 from the PPMC) and no 0 or -1 votes.
> >
> > Maturity Assessment:
> > http://apex.incubator.apache.org/maturity.html
> > Discussion:
> > https://s.apache.org/qrvY
> > Vote:
> > https://s.apache.org/R8MR
> > Result:
> > https://s.apache.org/sJIC
> >
> > Please vote on the resolution pasted below to graduate Apache Apex
> > from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Apex from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Apex from the Incubator becauseÖ
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> >
> > Pramod Immaneni, for the Apache Apex PPMC
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Quarks into the Apache Incubator

[Sandeep Deshmukh]

ience with Apache, including
> > a developer who is a committer on Derby and an Apache member.  All of
> the
> > core developers have some level of experience with the use of open
> source
> > packages and with contributions on projects on sites such as  GitHub.
> >
> >  Homogenous Developers 
> >  . The initial set of developers come from one company, but we are
> > committed to finding a diverse set of committers and contributors. The
> > current developers are already very familiar with working with many
> > geographies, including developers in most geographies around the world.
> >  They  are also very comfortable working in a distributed environment.
> >
> >  Reliance on Salaried Developers 
> >  . Quarks currently relies on salaried developers at this time, but we
> > expect that Quarks will attract a diverse mix of contributors going
> > forward.   For Quarks to fully transition to an "Apache Way" governance
> > model, we will embrace the meritocracy-centric way of growing the
> community
> > of contributors.
> >
> >  Relationships with Other Apache Products 
> >  . These Apache projects are used by the current codebase:
> >  .
> >  * Apache Ant - Build
> >  * Apache Common Math - Initial analytics
> >  * Apache HTTP Components HttpClient - HTTP connectivity
> >  * Apache Kafka - Kafka is supported as a message hub between edge Quarks
> > applications and back-end analytics systems Events from Quarks
> applications
> > sent through message hubs (such as  Apache Kafka) may be consumed by
> > back-end systems such as Apache Flink, Apache Spark, Apache Samza, Apache
> > Storm, Beam (in  incubation) or others.
> >
> >  A Excessive Fascination with the Apache Brand 
> >  . Quarks will benefit greatly from wide collaboration with developers
> > working in the device space.  We feel the Apache brand will help attract
> > those developers who really want to contribute to this space.  Several
> > developers involved with this project have a very positive history with
> > Derby and feel that Apache is the right place to grow the Quarks
> > community.  We will respect Apache brand policies and follow the Apache
> > way.
> >
> > === Documentation ===
> >  . http://quarks-edge.github.io/quarks.documentation
> >
> > === Initial Source ===
> >  . Quarks code has been recently released on Github under the Apache 2.0
> > license at https://github.com/quarks-edge/quarks . It was created by a
> > small team of developers, and is written in Java.
> >
> > === Source and Intellectual Property Submission Plan ===
> >  . After acceptance into the incubator, IBM will execute a Software Grant
> > Agreement and the source code will be transitioned to the Apache
> > infrastructure. The code is already licensed under the Apache Software
> > License, version 2.0. We do not know of any legal issues that would
> > inhibit the transfer to the ASF.
> >
> > === External Dependencies ===
> >  . The dependencies all have Apache compatible license. These include
> > Apache, MIT and EPL. The current dependencies are:
> >  * D3
> >  * Jetty
> >  * Apache Kafka
> >  * Metrics
> >  * MQTTV3
> >  * SLF4J
> >  * GSON
> >  * Apache commons Math3
> >  .
> >  . Development tools are
> >  .
> >  * Java SDK 8
> >  * Eclipse 4.5
> >  * Ant 1.9
> >  * Junit 4.10
> >
> > === Cryptography ===
> >  . No cryptographic code is involved with Quarks.
> >
> > === Required Resources ===
> >  Mailing lists 
> >  . priv...@quarks.incubator.apache.org (with moderated subscriptions)
> >  . d...@quarks.incubator.apache.org
> >  . comm...@quarks.incubator.apache.org
> >
> >  Git Repository 
> >  . https://git-wip-us.apache.org/repos/asf/incubator-quarks.git
> >
> >  Issue Tracking 
> >  . Jira Project Quarks (QUARKS)
> >
> >  Other Resources 
> >  . Means of setting up regular builds and test cycle.
> >
> > === Initial Committers ===
> >  .
> >  * Daniel Debrunner:  djd at apache dot org -  CLA on file
> >  * Susan Cline:  home4slc at pacbell dot net  - CLA on file
> >  * William Marshall:  wcmarsha at gmail dot com  - CLA on file
> >  * Victor Dogaru:  vdogaru at gmail dot com - CLA on file
> >  * Dale LaBossiere:  dml.apache at gmail dot com  - CLA on file
> >
> > === Affiliations ===
> >  * Daniel Debrunner IBM
> >  * Susan Cline IBM
> >  * William Marshall IBM
> >  * Victor Dogaru  IBM
> >  * Dale Labossiere IBM
> >
> > === Additional Interested Contributors ===
> >  * May Wone: mnwone at gmail dot com
> >  * Sandeep Deshmukh: sandeep at datatorrent dot com
> >  * Bhupesh Chawda: bhupeshchawda at gmail dot com
> >
> > === Sponsors ===
> >  Champion 
> >  . Katherine Marsden (kmarsden at apache dot org)
> >
> >  Nominated Mentors 
> >  * Katherine Marsden (kmarsden at apache dot org)
> >  * Daniel Debrunner (djd at apache dot org)
> >  * Luciano Resende (lresende at apache dot org)
> >  * Justin Mclean (justin at classsoftware dot com)
> >
> >  Sponsoring Entity 
> >  . The Incubator
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [DISCUSS] Quarks proposal

[Sandeep Deshmukh]

Hi All,

I would be happy to be part of this interesting project. Processing at the
edge nodes is going to help a lot in analyzing @ scaling in  IoT space.

While going through the proposal, I noticed following:

   1. Email id of Daniel Debrunner is djd at *apache* dot *com*. Should
   that be dot *org* ?
   2. Same with email id of Dale LaBossiere

Regards,
Sandeep

On Tue, Feb 16, 2016 at 6:35 AM, Katherine Marsden 
wrote:

> On 2/15/2016 4:59 PM, Katherine Marsden wrote:
>
>> Find below a draft proposal for a new incubator project, Quarks for
>> discussion.  Quarks is seeking experienced mentors  as well as contributors
>> to the project.  Please discuss and provide feedback. The proposal is also
>> available on the Wiki at https://wiki.apache.org/incubator/QuarksProposal
>> 
>>
>> Please forgive. The JoshuaProposal link was erroneous. I am not sure how
> that got in there.
> Only https://wiki.apache.org/incubator/QuarksProposal is relevant.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Write access to incubator wiki

[Sandeep Deshmukh]

Hi,

Can someone please give write access to incubator wiki? My id is
: SandeepDeshmukh

Regards,
Sandeep

Re: [VOTE] Apache Apex Core Release 3.2.0-incubating (RC2)

[Sandeep Deshmukh]

+1 ( binding as committer)

Regards,
Sandeep

On Fri, Oct 30, 2015 at 6:55 AM, Pramod Immaneni 
wrote:

> +1 carrying over from PPMC
>
> Thanks
>
> On Tue, Oct 27, 2015 at 1:39 PM, Thomas Weise  wrote:
>
> > Hi,
> >
> > Please vote on the following Apache Apex Core 3.2.0-incubating release
> > candidate. This is the first release after incubation. This is a source
> > release.
> >
> > The Apache Apex PPMC has voted to release this candidate.
> >
> > The community vote passed with 6 binding votes from the PPMC (including 3
> > votes from IPMC members). There were another 9 committer votes in favor
> of
> > the release.
> >
> > PPMC vote call:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDM5wnzmz8CcVbv6d2QM%2BAsaJ6pQ3EyG%2B8XRbSwYkfPX_g%40mail.gmail.com%3E
> >
> > PPMC vote result:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-apex-dev/201510.mbox/%3CCAKJfLDOY-SpcJfdFiJosoyZ2JidursecietvhT5AgUeX-%3Dw-Tw%40mail.gmail.com%3E
> >
> >
> > List of all issues fixed: http://s.apache.org/SRM
> >
> > Staging directory:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/
> > Source zip:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.zip
> > Source tar.gz:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apex/v3.2.0-incubating-RC2/apex-3.2.0-incubating-source-release.tar.gz
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheapex-1001/
> >
> > Git source:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.2.0-incubating-RC2
> >   (commit: d61ca617fd44bf9d74800838341f92018f2c7d10)
> >
> > PGP key:
> > *http://pgp.mit.edu:11371/pks/lookup?op=vindex=t...@apache.org
> > *
> > KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
> >
> > More information at:
> > http://apex.incubator.apache.org
> >
> >
> > Please try the release and vote; vote will close after 72 hours.
> >
> > [ ] +1 approve
> > [ ] -1 disapprove (and reason why)
> >
> > http://www.apache.org/foundation/voting.html
> >
> > Please add (binding) if your vote is binding.
> >
> > Thanks,
> > Thomas
> >
>