[RESULT][VOTE] Graduate Apache CarbonData Project from the Incubator

2017-03-21 Thread Jean-Baptiste Onofré 

Hi,

this vote passed with the following result:

+1 (binding): Niclas Hedhman, Julian Hyde, Henry Saputra, John D. Ament
+1 (non binding): Pierre Smits, Timothy Chen

Thanks all for the vote.

I will prepare the resolution submission for the next board meeting.

Regards
JB

On 03/15/2017 01:39 PM, Jean-Baptiste Onofré wrote:

Hi IPMC,

Following the previous discussion, please vote on the draft resolution proposed
by the Apache CarbonData PPMC below, which establishes Apache CarbonData as a
new top-level project at the Apache Software Foundation, as follows:

[ ] +1, Graduate Apache CarbonData from the Incubator.
[ ] +0, Don't care.
[ ] -1, Don't graduate Apache CarbonData from the Incubator (provide details)

The full text of the resolution is bellow.

If approved by the Apache Incubator PMC members, the proposed resolution will be
submitted to the Board of Directors for their consideration.

Thanks !

Regards
JB

The full-text of the draft resolution proposed by the Apache CarbonData PPMC:

 X. Establish the Apache CarbonData 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 an indexed columnar data format
   for fast analytics on big data platform.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache CarbonData Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache CarbonData 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 CarbonData"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 CarbonData Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache CarbonData 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 CarbonData Project:

* Liang Chen 
* Jean-Baptiste Onofré 
* Henry Saputra 
* Uma Maheswara Rao G 
* Jenny MA 
* Jacky Li 
* Vimal Das Kammath 
* Jarray Qiu 

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Chen be
   appointed to the office of Vice President, Apache CarbonData, 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 CarbonData PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache CarbonData Project; and be it further

   RESOLVED, that the Apache CarbonData Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator CarbonData podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator CarbonData podling encumbered upon the Apache Incubator
   Project are hereafter discharged.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Quickstep (incubating) 0.1.0 RC7

2017-03-21 Thread Josh Elser 
Fwding +1 (binding) from ppmc list.

On Mar 21, 2017 21:47, "Marc Spehlmann"  wrote:

> The Apache Incubator Quickstep community has approved a vote to release
> Quickstep-0.1.0 RC7. Quickstep is a high performance relational database
> system built from the ground up for modern hardware.
>
> We had a discussion on the general list in RC6 about fixing some issues
> with the LICENSE and NOTICE files. These are mostly fixed, though we did
> add a task in Jira to be even more prepared at our next release.
>
> Please vote on the release of 0.1.0.
>
> This vote will stay open through Friday evening.
>
> -Marc
> ___
> The vote and results thread from dev:
> *https://www.mail-archive.com/dev@quickstep.incubator.
> apache.org/msg02162.html
>  apache.org/msg02162.html>*
>
> *https://www.mail-archive.com/dev@quickstep.incubator.
> apache.org/msg02180.html
>  apache.org/msg02180.html>*
>
> The commit to be voted upon:
> *https://git-wip-us.apache.org/repos/asf?p=incubator-
> quickstep.git;a=shortlog;h=refs/heads/quickstep-0.1.0
>  quickstep.git;a=shortlog;h=refs/heads/quickstep-0.1.0>*
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC7/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/spehl
>

[VOTE] Apache Quickstep (incubating) 0.1.0 RC7

2017-03-21 Thread Marc Spehlmann 
The Apache Incubator Quickstep community has approved a vote to release
Quickstep-0.1.0 RC7. Quickstep is a high performance relational database
system built from the ground up for modern hardware.

We had a discussion on the general list in RC6 about fixing some issues
with the LICENSE and NOTICE files. These are mostly fixed, though we did
add a task in Jira to be even more prepared at our next release.

Please vote on the release of 0.1.0.

This vote will stay open through Friday evening.

-Marc
___
The vote and results thread from dev:
*https://www.mail-archive.com/dev@quickstep.incubator.apache.org/msg02162.html
*

*https://www.mail-archive.com/dev@quickstep.incubator.apache.org/msg02180.html
*

The commit to be voted upon:
*https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=shortlog;h=refs/heads/quickstep-0.1.0
*

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC7/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/spehl

Re: Creating a podli...@incubator.apache.org mailing list

2017-03-21 Thread John D. Ament 
On Tue, Mar 21, 2017 at 11:56 AM Dave Fisher  wrote:

