Re: Draft report November 2015 -- please review

[Marvin Humphrey]

On Tue, Nov 10, 2015 at 5:47 PM, Ate Douma  wrote:

> In this case, their first challenge clearly indicates making a next release
> with also providing convenience binary artifacts is seen as the next hurdle
> to take.  It is true AsterixDB already put out two releases, but those were
> source only releases.  And the AsterixDB team is well aware that next hurdle
> isn't going to be so easy.  So I would personally place them still at stage
> 2 for now.

That's a little confusing but the categorization doesn't have to be perfect.
I've put them into "No release".

Cheers,

Marvin Humphrey

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

Re: Draft report November 2015 -- please review

[Ate Douma]

On 2015-11-10 23:59, Marvin Humphrey wrote:

On Tue, Nov 10, 2015 at 12:22 PM, Ate Douma  wrote:

On 2015-11-09 18:12, Marvin Humphrey wrote:


Incubator PMC report for November 2015

* Ready to graduate

- AsterixDB



While IMO AsterixDB is doing great, it is not yet considering graduation so
I think it shouldn't be listed as such.

Ate (AsterixDB mentor)


Thanks for the review, Ate!

Podlings tend to progress linearly through 4 stages:

1. Getting started
2. No incubating release
3. Community growth
4. Ready to graduate

Although AsterixDB's report did not communicate that they were ready
to graduate, they've put out a release and they didn't mention needing
to grow the community as a challenge. Here are their "three issues to
address prior to graduation":

   1. Do an Apache release that can also provide binary artifacts with
  correct LICENSEs and NOTICEs.
   2.
   3.

Feel free to invent a custom category that describes where AsterixDB
is at. Otherwise, "Community growth" is a bit of a catch-all -- so if
there's not any other obvious choice we can put them there.


Hi Marvin,

I see how you got to your assessment and I think from the outside that makes 
sense :)


In this case, their first challenge clearly indicates making a next release with 
also providing convenience binary artifacts is seen as the next hurdle to take.
It is true AsterixDB already put out two releases, but those were source only 
releases.

And the AsterixDB team is well aware that next hurdle isn't going to be so easy.
So I would personally place them still at stage 2 for now.

Community growth, while not stated in this report (and probably an oversight 
from us mentors not requesting them to do so) also needs some further 
development. Although I don't see or expect that to be problematic either, just 
needs a little bit more time. The community is quite vibrant.


At any rate, I think they are in fine shape, just need a bit more time before 
they should start focusing on graduation, that's all.


Regards,
Ate



Marvin Humphrey

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




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

Re: Draft report November 2015 -- please review

[Marvin Humphrey]

On Tue, Nov 10, 2015 at 12:22 PM, Ate Douma  wrote:
> On 2015-11-09 18:12, Marvin Humphrey wrote:
>>
>> Incubator PMC report for November 2015
>>
>> * Ready to graduate
>>
>>- AsterixDB
>
>
> While IMO AsterixDB is doing great, it is not yet considering graduation so
> I think it shouldn't be listed as such.
>
> Ate (AsterixDB mentor)

Thanks for the review, Ate!

Podlings tend to progress linearly through 4 stages:

1. Getting started
2. No incubating release
3. Community growth
4. Ready to graduate

Although AsterixDB's report did not communicate that they were ready
to graduate, they've put out a release and they didn't mention needing
to grow the community as a challenge. Here are their "three issues to
address prior to graduation":

  1. Do an Apache release that can also provide binary artifacts with
 correct LICENSEs and NOTICEs.
  2.
  3.

Feel free to invent a custom category that describes where AsterixDB
is at. Otherwise, "Community growth" is a bit of a catch-all -- so if
there's not any other obvious choice we can put them there.

Marvin Humphrey

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

Re: Draft report November 2015 -- please review

[Ate Douma]

On 2015-11-09 18:12, Marvin Humphrey wrote:

Incubator PMC report for November 2015

* Ready to graduate

   - AsterixDB


While IMO AsterixDB is doing great, it is not yet considering graduation so I 
think it shouldn't be listed as such.


Ate (AsterixDB mentor)

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

Re: Draft report November 2015 -- please review

[Pierre Smits]

That made me remember:

Homer Simpson : [sarcastic
voice] Ooh, look at me! I'm making people happy! I'm the Magical Man from
Happy-Land, in a gumdrop house on Lollipop Lane!


