[RESULT][VOTE] Accept Apache Atlas into Apache Incubator

[Seetharam Venkatesh]

Hi folks,

With nine +1 binding votes, six +1 non-binding votes, (fifteen +1 votes
total) NO +/-0 or -1 votes, this VOTE PASSES.

Thanks to all who voted! Here's a tally of +1 binding votes:

Jitendra Pandey
Alan Gates
Jan I
Taylor Goetz
Arun C Murthy
Jean-Baptiste Onofre
Suresh Srinivas
Sharad Agarwal
Amareshwari

Non-binding:
Dilli Arumugam
Shwetha Shivalingamurthy
Venkatesh Seetharam
Ajay Yadav
Venkat Ranganathan
Suma Shivaprasad

Thanks!

On Fri, May 1, 2015 at 12:26 AM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> Hello folks,
>
> Following the discussion earlier in the thread: http://s.apache.org/r2
>
> I would like to call a VOTE for accepting Apache Atlas as a new incubator
> project.
>
> The proposal is available at:
> https://wiki.apache.org/incubator/AtlasProposal
> Also, the text of the latest wiki proposal is included at the bottom of
> this email.
>
> The VOTE is open for at least the next 72 hours:
>
>  [ ] +1 accept Apache Atlas into the Apache Incubator
>  [ ] ±0 Abstain
>  [ ] -1 because...
>
> Of course I am +1! (non-binding)
>
> Thanks!
>
>
> = Apache Atlas Proposal =
>
> == Abstract ==
>
> Apache Atlas is a scalable and extensible set of core foundational
> governance services that enables enterprises to effectively and efficiently
> meet their compliance requirements within Hadoop and allows integration
> with the complete enterprise data ecosystem.
>
> == Proposal ==
>
> Apache Atlas allows agnostic governance visibility into Hadoop, these
> abilities are enabled through a set of core foundational services powered
> by a flexible metadata repository.
>
> These services include:
>
>  * Search and Lineage for datasets
>  * Metadata driven data access control
>  * Indexed and Searchable Centralized Auditing operational Events
>  * Data lifecycle management – ingestion to disposition
>  * Metadata interchange with other metadata tools
>
> == Background ==
>
> Hadoop is one of many platforms in the modern enterprise data ecosystem
> and requires governance controls commensurate with this reality.
>
> Currently, there is no easy or complete way to provide comprehensive
> visibility and control into Hadoop audit, lineage, and security for
> workflows that require Hadoop and non-Hadoop processing.
>
> Many solutions are usually point based, and require a monolithic
> application workflow.  Multi-tenancy and concurrency are problematic as
> these offerings are not aware of activity outside of their narrow focus.
>
> As Hadoop gains greater popularity, governance concerns will become
> increasingly vital to increasing maturity and furthering adoption. It is a
> particular barrier to expanding enterprise data under management.
>
> == Rationale ==
>
> Atlas will address issues previously discussed by providing governance
> capabilities in Hadoop -- using both a prescriptive and forensic model
> enriched by business taxonomical metadata.Atlas, at its core, is
> designed to exchange metadata with other tools and processes within and
> outside of the Hadoop stack -- enable governance controls that are truly
> platform agnostic and effectively (and defensibly) address compliance
> concerns.
>
> Initially working with a group of leading partners in several industries,
> Atlas is built to solve specific real world governance problems that
> accelerate product maturity and time to value.
>
> Atlas aims to grow a community to help build a widely adopted pattern for
> governance, metadata modeling and exchange in Hadoop – which will advance
> the interests for the whole community.
>
> == Current Status ==
>
> An initial version with a valuable set of features is developed by the
> list of initial committers and is hosted on github.
>
> === Meritocracy ===
>
> Our intent with this proposal is to start building a diverse  developer
> community around Atlas following the Apache meritocracy model. We have
> wanted to make the project open source and encourage contributors from
> multiple organizations from the start.
>
> We plan to provide plenty of support to new developers and to quickly
> recruit those who make solid contributions to committer status.
>
> === Community ===
>
> We are happy to report that the initial team already represents multiple
> organizations. We hope to extend the user and developer base further in the
> future and build a solid open source community around Atlas.
>
> === Core Developers ===
>
> Atlas development is currently being led by engineers from Hortonworks –
> Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
> engineers have deep expertise in Hadoop and are quite familiar with the
> Hadoop Ecosystem.
>
> === Alignment ===
>
> The ASF is a natural host for Atlas given that it is already the home of
> Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
> data” software projects.
>
> Atlas has been designed to solve the data governance challenges and
> opportunities of the Hadoop ecosystem family of products as well a