>
> > On Mar 20, 2017, at 6:45 PM, Niclas Hedhman  wrote:
> >
> > +1 for a podlings@ alias.
> >
> > But what could you possibly want with a podlings-private@ ?  We are
> > expected to keep private to a minimum, typically involving individuals or
> > security issues, and I fail to see how that can apply to 50 or so very
> > disperse projects, that changes over time. So I am -1 on that, until I
> hear
> > some reasonable justification.
>
> I agree. Private matters will tend to be on a case by case basis. In the
> rare case where an all private email to all podlings must go out then each
> podling can be addressed one at a time via cut and paste.
>
>
Agreed.  Maybe to put it another way, I'm not against the idea of creating
a podlings-private style alias, but don't see a strong use case for it.


> >
> > The pmcs@ alias is IMHO a bad alias and should be changed to go to dev@.
> > Way back in time, we had p...@foo.apache.org and the pmcs@ came out of
> that
> > naming. BUT, we later recognized that pmc@ was being overused. The name
> > invited that overuse and we changed it to private@ to signal its intent,
> > but pmcs@ was left behind…
>
> This is not an Incubator mailing list and therefore this is Off Topic.
>
> Regards,
> Dave
>
> >
> >
> > Cheers
> > Niclas
> >
> >
> > On Tue, Mar 21, 2017 at 4:17 AM, John D. Ament 
> > wrote:
> >
> >> On Mon, Mar 20, 2017 at 12:55 PM Luciano Resende 
> >> wrote:
> >>
> >>> On Mon, Mar 20, 2017 at 12:00 PM John D. Ament 
> >>> wrote:
> >>>
>  All,
> 
>  Before I go ahead with it, wanted to see if others had any opinions.
> >> I'm
>  planning to ask infra to create a podlings@i.a.o mailing list, which
> >>> would
>  go to all podlings dev@ list.  There may be some scenarios where we
> >> need
>  to
>  communicate out to all podlings.  For instance, the logo change and
> how
> >>> it
>  impacts the podlings.
> 
>  John
> 
> >>>
> >>> This would be more like an alias, similar to @PMCs right ? Also, in the
> >>> past, some of these communications would go to podling private (e.g.
> Gsoc
> >>> info) where there was a request for the podling pmc to discuss this
> >>> appropriately in their dev lists? That might still be a viable
> approach.
> >>>
> >>>
> >> Yes, I believe that's how infra would implement it.  It isn't meant to
> >> replace general@ but instead allow us a convenient way to email blast
> all
> >> podlings.
> >>
> >> As I was typing the email, I thought about private lists.  I wouldn't
> mind
> >> a podlings-private@i.a.o as well.
> >>
> >>
> >>> BTW, podlings, particular podling mentors should (MUST) be following
> all
> >>> pertinent general@ discussions.
> >>> --
> >>> Sent from my Mobile device
> >>>
> >>
> >
> >
> >
> > --
> > Niclas Hedhman, Software Developer
> > http://polygene.apache.org  - New Energy for
> Java
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Apache Slider (incubating) release 0.92.0-incubating

2017-03-21 Thread Gour Saha 
Hello,

Here are the results of the vote for releasing Apache Slider (incubating) 
release 0.92.0-incubating-RC0

+1 votes: 5 (5 binding)
+0 votes: 0 (0 binding)
-1 votes: 0 (0 binding)

Thanks to Josh, Billie, John, Steve and Jean for your +1 binding votes.

The vote has succeeded - the release will now be completed.

- gourksaha on behalf of the Apache Slider (incubating) team


From: Gour Saha >
Date: Wednesday, March 15, 2017 at 4:15 PM
To: "general@incubator.apache.org" 
>
Subject: [VOTE] Apache Slider (incubating) release 0.92.0-incubating

Hello,

This is a call for a vote on the Apache Slider (incubating) release 
0.92.0-incubating.

This release candidate, 0.92.0-incubating-RC0 has successfully passed a vote 
for a release on the slider developer mailing list.

Vote thread:
  
http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4E792AE.2693A%25gsaha%40hortonworks.com%3E

Results:
  
http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201703.mbox/%3CD4EEB66E.26E31%25gsaha%40hortonworks.com%3E

Source artifacts:
  https://dist.apache.org/repos/dist/dev/incubator/slider/0.92.0-incubating-RC0

Staged artifacts:
  https://repository.apache.org/content/repositories/orgapacheslider-1017/

Git source:
  
https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=c41b1c7051d02c02b0d78cab859c7e15d0af92c9

