Re: Apache Apex as part of Bigtop

[Thomas Weise <th...@apache.org>]

Hi RJ,

Yes, we are going to nominate a maintainer and will ensure Apex related
build issues will be resolved.

Thanks,
Thomas


On Tue, Jan 26, 2016 at 7:00 PM, RJ Nowling <rn...@gmail.com> wrote:

> Hi Thomas,
>
> Is there someone who would be willing to take responsibility for
> maintaining the Apache Apex packages in Bigtop?
>
> We generally like to find a maintainer for each package and add them to
> our maintainers list.  This way we know who to contact if a build fails and
> blocks a release.  If there is no maintainer (and the build has problems),
> we use that as grounds for removing the package from Bigtop.
>
> Thanks,
> RJ
>
>
> On Tue, Jan 26, 2016 at 3:00 PM, <na...@reactor8.com> wrote:
>
>> Hi Thomas,
>>
>> Thanks for your interest in bigtop and getting apex componentized and
>> supported in bigtop.
>>
>> Some general getting started info on bigtop contributions:
>>
>> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
>>
>> Would start to look at src of the project at a few of the current
>> components.
>>
>> /bigtop/bigtop-packages/src/common
>> /bigtop/bigtop-packages/src/deb
>> /bigtop/bigtop-packages/src/rpm
>>
>> That will be the basics of build and packaging.  If datatorrent has some
>> existing rpm, deb setups can start with that and tweak to conform to bigtop
>> practices if needed.
>>
>> For deploy/config side of things can look at references in:
>>
>> /bigtop/bigtop-deploy/puppet/modules/*
>>
>> If you guys don’t have existing puppet resources feel free to ping the
>> list and one of a few in the group can help get you guys going with that.
>>
>> Also take a look at the root .bom file (/bigtop/bigtop.bom) and look at
>> how you guys might define apex and some of its possible build dependencies
>> (ie: apex requires that hdfs be running underneath it)
>>
>> After build and packaging going can start to look at some relevant apex
>> smoke tests that might already be available and included, some references
>> there at:
>>
>> /bigtop/bigtop-tests/smoke-tests/*
>>
>> Ping list as you guys dig in with any questions/issues
>>
>> Nate
>>
>>
>> -----Original Message-----
>> From: Thomas Weise [mailto:thw@apache.org]
>> Sent: Monday, January 25, 2016 5:21 PM
>> To: dev@bigtop.apache.org
>> Subject: Apache Apex as part of Bigtop
>>
>> Dear Bigtop community,
>>
>> I'm member of the Apache Apex (incubating) PPMC and wanted to explore the
>> possibility of getting Apex into Bigtop. Our web site is at:
>>
>> http://apex.incubator.apache.org/
>>
>> Apex was originally developed at DataTorrent since 2012 and entered
>> incubation last August.
>>
>> Thanks,
>> Thomas
>>
>>
>

Re: Apache Apex as part of Bigtop

[RJ Nowling <rn...@gmail.com>]

Great, thanks!  When you create the patches, please add that person to our
MAINTAINERS file as part of the patch.

On Tue, Jan 26, 2016 at 9:21 PM, Thomas Weise <th...@apache.org> wrote:

> Hi RJ,
>
> Yes, we are going to nominate a maintainer and will ensure Apex related
> build issues will be resolved.
>
> Thanks,
> Thomas
>
>
> On Tue, Jan 26, 2016 at 7:00 PM, RJ Nowling <rn...@gmail.com> wrote:
>
>> Hi Thomas,
>>
>> Is there someone who would be willing to take responsibility for
>> maintaining the Apache Apex packages in Bigtop?
>>
>> We generally like to find a maintainer for each package and add them to
>> our maintainers list.  This way we know who to contact if a build fails and
>> blocks a release.  If there is no maintainer (and the build has problems),
>> we use that as grounds for removing the package from Bigtop.
>>
>> Thanks,
>> RJ
>>
>>
>> On Tue, Jan 26, 2016 at 3:00 PM, <na...@reactor8.com> wrote:
>>
>>> Hi Thomas,
>>>
>>> Thanks for your interest in bigtop and getting apex componentized and
>>> supported in bigtop.
>>>
>>> Some general getting started info on bigtop contributions:
>>>
>>> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute
>>>
>>> Would start to look at src of the project at a few of the current
>>> components.
>>>
>>> /bigtop/bigtop-packages/src/common
>>> /bigtop/bigtop-packages/src/deb
>>> /bigtop/bigtop-packages/src/rpm
>>>
>>> That will be the basics of build and packaging.  If datatorrent has some
>>> existing rpm, deb setups can start with that and tweak to conform to bigtop
>>> practices if needed.
>>>
>>> For deploy/config side of things can look at references in:
>>>
>>> /bigtop/bigtop-deploy/puppet/modules/*
>>>
>>> If you guys don’t have existing puppet resources feel free to ping the
>>> list and one of a few in the group can help get you guys going with that.
>>>
>>> Also take a look at the root .bom file (/bigtop/bigtop.bom) and look at
>>> how you guys might define apex and some of its possible build dependencies
>>> (ie: apex requires that hdfs be running underneath it)
>>>
>>> After build and packaging going can start to look at some relevant apex
>>> smoke tests that might already be available and included, some references
>>> there at:
>>>
>>> /bigtop/bigtop-tests/smoke-tests/*
>>>
>>> Ping list as you guys dig in with any questions/issues
>>>
>>> Nate
>>>
>>>
>>> -----Original Message-----
>>> From: Thomas Weise [mailto:thw@apache.org]
>>> Sent: Monday, January 25, 2016 5:21 PM
>>> To: dev@bigtop.apache.org
>>> Subject: Apache Apex as part of Bigtop
>>>
>>> Dear Bigtop community,
>>>
>>> I'm member of the Apache Apex (incubating) PPMC and wanted to explore
>>> the possibility of getting Apex into Bigtop. Our web site is at:
>>>
>>> http://apex.incubator.apache.org/
>>>
>>> Apex was originally developed at DataTorrent since 2012 and entered
>>> incubation last August.
>>>
>>> Thanks,
>>> Thomas
>>>
>>>
>>
>