[DRAFT] Incubator PMC Board Report - March 2018

[John D. Ament]

frequent release cadence.
  [X](ariatosca) John D. Ament
 Comments: It's a small group.  On list communication is still a
struggle.
  [X](ariatosca) Jakob Homan
 Comments: Small but growing slowly and heading in the right direction.

IPMC/Shepherd notes:




Crail

Crail is a storage platform for sharing performance critical
data in distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

Three most important issues to address in the move towards graduation:

1  Community building
2. Improve project visibility
3. Create a first release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

* None

How has the community developed since the last report?

* We got one new active committer.
  After moving the code base under apache/incubator-crail,
  we are re-gaining frequency on downloads and followers
* To advertise the project, we are preparing for the
  SF Spark Summit presentation on Crail.
  We got a presentation on Crail's non-volatile data
  management accepted at OpenFabrics workshop in April.

How has the project developed since the last report?

* Podling name search done and approved by Legal.
* Applied fixes resolving two major bugs within Crail code.
* New project front end website.


How would you assess the podling's maturity?

 [X] Initial setup
 [X] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:
 N/A

When were the last committers or PPMC members elected?
 2017-11-01 (entering incubation)

Signed-off-by:

 [x] (crail) Julian Hyde
 Comments: Good progress on the "admin" aspects of incubation,
   and dev list is showing good activity.
 [ ] (crail) Luciano Resende
 Comments:
 [ ] (crail) Raphael Bircher
 Comments:

IPMC/Shepherd notes:




Daffodil

Apache Daffodil is an implementation of the Data Format Description
Language (DFDL) used to convert between fixed format data and XML/JSON.

Daffodil has been incubating since 2017-08-27.

Three most important issues to address in the move towards graduation:

  1. Complete first Apache release as an Incubator
  2. Broaden base of contributors and build the community (e.g. work with
other Apache projects where Daffodil could provide extra functionality)
  3. Improve documentation on setting up a development environment to ease
the addition of new developers

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

- Outstanding legal issue regarding Open Grid Forum document inclusion in
Daffodil (LEGAL-369)

How has the community developed since the last report?

- No new committers. However, we have had activity from a couple outside
users on the mailing lists asking about Daffodil capabilities/usage

How has the project developed since the last report?

- All SGA/CLAs have been submitted (from Tresys, IBM, and NCSA), all code
relicensed to ASF, and package namespace switched to org.apache.daffodil
- Development pace has continued without any notable issues
- The first release candidate was created in February 2018. However, bugs
were found that required an rc2 release. Those issues were resolved, but
issues related to the LICENSE and NOTICE files were raised in the rc2
release vote. This is expected to require an rc3 release, planned to start
voting in early March.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-09-06 - 2.0.0 (pre-Apache release)

When were the last committers or PPMC members elected?

- None, same as project incubation

Signed-off-by:

  [X](daffodil) John D. Ament
 Comments: Project is moving in the right direction, and aiming for
their first ASF release.
  [ ](daffodil) David Fisher
 Comments:

IPMC/Shepherd notes:




Druid


Druid is a high-performance, column-oriented, distributed data store.

Druid has been incubating since 2018-02-28.

Three most important issues to address in the move towards graduation:
 1. Migrate existing contributors and users to apache mailing lists.
 2. Move the source code and website to apache infrastructure.
 3. Plan and execute our first Apache release.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* The team is working on the items on the Incubation Checklist.
* We’re working on moving the existing mailing lists, source code, github
issues and website to Apache Infrastructure.
* In order to keep the project momentum up until the migration is complete
we are continuing the development on existing druid repository.
* We are considering doing the 0.12.0 release before migrating source code
to apache, since the IPMC has already voted for it and migrating infra to
apache might take a while, and we don't want to bl

Re: Please do not retire Myriad

[John D . Ament]

Javi,

It looks like your repo is at 
https://git-wip-us.apache.org/repos/asf?p=incubator-myriad.git;a=summary
the push URL would be 
https://git-wip-us.apache.org/repos/asf/incubator-myriad.git

However, only committers on the project have write access.

John

On 2018/02/28 08:26:10, Javi Roman  wrote: 
> Totally agree Justin, I really don't like a parallel infrastructure
> ... I would be happy erasing all this parallel stuff and continuing
> with the ASF incubator infra. We only need some help in order to avoid
> the death of this project.
> 
> (I know www.myriad-framework.org breaks the trading and trademarks of
> ASF, this is something to change whether the only option is to
> continue the project out of ASF).
> 
> I have to say I don't know how to push up the project inside ASF, I
> can create PRs at GitHub ... but I afraid never will be attended, the
> same with JIRA and so on.
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> 
> 
> On Wed, Feb 28, 2018 at 9:05 AM, Justin Mclean  
> wrote:
> > Hi,
> >
> >> Unfortunately I don't have permissions for updating the report.
> >
> > It possible to email the report in and/or ask for someone to submit it for 
> > you.
> >
> > It’s unclear to me why you seem to be duplicating the site and mailing 
> > list if you want to keep the project at Apache. Decisions and communication 
> > needs to be happening on this list and you need to use Apache 
> > infrastructure for the site. I'm not sure trademarks would look too fondly 
> > on the site being hosted at http://www.myriad-framework.org.  Either you 
> > want the project to stay at Apache or you are forking it. If you are 
> > forking it then your project is not an Apache incubating project and that 
> > site (including probably the domain name) http://www.myriad-framework.org 
> > would need some work to comply with ASF policy on branding and trademarks. 
> > [1]
> >
> >> The other option is to change the incubator ownership to interested
> >> people like some of us.
> >
> > Are your project mentors still active? They may be able to help here. 
> > Ownership cannot just be handed over but they (and any other active PMC 
> > member) could vote new PMC members in.
> >
> > Thanks,
> > Justin
> >
> > 1. https://www.apache.org/foundation/marks/domains.html
> 

Re: Please do not retire Myriad

[John D . Ament]

Javi,

Anyone from the community can work on the report.  

John