Git commit SHA1: c41b1c7051d02c02b0d78cab859c7e15d0af92c9

Issues fixed:
  https://issues.apache.org/jira/browse/SLIDER/fixforversion/12339846/

Release Notes:
  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315422=12339846

PGP key:
  http://pgp.mit.edu:11371/pks/lookup?op=vindex=gourks...@apache.org

Please vote on releasing this package as Apache Slider 0.92.0-incubating:

This vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

gourksaha on behalf of the Apache Slider (incubating) team

Re: Creating a podli...@incubator.apache.org mailing list

2017-03-21 Thread Dave Fisher 

> On Mar 20, 2017, at 6:45 PM, Niclas Hedhman  wrote:
> 
> +1 for a podlings@ alias.
> 
> But what could you possibly want with a podlings-private@ ?  We are
> expected to keep private to a minimum, typically involving individuals or
> security issues, and I fail to see how that can apply to 50 or so very
> disperse projects, that changes over time. So I am -1 on that, until I hear
> some reasonable justification.

I agree. Private matters will tend to be on a case by case basis. In the rare 
case where an all private email to all podlings must go out then each podling 
can be addressed one at a time via cut and paste.

> 
> The pmcs@ alias is IMHO a bad alias and should be changed to go to dev@.
> Way back in time, we had p...@foo.apache.org and the pmcs@ came out of that
> naming. BUT, we later recognized that pmc@ was being overused. The name
> invited that overuse and we changed it to private@ to signal its intent,
> but pmcs@ was left behind…

This is not an Incubator mailing list and therefore this is Off Topic.

Regards,
Dave

> 
> 
> Cheers
> Niclas
> 
> 
> On Tue, Mar 21, 2017 at 4:17 AM, John D. Ament 
> wrote:
> 
>> On Mon, Mar 20, 2017 at 12:55 PM Luciano Resende 
>> wrote:
>> 
>>> On Mon, Mar 20, 2017 at 12:00 PM John D. Ament 
>>> wrote:
>>> 
 All,
 
 Before I go ahead with it, wanted to see if others had any opinions.
>> I'm
 planning to ask infra to create a podlings@i.a.o mailing list, which
>>> would
 go to all podlings dev@ list.  There may be some scenarios where we
>> need
 to
 communicate out to all podlings.  For instance, the logo change and how
>>> it
 impacts the podlings.
 
 John
 
>>> 
>>> This would be more like an alias, similar to @PMCs right ? Also, in the
>>> past, some of these communications would go to podling private (e.g. Gsoc
>>> info) where there was a request for the podling pmc to discuss this
>>> appropriately in their dev lists? That might still be a viable approach.
>>> 
>>> 
>> Yes, I believe that's how infra would implement it.  It isn't meant to
>> replace general@ but instead allow us a convenient way to email blast all
>> podlings.
>> 
>> As I was typing the email, I thought about private lists.  I wouldn't mind
>> a podlings-private@i.a.o as well.
>> 
>> 
>>> BTW, podlings, particular podling mentors should (MUST) be following all
>>> pertinent general@ discussions.
>>> --
>>> Sent from my Mobile device
>>> 
>> 
> 
> 
> 
> -- 
> Niclas Hedhman, Software Developer
> http://polygene.apache.org  - New Energy for Java


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Release Apache Mynewt 1.0.0-incubating-rc1

2017-03-21 Thread marko kiiskila 
Hello all,

Voting for Apache Mynewt 1.0.0-incubating-rc1 is now closed. The release has
passed. The vote breakdown is as follows:

+1 Sterling Hughes (binding)
+1 John D. Ament (binding)
+1 Josh Elser (binding)

Total: +3

Thank you to all who voted.
—
M
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Fineract podling graduation

2017-03-21 Thread Myrle Krantz 
Hi Bertrand,

On Mon, Mar 20, 2017 at 2:17 PM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi Myrle,
>
> +1 to graduating in principle but the project descriptions quoted
> below are inconsistent.
>

You are absolutely correct -- I used Geode's graduation resolution as a
template and missed that one when editing it.  Thank you for catching my
error.

I've attached a new version of the resolution below with the WHEREAS
attached.  Do I need to restart the vote?

Greets,
Myrle



Resolution:

Establish the Apache Fineract 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 core banking platform that provides a reliable,
robust, and affordable solution for entrepreneurs, financial
institutions, and service providers to offer financial
services to the world's underbanked and unbanked.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Fineract Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Fineract Project be and hereby is
responsible for the creation and maintenance of software
related to a core banking platform that provides a reliable,
robust, and affordable solution for entrepreneurs, financial
institutions, and service providers to offer financial
services to the world's underbanked and unbanked.

RESOLVED, that the office of "Vice President, Apache Fineract" 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 Fineract Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Fineract 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 Fineract Project:

* Vishwas Babu AJ 
* Edward Cable 
* Markus Geiss 
* Sander van der Heijden 
* Ishan Khanna 
* Myrle Krantz 
* Terence Monteiro 
* Adi Nayaran Raju 
* Gaurav Saini 
* Nazeer Hussain Shaik 
* Jim Jagielski 
* Michael Vorburger 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
be appointed to the office of Vice President, Apache Fineract, 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 Fineract PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Fineract Project; and be it further

RESOLVED, that the Apache Fineract Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Fineract podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Fineract podling encumbered upon the Apache Incubator
Project are hereafter discharged.

Re: [VOTE] Release Apache Mynewt 1.0.0-incubating-rc1

2017-03-21 Thread marko kiiskila 
Hi Josh,

you’re right about us missing lwip & tinycrypt info in LICENSE file.

They’re referenced elsewhere where we mention that these are BSD,
but that’s not enough. This’ll be fixed before next release.

Thanks for pointing this out,
M

> On Mar 19, 2017, at 11:26 AM, Josh Elser  wrote:
> 
> +0 (binding)
> 
> * L pretty good (caveat below)
> * sigs/xsums OK
> * Was able to build all but mynewt-core (thus the +0). Am still trying to 
> figure this out so I can switch to a +1.
> * Didn't see any binaries in source release(s)
> * DISCLAIMER is present
> * Website has incubator reference
> * incubating used in project name
> 
> LICENSE in mynewt-core appears to be missing entries for
>  - net/ip/lwip_base (3-clause BSD)
>  - crypto/tinycrypt (3-clause BSD)
> 
> Please make sure these get fixed for your next release (or tell me that I'm 
> wrong :P)
> 
> I also see that tinycrypt is not mentioned in the export-control section in 
> your README.md. I'm guessing that you might need to send an another TSU 
> notification email and update this section?
> 
> - Josh
> 
> marko kiiskila wrote:
>> The Apache Mynewt Incubator PPMC has approved a proposal to release
>> Apache Mynewt 1.0.0-incubating-rc1. We now kindly request that the
>> Incubator PMC members review and vote on this incubator release.
>> 
>> Apache Mynewt is a community-driven, permissively licensed open source
>> initiative for constrained, embedded applications.  Mynewt provides a
>> real-time operating system, flash file system, network stacks, and
>> support utilities for real-world embedded systems.
>> 
>> For full release notes, please visit the Apache Mynewt Wiki:
>> https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes
>> 
>> [VOTE] thread:
>> https://lists.apache.org/thread.html/030cd65553128847b6931b3e32e0536326036ce9f332feb988759f55@%3Cdev.mynewt.apache.org%3E
>> 
>> [RESULT][VOTE] thread:
>> https://lists.apache.org/thread.html/e863e81c7b4af0981610775d541f2a51a6814e4523fd74e1a402341a@%3Cdev.mynewt.apache.org%3E
>> 
>> [DISCUSS] thread:
>> https://lists.apache.org/thread.html/f2e3c8bc63a377dd628a2bdafb7b160868525a134f75d766d7244578@%3Cdev.mynewt.apache.org%3E
>> 
>> This release candidate was tested as follows:
>>  1. Manual execution of the Mynewt test plan:
>> 
>> https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
>> The test results can be found at:
>> 
>> https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0+Test+Results
>>  2. The full unit test suite for this release was executed via "newt
>> test all" with no failures.  This testing was performed on the
>> following platforms:
>>   * OS X 10.12.3
>>   * Linux Ubuntu 14.04.4
>> 
>> The release candidate to be voted on is available at:
>> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/
>> 
>> The commits under consideration are as follows:
>> blinky:
>>  repos: 
>> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky
>>  commit 15496854000a2b0cc9d19c05e069d18be313fa28
>> core:
>>  repos: 
>> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core
>>  commit 0db6321a75deda126943aa187842da6b977cd1c1
>> newt:
>>  repos: 
>> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
>>  commit c42ebdce8c278a00fa8d68ed342c45cd22e44dfb
>> 
>> In addition, the following newt convenience binaries are available:
>>  linux: 
>> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-linux-1.0.0-incubating.tgz
>>  osx: 
>> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-incubating/rc1/apache-mynewt-newt-bin-osx-1.0.0-incubating.tgz
>> 
>> The release candidate is signed with a GPG key available at:
>>