[ANNOUNCE] Apache Lens 2.1.0-beta-incubating released

[Amareshwari Sriramdasu]

Hi all,

The Apache Lens team is proud to announce the release of Apache Lens
2.1.0-beta-incutaing. This is the second release of Apache Lens.

Apache Lens provides an Unified Analytics interface. Its a platform
which enables multi-dimensional queries in a unified way over datasets
stored in multiple warehouses. Lens aims to cut the data Analytics
silos by providing a single view of data across multiple tiered data
stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to
appear like one.

More details on Apache Lens can be found at http://lens.incubator.apache.org/

Getting started available at
http://lens.incubator.apache.org/lenshome/quick-start.html

The release artifacts are downloadable from
http://lens.incubator.apache.org/releases/download.html

Maven jar artifacts have also been made available on
https://repository.apache.org/content/repositories/releases/org/apache/lens/

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923&version=12328991

We would like to thank all the contributors who made this release possible.

Thanks,
The Apache Lens team

-

DISCLAIMER

Apache Lens is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by  Apache Incubator. Incubation is
required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.

Re: [VOTE] Release of Apache Lens 2.1.0-beta-incubating

[amareshwarisr .]

Hello Justin,

Thanks for reporting the minor issues. We will look into them and try
fixing them by next release.

Thanks
Amareshwari

On Sat, May 2, 2015 at 7:03 AM, Justin Mclean  wrote:

> Hi,
>
> +1 binding
>
>
> I did have issues getting the tests to run with this error, but I’d assume
> it’s just my setup.
> "There is no database named testqueryrewrite)”
>
You may want to add a little more information the README on running the
> tests and what is required. You might also want to suggest recommended
> values for MAVEN_OPTS.
>
> Binary LICENSE and NOTICE  are comprehensive and seem correct, but I did't
> check every detail.
>
> (Very) minor issues:
> - MD5 content is oddly formatted (make comparison a little harder)
> - Signed email has "(Works for Hadoop and ecosystem)” which is probably
> not needed
> - Pom.xml lists developers and their companies, software is developed by
> individuals at the the ASF
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Suma Shivaprasad]

+1(non binding)

Thanks
Suma

On Tue, May 5, 2015 at 8:23 PM, Venkat Ranganathan <
vranganat...@hortonworks.com> wrote:

> +1 (non binding)
>
> Minor nit: Please update my email address to venkatran...@apache.org
>
> Thanks
>
> Venkat
>
>
>
> On 5/1/15, 12:26 AM, "Seetharam Venkatesh" 
> wrote:
>
> >Hello folks,
> >
> >Following the discussion earlier in the thread: http://s.apache.org/r2
> >
> >I would like to call a VOTE for accepting Apache Atlas as a new incubator
> >project.
> >
> >The proposal is available at:
> >https://wiki.apache.org/incubator/AtlasProposal
> >Also, the text of the latest wiki proposal is included at the bottom of
> >this email.
> >
> >The VOTE is open for at least the next 72 hours:
> >
> > [ ] +1 accept Apache Atlas into the Apache Incubator
> > [ ] ±0 Abstain
> > [ ] -1 because...
> >
> >Of course I am +1! (non-binding)
> >
> >Thanks!
> >
> >
> >= Apache Atlas Proposal =
> >
> >== Abstract ==
> >
> >Apache Atlas is a scalable and extensible set of core foundational
> >governance services that enables enterprises to effectively and
> efficiently
> >meet their compliance requirements within Hadoop and allows integration
> >with the complete enterprise data ecosystem.
> >
> >== Proposal ==
> >
> >Apache Atlas allows agnostic governance visibility into Hadoop, these
> >abilities are enabled through a set of core foundational services powered
> >by a flexible metadata repository.
> >
> >These services include:
> >
> > * Search and Lineage for datasets
> > * Metadata driven data access control
> > * Indexed and Searchable Centralized Auditing operational Events
> > * Data lifecycle management – ingestion to disposition
> > * Metadata interchange with other metadata tools
> >
> >== Background ==
> >
> >Hadoop is one of many platforms in the modern enterprise data ecosystem
> and
> >requires governance controls commensurate with this reality.
> >
> >Currently, there is no easy or complete way to provide comprehensive
> >visibility and control into Hadoop audit, lineage, and security for
> >workflows that require Hadoop and non-Hadoop processing.
> >
> >Many solutions are usually point based, and require a monolithic
> >application workflow.  Multi-tenancy and concurrency are problematic as
> >these offerings are not aware of activity outside of their narrow focus.
> >
> >As Hadoop gains greater popularity, governance concerns will become
> >increasingly vital to increasing maturity and furthering adoption. It is a
> >particular barrier to expanding enterprise data under management.
> >
> >== Rationale ==
> >
> >Atlas will address issues previously discussed by providing governance
> >capabilities in Hadoop -- using both a prescriptive and forensic model
> >enriched by business taxonomical metadata.Atlas, at its core, is
> >designed to exchange metadata with other tools and processes within and
> >outside of the Hadoop stack -- enable governance controls that are truly
> >platform agnostic and effectively (and defensibly) address compliance
> >concerns.
> >
> >Initially working with a group of leading partners in several industries,
> >Atlas is built to solve specific real world governance problems that
> >accelerate product maturity and time to value.
> >
> >Atlas aims to grow a community to help build a widely adopted pattern for
> >governance, metadata modeling and exchange in Hadoop – which will advance
> >the interests for the whole community.
> >
> >== Current Status ==
> >
> >An initial version with a valuable set of features is developed by the
> list
> >of initial committers and is hosted on github.
> >
> >=== Meritocracy ===
> >
> >Our intent with this proposal is to start building a diverse  developer
> >community around Atlas following the Apache meritocracy model. We have
> >wanted to make the project open source and encourage contributors from
> >multiple organizations from the start.
> >
> >We plan to provide plenty of support to new developers and to quickly
> >recruit those who make solid contributions to committer status.
> >
> >=== Community ===
> >
> >We are happy to report that the initial team already represents multiple
> >organizations. We hope to extend the user and developer base further in
> the
> >future and build a solid open source community around Atlas.
> >
> >=== Core Developers ===
> >
> >Atlas development is currently being led by engineers from Hortonworks –
> >Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
> >engineers have deep expertise in Hadoop and are quite familiar with the
> >Hadoop Ecosystem.
> >
> >=== Alignment ===
> >
> >The ASF is a natural host for Atlas given that it is already the home of
> >Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
> >data” software projects.
> >
> >Atlas has been designed to solve the data governance challenges and
> >opportunities of the Hadoop ecosystem family of products as well as
> >integration to the tradition Enterprise Data ecosystem.
> >
> >Atlas fi

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[amareshwarisr .]

+1 (binding)

Thanks
Amareshwari