On 2018/02/13 06:35:29, Javi Roman <jroman.espi...@gmail.com> wrote: 
> Hi John, this report is something that anyone can fill, or it's
> restricted to PMCs only?
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> 
> 
> On Sun, Feb 11, 2018 at 2:28 PM, John D. Ament <johndam...@apache.org> wrote:
> > All,
> >
> > If you don't want the podling to retire, the biggest impacting thing you 
> > can do is make sure a report is filed for the next reporting period.
> >
> > I believe without that, I can only assume that there's no interest in 
> > remaining as an Apache project.
> >
> > John
> >
> > On 2018/02/02 19:45:22, Brandon Gulla <gulla.bran...@gmail.com> wrote:
> >> While I am not a committer at the moment, having contributed to Myriad in
> >> the early days, I am able to help review potential PRs and changes down the
> >> road.
> >>
> >> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean <jus...@classsoftware.com>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > > 1. Try to convince to Apache managers (I don't now the correct term)
> >> > > for an exception to allow you accept commits from external
> >> > > contributors (like me).
> >> >
> >> > All and any contributions are welcome, that is not he issue here. The
> >> > board requires oversight of at least 3 (P)PMC members. For incubating
> >> > project generally the committers are the PPMC.
> >> >
> >> > > 2. Follow your first proposal, create a new github organization, for
> >> > > example (github.com/myriad) and working there.
> >> >
> >> > As the software is under the Apache license anyone can do this, you don't
> >> > need to ask for permission.
> >> >
> >> > > Maybe in the future we can try go to Apache incubation again.
> >> >
> >> > And I’m sure the Apache incubator would welcome that.
> >> >
> >> > > I guess we are three people with interest into continue the project,
> >> > > you, Juan P. and myself. From my side I am working in a local fork for
> >> > > enhancing some stuff.
> >> >
> >> > Alternatively if the people above have contributed and promoted the
> >> > project (I’m sorry but I don’t know the full history here) and the 
> >> > currenrt
> >> > PPMC recognise that and votes you in as PPMC members then that may be
> >> > enough to continue the project at Apache.
> >> >
> >> > Thanks.
> >> > Justin
> >>
> >>
> >>
> >>
> >> --
> >> Brandon
> >>
> 

Re: Please do not retire Myriad

[John D . Ament]

All,

If you don't want the podling to retire, the biggest impacting thing you can do 
is make sure a report is filed for the next reporting period.

I believe without that, I can only assume that there's no interest in remaining 
as an Apache project.

John

On 2018/02/02 19:45:22, Brandon Gulla  wrote: 
> While I am not a committer at the moment, having contributed to Myriad in
> the early days, I am able to help review potential PRs and changes down the
> road.
> 
> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
> wrote:
> 
> > Hi,
> >
> > > 1. Try to convince to Apache managers (I don't now the correct term)
> > > for an exception to allow you accept commits from external
> > > contributors (like me).
> >
> > All and any contributions are welcome, that is not he issue here. The
> > board requires oversight of at least 3 (P)PMC members. For incubating
> > project generally the committers are the PPMC.
> >
> > > 2. Follow your first proposal, create a new github organization, for
> > > example (github.com/myriad) and working there.
> >
> > As the software is under the Apache license anyone can do this, you don't
> > need to ask for permission.
> >
> > > Maybe in the future we can try go to Apache incubation again.
> >
> > And I’m sure the Apache incubator would welcome that.
> >
> > > I guess we are three people with interest into continue the project,
> > > you, Juan P. and myself. From my side I am working in a local fork for
> > > enhancing some stuff.
> >
> > Alternatively if the people above have contributed and promoted the
> > project (I’m sorry but I don’t know the full history here) and the 
> > currenrt
> > PPMC recognise that and votes you in as PPMC members then that may be
> > enough to continue the project at Apache.
> >
> > Thanks.
> > Justin
> 
> 
> 
> 
> -- 
> Brandon
> 

Re: [Github] PR review

[John D . Ament]

Hi,

I just want to point out, Mohit is a committer on the project.  I'm not sure 
what your workflow is, but considering the lack of developers on the project 
maybe it makes sense to recommend people to commit directly to the repository?

John

On 2018/02/07 09:07:18, Juan P  wrote: 
> Please, can anyone merge this PR?
> 
> https://github.com/apache/incubator-myriad/pull/104
> 
> It is very important/necessary for the proper functioning of Travis.
> 
> 
> Thanks
> 

[DISCUSS] Retire Myriad?

[John D. Ament]

Hi All,

It seems that Myriad has more or less stopped activity.  Recent user
question has lead to a recommendation to avoid using Myriad in production
[1], git commits seem to have stopped a long time ago [2], and potential
community contributions [3] have gone unanswered.  Your reports have been
missing for some time.

I believe based on this, it's time for the Myriad podling

[1]:
https://lists.apache.org/thread.html/4d5db8709e48a6de732726ab68e6b6b09768a2f026a5ad1b44a208a1@%3Cdev.myriad.apache.org%3E
[2]:
https://github.com/apache/incubator-myriad/commit/382eb7bc77cec1ac7a13d027d8c28cfb1a379a6b
[3]: https://github.com/apache/incubator-myriad/pulls

January 2018 Report Finalized

[John D. Ament]

I have finalized the report and plan to submit to the board shortly -
https://wiki.apache.org/incubator/January2018

The reports from Livy, Spot, Milagro and Myriad were not received.  The
report from Airflow was received but did not receive mentor sign off.

John

[DRAFT] Incubator PMC Board Report - January 2018

[John D. Ament]

rding of new committers and will be
continuing to do this (extended emails with a lot of explanations on why we
are doing things the way we are)
  *   Project has bootstrapped quickly and we have mailing lists, website,
JIRA etc. all set up and running.
  *   Testing coverage has been improved over the initial code base

How has the project developed since the last report?

  *   There was no last report.

How does the podling rate their own maturity?

  *   We have a mix of new participants and experienced Apache people
involved.
  *   So far, the new participants have shown great willingness and success
in adopting the Apache Way.
  *   However, we still need to continue:
 *   the on-boarding
 *   increasing the diversity of the team
  *   Also, will we need to decide and establish all the processes involved
in releasing software at Apache


Date of last release:

  N/A

When were the last committers or PPMC members elected?

  N/A

Signed-off-by:

  [ ](plc4x) Greg Trasuk
 Comments:
  [ ](plc4x) Justin Mclean
 Comments:
  [ ](plc4x) Luciano Resende
 Comments:
  [X](plc4x) Stefan Bodewig
 Comments:

IPMC/Shepherd notes:




Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that
can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

Three most important issues to address in the move towards graduation:

  1. Grow the community
  2. Get the 0.10 release out
  3. Address issues

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  There's been a bit of a lull as of late in the project.
  I'm hopeful that it will pick up some speed soon.

How has the community developed since the last report?

  No noticeable change since last report.

How has the project developed since the last report?

  N/A. Working on it!

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [x] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](ponymail) Andrew Bayer
 Comments:
  [X](ponymail) John D. Ament
 Comments: Would be good to get this podling moving.  Needs more
committers to be truly viable.

IPMC/Shepherd notes:




Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system built
on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
processing techniques that scale to billions of triples across multiple
nodes.
Rya provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:
  1. Have more releases as part of the Apache Foundation
  2. Increase diversity of contributors.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No

How has the community developed since the last report?

  * Working on the next release
  * Starting discussions about graduation

How has the project developed since the last report?

  * Implemented a cache for Fluo query metadata
  * Added a Twill App for running the periodic service
  * Fixed several bugs

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [x] Nearing graduation
  [ ] Other:

Date of last release:

  2017-10-10

When were the last committers or PPMC members elected?

 * PPMC member Caleb Meier elected on Jan 3rd, 2017

Signed-off-by:

  [x](rya) Josh Elser
 Comments: Have been pushing community towards graduation. IMO, they
are ready.
  [ ](rya) Edward J. Yoon
 Comments:
  [ ](rya) Venkatesh Seetharam
 Comments:
  [ ](rya) Billie Rinaldi
 Comments:

IPMC/Shepherd notes:



SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

Three most important issues to address in the move towards graduation:

  1.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](sdap) Jörn Rottmann
 Comments:
  [ ](sdap) Raphael Bircher
 Comments:
  [ ](sdap) Suneel Marthi
 Comments

[DRAFT] Incubator PMC Board Report - December 2017

[John D. Ament]

All,

Below is the current draft of our report.  As of now, we have 5 reports
missing and 4 reports not signed off on.  I hope we can get that resolved
in the next few days.  I have copied those podlings impacted.

Incubator PMC report for December 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are currently 53 podlings incubating.  In the month of November, we
executed six releases, added one IPMC member and received the resignation
of another (which is in flight until their sole podling retires).  We added
two podlings to our roster, have a few more in the pipeline and have one
podling planning to graduate this month.

* Community

  New IPMC members:

  - Michael Semb Wever

  People who left the IPMC:

  - Upayavira (not processed in LDAP yet)

* New Podlings

  - Crail
  - Service Comb

* Podlings that failed to report, expected next month

  - Amaterasu - Activity stopped late November
  - Aria Tosca
  - HTrace - 0 on list activity
  - Pony Mail - Low activity, suspect just missed.
  - Wave - Retiring

* Podlings Missing sign off

  - Griffin
  - Myriad
  - OpenWhisk
  - Spot

* Graduations

  The board has motions for the following:

  - Trafodion
  - Your podling here?
  - Your podling here?

* Releases

  The following releases entered distribution during the month of
  November:

  - 2017-11-01 Apache Freemarker  2.3.27
  - 2017-11-08 Apache Netbeans HTML4J 1.5
  - 2017-11-15 Apache Mnemonic0.10.0
  - 2017-11-15 Apache MXNet   0.12.1
  - 2017-11-18 Apache Netbeans HTML4J 1.5.1
  - 2017-11-28 Apache Griffin 0.1.6

* IP Clearance



* Legal / Trademarks



* Infrastructure



* Miscellaneous



* Credits

--
   Table of Contents
Amaterasu
AriaTosca
Crail
Daffodil
Gearpump
Griffin
Hivemall
HTrace
Myriad
Omid
OpenWhisk
PageSpeed
Pony Mail
Pulsar
Quickstep
SAMOA
SDAP
SINGA
Spot
Superset
Taverna
Tephra
Trafodion
Wave

--


Amaterasu

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

Amaterasu has been incubating since 2017-09-07.

Three most important issues to address in the move towards graduation:

  1.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](amaterasu) Jean-Baptiste Onofré
 Comments:
  [ ](amaterasu) Olivier Lamy
 Comments:
  [ ](amaterasu) Davor Bonaci
 Comments:

IPMC/Shepherd notes:

  johndament:
The podling was moving OK until the end of November, not sure if it's a
holiday lull.


AriaTosca

ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.

AriaTosca has been incubating since 2016-08-27.

Three most important issues to address in the move towards graduation:

  1.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](ariatosca) Suneel Marthi
 Comments:
  [ ](ariatosca) John D. Ament
 Comments:  Activity on list is picking up over the slack