Best regards,

Pierre Smits

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

On Tue, Nov 10, 2015 at 3:39 PM, Marko Rodriguez 
wrote:

> Hello,
>
> >> TinkerPop
> >
> >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >> aware of?
> >>
> >>  No. Recently, we have really appreciated Daniel Gruno's (mentor)
> efforts
> >>  to get our development community more connected by setting up an Apache
> >>  HipChat account for us and interacting with us in a more real-time
> fashion
> >>  on various procedures/policies of Apache in a proactive manner. This
> has
> >>  helped to explain to us (through doing) what is required of Apache.
> >
> > Glad to hear that TinkerPop's contributors are feeling a little more at
> > home!  It's not clear that this passage contains an issue that needs
> > specific attention by the IPMC/Board;  I guess I'll comment that while
> > HipChat and other realtime communications are great, hopefully TinkerPop
> is
> > also mastering *asynchronous* communication, which is essential for
> ensuring
> > inclusive development.
>
> You would be astonished about how over the top we have gone with the
> Apache Way. I say this with the utmost confidence -- find me ANY other
> Apache Incubator project that does it this soundly:
>
>
> http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/developer.html
> (ain't no awkard txt README)
>
> http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/tutorials-getting-started.html
> (we care…we really really care about the work we do).
> http://tinkerpop.incubator.apache.org/ (scroll to the bottom -- 2
> new committers since the November report)
>
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.1.0-incubating%20AND%20project%20%3D%20TINKERPOP3
> (RTC policy in effect -- big time)
> https://builds.apache.org/view/All/job/tinkerpop-master/ (got all
> set up with Apache Jenkins thanks to The Gruno)
>
> https://pony-poc.apache.org/trends.html?d...@tinkerpop.apache.org:lte=3M
> (find a more active incubator mailing list -- ain't happening)
>
> And -- in super secret informal talky talky private@, we got Gruno happy
> to join the TinkerPop PMC when we graduate and he relinquishes his IPMC
> role. We will have the fuzz on us at all times. Entailment -- a bullet
> proof project. "Oh you have a problem with us Big Mega Corp, Inc.? You best
> focus on taking down Apache Hadoop before you get through our
> titanium-strength legal armor."
>
> *** Once we get one more PMC, we are coming for you general@incubators.
> Soon we will throw our square hat tassel to the other side.
>
> ,
> Marko.
>
> http://markorodriguez.com

Re: Draft report November 2015 -- please review

[Marko Rodriguez]

Hello,

>> TinkerPop
> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>> 
>>  No. Recently, we have really appreciated Daniel Gruno's (mentor) efforts
>>  to get our development community more connected by setting up an Apache
>>  HipChat account for us and interacting with us in a more real-time fashion
>>  on various procedures/policies of Apache in a proactive manner. This has
>>  helped to explain to us (through doing) what is required of Apache.
> 
> Glad to hear that TinkerPop's contributors are feeling a little more at
> home!  It's not clear that this passage contains an issue that needs
> specific attention by the IPMC/Board;  I guess I'll comment that while
> HipChat and other realtime communications are great, hopefully TinkerPop is
> also mastering *asynchronous* communication, which is essential for ensuring
> inclusive development.

You would be astonished about how over the top we have gone with the Apache 
Way. I say this with the utmost confidence -- find me ANY other Apache 
Incubator project that does it this soundly:


http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/developer.html (ain't 
no awkard txt README)

http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/tutorials-getting-started.html
 (we care…we really really care about the work we do).
http://tinkerpop.incubator.apache.org/ (scroll to the bottom -- 2 new 
committers since the November report)

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.1.0-incubating%20AND%20project%20%3D%20TINKERPOP3
 (RTC policy in effect -- big time)
https://builds.apache.org/view/All/job/tinkerpop-master/ (got all set 
up with Apache Jenkins thanks to The Gruno)

https://pony-poc.apache.org/trends.html?d...@tinkerpop.apache.org:lte=3M (find 
a more active incubator mailing list -- ain't happening)

And -- in super secret informal talky talky private@, we got Gruno happy to 
join the TinkerPop PMC when we graduate and he relinquishes his IPMC role. We 
will have the fuzz on us at all times. Entailment -- a bullet proof project. 
"Oh you have a problem with us Big Mega Corp, Inc.? You best focus on taking 
down Apache Hadoop before you get through our titanium-strength legal armor."