On Fri, May 1, 2015 at 12:56 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> Hello folks,
>
> Following the discussion earlier in the thread: http://s.apache.org/r2
>
> I would like to call a VOTE for accepting Apache Atlas as a new incubator
> project.
>
> The proposal is available at:
> https://wiki.apache.org/incubator/AtlasProposal
> Also, the text of the latest wiki proposal is included at the bottom of
> this email.
>
> The VOTE is open for at least the next 72 hours:
>
>  [ ] +1 accept Apache Atlas into the Apache Incubator
>  [ ] ±0 Abstain
>  [ ] -1 because...
>
> Of course I am +1! (non-binding)
>
> Thanks!
>
>
> = Apache Atlas Proposal =
>
> == Abstract ==
>
> Apache Atlas is a scalable and extensible set of core foundational
> governance services that enables enterprises to effectively and efficiently
> meet their compliance requirements within Hadoop and allows integration
> with the complete enterprise data ecosystem.
>
> == Proposal ==
>
> Apache Atlas allows agnostic governance visibility into Hadoop, these
> abilities are enabled through a set of core foundational services powered
> by a flexible metadata repository.
>
> These services include:
>
>  * Search and Lineage for datasets
>  * Metadata driven data access control
>  * Indexed and Searchable Centralized Auditing operational Events
>  * Data lifecycle management – ingestion to disposition
>  * Metadata interchange with other metadata tools
>
> == Background ==
>
> Hadoop is one of many platforms in the modern enterprise data ecosystem and
> requires governance controls commensurate with this reality.
>
> Currently, there is no easy or complete way to provide comprehensive
> visibility and control into Hadoop audit, lineage, and security for
> workflows that require Hadoop and non-Hadoop processing.
>
> Many solutions are usually point based, and require a monolithic
> application workflow.  Multi-tenancy and concurrency are problematic as
> these offerings are not aware of activity outside of their narrow focus.
>
> As Hadoop gains greater popularity, governance concerns will become
> increasingly vital to increasing maturity and furthering adoption. It is a
> particular barrier to expanding enterprise data under management.
>
> == Rationale ==
>
> Atlas will address issues previously discussed by providing governance
> capabilities in Hadoop -- using both a prescriptive and forensic model
> enriched by business taxonomical metadata.Atlas, at its core, is
> designed to exchange metadata with other tools and processes within and
> outside of the Hadoop stack -- enable governance controls that are truly
> platform agnostic and effectively (and defensibly) address compliance
> concerns.
>
> Initially working with a group of leading partners in several industries,
> Atlas is built to solve specific real world governance problems that
> accelerate product maturity and time to value.
>
> Atlas aims to grow a community to help build a widely adopted pattern for
> governance, metadata modeling and exchange in Hadoop – which will advance
> the interests for the whole community.
>
> == Current Status ==
>
> An initial version with a valuable set of features is developed by the list
> of initial committers and is hosted on github.
>
> === Meritocracy ===
>
> Our intent with this proposal is to start building a diverse  developer
> community around Atlas following the Apache meritocracy model. We have
> wanted to make the project open source and encourage contributors from
> multiple organizations from the start.
>
> We plan to provide plenty of support to new developers and to quickly
> recruit those who make solid contributions to committer status.
>
> === Community ===
>
> We are happy to report that the initial team already represents multiple
> organizations. We hope to extend the user and developer base further in the
> future and build a solid open source community around Atlas.
>
> === Core Developers ===
>
> Atlas development is currently being led by engineers from Hortonworks –
> Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
> engineers have deep expertise in Hadoop and are quite familiar with the
> Hadoop Ecosystem.
>
> === Alignment ===
>
> The ASF is a natural host for Atlas given that it is already the home of
> Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
> data” software projects.
>
> Atlas has been designed to solve the data governance challenges and
> opportunities of the Hadoop ecosystem family of products as well as
> integration to the tradition Enterprise Data ecosystem.
>
> Atlas fills the gap that the Hadoop Ecosystem has been lacking in the areas
> of data governance and compliance management.
>
> == Known Risks ==
>
> === Orphaned products & Reliance on Salaried Developers ===
> The core developers plan to work full time on the project. There is very
> little risk of Atlas getting orphaned.  A prototype of Atlas i

[RESULT] [VOTE] Release of Apache Lens 2.1.0-beta-incubating

[amareshwarisr .]

Hi all,

The vote is now closed and passed with 6 binding +1 votes, no -1 votes and
no 0 votes.
We now have the required number of positive binding votes and will therefore
proceed with publishing this release.

Thank you all for voting.

Binding votes :
+1 *Amareshwari Sriramadasu*
+1 Jean-Baptiste Onofré
+1 Justin Mclean
+1 *Chris Douglas*
+1 Jakob Homan
+1 *Sharad Agarwal*

Vote on incubator list :
*http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCABJEuZdM%3D56%2Bzx1_RT1NQ%2BxcwS_uuuiWXMBn7y-f%2BYRYGM3Amw%40mail.gmail.com%3E
*

Vote on dev list :
http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZfT4HDK3c4rKxPg0_Kkc8KDfRjUr%2BHmKaJH44H77OeU0g%40mail.gmail.com%3E

Thanks
Amareshwari