conversations.  A community member is planning to write a report, however
it indicates a corporate hierarchy issue within the project that needs to
get solved.
  [ ](ariatosca) Jakob Homan
 Comments:

IPMC/Shepherd notes:



---
Crail

Crail is a storage platform for sharing performance critical
data in distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

Three most important issues to address in the move towards graduation:

  1. Finish project setup
  2. Community building
  3. Create a first release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None.

How has the community developed since the last report?

  N/A

How has the project developed since

Re: [DRAFT] Incubator PMC Board Report - November 2017

[John D. Ament]

Hi,

Still missing sign off from: Guacamole and Ratis.  Please get these in
ASAP, to avoid being marked monthly (especially concerning for Guacamole
who's possibly graduating this month).

The following reports have not been filed, at this point I am assuming they
will be missed and roll over: iota (likely to retire), Milagro, Myriad
(also likely to retire).

John

On Mon, Nov 6, 2017 at 2:46 PM John D. Ament <johndam...@apache.org> wrote:

> All,
>
> Below is the current draft.  We have 7 podling reports missing/not signed
> off.  Hopefully they can come soon.
>
> Incubator PMC report for November 2017
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> October was a quieter month in the incubator.  We executed 4 podling
> releases, had no changes in staff.  One new podling joined, and are having
> graduation discussions for two podlings.  We expect Mnemonic to fully
> graduate this month.
>
> * Community
>
>   New IPMC members:
>
>   - None
>
>   People who left the IPMC:
>
>   - None
>
> * New Podlings
>
>   - SDAP
>
> * Podlings that failed to report, expected next month
>
>
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Guacamole?
>   - Impala?
>   - Mnemonic
>   - Your podling here?
>   - Your podling here?
>
> * Releases
>
>   The following releases entered distribution during the month of
>   October:
>
>   - 2017-10-04 Apache Juneau 6.4.0
>   - 2017-10-11 Apache Rya 3.2.11
>   - 2017-10-13 Apache Pulsar 1.20.0
>   - 2017-10-30 Apache MXNet 0.12.0
>
> * IP Clearance
>
>
>
> * Legal / Trademarks
>
>
>
> * Infrastructure
>
>
>
> * Miscellaneous
>
>
>
> * Credits
>
> --
>Table of Contents
> Amaterasu
> Daffodil
> Edgent
> Guacamole
> Heron
> Impala
> iota
> Joshua
> Milagro
> Myriad
> PageSpeed
> Ratis
> S2Graph
> Slider
> Tamaya
> Toree
> Unomi
>
> --
>
> 
> Amaterasu
>
> 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, the 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.
>
> Amaterasu has been incubating since 2017-09.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Prepare the first release
>   2. Grow up user and contributor communities
>   3. Prepare documentation
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Talks have been given in different events to promote and give
> visibility to Amaterasu
>
> How has the project developed since the last report?
>
>   * Code based was moved to the ASFs git box
>   * One new pull request was issued
>
> Date of last release:
>
>   N/A
>
> When were the last committers or PMC members elected?
>
>   N/A
>
>
>   [X] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   N/A
>
> Signed-off-by:
>
>   [X](amaterasu) Jean-Baptiste Onofré
>  Comments:
>   [ ](amaterasu) Olivier Lamy
>  Comments:
>   [X](amaterasu) Davor Bonaci
>  Comments: Initial setup continues: codebase has moved to the ASF
> repository.
>
> IPMC/Shepherd notes:
>
>
>
> 
> Daffodil
>
> Apache Daffodil is an implementation of the Data Format Description
> Language
> (DFDL) used to convert between fixed format data and XML/JSON.
>
> Daffodil has been incubating since 2017-08-27.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Obtaining SGAs
>   2. Establishing new apache-centric infrastructure
>   3. Broadening base of contributors
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> - Only that chasing the SGAs down is going to take some time, th

Re: [DISCUSS] Retire Myriad

[John D. Ament]

Ok.  I'm willing to wait.  However, you'll need to follow up quickly.  I'll 
also point out that the podling report is due, none submitted.  Hopefully one 
can be provided soon.

John

On 2017-11-07 12:57, mohit soni <mohitsoni1...@gmail.com> wrote: 
> I think we should be able to address the concerns around PR reviews and
> releases while still being a part of the Incubator.
> 
> Also, I am fine with driving future features with help of Darin and others
> in the community.
> 
> Honestly, I would prefer to keep the project in the Incubator for all the
> benefits it provides. At the very least, we can give it another shot.
> 
> If we are all fine with keeping the project alive in the Incubator, we can
> then move on to discuss future features and releases.
> 
> Best
> Mohit
> 
> On Tue, Nov 7, 2017 at 7:04 AM, John D. Ament <johndam...@apache.org> wrote:
> 
> > Just so you are aware, it is completely feasible to fork the project to
> > continue work on it outside of Apache, if you decide on retirement.  We
> > generally don't even pursue naming issues for former podlings, since we
> > would have not done anything to claim the TM.
> >
> > Maybe it is possible to build up the project outside of apache with just a
> > couple of committers and roll your own releases.  Build up a strong enough
> > community and come back (if it makes sense).
> >
> > John
> >
> > On 2017-11-06 14:56, Santosh Marella <mare...@gmail.com> wrote:
> > > Agree with Darin and Mohit. I think the project is still very relevant,
> > but
> > > there is no one actively working on it - I myself couldn't put time on it
> > > as the problem space my employer operates in is very different from
> > > Myriad's. If Mohit is willing to drive the future features and Darin is
> > > ready to back him up, I honestly think this deserves another shot. We
> > have
> > > already seen other folks expressing interest to offer support (in terms
> > of
> > > code reviews, vetting releases etc).
> > >
> > > Thanks,
> > > Santosh.
> > >
> > > On Mon, Nov 6, 2017 at 11:45 AM, Darin Johnson <dbjohnson1...@gmail.com>
> > > wrote:
> > >
> > > > I certainly think the project is relevant but I'm concerned if it
> > belongs
> > > > in Apache.  When I was active it was difficult to get people to review
> > pull
> > > > requests and when releasing v0.2.0 it was hard to even get people to
> > vote
> > > > for a release.  If only a few people are going to work on it, maybe
> > it's
> > > > easier to develop outside the incubator until there's something stable?
> > > >
> > > > I'd be interested in potentially working on it again provided there's
> > at
> > > > least two other people actively working on it.
> > > >
> > > > Darin
> > > >
> > > > On Mon, Nov 6, 2017 at 1:13 PM, mohit soni <mohitsoni1...@gmail.com>
> > > > wrote:
> > > >
> > > > > The project's core idea of dynamic creation and management of YARN
> > > > clusters
> > > > > without creating static partitions is still relevant. This project
> > and
> > > > it's
> > > > > community were one of the first movers in the still developing space
> > of
> > > > > stateful containerized distributed systems.
> > > > >
> > > > > I believe the project is currently lagging behind the fast paced
> > > > > development of Apache Mesos ecosystem project and is currently not
> > > > designed
> > > > > to take advantage of the fast growing Kubernetes (Apache License 2.0)
> > > > > ecosystem.
> > > > >
> > > > > I also believe the project is not just about the code which gets old
> > once
> > > > > it's written, unless tendered and cared for regularly, it's also
> > about
> > > > the
> > > > > community, and the mindshare.
> > > > >
> > > > > Here are the things that we can do to bring life to the project
> > again:
> > > > > 1. Refactor the project codebase to take advantage of the advances
> > in the
> > > > > Apache Mesos Ecosystem, which from my direct experience, will
> > simplify
> > > > the
> > > > > project codebase a lot, making it easier once again to maintain it,
> > while
> > > > > making it more relevant to the Apache Mesos community again.
> &

Re: [DISCUSS] Retire Myriad

[John D. Ament]

Just so you are aware, it is completely feasible to fork the project to 
continue work on it outside of Apache, if you decide on retirement.  We 
generally don't even pursue naming issues for former podlings, since we would 
have not done anything to claim the TM.

Maybe it is possible to build up the project outside of apache with just a 
couple of committers and roll your own releases.  Build up a strong enough 
community and come back (if it makes sense).

John

On 2017-11-06 14:56, Santosh Marella <mare...@gmail.com> wrote: 
> Agree with Darin and Mohit. I think the project is still very relevant, but
> there is no one actively working on it - I myself couldn't put time on it
> as the problem space my employer operates in is very different from
> Myriad's. If Mohit is willing to drive the future features and Darin is
> ready to back him up, I honestly think this deserves another shot. We have
> already seen other folks expressing interest to offer support (in terms of
> code reviews, vetting releases etc).
> 
> Thanks,
> Santosh.
> 
> On Mon, Nov 6, 2017 at 11:45 AM, Darin Johnson <dbjohnson1...@gmail.com>
> wrote:
> 
> > I certainly think the project is relevant but I'm concerned if it belongs
> > in Apache.  When I was active it was difficult to get people to review pull
> > requests and when releasing v0.2.0 it was hard to even get people to vote
> > for a release.  If only a few people are going to work on it, maybe it's
> > easier to develop outside the incubator until there's something stable?
> >
> > I'd be interested in potentially working on it again provided there's at
> > least two other people actively working on it.
> >
> > Darin
> >
> > On Mon, Nov 6, 2017 at 1:13 PM, mohit soni <mohitsoni1...@gmail.com>
> > wrote:
> >
> > > The project's core idea of dynamic creation and management of YARN
> > clusters
> > > without creating static partitions is still relevant. This project and
> > it's
> > > community were one of the first movers in the still developing space of
> > > stateful containerized distributed systems.
> > >
> > > I believe the project is currently lagging behind the fast paced
> > > development of Apache Mesos ecosystem project and is currently not
> > designed
> > > to take advantage of the fast growing Kubernetes (Apache License 2.0)
> > > ecosystem.
> > >
> > > I also believe the project is not just about the code which gets old once
> > > it's written, unless tendered and cared for regularly, it's also about
> > the
> > > community, and the mindshare.
> > >
> > > Here are the things that we can do to bring life to the project again:
> > > 1. Refactor the project codebase to take advantage of the advances in the
> > > Apache Mesos Ecosystem, which from my direct experience, will simplify
> > the
> > > project codebase a lot, making it easier once again to maintain it, while
> > > making it more relevant to the Apache Mesos community again.
> > > 2. Extend the project to take advantage of Kubernetes project's and
> > enable
> > > dynamic creation and management of YARN clusters on Kubernetes.
> > Kubernetes
> > > project now has great support for building stateful containerized
> > > applications. Refactoring work in Step #1 will lay the groundwork that
> > will
> > > make it easier to extend the project for the Kubernetes ecosystem.
> > >
> > > I'm happy to take a lead to drive both above initiatives, and can post a
> > > detailed plan and design for accomplishing above in coming months. I am
> > > also happy to take a lead on submitting monthly incubator reports.
> > >
> > > I truly believe that we should give the project one more chance to
> > > recuperate and thrive.
> > >
> > > Best
> > > Mohit
> > >
> > >
> > > On Mon, Nov 6, 2017 at 5:06 AM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > Just to be clear, this is a discussion thread.  Not a vote thread.
> > While
> > > > I believe many people vote +1 because they feel its clear why, when you
> > > > vote against the idea you should explain why.
> > > >
> > > > So please, treat this more like a discussion rather than a vote and
> > > > explain why.
> > > >
> > > > On 2017-11-05 13:50, mohit soni <mohitsoni1...@gmail.com> wrote:
> > > > > -1 vote to not retire the project (committer, PMC)
> > > > >
> > > > >

[DRAFT] Incubator PMC Board Report - November 2017

[John D. Ament]

All,

Below is the current draft.  We have 7 podling reports missing/not signed
off.  Hopefully they can come soon.

Incubator PMC report for November 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

October was a quieter month in the incubator.  We executed 4 podling
releases, had no changes in staff.  One new podling joined, and are having
graduation discussions for two podlings.  We expect Mnemonic to fully
graduate this month.

* Community

  New IPMC members:

  - None

  People who left the IPMC:

  - None

* New Podlings

  - SDAP

* Podlings that failed to report, expected next month



* Graduations

  The board has motions for the following:

  - Guacamole?
  - Impala?
  - Mnemonic
  - Your podling here?
  - Your podling here?

* Releases

  The following releases entered distribution during the month of
  October:

  - 2017-10-04 Apache Juneau 6.4.0
  - 2017-10-11 Apache Rya 3.2.11
  - 2017-10-13 Apache Pulsar 1.20.0
  - 2017-10-30 Apache MXNet 0.12.0

* IP Clearance



* Legal / Trademarks



* Infrastructure



* Miscellaneous



* Credits

--
   Table of Contents
Amaterasu
Daffodil
Edgent
Guacamole
Heron
Impala
iota
Joshua
Milagro
Myriad
PageSpeed
Ratis
S2Graph
Slider
Tamaya
Toree
Unomi

--


Amaterasu

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

Amaterasu has been incubating since 2017-09.

Three most important issues to address in the move towards graduation:

  1. Prepare the first release
  2. Grow up user and contributor communities
  3. Prepare documentation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * Talks have been given in different events to promote and give
visibility to Amaterasu

How has the project developed since the last report?

  * Code based was moved to the ASFs git box
  * One new pull request was issued

Date of last release:

  N/A

When were the last committers or PMC members elected?

  N/A


  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  N/A

Signed-off-by:

  [X](amaterasu) Jean-Baptiste Onofré
 Comments:
  [ ](amaterasu) Olivier Lamy
 Comments:
  [X](amaterasu) Davor Bonaci
 Comments: Initial setup continues: codebase has moved to the ASF
repository.

IPMC/Shepherd notes:




Daffodil

Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.

Daffodil has been incubating since 2017-08-27.

Three most important issues to address in the move towards graduation:

  1. Obtaining SGAs
  2. Establishing new apache-centric infrastructure
  3. Broadening base of contributors

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

- Only that chasing the SGAs down is going to take some time, though
this may be typical.

How has the community developed since the last report?

- Users: No change.

- Developers/Contributors: No change.

How has the project developed since the last report?

- Completed setup of the git repo.
- Started process of transfer of existing JIRA
tickets to Apache.
- Established our contributor/branch workflow and
published to wiki.
- Submitted Tresys SGA.
- Progress is being made on obtaining organizational
SGAs from NCSA and IBM.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

- No changes yet - same as at our project incubator
inception

Signed-off-by:

  [X](daffodil) John D. Ament
 Comments:
  [X](daffodil) David Fisher
 Comments:

IPMC/Shepherd notes:




Edgent

Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry

Re: [DISCUSS] Retire Myriad

[John D. Ament]

Just to be clear, this is a discussion thread.  Not a vote thread.  While I 
believe many people vote +1 because they feel its clear why, when you vote 
against the idea you should explain why.

So please, treat this more like a discussion rather than a vote and explain why.

On 2017-11-05 13:50, mohit soni <mohitsoni1...@gmail.com> wrote: 
> -1 vote to not retire the project (committer, PMC)
> 
> I believe the project is still relevant.
> 
> On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes <ni...@basjes.nl> wrote:
> 
> > +1 vote to retire (non-committer)
> >
> > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla <gulla.bran...@gmail.com>
> > wrote:
> >
> > > +1 vote to retire (non-committer)
> > >
> > > On Sun, Nov 5, 2017 at 9:03 AM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > All,
> > > >
> > > > Based on the current state of Myriad and prior discussions I'd like to
> > > > start the discussions around retiring the project.
> > > >
> > > > John
> > > >
> > >
> > >
> > >
> > > --
> > > Brandon
> > >
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
> 

[DISCUSS] Retire Myriad

[John D. Ament]

All,

Based on the current state of Myriad and prior discussions I'd like to
start the discussions around retiring the project.

John

Re: [FINAL DRAFT] Incubator PMC Board Report

[John D. Ament]

The final version of the report has been submitted -
https://wiki.apache.org/incubator/October2017

On Fri, Oct 13, 2017 at 1:52 PM John D. Ament <johndam...@apache.org> wrote:

> All,
>
> I plan to submit the below report to the board tomorrow, barring any major
> changes to the contents.  I have removed the completely non reporting
> podlings (Gossip, Myriad), but left in the two that reported without sign
> off (BatchEE, Milagro).  I hope that their mentors can review.  Thank you
> to everyone else for your diligence in getting the contents together.
>
> John
>
> ---
>
> Incubator PMC report for October 2017
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> There are currently 54 podlings incubating.  Podlings executed seven
> releases last month.  Two new IPMC members joined our fold and one new
> podling joined.  We presently have two or three podlings preparing to
> graduate this month.
>
> * Community
>
>   New IPMC members:
>
>   - Davor Bonaci
>   - Jacques Le Roux
>
> * New Podlings
>
>   - PageSpeed
>
> * Podlings that failed to report, expected next month
>
>   - BatchEE (report filed, not signed off by mentors)
>   - Gossip
>   - Milagro (report filed, not signed off by mentors)
>   - Myriad
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Mnemonic
>   - PredictionIO
>   - Juneau
>
> * Releases
>
>   The following releases entered distribution during the month of
>   September:
>
>   - 2017-09-04 Apache Airflow 1.8.2
>   - 2017-09-05 Apache MXNet 0.11.0
>   - 2017-09-13 Apache Impala 2.10.0
>   - 2017-09-13 Apache Mnemonic 0.9.0
>   - 2017-09-21 Apache Tephra 0.13.0
>   - 2017-09-27 Apache PredictionIO 0.12.0
>   - 2017-09-29 Apache Unomi 1.2.0
>
> * Legal / Trademarks
>
>   - Multiple podlings have pending requests in to legal to clarify SGAs,
> ICLAs.  Prompt responses would be appreciated.
>
> * Infrastructure
>
>   - A change to the mlreq process caused delays in creation of mailing
> lists for PageSpeed.  Work is on going to migrate to a new process for
> these requests that is agreeable for IPMC members to execute on.
>
> --
>Table of Contents
> Airflow
> Amaterasu
> Annotator
> BatchEE
> Daffodil
> DataFu
> FreeMarker
> Gobblin
> Gossip
> HAWQ
> Heron
> Juneau
> Livy
> Milagro
> MXNet
> Myriad
> NetBeans
> ODF Toolkit
> Rya
> SensSoft
> Spot
> Traffic Control
> Weex
>
> --
>
> 
> Airflow
>
> Airflow is a workflow automation and scheduling system that can be used to
> author and manage data pipelines.
>
> Airflow has been incubating since 2016-03-31.
>
> Three most important issues to address in the move towards graduation:
>
>   1. We are working on our 4th apache release 1.9.0 and are getting better
> at releases
>   2.
>   3.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> None
>
>
> How has the community developed since the last report?
>   1. We had our third official release 1.8.2 on Aug 7th 2017.
>   2. Since our last podling report 3 months ago (i.e. between July
>  5 & Sept 25, inclusive), we grew our contributors from 280 to 315
>   4. Since our last podling report 3 months ago (i.e. between July
>  5 & Sept 25, inclusive), we resolved 167 pull requests (currently at
> 1797 closed
>  PRs)
>   5. Since being accepted into the incubator, the number of companies
>  officially using Apache Airflow has risen from 30 to 114, 16 new from
> the last podling report.
>
>
>
> How has the project developed since the last report?
> See above : 167 PR resolved, 35 new contributors, & 16 new companies
> officially using it.
>
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [x] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   2017-08-07
>
> When were the last committers or PPMC members elected?
>
>   2017-01-01 fokko a.k.a Fokko Driespong (committer/PMC)
>
> Signed-off-by:
>
>   [ ](airflow) Chris Nauroth
>  Comments:
>   [x](airflow) Hitesh Shah
>  Comments:
>   [ ](airflow) Jakob Homan
>  Comments:
>
> IPMC/Shepherd notes:
> A quick look at this month's email and it

[FINAL DRAFT] Incubator PMC Board Report

[John D. Ament]

veloper has been setup, and has
started a project modifying the Daffodil code-base. This is still in the
pre-Apache
context, and we've no idea if they'll want to contribute back. But it does
show
both interest and that the technical barriers to entry for new developers
to be
productive are surmountable.

How has the project developed since the last report?

- A final consistent release/build of the legacy (pre-Apache) code-base
is over, all project efforts going forward can be Apache focused
once we have infrastructure setup.
- Progress is being made on obtaining the individual and organizational
SGAs.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [X] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 (none yet) -XX-XX

When were the last committers or PPMC members elected?

- No changes yet - same as at our project incubator inception

Signed-off-by:

 [X](daffodil) John D. Ament
Comments: Podling is still bootstrapping, looking for some feedback
from legal on approaches due to public sector relationship.
 [X](daffodil) David Fisher
Comments:


DataFu

DataFu provides a collection of Hadoop MapReduce jobs and functions in
higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.

DataFu has been incubating since 2014-01-05.

Three most important issues to address in the move towards graduation:

  1. Positive IPMC recommendation vote for graduation
  2. Address any IPMC feedback regarding graduation
  3. Continue releases

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  No new developments

How has the project developed since the last report?

  Added support for Pig macros distributed in JAR.
  Added a couple counting macros and TFIDF.
  Started graduation discussion in general list.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [x] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-10

When were the last committers or PPMC members elected?

  July 2016 (Eyal Allweil)

Signed-off-by:

  [ ](datafu) Ashutosh Chauhan
 Comments:
  [ ](datafu) Roman Shaposhnik
 Comments:
  [X](datafu) Ted Dunning
 Comments:

IPMC/Shepherd notes:

  johndament: The podling is attempting to graduate, however there are some
concerns raised within the discussion over how big the actual PMC is.
There have also been concerns raised over the removal of committer status.


FreeMarker

FreeMarker is a template engine, i.e. a generic tool to generate text output
based on templates. FreeMarker is implemented in Java as a class library for
programmers.

FreeMarker has been incubating since 2015-07-01.

Three most important issues to address in the move towards graduation:

  We have a large user base but a rather small group of committers.
  This was actually expected, given the maturity (and topic) of the project.
  While the FreeMarker 3 branch, which was started 8 month ago, will be much
  more appealing for contributors, development and growth due to that will
  certainly take a long time. In other respects the project is mature and
  ready for graduation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  We are eager to graduate but we're afraid that the number of active
  contributors will prevent that in the foreseeable future. But remaining in
  the incubator for serveral years is obviosly a problem as well.

How has the community developed since the last report?

  There were no changes since the last report.

How has the project developed since the last report?

  Most activity was in the FreeMarker 3 branch.
  The FreeMarker 2 branch was less active, but had some fixes and new
features.
  At the moment we are nearing the next release from the 2 branch.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-25

When were the last committers or PPMC members elected?

  2017-02-13 Woonsan Ko, committer (non-PMC)

Signed-off-by:

  [X](freemarker) Jacopo Cappellato
 Comments:
  [X](freemarker) Jean-Frederic Clere
 Comments:
  [X](freemarker) David E. Jones
 Comments:
  [X](freemarker) Ralph Goers
 Comments:
  [ ](freemarker) Sergio Fernández
 Comments:

IPMC/Shepherd notes:

  johndament: What is stopping Freemarker from graduating?

Re: [DRAFT] Incubator PMC Board Report - October 2017

[John D. Ament]

ntext, and we've no idea if they'll want to contribute back. But it does
show
both interest and that the technical barriers to entry for new developers
to be
productive are surmountable.

How has the project developed since the last report?

- A final consistent release/build of the legacy (pre-Apache) code-base
is over, all project efforts going forward can be Apache focused
once we have infrastructure setup.
- Progress is being made on obtaining the individual and organizational
SGAs.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [X] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 (none yet) -XX-XX

When were the last committers or PPMC members elected?

- No changes yet - same as at our project incubator inception

Signed-off-by:

 [X](daffodil) John D. Ament
Comments: Podling is still bootstrapping, looking for some feedback
from legal on approaches due to public sector relationship.
 [X](daffodil) David Fisher
Comments:

IPMC/Shepherd notes:



DataFu

DataFu provides a collection of Hadoop MapReduce jobs and functions in
higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.

DataFu has been incubating since 2014-01-05.

Three most important issues to address in the move towards graduation:

  1. Positive IPMC recommendation vote for graduation
  2. Address any IPMC feedback regarding graduation
  3. Continue releases

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  No new developments

How has the project developed since the last report?

  Added support for Pig macros distributed in JAR.
  Added a couple counting macros and TFIDF.
  Started graduation discussion in general list.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [x] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-10

When were the last committers or PPMC members elected?

  July 2016 (Eyal Allweil)

Signed-off-by:

  [ ](datafu) Ashutosh Chauhan
 Comments:
  [ ](datafu) Roman Shaposhnik
 Comments:
  [X](datafu) Ted Dunning
 Comments:

IPMC/Shepherd notes:

  johndament: The podling is attempting to graduate, however there are some
concerns raised within the discussion over how big the actual PMC is.
There have also been concerns raised over the removal of committer status.


FreeMarker

FreeMarker is a template engine, i.e. a generic tool to generate text output
based on templates. FreeMarker is implemented in Java as a class library for
programmers.

FreeMarker has been incubating since 2015-07-01.

Three most important issues to address in the move towards graduation:

  We have a large user base but a rather small group of committers.
  This was actually expected, given the maturity (and topic) of the project.
  While the FreeMarker 3 branch, which was started 8 month ago, will be much
  more appealing for contributors, development and growth due to that will
  certainly take a long time. In other respects the project is mature and
  ready for graduation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  We are eager to graduate but we're afraid that the number of active
  contributors will prevent that in the foreseeable future. But remaining in
  the incubator for serveral years is obviosly a problem as well.

How has the community developed since the last report?

  There were no changes since the last report.

How has the project developed since the last report?

  Most activity was in the FreeMarker 3 branch.
  The FreeMarker 2 branch was less active, but had some fixes and new
features.
  At the moment we are nearing the next release from the 2 branch.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-25

When were the last committers or PPMC members elected?

  2017-02-13 Woonsan Ko, committer (non-PMC)

Signed-off-by:

  [X](freemarker) Jacopo Cappellato
 Comments:
  [X](freemarker) Jean-Frederic Clere
 Comments:
  [X](freemarker) David E. Jones
 Comments:
  [X](freemarker) Ralph Goers
 Comments:
  [ ](freemarker) Sergio Fernández
 Comments:

IPMC/Shepherd notes:




Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingest

[DRAFT] Incubator PMC Board Report - October 2017

[John D. Ament]

ional
SGAs.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [X] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 (none yet) -XX-XX

When were the last committers or PPMC members elected?

- No changes yet - same as at our project incubator inception

Signed-off-by:

 [X](daffodil) John D. Ament
Comments: Podling is still bootstrapping, looking for some feedback
from legal on approaches due to public sector relationship.
 [X](daffodil) David Fisher
Comments:

IPMC/Shepherd notes:



DataFu

DataFu provides a collection of Hadoop MapReduce jobs and functions in
higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.

DataFu has been incubating since 2014-01-05.

Three most important issues to address in the move towards graduation:

  1. Positive IPMC recommendation vote for graduation
  2. Address any IPMC feedback regarding graduation
  3. Continue releases

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  No new developments

How has the project developed since the last report?

  Added support for Pig macros distributed in JAR.
  Added a couple counting macros and TFIDF.
  Started graduation discussion in general list.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [x] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-10

When were the last committers or PPMC members elected?

  July 2016 (Eyal Allweil)

Signed-off-by:

  [ ](datafu) Ashutosh Chauhan
 Comments:
  [ ](datafu) Roman Shaposhnik
 Comments:
  [ ](datafu) Ted Dunning
 Comments:

IPMC/Shepherd notes:

  johndament: The podling is attempting to graduate, however there are some
concerns raised within the discussion over how big the actual PMC is.
There have also been concerns raised over the removal of committer status.


FreeMarker

FreeMarker is a template engine, i.e. a generic tool to generate text output
based on templates. FreeMarker is implemented in Java as a class library for
programmers.

FreeMarker has been incubating since 2015-07-01.

Three most important issues to address in the move towards graduation:

  We have a large user base but a rather small group of committers.
  This was actually expected, given the maturity (and topic) of the project.
  While the FreeMarker 3 branch, which was started 8 month ago, will be much
  more appealing for contributors, development and growth due to that will
  certainly take a long time. In other respects the project is mature and
  ready for graduation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  We are eager to graduate but we're afraid that the number of active
  contributors will prevent that in the foreseeable future. But remaining in
  the incubator for serveral years is obviosly a problem as well.

How has the community developed since the last report?

  There were no changes since the last report.

How has the project developed since the last report?

  Most activity was in the FreeMarker 3 branch.
  The FreeMarker 2 branch was less active, but had some fixes and new
features.
  At the moment we are nearing the next release from the 2 branch.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-25

When were the last committers or PPMC members elected?

  2017-02-13 Woonsan Ko, committer (non-PMC)

Signed-off-by:

  [X](freemarker) Jacopo Cappellato
 Comments:
  [X](freemarker) Jean-Frederic Clere
 Comments:
  [X](freemarker) David E. Jones
 Comments:
  [X](freemarker) Ralph Goers
 Comments:
  [ ](freemarker) Sergio Fernández
 Comments:

IPMC/Shepherd notes:




Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

Gobblin has been incubating since 2017-02-23.

Three most important issues to address in the move towards graduation:

  1. Cut our first release.
  2. Elect new Committer(s) / PPMC.
  3. Update links on website and documentation.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

* 15+ maj

Re: Podling Report Reminder - September 2017

[John D. Ament]

Any other thoughts?  We're almost a month later, with very little on list 
activity.

On 2017-09-11 14:46, Darin Johnson <dbjohnson1...@gmail.com> wrote: 
> +1 retire
> 
> On Sun, Sep 10, 2017 at 8:41 PM, John D. Ament <johndam...@apache.org>
> wrote:
> 
> > All,
> >
> > A discussion back in July indicated the project had enough people to stay
> > alive.  There has been no report submitted and no on list activity since
> > then.
> >
> > Should we plan to retire Myriad after all?
> >
> > https://lists.apache.org/thread.html/7ef01bd386dea6ed651b6aea6783e4
> > e8e1d3cc5ace9b73bc7fae225f@%3Cdev.myriad.apache.org%3E
> >
> > John
> >
> > On 2017-09-05 21:40, johndam...@apache.org wrote:
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 20 September 2017, 10:30 am PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, September 06).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no knowledge of
> > > the project or necessarily of its field
> > > *   A list of the three most important issues to address in the move
> > > towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > > aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > > *   How does the podling rate their own maturity.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > https://wiki.apache.org/incubator/September2017
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> >
> 

