Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Shwetha Shivalingamurthy]

+1 (non-binding)

On 01/05/15 12:56 pm, "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 companies and have vested interest in
>its continued vitality and adoption.
>
>=== I

Re: updating the incubator website

[Till Westmann]

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

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Jake Farrell]

Sorry I missed the discussion thread for this proposed podling, the name
for this project may have an issue with Netflix Atlas [1] when it comes
time to graduate, may be worth the discussion of switching names if voted
in before any infra resources are setup

-Jake

[1]:
http://techblog.netflix.com/2014/12/introducing-atlas-netflixs-primary.html
[2]: https://github.com/netflix/atlas


On Fri, May 1, 2015 at 3: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 th

Re: updating the incubator website

[Ted Dunning]

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>
> >
>
>

Re: updating the incubator website

[Till Westmann]

Sorry, just found out that there’s already an issue filed for this:
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 
> 
> [2] http://incubator.staging.apache.org 
> [3] https://cms.apache.org/incubator/publish 
> 
> 

updating the incubator website

[Till Westmann]

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 

[2] http://incubator.staging.apache.org 
[3] https://cms.apache.org/incubator/publish 

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Arun C Murthy]

+1 (binding)

thanks,
Arun

On May 1, 2015, at 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