Re: Donating freemarker-online as part of the FreeMarker project, how?

2017-03-07 Thread Daniel Dekany 
Yesterday the ASF have received the CCLA. Does the IPMC accept it, can
we go ahead with the pull request?


Thursday, February 23, 2017, 7:15:29 AM, Craig Russell wrote:

> Hi Daniel,
>
>> On Feb 22, 2017, at 9:24 PM, Daniel Dekany  wrote:
>> 
>> Wednesday, February 22, 2017, 8:12:32 PM, Craig Russell wrote:
>> 
>>> Hi,
>>> 
>>> Sounds like the easiest way to handle this is as you described. 
>> 
>> If we can do that, that's great! I will wait a few days to see if
>> someone else has anything to add, then I will assume that the
>> Incubator PMC has agreed and I will go ahead.
>> 
>>> Get a CCLA from Kenshoo with
>>> https://github.com/kenshoo/freemarker-online describing the code being 
>>> contributed
>>> Add any current Kenshoo employees 
>>> Get an ICLA from non-Kenshoo folks
>> 
>> I'm a bit confused regarding the last point above. We already got
>> ICLA-s from the non-Kenshoo folks at the ASF, but they have
>> contributed code to a non-ASF project back then. (Do we rather need an
>> SGA from them maybe?)
>
> If you have ICLAs from all of the non-Kenshoo folks then nothing
> else is needed from them. The ICLA is not project specific.
>
> Craig
>> 
>>> Create a git repo for the new content
>>> After we accept the CCLA, generate a pull request and take in the code
>>> Change package names
>>> Change license headers
>>> 
>>> Craig
>>> 
 On Feb 22, 2017, at 10:39 AM, Daniel Dekany  wrote:
 
 Hello,
 
 This is related to the incubating FreeMarker project.
 
 A company called Kenshoo has developed a simple but handy online
 evaluator service for FreeMarker, some 3 years ago, and they are still
 hosting it. Because they don't develop this service anymore, and
 because timely pull request merging and deployment seems to become an
 issue, we would like to bring the source code over to be part of the
 FreeMarker project. They are willing to donate the source code to the
 ASF.
 
 As of the more technical aspect of this, the FreeMarker project has
 multiple Git repos, one for each "product" (one product is the engine
 itself, another is the documentation/website generator Ant task, and
 yet another is the website content). These are separate products,
 because their versioning/releasing is independent. We would like to
 add one more such Git repo and product, for freemarker-online.
 
 We are trying to find out what's the most efficient yet legally
 acceptable way of doing this. Just as an example, after the repo was
 created and we add LICENSE and such, we could, technically, accept a
 pull request from Kenshoo if they sign a Corporate CLA. I know it's an
 extreme approach as they contribute to an almost empty repo, OTOH we
 are talking about only 31 classes and some build files (~160 KB source
 code). Anyway, how should we do it?
 
 The source code we want to bring over:
 https://github.com/kenshoo/freemarker-online
 
 Note that the 2 contributors from outside Kenshoo are also FreeMarker
 contributors, so we can get any papers needed from them (as there was
 no CLA signed at Kenshoo).
 
 -- 
 Thanks,
 Daniel Dekany
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 
>> -- 
>> Thanks,
>> Daniel Dekany
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>
> Craig L Russell
> Architect
> craig.russ...@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Thanks,
 Daniel Dekany


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