Planning to remove rosters from active podlings

[John D. Ament]

All,

This coming weekend (9/29) I plan to remove the roster sections from all
podling status pages.

Podling rosters are meant to be managed in Whimsy.  The roster in the
status page is redundant and end up out of sync.  In place of the roster, I
will be adding a link automatically to all podling rosters.

John

[DRAFT] Incubator PMC Board Report - September 2017

[John D. Ament]

All,

Below is our current draft of the Incubator PMC board report.  We have 2
podlings not signed off and 4 podlings not reporting.   Hopefully they can
report soon.

John

Incubator PMC report for September 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are currently 54 podlings incubating.  We executed nine podling
releases and have one podling planning to graduate this month.  No changes
to the PMC structure this month.

* Community

  New IPMC members:

  - None

  People who left the IPMC:

  - None

* New Podlings

  - Daffodil

* Podlings that Retired

  - MRQL

* Podlings that failed to report, expected next month

Missing Sign Off:

  - Myriad
  - OpenWhisk
  - Quickstep
  - Spot

* Reports Missing Sign off

  - Griffin
  - Pulsar

* Graduations

  The board has motions for the following:

  - RocketMQ
  - Your podling here?

* Releases

  The following releases entered distribution during the month of
  August:

  - 2017-08-01 Apache Juneau 6.3.1
  - 2017-08-01 Apache Tamaya 0.3.0
  - 2017-08-05 Apache Tamaya Extensions 0.3.0
  - 2017-08-08 Apache Pulsar 1.19.0
  - 2017-08-16 Apache HTrace 4.3.0
  - 2017-08-16 Apache Spot 1.0
  - 2017-08-17 Apache Fluo 1.0.0
  - 2017-08-23 Apache S2Graph 0.2.0
  - 2017-08-29 Apache Livy 0.4.0