On Thu, Apr 30, 2015 at 5:35 PM, Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Hello everyone,
>
> This is the call for vote for the following RC to be released as official
> ApacheLens 2.1.0-beta-incubating release. This is our second release.
>
> Apache Lens provides an Unified Analytics interface. Lens aims to cut the
> Data Analytics silos by providing a single view of data across multiple
> tiered data stores and optimal execution environment for the analytical
> query. It seamlessly integrates Hadoop with traditional data warehouses to
> appear like one.
> Vote on dev list:
>
> http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZfT4HDK3c4rKxPg0_Kkc8KDfRjUr%2BHmKaJH44H77OeU0g%40mail.gmail.com%3E
>
> Results of vote on dev list:
>
> http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/201504.mbox/%3CCABJEuZe7rbjbwoiiOWKL8Lef%3Dsc%2BXcV173aiQ6Tpdwq7jz9ycQ%40mail.gmail.com%3E
>
> The commit id is fdd19b9c2b17e329465cbde62dbce6f8be435cec 
> :https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=commit;h=fdd19b9c2b17e329465cbde62dbce6f8be435cec
>
> This corresponds to the tag: apache-lens-2.1.0-beta-incubating 
> :https://git-wip-us.apache.org/repos/asf?p=incubator-lens.git;a=tag;h=refs/tags/apache-lens-2.1.0-beta-incubating
>
> The release archives (tar.gz/.zip), signature, and checksums are 
> here:https://dist.apache.org/repos/dist/dev/incubator/lens/apache-lens-2.1.0-beta-incubating-rc0
>
> You can find the KEYS file here:
> * https://dist.apache.org/repos/dist/release/incubator/lens/KEYS
>
> The release candidate consists of the following source distribution
> archive:
> apache-lens-2.1.0-beta-incubating-source-release.zip
>
> In addition, the following supplementary binary distributions are
> provided for user convenience at the same location:
> apache-lens-2.1.0-beta-incubating-bin.tar.gz
>
> The licensing of bundled bits in the archives have not changed from previous 
> release, which are documented at 
> https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachelens-1003
>
> Release notes available at 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923&version=12328991
>
>
> Vote will be open for at least 72 hours . Please vote on releasing this RC
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> Amareshwari
>

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Venkat Ranganathan]

+1 (non binding)

Minor nit: Please update my email address to venkatran...@apache.org

Thanks

Venkat



On 5/1/15, 12:26 AM, "Seetharam Venkatesh"  wrote:

>Hello folks,
>
>Following the discussion earlier in the thread: http://s.apache.org/r2
>
>I would like to call a VOTE for accepting Apache Atlas as a new incubator
>project.
>
>The proposal is available at:
>https://wiki.apache.org/incubator/AtlasProposal
>Also, the text of the latest wiki proposal is included at the bottom of
>this email.
>
>The VOTE is open for at least the next 72 hours:
>
> [ ] +1 accept Apache Atlas into the Apache Incubator
> [ ] ±0 Abstain
> [ ] -1 because...
>
>Of course I am +1! (non-binding)
>
>Thanks!
>
>
>= Apache Atlas Proposal =
>
>== Abstract ==
>
>Apache Atlas is a scalable and extensible set of core foundational
>governance services that enables enterprises to effectively and efficiently
>meet their compliance requirements within Hadoop and allows integration
>with the complete enterprise data ecosystem.
>
>== Proposal ==
>
>Apache Atlas allows agnostic governance visibility into Hadoop, these
>abilities are enabled through a set of core foundational services powered
>by a flexible metadata repository.
>
>These services include:
>
> * Search and Lineage for datasets
> * Metadata driven data access control
> * Indexed and Searchable Centralized Auditing operational Events
> * Data lifecycle management – ingestion to disposition
> * Metadata interchange with other metadata tools
>
>== Background ==
>
>Hadoop is one of many platforms in the modern enterprise data ecosystem and
>requires governance controls commensurate with this reality.
>
>Currently, there is no easy or complete way to provide comprehensive
>visibility and control into Hadoop audit, lineage, and security for
>workflows that require Hadoop and non-Hadoop processing.
>
>Many solutions are usually point based, and require a monolithic
>application workflow.  Multi-tenancy and concurrency are problematic as
>these offerings are not aware of activity outside of their narrow focus.
>
>As Hadoop gains greater popularity, governance concerns will become
>increasingly vital to increasing maturity and furthering adoption. It is a
>particular barrier to expanding enterprise data under management.
>
>== Rationale ==
>
>Atlas will address issues previously discussed by providing governance
>capabilities in Hadoop -- using both a prescriptive and forensic model
>enriched by business taxonomical metadata.Atlas, at its core, is
>designed to exchange metadata with other tools and processes within and
>outside of the Hadoop stack -- enable governance controls that are truly
>platform agnostic and effectively (and defensibly) address compliance
>concerns.
>
>Initially working with a group of leading partners in several industries,
>Atlas is built to solve specific real world governance problems that
>accelerate product maturity and time to value.
>
>Atlas aims to grow a community to help build a widely adopted pattern for
>governance, metadata modeling and exchange in Hadoop – which will advance
>the interests for the whole community.
>
>== Current Status ==
>
>An initial version with a valuable set of features is developed by the list
>of initial committers and is hosted on github.
>
>=== Meritocracy ===
>
>Our intent with this proposal is to start building a diverse  developer
>community around Atlas following the Apache meritocracy model. We have
>wanted to make the project open source and encourage contributors from
>multiple organizations from the start.
>
>We plan to provide plenty of support to new developers and to quickly
>recruit those who make solid contributions to committer status.
>
>=== Community ===
>
>We are happy to report that the initial team already represents multiple
>organizations. We hope to extend the user and developer base further in the
>future and build a solid open source community around Atlas.
>
>=== Core Developers ===
>
>Atlas development is currently being led by engineers from Hortonworks –
>Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
>engineers have deep expertise in Hadoop and are quite familiar with the
>Hadoop Ecosystem.
>
>=== Alignment ===
>
>The ASF is a natural host for Atlas given that it is already the home of
>Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
>data” software projects.
>
>Atlas has been designed to solve the data governance challenges and
>opportunities of the Hadoop ecosystem family of products as well as
>integration to the tradition Enterprise Data ecosystem.
>
>Atlas fills the gap that the Hadoop Ecosystem has been lacking in the areas
>of data governance and compliance management.
>
>== Known Risks ==
>
>=== Orphaned products & Reliance on Salaried Developers ===
>The core developers plan to work full time on the project. There is very
>little risk of Atlas getting orphaned.  A prototype of Atlas is in use and
>being actively developed by several co

Re: updating the incubator website

[Ted Dunning]

Exactly.

And here is the final product for Drill.

http://drill.apache.org/

Info on how to update the drill web site:

https://github.com/apache/drill-site





On Tue, May 5, 2015 at 8:14 AM, Alexander Bezzubov 
wrote:

> This workflow works pretty well indeed,
>
> AFAIK https://github.com/apache/drill/tree/gh-pages is using it with
> http://apache.github.io/drill/ as a preview, as well as Zeppelin
> (incubating) https://github.com/apache/incubator-zeppelin/tree/gh-pages
> for
> http://zeppelin-project.org
>
> but I'm pretty sure there are other project who use it as well.
>
>
> On Mon, May 4, 2015 at 3:02 PM, Till Westmann  wrote:
>
> > That sounds interesting.
> > Could you point me to a project that has implemented such a workflow?
> >
> > > On May 3, 2015, at 17:11, Ted Dunning  wrote:
> > >
> > > Depending on your preferences, you can also switch to an SVN-only or
> > > git-only workflow which avoids the CMS applet entirely.  You will have
> to
> > > set up your own preview method.  Some projects use an alternative
> thread
> > > (typically "gh-pages") to store the site content without the project
> > > sources.  This allows github to be used as a preview.
> > >
> > > You then pre-process the site and check it in to eiether SVN or git in
> > > order to propagate the content to the web servers.
> > >
> > >
> > >> On Sun, May 3, 2015 at 9:36 PM, Till Westmann 
> wrote:
> > >>
> > >> Sorry, just found out that there’s already an issue filed for this:
> > >> https://issues.apache.org/jira/browse/INFRA-9574 <
> > >> https://issues.apache.org/jira/browse/INFRA-9574>
> > >>
> > >> Till
> > >>
> > >>> On May 3, 2015, at 1:31 PM, Till Westmann  wrote:
> > >>>
> > >>> Following the instructions [1] I fixed a few things on the AsterixDB
> > >> incubation status page.
> > >>> My local build and svn submission worked fine and I can see the
> changes
> > >> on the staging site [2].
> > >>> However, when I go to the “publish site” page [3], I get:
> > >>>
> > >>> Error
> > >>>
> > >>> Can't call method "ASF::CMS::Cookie::bake" on an undefined value at
> > >> /usr/local/cms/webgui/lib/ASF/CMS.pm line 684,  line 741.
> > >>>
> > >>> Help?
> > >>>
> > >>> Thanks,
> > >>> Till
> > >>>
> > >>>
> > >>> [1] http://incubator.apache.org/guides/website.html <
> > >> http://incubator.apache.org/guides/website.html>
> > >>> [2] http://incubator.staging.apache.org <
> > >> http://incubator.staging.apache.org/>
> > >>> [3] https://cms.apache.org/incubator/publish <
> > >> https://cms.apache.org/incubator/publish>
> > >>>
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> --
> Kind regards,
> Alexander.
>

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Ajay Yadav]