Re: [DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-07 Thread Yaniv Rodenski 
Hi Liang,

Currently the deployment is really extracting the tar on a node that can be
access by the Mesos cluster and running a job (once you do that the Mesos
framework takes care of everything).
Next versions (especially once adding YARN support) we will have more
moving parts and we will make sure installation remains a simple process.

Cheers,
Yaniv


On Wed, Mar 8, 2017 at 1:30 PM, Liang Chen  wrote:

> Hi Yaniv
>
> Thanks, i would find some time to try it.
>
> Is there any deployment UI from Amaterasu for easier using?
>
> Regards
> Liang
>
>
> Yaniv Rodenski wrote
> > Hi Liang,
> >
> > We are currently working on YARN support, but it's not quite there yet.
> >
> > What you can do at this point (as a workaround) is setup a single node
> > Mesos cluster and configure it to use your YARN cluster.
> >
> > If you would like to try that LMK, and I'll help you set it up (it's not
> > that straight forward).
> >
> > Cheers,
> > Yaniv
> >
> > On Wed, 8 Mar 2017 at 11:04 am, Liang Chen 
>
> > chenliang6136@
>
> >  wrote:
> >
> >> Hi
> >> Good luck!
> >> one question:If my system using YARN cluster, can i use Amaterasu for
> >> development?
> >>
> >> 
> --
> >> We have also created a Mesos cluster you can use to test Amaterasu or
> use
> >> for development purposes
> >>
> >> Regards
> >> Liang
> >>
> >> 2017-03-08 4:49 GMT+08:00 Jean-Baptiste Onofré 
>
> > jb@
>
> > :
> >>
> >> > 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

Re: GitHub workflows?

2017-03-07 Thread Marvin Humphrey 
On Mon, Mar 6, 2017 at 10:23 PM, Greg Stein  wrote:
> On Mon, Mar 6, 2017 at 11:34 PM, Marvin Humphrey 
> wrote:

>> For what it's worth, on one dev list I'm on, pull requests make it to the
>> dev list, but commenting on a commit via the Github interface only triggers
>> a private notification -- the comment never makes it to our dev list.  We
>> mostly avoid Github commit comments for that reason, so inclusiveness is
>> not harmed -- but people new to Apache might not handle things that way.
>>
> We can forward those, if you want. Probably should.

I think that's worthwhile as a feature request.

(To be clear since I just became VP Legal, no one should take this as a ruling
resulting in a new requirement -- it's a feature request humbly submitted for
Infra to consider.  Right now I'm just wearing my usual "Incubator contributor
hat".  I will make sure it's obvious when I put on the "VP Legal hat".)

Marvin Humphrey

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

Re: [DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-07 Thread Liang Chen 
Hi Yaniv

Thanks, i would find some time to try it.

Is there any deployment UI from Amaterasu for easier using?

Regards
Liang 


Yaniv Rodenski wrote
> Hi Liang,
> 
> We are currently working on YARN support, but it's not quite there yet.
> 
> What you can do at this point (as a workaround) is setup a single node
> Mesos cluster and configure it to use your YARN cluster.
> 
> If you would like to try that LMK, and I'll help you set it up (it's not
> that straight forward).
> 
> Cheers,
> Yaniv
> 
> On Wed, 8 Mar 2017 at 11:04 am, Liang Chen 

> chenliang6136@

>  wrote:
> 
>> Hi
>> Good luck!
>> one question:If my system using YARN cluster, can i use Amaterasu for
>> development?
>>
>> --
>> We have also created a Mesos cluster you can use to test Amaterasu or use
>> for development purposes
>>
>> Regards
>> Liang
>>
>> 2017-03-08 4:49 GMT+08:00 Jean-Baptiste Onofré 

> jb@

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

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc6 as 0.1.0

2017-03-07 Thread Luciano Resende 
ping, any other volunteers to review the release candidate ?

On Tue, Feb 28, 2017 at 2:57 PM, Luciano Resende 
wrote:

> +1 (binding)
>
> Verified licenses, signatures, overall layout for the three distros
> packages, no binary jars on source distro,
>
> On Tue, Feb 21, 2017 at 12:13 PM, Chip Senkbeil 
> wrote:
>
>> Please vote on releasing the following candidate as Apache Toree
>> (incubating) version 0.1.0.
>>
>> A vote on this release has passed within the Toree PPMC.
>>
>> PPMC vote result thread:
>> https://lists.apache.org/thread.html/44231a84f4034482b81bd03
>> 4d800e1f03243e21894da8550a75ae389@
>>
>> PPMC vote thread:
>> https://lists.apache.org/thread.html/f5decfdd2e44ea310253ab0
>> 37239713c5a4cfbb0d9f733b1197ffddf@
>>
>> The tag to be voted on is v0.1.0-rc6
>> (51fa49cb5898e0c5b7824f986382436b969cabc7), located here:
>> https://github.com/apache/incubator-toree/commit/51fa49cb589
>> 8e0c5b7824f986382436b969cabc7
>>
>> All distribution packages, including signatures, digests, etc. can be
>> found
>> at:
>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc6/
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/chipsenkbeil.asc
>>
>> The list of keys associated with Toree is available at:
>> https://people.apache.org/keys/group/toree.asc
>>
>> Staging artifacts can be found at:
>> https://repository.apache.org/content/repositories/orgapachetoree-1006/
>>
>> Please vote on releasing this package as Apache Toree 0.1.0-incubating!
>>
>> The vote is open for a minimum of 72 hours and passes if a majority of at
>> least 3 +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Toree 0.1.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Toree, please see
>> http://toree.incubator.apache.org/
>>
>> Instructions on testing Apache Toree can be found in the vote thread.
>>
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-07 Thread Yaniv Rodenski 
Hi Liang,

We are currently working on YARN support, but it's not quite there yet.

What you can do at this point (as a workaround) is setup a single node
Mesos cluster and configure it to use your YARN cluster.

If you would like to try that LMK, and I'll help you set it up (it's not
that straight forward).