* IP Clearance



* Legal / Trademarks



* Infrastructure



* Miscellaneous



* Credits

--
   Table of Contents
AriaTosca
Daffodil
Gearpump
Gobblin
Griffin
Heron
Hivemall
HTrace
Livy
Mnemonic
MRQL
Myriad
Omid
OpenWhisk
Pony Mail
Pulsar
Quickstep
SAMOA
SINGA
Spot
Superset
Taverna
Tephra
Trafodion
Wave

--


AriaTosca

ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.

AriaTosca has been incubating since 2016-08-27.

Three most important issues to address in the move towards graduation:

  1. Grow the community and enroll new committers.
  2. Rotate Release Managers for future releases.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?

 Seeing some contributions now from independent developers.
 Active discussions on mailing lists with potential users and contributors.

How has the project developed since the last report?

 The project has had its first two releases in July 2017 - 0.1 and 0.1.1

 Important new features have been added:
   - Resumable workflows
   - Scaling nodes during service creation
   - AWS plugin support
   - Additional work towards being more TOSCA-compliant (e.g. interface
inputs support)
   - Additional usage examples have been added, including ones that use
IaaS plugins (Openstack, AWS), as well as one covering a real-life NFV
use-case (Clearwater example)
   - More comprehensive tests, including for documentation generation, and