+1 (non-binding)

Cheers
Ajay Yadava

On Tue, May 5, 2015 at 10:04 AM, Sharad Agarwal  wrote:

> +1 (binding)
>
> On Fri, May 1, 2015 at 12:56 PM, Seetharam Venkatesh <
> venkat...@innerzeal.com> wrote:
>
> > Hello folks,
> >
> > Following the discussion earlier in the thread: http://s.apache.org/r2
> >
> > I would like to call a VOTE for accepting Apache Atlas as a new incubator
> > project.
> >
> > The proposal is available at:
> > https://wiki.apache.org/incubator/AtlasProposal
> > Also, the text of the latest wiki proposal is included at the bottom of
> > this email.
> >
> > The VOTE is open for at least the next 72 hours:
> >
> >  [ ] +1 accept Apache Atlas into the Apache Incubator
> >  [ ] ±0 Abstain
> >  [ ] -1 because...
> >
> > Of course I am +1! (non-binding)
> >
> > Thanks!
> >
> >
> > = Apache Atlas Proposal =
> >
> > == Abstract ==
> >
> > Apache Atlas is a scalable and extensible set of core foundational
> > governance services that enables enterprises to effectively and
> efficiently
> > meet their compliance requirements within Hadoop and allows integration
> > with the complete enterprise data ecosystem.
> >
> > == Proposal ==
> >
> > Apache Atlas allows agnostic governance visibility into Hadoop, these
> > abilities are enabled through a set of core foundational services powered
> > by a flexible metadata repository.
> >
> > These services include:
> >
> >  * Search and Lineage for datasets
> >  * Metadata driven data access control
> >  * Indexed and Searchable Centralized Auditing operational Events
> >  * Data lifecycle management – ingestion to disposition
> >  * Metadata interchange with other metadata tools
> >
> > == Background ==
> >
> > Hadoop is one of many platforms in the modern enterprise data ecosystem
> and
> > requires governance controls commensurate with this reality.
> >
> > Currently, there is no easy or complete way to provide comprehensive
> > visibility and control into Hadoop audit, lineage, and security for
> > workflows that require Hadoop and non-Hadoop processing.
> >
> > Many solutions are usually point based, and require a monolithic
> > application workflow.  Multi-tenancy and concurrency are problematic as
> > these offerings are not aware of activity outside of their narrow focus.
> >
> > As Hadoop gains greater popularity, governance concerns will become
> > increasingly vital to increasing maturity and furthering adoption. It is
> a
> > particular barrier to expanding enterprise data under management.
> >
> > == Rationale ==
> >
> > Atlas will address issues previously discussed by providing governance
> > capabilities in Hadoop -- using both a prescriptive and forensic model
> > enriched by business taxonomical metadata.Atlas, at its core, is
> > designed to exchange metadata with other tools and processes within and
> > outside of the Hadoop stack -- enable governance controls that are truly
> > platform agnostic and effectively (and defensibly) address compliance
> > concerns.
> >
> > Initially working with a group of leading partners in several industries,
> > Atlas is built to solve specific real world governance problems that
> > accelerate product maturity and time to value.
> >
> > Atlas aims to grow a community to help build a widely adopted pattern for
> > governance, metadata modeling and exchange in Hadoop – which will advance
> > the interests for the whole community.
> >
> > == Current Status ==
> >
> > An initial version with a valuable set of features is developed by the
> list
> > of initial committers and is hosted on github.
> >
> > === Meritocracy ===
> >
> > Our intent with this proposal is to start building a diverse  developer
> > community around Atlas following the Apache meritocracy model. We have
> > wanted to make the project open source and encourage contributors from
> > multiple organizations from the start.
> >
> > We plan to provide plenty of support to new developers and to quickly
> > recruit those who make solid contributions to committer status.
> >
> > === Community ===
> >
> > We are happy to report that the initial team already represents multiple
> > organizations. We hope to extend the user and developer base further in
> the
> > future and build a solid open source community around Atlas.
> >
> > === Core Developers ===
> >
> > Atlas development is currently being led by engineers from Hortonworks –
> > Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
> > engineers have deep expertise in Hadoop and are quite familiar with the
> > Hadoop Ecosystem.
> >
> > === Alignment ===
> >
> > The ASF is a natural host for Atlas given that it is already the home of
> > Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
> > data” software projects.
> >
> > Atlas has been designed to solve the data governance challenges and
> > opportunities of the Hadoop ecosystem family of products as well as
> > integration to the tradition Enterprise Data ecosystem.
> >
> > Atlas fills the 