Re: [DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-21 Thread Jean-Baptiste Onofré 

Hi all,

gently reminder about this thread.

I would like to start a formal vote pretty soon.

Thanks,
Regards
JB

On 03/07/2017 09:49 PM, Jean-Baptiste Onofré wrote:

Hi all,

I would like to submit a new proposal to bring Amaterasu to the Apache Software
Foundation incubator.

The proposal is included below and available on the wiki:

https://wiki.apache.org/incubator/AmaterasuProposal

We are eager to get your comments and questions.

Thanks !
JB (on behalf of the Amaterasu community)

= Apache Amaterasu =

== Abstract ==

Apache Amaterasu is a framework providing continuous deployment for Big Data
pipelines.

It provides the following capabilities:

 * '''Continuous integration''' tools to '''package pipelines and run tests'''.
 * A repository to store those packaged applications: the '''applications
repository'''.
 * A repository to store the pipelines, and engine configuration (for instance,
location of the Spark master, etc.): per environment - the '''configuration
repository'''.
 * A '''dashboard''' to monitor the pipelines.
 * A '''DSL and integration hooks''' allowing third parties to easily integrate.

== Proposal ==

Amaterasu is a simple and powerful framework to build and dispense pipelines.
It aims to help data engineers and data scientists to compose, configure, test,
package, deploy and execute data pipelines written using multiple tools,
languages and frameworks. Amaterasu provides a standard repo structure to
package big data pipelines, a YAML based Domain Specific Languages (DSL) for
data engineers, data scientists and operations engineers to manage complex
pipelines throughout their entire lifecycle (Dev, UAT, Prod, etc.).

== Background ==

Amaterasu is a relatively new project that was created to deal with some of the
issues that as Consultants, we have seen recurring at different client sites.
Mainly the need to continuously deploy complex pipelines built in multiple tools
and languages.
Amaterasu started as a pet project and is currently being evaluated by a couple
of organizations, supported by the contributors, on a personal time and
voluntary bases.

== Rational ==

As software engineers working on big data projects we have straggled for a long
time to apply the same CI/CD practices that have become the standard in the
software industry for the last few years. While some of them are possible, for
example Apache Spark is easy to unit test. However large scale pipelines are
more complex and often use data, which might be un-structured as integration
point, which requires heavy integration tests.

To automate such tests and complex deployments, we have found the need to often
handcraft scripts and use a mixture tools, so we have decided to finally build a
tool we can apply in a general way and not on a project by project basis.

Another issue Amaterasu is trying to tackle is the Integrating between the work
of software engineers, data scientists, and sometimes operations engineers. The
approach Amaterasu takes to integrate between those three schools of thought it
to provide a simple YAML based DSL that provides a simple way to integrate
different pipeline written in the native tools for each task (R, Spark in
different languages, etc.).

== Initial Goals ==

Our initial goals are to bring Amaterasu into the ASF, transition internal
engineering processes into the open, and foster a collaborative development
model according to the "Apache Way".

In addition, we intend to continue the development of Amaterasu, add new
features as well as  integrate better with other frameworks, including:

 * Apache Arrow
 * Apache Hive
 * Apache Drill
 * Apache Beam
 * Apache YARN
 * Farther and more complete integration with Apache Spark

Other frameworks will be evaluated after those initial goals are reached.

== Current Status ==

Amaterasu is preview state but provide a large set of features. We plan to
stabilize and head to a first production ready release during the incubation
process. The current license is already Apache 2.0.

=== Meritocracy ===

We intend to radically expand the initial developer and user community by
running the project in accordance with the "Apache Way". Users and new
contributors will be treated with respect and welcomed. By participating in the
community and providing quality patches/support that move the project forward,
they will earn merit. They also will be encouraged to provide non-code
contributions (documentation, events, community management, etc.) and will gain
merit for doing so. Those with a proven support and quality track record will be
encouraged to become committers.

=== Community ===

As a relatively new project, Amaterasu has a small, but growing community.
Amaterasu is an open project, not just with it’s source code but also with our
discussions which are held openly in our slack https://shintoio.slack.com which
contains channels for design, tech and future directions discussions.

If Amaterasu is accepted for incubation, the primary initial goal