parallelization of test suites
   - Standardized the release process with automatic shell scripts,
allowing anyone to easily create additional releases for the project
   - 64 JIRA issues have been resolved since the last report

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  July 17, 2017

When were the last committers or PPMC members elected?

  Project is still functioning with the initial set of committers.

Signed-off-by:

  [X](ariatosca) Suneel Marthi
 Comments:
  [X](ariatosca) John D. Ament
 Comments: The project has started to see more community interest.
Need to figure out how to drive development more on list to get more
outside contributions.
  [ ](ariatosca) Jakob Homan
 Comments:

IPMC/Shepherd notes:




Daffodil

Apache Daffodil is an implementation of the Data Format Description
Language (DFDL) used to convert between fixed format data and XML/JSON.

Daffodil has been incubating since 2017-08-27.

Three most important issues to address in the move towards graduation:

  1. Initial setup (finalize infrastructure setup, get SGAs in place, move
code/documentation/bugs/etc. over to Apache infrastructure, modify licenses)
  2. Establish guidelines regarding release cycles, code reviews, bug
management, etc.
  3. Work to grow the community to establish a diversity of backgrounds and
expertise

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  N/A

How has the project developed since the last report?

  N/A

How would you assess the podling's maturity?
Please feel free to add

Re: Podling Report Reminder - September 2017