*** Once we get one more PMC, we are coming for you general@incubators. Soon we 
will throw our square hat tassel to the other side.

,
Marko.

http://markorodriguez.com

Re: Draft report November 2015 -- please review

[Marvin Humphrey]

> Apex

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The project is still using the original Atlassian instance of JIRA.
>   INFRA-10144 has tracked the Apache JIRA migration request since August.

JIRA imports are non-trivial and Apex is not the first project to get
snagged.  I would expect a resolution eventually through interaction between
Infra and podling contributors or Mentors without requiring escalation to
IPMC or Board, but thanks for keeping the IPMC/Board informed.

>   Chris Nauroth (cnauroth):

> I would like to request that the infra team prioritize completion of
> the JIRA migration tracked in INFRA-10144.

Anyone have suggestions about the most constructive ways to for Apex to
pursue this?

> AsterixDB

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The discussion on the use of an external Gerrit instance for code
>   reviews is considered to be resolved.
>   The current workflow ensures that
>   a) The ASF git repository is the canonical repository for the project.
>   b) Only committers can manually commit changes to the ASF git
>  repository.
>   c) All discussions on the Gerrit instance are sent to
>  notificati...@asterixdb.incubator.apache.org.
>   While it would be good to also have the Gerrit instance run on ASF
>   hardware, this is neither necessary to document the provenance of the
>   code nor to enable list members to follow and participate in the
>   activities of the project. Also, there seems to be no infra capacity
>   to provide a Gerrit service.

Thanks for the update, AsterixDB.  The broader issue is being discussed
extensively elsewhere within the Foundation.

Unfortunately most of the debate is on private lists (board@apache,
members@apache, operations@apache), which excludes stakeholders such as most
contributors to AsterixDB -- among many others.  Personally, this bothers me
quite a bit, as it clashes with what we claim are Apache ideals of openness.
Hopefully efforts to move the conversations public will succeed sooner
rather than later.

I suggest that interested parties subscribe to infrastructure-dev@apache,
since that is the public venue where some discussion has been taking place.
Discussions may also emerge on legal-discuss@apache or dev@community.apache.

> 
> Blur
>
> Blur is a search platform capable of searching massive amounts of data
> in a cloud computing environment.
>
> Blur has been incubating since 2012-07-24.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Greater community involvement.
>   2. Produce releases.
>   3.
>
> 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?
>
>  - Subscriptions: user@ - 55[0]; dev@ - 70[+3]
>
> How has the project developed since the last report?
>
>  - A few additional features, and bug fixes.
>
> Date of last release:
>
>   2014-07-29
>
> When were the last committers or PMC members elected?
>
>   2014-07-28
>
> Signed-off-by:
>
>   [ ](blur) Doug Cutting
>   [X](blur) Patrick Hunt
>   [ ](blur) Tim Williams
>
> Shepherd/Mentor notes:
>
>
>

This report yields very little insight about the state of Blur's community.
There are many excellent reports from other podlings this month; perhaps
Blur could look to them for inspiration.

> Climate Model Diagnostic Analyzer

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The project is still in its nascence and the PPMC is still learning the
>   Apache way and moving out of JPL/CMU centric development. The project team
>   wants to do a good job they are just moving along slowly.

Thanks for the update, CMDA -- we look forward to continued progress.  It's
great to have you here in the Incubator, but please don't stay too long! ;)

> Cotton

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   Development of Cotton has largely been inactive for the last two months,
>   due to limited time from the original developer and community engagements
>   including MesosCon Seattle and MesosCon Europe.
>
> How has the community developed since the last report?
>
>   There has been limited participation on the mailing lists and JIRA,
>   however a discussion on the private@ list was established about this issue
>   and there's a desire to keep the project in the incubator and be more
>   proactive in building community in the coming months.

Kudos for transparency, Cotton.  Hope that things go well -- building a
community takes hard work!

> DataFu

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   * Performing the initial release remains the most important milestone.

Nice report in general, DataFu.  This bullet point isn't really an issue that
the IPMC or Board needs to be monitor closely though.  For future re

Draft report November 2015 -- please review

[Marvin Humphrey]

Incubator PMC report for November 2015

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 47 podlings currently undergoing incubation.

With 702 messages to general@incubator, October was one of the heaviest
months for email traffic in a long time.