Cheers,
Yaniv

On Wed, 8 Mar 2017 at 11:04 am, Liang Chen  wrote:

> Hi
> Good luck!
> one question:If my system using YARN cluster, can i use Amaterasu for
> development?
>
> --
> We have also created a Mesos cluster you can use to test Amaterasu or use
> for development purposes
>
> Regards
> Liang
>
> 2017-03-08 4:49 GMT+08:00 Jean-Baptiste Onofré :
>
> > 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

Re: [DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-07 Thread Liang Chen 
Hi
Good luck!
one question:If my system using YARN cluster, can i use Amaterasu for
development?
--
We have also created a Mesos cluster you can use to test Amaterasu or use
for development purposes

Regards
Liang

2017-03-08 4:49 GMT+08:00 Jean-Baptiste Onofré :

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

[ANNOUNCE] Release Apache Traffic Control 1.8.0 (incubating)

2017-03-07 Thread Dan Kirkwood 
The Apache Traffic Control team would like to announce the release of
Apache Traffic Control 1.8.0 (incubating).

More details regarding Apache Traffic Control can be found at:
http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/1.8.0-incubating/

The release notes can be found here:
http://trafficcontrol.incubator.apache.org/downloads/index.html

Thanks!
The Apache Traffic Control Team


Apache Traffic Control is an effort undergoing Incubation at The
Apache Software Foundation (ASF), sponsored by the 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.

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

[DISCUSS] Apache Amaterasu Incubator Proposal

2017-03-07 Thread Jean-Baptiste Onofré 

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 is to 
build a large and strong community. We are confident that Amaterasu can 
become a key project

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

2017-03-07 Thread Billie Rinaldi 
+1 binding
- signature and checksums are good
- artifact name contains incubating
- tarball matches tag
- builds from source
- license and notice seem appropriate

On Mon, 27 Feb 2017 13:53:28 -0500, Casey Stella  wrote:
> This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating
>
> Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
-incubating/CHANGES

>
> The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc5-incubating
>
> The source archive being voted upon can be found here:
https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
-incubating/apache-metron-0.3.1-rc5-incubating.tar.gz

>
> Other release files, signatures and digests can be found here:
https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
-incubating/

>
> The release artifacts are signed with the following key:
https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/
apache-metron-0.3.1-rc5-incubating
>
> The book associated with this RC is located at
https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
-incubating/book-site/index.html

>
> Please vote on releasing this package as Apache Metron 0.3.1-RC5
incubating
>
> When voting, please list the actions taken to verify the release.
>
> Recommended build validation and verification instructions are posted
here:
> https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds
>
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Metron 0.3.1-RC5 incubating
>
> [ ]  0 No opinion
>
> [ ] -1 Do not release this package because...

[VOTE] Release of Apache Mnemonic-0.5.0-incubating [rc1]

2017-03-07 Thread Gary 
Hello incubator PMCs,

The Apache Mnemonic community PPMCs and developers have voted and approved the 
proposal to release Apache Mnemonic 0.5.0 (incubating).

Apache Mnemonic is an advanced hybrid memory storage oriented library, it's 
proposed a non-volatile/durable Java object model and durable computing model 
that bring several advantages to significantly improve the performance of 
massive real-time data processing/analytic. developers are able to use this 
library to design their cache-less and SerDe-less high performance applications.

[VOTE] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3CCANLc_9JT3r3YWpNDD_is50KOME4B8w3SySOACQ2DmGVh-ah1-A%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3CCAG7vPR%2B9EfGk4%2BW1Hi_RQ56vYovJ3Bdidv0e5OH%2BFvE2dYuXdw%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3Cab49772b-f91b-4f07-3a4d-37259b030d1a%40apache.org%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3CCALuGr6b3KJz24HwQvT82WwgdHnH-2d6JdkhfDUz60_nb8H8HMg%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3CD4E3A5FA.2E7D3%25uma.gangumalla%40intel.com%3E

[VOTE RESULT] thread:
http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201703.mbox/%3c94f4761f-1c3c-0730-0fb0-bf9e3168d...@apache.org%3e

We now kindly request the Incubator PMC members review and vote on this 
incubator release.

The Apache Mnemonic-0.5.0-incubating release candidate is now available with 
the following artifacts for a project vote:

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.5.0-incubating-rc1/src/

The tag to be voted upon is v0.5.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=shortlog;h=refs/tags/v0.5.0-incubating

The release hash is d40a8f23bd18954b0d93ba7f8196f40d05c55dcc:
https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=commit;h=d40a8f23bd18954b0d93ba7f8196f40d05c55dcc

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS

For information about the contents of this release, see:
https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.5.0-incubating-rc1/CHANGES.txt

The vote will be open for ~72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.  The
please vote:

[ ] +1 Release this package as apache-mnemonic-0.5.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because because...


Thanks,
Gary on behalf of the Apache Mnemonic (incubating) team






signature.asc
Description: OpenPGP digital signature

[VOTE] MADlib v1.10-rc2

2017-03-07 Thread Frank McQuillan 
Hello Incubator PMC,

The Apache MADlib (incubating) community has voted on and approved the
proposal to release MADlib v1.10-rc2.

The voting result is available at:
http://mail-archives.apache.org/mod_mbox/incubator-madlib-dev/201703.mbox/%3CCAKBQfzQ_BeetybM9cOkXd%2BAvGDQY_BM3KMs3d28sH8tPFzDU8Q%40mail.gmail.com%3E

This will be the 4th release for Apache MADlib (incubating).

The main goals of this release are:
* new modules (single source shortest path for graph analytics, encode
categorical variables, K-nearest neighbors)
* improvements to existing modules (add grouping support to elastic
net and PCA, add cross validation to elastic net, array input for
K-means, verbose output option for DT and RF, limit itemset size in
association rules, various madpack installer improvements)
* platform updates (PostgreSQL 9.6)
* bug fixes
* doc improvements

For more information including release notes, please see:
https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.10

To run check RAT, please do:

$mvn verify

first to get the correct RAT output.  Look inside of pom.xml to see the
classes of exceptions we're managing there for RAT.

We're voting upon the source (tag):  rc/1.10.0-rc2
https://github.com/apache/incubator-madlib/tree/rc/1.10.0-rc2

Source Files:
https://dist.apache.org/repos/dist/dev/incubator/madlib/1.10.0-incubating-rc2/

Commit to be voted upon:
https://github.com/apache/incubator-madlib/commit/a3863b6c2407eb28ba007f6288d167bf88674e6d

KEYS file containing PGP Keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS

For your convenience, the recent ASF licensing guidance to the MADlib
community is summarized here:
https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance

Please vote:

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

*** The vote will be open until Friday Mar 10 at 6 pm Pacific time. ***

Thank you,
Frank McQuillan

New opportunity at ApacheCon: Community Sponsorship

2017-03-07 Thread Sally Khudairi 
Hello Apache Community --it's my pleasure to announce that we have a new 
opportunity for Apache projects, communities, and their supporters to bolster 
their commitment and visibility at ApacheCon.


For the first time, community members of a single Apache Project (e.g., Flex) 
or category (e.g., IoT) have the opportunity to contribute single-source or 
pooled funds towards its presence at ApacheCon. 

This can represent a collective of contributors comprising organizations and 
individuals. Sponsorship may be coordinated internally from within an Apache 
community (e.g., CloudStack) or activity area (e.g., Web Frameworks). 

Whether contributing a few hundred dollars or the full amount, individuals and 
organizations can now apply their collective resources to directly benefit 
Apache projects and areas of interest at the conference. Standing stronger 
together! 

A minimum financial commitment is required, and contributors will be recognized 
and receive select Sponsor benefits. Details can be found at 
http://events.linuxfoundation.org/events/apachecon-north-america/sponsors/community-sponsor

I am very excited to have developed this program to help our communities, and 
am thrilled that ApacheCon's producers, The Linux Foundation, have agreed to 
work with us on this.

Feel free to let me know if you have any questions.


Thank you in advance for your support!

Warmest regards,
Sally

= = = = =  
vox +1 617 921 8656
gvox +1 646 598 4616
skype sallykhudairi

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

Re: [DISCUSS] Apache CarbonData podling graduation

2017-03-07 Thread Niclas Hedhman 
I think the wording needs tuning, and my own interpretation of the intent
has been,

Project claims itself to comply, and list any exceptions and why that is
the case.

I think that can deal with the invariance that exists.

Cheers
Niclas


On Mar 7, 2017 14:48, "Jim Apple"  wrote:

> > Actually, the Maturity Model can be a very nice framework to organize
> > incubation around.
>
> If you're talking about a platonic MM, then I agree. If you are
> talking about the MM at
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> ,
> I think it needs to be much more carefully written and much more
> accurate to be a "nice framework". In particular, "aims to capture the
> invariants of Apache projects ... A mature Apache project complies
> with all the elements of this model" is wishful thinking or outdated
> or both.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: GitHub workflows?

2017-03-07 Thread Niclas Hedhman 
Thanks Marvin for the pointers.
But my question is not so much whether we can accept pull requests or
handle GH issues. It is whether it is ok to be the *primary* workflow and
dev@ is an archive.

The podling is coming from a GitHub-only culture, and the core team in the
same company. S...

1. I think all development is pull requests, whether it is from committers
or external contributors. I.e. RTC. Hard to tell external from internal
patches, so to speak

2. the dev@ list receives all the Issue comments and pull requests.

3. A somewhat large number (300) of open GH issues are on the old GH
repository, brought over selectively, seemingly along with the work that
goes with them (but I could be wrong here).

3. Some decision-making is _likely_ happening face-to-face.

The overall effect is that if you are used to ASF projects, this podling
feels very different than most other projects here. dev@ is a cold place at
the moment, and I don't like it. A bit like some projects have tried to do
(nearly) "JIRA only" discussions, which I also found somewhat "off-putting".

Anyway, I will continue to nudge them in the "common direction" and shout
again if I feel there is a problem.

Cheers
Niclas



On Tue, Mar 7, 2017 at 2:23 PM, Greg Stein  wrote:

> On Mon, Mar 6, 2017 at 11:34 PM, Marvin Humphrey 
> wrote:
> >...
>
> > So, the questions I would ask are, are all those comments making it to
> the
> > list?  And are the podling participants showing through their actions
> that
> > they understand inclusiveness, by ensuring that dev list readers are able
> > to
> > follow along?
> >
>
> Pull requests and issues, and the comments upon them are all delivered to
> an archived PMC mailing list. These tend to go to dev@, issues@, or
> notifications@ ... as a PMC chooses.
>
> I checked with Legal, and we are required to forward this stuff to a list.
>
>
> > For what it's worth, on one dev list I'm on, pull requests make it to the
> > dev
> > list, but commenting on a commit via the Github interface only triggers a
> > private notification -- the comment never makes it to our dev list.  We
> > mostly
> > avoid Github commit comments for that reason, so inclusiveness is not
> > harmed
> > -- but people new to Apache might not handle things that way.
> >
>
> We can forward those, if you want. Probably should.
>
> Cheers,
> -g
>



-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org  - New Energy for Java