[John D. Ament]

All,

A discussion back in July indicated the project had enough people to stay 
alive.  There has been no report submitted and no on list activity since then.

Should we plan to retire Myriad after all?

https://lists.apache.org/thread.html/7ef01bd386dea6ed651b6aea6783e4e8e1d3cc5ace9b73bc7fae225f@%3Cdev.myriad.apache.org%3E

John

On 2017-09-05 21:40, johndam...@apache.org wrote: 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 20 September 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, September 06).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/September2017
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC
> 

[REMINDER] Policies around Publicity & Press

[John D. Ament]

All Podlings,

In recent days I've been contacted about several publicity issues that have
gone a bit off kilter.  I wanted to remind podlings two very import
policies.

1. Podlings MUST coordinate with the Public Relations Committee with all
publicity activities.
2. The Press Team MUST review any press releases or similar communication
referencing a podling before it is published.

Relevant Links:

https://incubator.apache.org/guides/branding.html#publicity_activities
https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process

Please reach out with any concerns.

Regards,

John D. Ament
VP, Apache Incubator

Dist Area permissions problem

[John D. Ament]

All,

Please be advised that the infra team is aware of a permission problem that
is affecting podlings ability to write to the incubator dist area.  This
may cause you to be unable to create staged releases and promote those to
the public mirrors.  You can track the status in
https://issues.apache.org/jira/browse/INFRA-14609 .

Likewise, I want to make the podlings aware of a permission problem from
the weekend where git permissions were a little off.  That has since been
fixed.

Apologies for any inconvenience.

John

Re: Podling Report Reminder - July 2017

[John D. Ament]

Swapnil,

I've added your account.  Please note that it's not tied to your ASF committer 
account, you'll need to register separately.

John

On 2017-07-07 08:30 (-0400), Darin Johnson <dbjohnson1...@gmail.com> wrote: 
> Swapnil, generally a request on incubator does it.
> 
> On Jul 7, 2017 5:23 AM, "Swapnil Daingade" <swapnil.daing...@gmail.com>
> wrote:
> 
> > I created an account on the wiki but was not able to edit the page.
> > Do I need permissions to edit it? I'll try to figure it out but any
> > pointers would
> > be helpful. My account name is sdaingade
> >
> > Regards
> > Swapnil
> >
> >
> > On 07/06/2017 08:20 PM, John D. Ament wrote:
> >
> >> Ping.  Based on the active dicsussion around retirement, is anyone
> >> available to write a report?
> >>
> >> On 2017-06-27 20:10 (-0400), Adam Bordelon <a...@mesosphere.io> wrote:
> >>
> >>> I will be out of town during this period. Can somebody else fill out the
> >>> podling report in the wiki, with particular attention to the retirement
> >>> vote/discussion?
> >>>
> >>> On Tue, Jun 27, 2017 at 4:54 PM, <johndam...@apache.org> wrote:
> >>>
> >>> Dear podling,
> >>>>
> >>>> This email was sent by an automated system on behalf of the Apache
> >>>> Incubator PMC. It is an initial reminder to give you plenty of time to
> >>>> prepare your quarterly board report.
> >>>>
> >>>> The board meeting is scheduled for Wed, 19 July 2017, 10:30 am PDT.
> >>>> The report for your podling will form a part of the Incubator PMC
> >>>> report. The Incubator PMC requires your report to be submitted 2 weeks
> >>>> before the board meeting, to allow sufficient time for review and
> >>>> submission (Wed, July 05).
> >>>>
> >>>> Please submit your report with sufficient time to allow the Incubator
> >>>> PMC, and subsequently board members to review and digest. Again, the
> >>>> very latest you should submit your report is 2 weeks prior to the board
> >>>> meeting.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> The Apache Incubator PMC
> >>>>
> >>>> Submitting your Report
> >>>>
> >>>> --
> >>>>
> >>>> Your report should contain the following:
> >>>>
> >>>> *   Your project name
> >>>> *   A brief description of your project, which assumes no knowledge of
> >>>>  the project or necessarily of its field
> >>>> *   A list of the three most important issues to address in the move
> >>>>  towards graduation.
> >>>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >>>>  aware of
> >>>> *   How has the community developed since the last report
> >>>> *   How has the project developed since the last report.
> >>>> *   How does the podling rate their own maturity.
> >>>>
> >>>> This should be appended to the Incubator Wiki page at:
> >>>>
> >>>> https://wiki.apache.org/incubator/July2017
> >>>>
> >>>> Note: This is manually populated. You may need to wait a little before
> >>>> this page is created from a template.
> >>>>
> >>>> Mentors
> >>>> ---
> >>>>
> >>>> Mentors should review reports for their project(s) and sign them off on
> >>>> the Incubator wiki page. Signing off reports shows that you are
> >>>> following the project - projects that are not signed may raise alarms
> >>>> for the Incubator PMC.
> >>>>
> >>>> Incubator PMC
> >>>>
> >>>>
> >
> 

Re: Podling Report Reminder - July 2017

[John D. Ament]

Ping.  Based on the active dicsussion around retirement, is anyone available to 
write a report?

On 2017-06-27 20:10 (-0400), Adam Bordelon  wrote: 
> I will be out of town during this period. Can somebody else fill out the
> podling report in the wiki, with particular attention to the retirement
> vote/discussion?
> 
> On Tue, Jun 27, 2017 at 4:54 PM,  wrote:
> 
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 19 July 2017, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, July 05).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/July2017
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> 

Re: [Vote] Retire Myriad

[John D. Ament]

Hi,

Just to be clear.  The discussion around voting to retire is about the 
feasibility of the project.  You need a few people writing code, some PMC 
members for voting on a release.  While its good to have people who can vet a 
release, if you don't have anyone who's willing to write code, there won't be 
anything to release.  

According to [1] there's been no commits since October.

There's a bunch of pull requests open [2], but no one to merge them?

[1]: https://github.com/apache/incubator-myriad
[2]: https://github.com/apache/incubator-myriad/pulls