Podlings nearing graduation received extra scrutiny this month, presumably
as an indirect result of various recent proposals to rework graduation to
include more structured review.  Such evaluations of podling readiness,
while illuminating, put stress on the Mentors and contributors to the
podling under the microscope and raise the overall tension in the
Incubator.

Another topic of discussion was disengaged Mentors.  An initiative to engage
Mentors privately when podlings do not report for two months or more yielded
positive results, with some Mentors reaffirming their commitment and others
officially moving on.

* Community

  New IPMC members:

  - Tom Barber (magicaltrout)
  - Patrick Wendell (pwendell)
  - Reynold Xin (rxin)
  - Phil Sorber (sorber)
  - Julien Le Dem (julien)
  - Jacques Nadeau (jacques)

  No one left the IPMC this month, but a handful of Mentors have stepped
  down from their posts with various podlings.  Most of the resignations
  were from Mentors who had become inactive, so the Incubator's rolls have
  become a bit more accurate.

* New Podlings

  - Eagle
  - Mynewt
  - Concerted
  - SystemML

* Graduations

  The board has motions for the following:

  - Brooklyn
  - Groovy

* Releases

  The following releases were made since the last Incubator report:

  - 2015-10-05 Apache Johnzon 0.9.2-incubating
  - 2015-10-07 Apache Singa 0.1.0
  - 2015-10-14 Apache AsterixDB 0.8.7-incubating
  - 2015-10-14 Apache REEF 0.13.0-incubating
  - 2015-10-23 Apache Kylin 1.1-incubating
  - 2015-10-28 Apache TinkerPop 3.0.2-incubating
  - 2015-10-30 Apache Apex v3.2.0-incubating
  - 2015-10-31 Apache Slider 0.81.1-incubating

* IP Clearance

  - Taobao (China) Software Co., Ltd and several individuals donated Alibaba
JStorm, "A fork of Apache Storm with Clojure code replaced with Java,
and several other improvements".

  A discussion calling into question what responsibilities -- if any -- the
  Incubator should have with regards to IP Clearance eventually went quiet,
  leaving the status quo intact.

* Miscellaneous

  - Droids has retired.
  - Kalumet has retired.
  - The Corinthia community is voting on retirement.

 Summary of podling reports 

* Still getting started at the Incubator

  - Concerted
  - Mynewt
  - Rya

* Not yet ready to graduate

  No release:

  - Climate Model Diagnostic Analyzer
  - Cotton
  - MADlib
  - DataFu
  - HAWQ
  - HORN

  Community growth:

  - Apex
  - Blur
  - Slider
  - Tamaya
  - TinkerPop
  - Twill

* Ready to graduate

  - AsterixDB
  - Kylin
  - REEF

* Did not report, expected next month

  - Ripple (5 months late)
  - Sirona
  - Unomi

--
   Table of Contents
Apex
AsterixDB
Blur
Climate Model Diagnostic Analyzer
Concerted
Cotton
DataFu
HAWQ
HORN
Kylin
MADlib
Mynewt
REEF
Ripple
Rya
Sirona
Slider
Tamaya
TinkerPop
Twill
Unomi

--


Apex

Apex is an enterprise grade native YARN big data-in-motion platform that
unifies stream processing as well as batch processing.

Apex has been incubating since 2015-08-17.

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

  1. Release Apex-Core, and Apex-Malhar on ongoing basis.
  2. Grow contributors beyond the initial set.
  3. Move to using Apache JIRA

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

  The project is still using the original Atlassian instance of JIRA.
  INFRA-10144 has tracked the Apache JIRA migration request since August.

How has the community developed since the last report?

  The community is very engaged with the development of the project. There
  have been 788 messages on dev@ for October.

  The community has been active building meetup groups in various locations:
  http://s.apache.org/jKT

  - Number of meetups: 6 in total so far: 4 in USA cities and 2 in Indian
cities
  - Total members in worldwide Apache Apex meetups: 495
  - Events: 1 in Oct; 4 scheduled in Nov: CapitalOne presentation in
Chicago; DataTorrent presentation in Pune; GE presentation in San Ramon;
PubMatic presentation in San Jose;

  Future: Planning to start meetups in more cities, and be able to organize
  2-3 events a month.

How has the project developed since the last report?

  The first release under incubation passed voting. Apex (Core)
  3.2.0-incubating was released 2015-10-30.  The community is currently
  discussing roadmap for upcoming releases.

  Various metrics are as follows:
  +--