Re: updating the incubator website

[Alexander Bezzubov]

This workflow works pretty well indeed,

AFAIK https://github.com/apache/drill/tree/gh-pages is using it with
http://apache.github.io/drill/ as a preview, as well as Zeppelin
(incubating) https://github.com/apache/incubator-zeppelin/tree/gh-pages for
http://zeppelin-project.org

but I'm pretty sure there are other project who use it as well.


On Mon, May 4, 2015 at 3:02 PM, Till Westmann  wrote:

> That sounds interesting.
> Could you point me to a project that has implemented such a workflow?
>
> > On May 3, 2015, at 17:11, Ted Dunning  wrote:
> >
> > Depending on your preferences, you can also switch to an SVN-only or
> > git-only workflow which avoids the CMS applet entirely.  You will have to
> > set up your own preview method.  Some projects use an alternative thread
> > (typically "gh-pages") to store the site content without the project
> > sources.  This allows github to be used as a preview.
> >
> > You then pre-process the site and check it in to eiether SVN or git in
> > order to propagate the content to the web servers.
> >
> >
> >> On Sun, May 3, 2015 at 9:36 PM, Till Westmann  wrote:
> >>
> >> Sorry, just found out that there’s already an issue filed for this:
> >> https://issues.apache.org/jira/browse/INFRA-9574 <
> >> https://issues.apache.org/jira/browse/INFRA-9574>
> >>
> >> Till
> >>
> >>> On May 3, 2015, at 1:31 PM, Till Westmann  wrote:
> >>>
> >>> Following the instructions [1] I fixed a few things on the AsterixDB
> >> incubation status page.
> >>> My local build and svn submission worked fine and I can see the changes
> >> on the staging site [2].
> >>> However, when I go to the “publish site” page [3], I get:
> >>>
> >>> Error
> >>>
> >>> Can't call method "ASF::CMS::Cookie::bake" on an undefined value at
> >> /usr/local/cms/webgui/lib/ASF/CMS.pm line 684,  line 741.
> >>>
> >>> Help?
> >>>
> >>> Thanks,
> >>> Till
> >>>
> >>>
> >>> [1] http://incubator.apache.org/guides/website.html <
> >> http://incubator.apache.org/guides/website.html>
> >>> [2] http://incubator.staging.apache.org <
> >> http://incubator.staging.apache.org/>
> >>> [3] https://cms.apache.org/incubator/publish <
> >> https://cms.apache.org/incubator/publish>
> >>>
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
--
Kind regards,
Alexander.