On 2017-06-25 17:12 (-0400), Swapnil Daingade  
wrote: 
> yes, I'll have to vote -1.
> 
> My reason being, I have not seen convincing reasons on why retiring is a
> better alternative for the project.
> 
> I am glad to see many committers speaking for continuing with the project.
> 
> I am all for discussing community building and what we can do to encourage
> more contributions, but that should be
> a separate discussion.
> 
> Regards
> Swapnil
> 
> 
> 
> On Sat, Jun 24, 2017 at 6:09 AM, Darin Johnson 
> wrote:
> 
> > Swapnil, I'm happy to count you as a -1.  I'd like to see if anyone else is
> > a -1 though as I've seen lots of +1's though contributors (but not any
> > explicit votes from committers).
> >
> >
> > On Jun 22, 2017 6:09 PM, "Swapnil Daingade" 
> > wrote:
> >
> > > yes, for more discussion.
> > >
> > > Unfortunately my situation too is no different, at least for the next 3-4
> > > months.
> > >
> > > I am happy to vote -1 to buy us more time or we can cancel the vote.
> > >
> > > Regards
> > > Swapnil
> > >
> > >
> > > On Thu, Jun 22, 2017 at 9:41 AM, Darin Johnson 
> > > wrote:
> > >
> > > > Sounds like lots of committers are interested in vetting/merging, but
> > not
> > > > leading new releases or building community.  Is it worth putting a
> > > discuss
> > > > up about that?
> > > >
> > > > Darin
> > > >
> > > > On Wed, Jun 21, 2017 at 6:34 PM, Mohit Soni  wrote:
> > > >
> > > > > I'm coming in pretty late to the conversation, but I am disengaged
> > for
> > > a
> > > > > long time now. I won't be able to actively contribute new features.
> > > But,
> > > > I
> > > > > can certainly help with refactoring the project to use
> > > > > https://github.com/mesosphere/dcos-commons, if somebody is willing
> > to
> > > > lead
> > > > > that effort. I personally think that will help us reduce the overall
> > > > > complexity. And, will make it easier for us to keep the project alive
> > > > > moving forward.
> > > > >
> > > > > On Tue, Jun 20, 2017 at 11:54 AM, Swapnil Daingade <
> > > > > swapnil.daing...@gmail.com> wrote:
> > > > >
> > > > > > @Darin Initially it was you, Adam, me & Santosh who replied.
> > > > > >
> > > > > > I think the confusion may have been due to me replying directly to
> > > Ted
> > > > > > (instead of reply all)
> > > > > > and later forwarding the reply to dev@myriad. My bad
> > > > > >
> > > > > > Now with Yuliya and Ken, we have 6 committers who are willing to
> > vet
> > > > and
> > > > > > merge commits!
> > > > > >
> > > > > > Regards
> > > > > > Swapnil
> > > > > >
> > > > > >
> > > > > > On Tue, Jun 20, 2017 at 11:30 AM, Ken Sipe 
> > > wrote:
> > > > > >
> > > > > > > I’ve been busy keeping up with a number of things and disengaged
> > > for
> > > > > some
> > > > > > > time.. I would like to come back to active status as a committer
> > > and
> > > > > I’m
> > > > > > > willing to commit to:
> > > > > > > 1. Review and merge of code.
> > > > > > > 2. Vet releases
> > > > > > >
> > > > > > > Ken
> > > > > > >
> > > > > > > > On Jun 20, 2017, at 10:26 AM, yuliya Feldman
> > > > > > 
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Sorry for chiming in late. I was out of town.
> > > > > > > > I think we should keep the project going if there is an
> > activity
> > > on
> > > > > the
> > > > > > > project.
> > > > > > > > I can definitely contribute time to vet the release, review and
> > > > > merge.
> > > > > > I
> > > > > > > may not be able to actively work on the project as it is not
> > inline
> > > > > with
> > > > > > my
> > > > > > > current work schedule.
> > > > > > > > Thanks,Yuliya
> > > > > > > >
> > > > > > > >  From: Darin Johnson 
> > > > > > > > To: Dev 
> > > > > > > > Sent: Tuesday, June 20, 2017 11:19 AM
> > > > > > > > Subject: Re: [Vote] Retire Myriad
> > > > > > > >
> > > > > > > > Swapnil: I only counted myself and Adam, if there's two
> > > additional
> > > > > > > > committers who are willing to vet the release AND merge commits
> > > > I'll
> > > > > > > > consider changing my vote.
> > > > > > > >
> > > > > > > > Darin
> > > > > > > >
> > > > > > > > On Tue, Jun 20, 2017 at 12:54 PM, Swapnil Daingade <
> > > > > > > > 

Re: Please review Myriad Report

[John D. Ament]

Danese,

You need to sign it on the wiki.

John

On Wed, Dec 14, 2016 at 1:08 AM Danese Cooper <dan...@gmail.com> wrote:

> I sign off on this report.
>
> One question, you call out seeking "more support" from Hadoop / Mesos
> vendors. What exactly are you looking to get them to do?
>
> Danese
>
> On Dec 13, 2016, at 4:29 PM, John D. Ament <johndam...@apache.org> wrote:
>
> Dear Myriad Mentors,
>
> Please review the Myriad report submitted at
> https://wiki.apache.org/incubator/December2016
> If you have concerns about the contents, please raise them to the podling.
>
> Regards,
>
> John
>
>

Please review Myriad Report

[John D. Ament]

Dear Myriad Mentors,

Please review the Myriad report submitted at
https://wiki.apache.org/incubator/December2016
If you have concerns about the contents, please raise them to the podling.

Regards,

John

Re: [2ND DRAFT] Incubator PMC Board Report - June 2016

[John D. Ament]

Some in line commentary.  I've also included in the to podlings I've made
comments on.

On Sun, Jun 5, 2016 at 10:11 AM John D. Ament <johndam...@apache.org> wrote:

> All,
>
> Please find the current draft of the board report below.  Its still
> missing sign off from mentors on several projects.
>
> John
>
> Incubator PMC report for June 2016
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> There are 56 podlings currently undergoing incubation.  We have one
> podling planning to graduate this month and added two podlings to the
> roster.  May was a generally quiet month, adding a single IPMC member,
> and completing four releases.
>
> * Community
>
>   New IPMC members:
>
>   - Joe Witt
>
>   People who left the IPMC:
>
>
>
> * New Podlings
>
>  - Pony Mail
>  - Fluo
>
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Twill (Pending)
>
> * Releases
>
>   The following releases entered distribution during the month of
>   May:
>
>   - 2016-05-05 Apache Mynewt 0.8.0
>   - 2016-05-24 Apache Tephra 0.8.0
>   - 2016-05-24 Apache CommonsRDF 0.2.0
>   - 2016-05-24 Apache Mnemonic 0.1.2
>
> * IP Clearance
>
>
>
> * Legal / Trademarks
>
>   - A comment on a recent Podling Name Search indicated that there was a
> desire
>   to have PNS's come later on during incubation.  Many IPMC members seem
> to believe
>   that they should happen earlier.  An email requesting clarification has
> been
>   sent.
>
> * Infrastructure
>
>   - Multiple former podlings are reporting delays in being converted to
> TLPs.
>
> * Miscellaneous
>
>   - The CMDA podling is now 2 months behind.  In response to the lack of
> activity,
>   a mentor has begun retirement discussions with the podling.
>
> * Credits
>
>   - Report Manager: John D. Ament
>
>  Summary of podling reports 
>
> * Still getting started at the Incubator
>
>   - Fluo
>   - Gossip
>   - Pony Mail
>
> * Not yet ready to graduate
>
>   No release:
>
>   - Airflow
>   - Gearpump
>   - iota
>   - log4cxx2
>   - Quarks
>   - Quickstep
>   - Streams
>   - Toree
>
>   Community growth:
>
>   - Atlas
>   - CommonsRDF
>   - HTrace
>   - Mnemonic
>   - MRQL
>   - Myriad
>   - Omid
>   - OpenAz
>   - Ranger
>   - SAMOA
>   - Singa
>   - Taverna
>   - Tephra
>   - Trafodion
>   - Wave
>
> * Ready to graduate
>
>   The Board has motions for the following:
>
>   - Twill (Pending)
>
> * Did not report, expected next month
>
>   - Climate Model Diagnostic Analyzer (2 months)
>
> --
>Table of Contents
> Airflow
> Atlas
> CommonsRDF
> Fluo
> Gearpump
> Gossip
> HTrace
> iota
> log4cxx2
> Mnemonic
> MRQL
> Myriad
> Omid
> OpenAz
> Pony Mail
> Quarks
> Quickstep
> Ranger
> SAMOA
> Singa
> Streams
> Taverna
> Tephra
> Toree
> Trafodion
> Wave
>
> --
>
> 
> Airflow
>
> Airflow is a workflow automation and scheduling system that can be used to
> author and manage data pipelines.
>
> Airflow has been incubating since 2016-03-31.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Releases
>   2. Grow up user and contributor communities
>   3. Improve and extend documentation and samples on the website
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Since our last podling report 1 month ago, we grew
> our contributors from 137 to 148
>   * Since our last podling report 1 month ago, we
> accepted/merged 51 PRs
>   * We voted on the following matters according to Apache guidelines:
>  * We voted to make all current and future committers part of the PPMC
>  * We voted in a new committer and PPMC member : Steven Yvinec-Kruyk
> and
>he accepted
>  * We voted in a commit policy of "RTC with a +1 vote from a committer
>other than the author (assuming no vetos)"
>
> How has the project developed since the last report?
>
>   * All resources have been created and all migrations are complete - code
> donation included
>   * The website is in progress
>
> Date of last release:
>
>