Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-08-16 20:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Edgent

16 Aug 2017

Report was filed, but display is awaiting the approval of the Board minutes.

17 May 2017

Apache Edgent is a programming model 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 Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.

Edgent has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around the Edgent project.
 2. Checking of all items in the project's Maturity Model
    (https://cwiki.apache.org/confluence/display/EDGENT/Apache+Maturity+Model+For+Edgent)
 3. Although not required to graduate, it might be good to attract at
    least another independent committer/ppmc member.

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?

 * Three speakers will present their experience with Edgent at the
   ApacheCon North America in May 2017:

   * Video Analytics at the Edge: Fun with Apache Edgent, OpenCV and a
     Raspberry Pi - Dale LaBossiere and William Marshall, ppmc members and
     committers for Edgent.

   * Having fun with Raspberry(s) and Apache Projects - Jean-Frederic Clere.

 * Since the last report, 2 individuals have subscribed to the Apache
   Edgent dev mailing list.  There were 65 subscribers as of the end of
   April 2017.

How has the project developed since the last report?

 * Release 1.1.0 of Edgent as part of the Apache incubator was created on
   17 March 2017. This represented 26 bug fixes and improvements,
   including more usage examples, application autoSubmit capability to
   IotProvider, support for publishing WIoTP device events using HTTP,
   and many others.
 * According to JIRA, 33 new issues were added to the project and 81
   issues have been resolved or closed between February 2017 and April 2017.

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:

 2017-03-17

When were the last committers or PPMC members elected?

 In May 2016, we added two new committers and PPMC members,
 Kathy Saunders and Queenie Ma.

Signed-off-by:

 [ ](edgent) Daniel Debrunner
    Comments:
 [x](edgent) Luciano Resende
    Comments:
 [ X ](edgent) Katherine Marsden
    Comments:  Great product. Great Apache way attitude. Everything in place,
    but just need to focus community growth and diversity.  I am hoping the
    Apachecon presentations will help bring this great product and project on
    the radar.
 [ ](edgent) Justin Mclean
    Comments:

IPMC/Shepherd notes:

27 Feb 2017

Edgent is a stream processing programming model and lightweight runtime to
execute analytics at devices on the edge or at the gateway.

Edgent has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around the Edgent project
 2. Checking of all items in the project's Maturity Model
    https://cwiki.apache.org/confluence/display/EDGENT/Apache+Maturity+Model+For+Edgent
 3. Create a second release of Apache Edgent with additional features and
    fixes.

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?

 * A well attended meetup in San Francisco, CA about Apache Edgent was held
   on January 18th. It covered introductory concepts of datastreaming, the
   positioning of Edgent in the datastreaming universe, and examples and
   use cases of Edgent. The meetup was attended by roughly 40 developers.
   "Apache Edgent: Datastreaming and Analytics for IoT Devices "
   https://www.meetup.com/SF-Data-Science/events/236682354/
 * There has been at least one question both asked and answered on
   Stackoverflow by a non-committer non-PPMC member of the community.
   http://stackoverflow.com/questions/41280097/joining-streams-of-different-types-in-apache-edgent
 * Since the last report, at least 5 individuals have subscribed to the
   Apache Edgent dev mailing list.

How has the project developed since the last report?

 * The first release of Edgent as part of the Apache incubator was created
   on 2016-12-15. This represents a large amount of work, including
   numerous improvements to connectors, the console, and a complete
   overhaul of the build system to use Gradle.
 * According to JIRA, the project has added the following:
   * November 2016: 6 new issues; 18 issues resolved.
   * December: 18 new issues; 29 issues resolved.
   * January: 15 new issues; 12 issues resolved

Date of last release:

 * The most recent release of Apache Edgent was 2016-12-15.

When were the last committers or PMC members elected?

 * In May 2016, we added two new committers and PPMC members, Kathy
   Saunders and Queenie Ma.

Signed-off-by:

 [ ](edgent) Daniel Debrunner
 [ ](edgent) Luciano Resende
 [X](edgent) Katherine Marsden
 [X](edgent) Justin Mclean

Shepherd/Mentor notes:

 Katherine Marsden:

   Checking of the Maturity model is not yet complete and is just being
   used as an aid to help assess our progress.  Hopefully now that we have
   a release and with the meetup we will have more people get interested
   and involved. The active development community, while still small seems
   to be communicating well on the list and it was great to see the
   release.

 Justin Mclean:

   Great work on the release, project progressing along well.

16 Nov 2016

Edgent is a stream processing programming model and lightweight runtime to
execute analytics at devices on the edge or at the gateway.

Edgent has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around the Edgent project
 2. Create the first Apache release of Edgent
 3. Document a repeatable release process.

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?

 * A well attended meetup in Plano, TX about Apache Edgent was held on
   September 9th "Sensor Data Analytics Acceleration with Apache Edgent"
   http://www.meetup.com/DFW-Sensor-Technology/events/233150402/
 * A presentation about Apache Edgent was presented on October 21st @ Open
   Source India 2016. Approximately 400 attendees were present.
 * A presentation about Apache Edgent, Streaming Analytics and Weather
   Company Data was presented at World of Watson in Las Vegas on October
   26th.
 * A demo about Apache Edgent was presented at World of Watson in Las Vegas
   on October 24th.  "IoT Device Events to Streaming Analytics in 15 Minutes
   with Bluemix"
 * For the months of September and October four new community members either
   subscribed to the edgent-dev mailing list, or opened JIRAs.

How has the project developed since the last report?

 * A new build system was created using Gradle. The initial contribution for
   this work came from two community contributors.  The follow up work was
   done by committers.

 According to JIRA, the project has added the following:

 * September: 11 new issues; 15 issues resolved.
 * October: 46 new issues; 23 issues resolved.
 * October activity was almost exclusively due to readying for the first
   Edgent release.

Date of last release:

 * We have not created an Apache release, but are working on one to be ready
   soon. During the September and October time period we made build changes
   and handled licensing work and are poised to create our first release.

When were the last committers or PMC members elected?

 * In May, we added two new committers and PPMC members, Kathy Saunders and
 * Queenie Ma.

Signed-off-by:

 [ ](edgent) Daniel Debrunner
 [x](edgent) Luciano Resende
 [X](edgent) Katherine Marsden
 [X](edgent) Justin Mclean

21 Sep 2016

 Apache Edgent is a programming model 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 Pis or smart phones). Working in conjunction with
 centralized analytic systems, Apache Edgent provides efficient and timely
 analytics across the whole IoT ecosystem: from the center to the edge.

 Edgent has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around Edgent project
 2. Set up new build system, allowing us to remove code dependencies from
    our repository
 3. Create the first Apache release of Edgent

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?

 Significant progress has been made on a new build system, using  Gradle.
 One of the goals is to remove third party code, so we can work toward a
 release.

 The community has been active and participating in voting.  Heavy commit
 activity, but light Jira activity, recently as the name change was
 implemented in the code, documentation and web site.

How has the project developed since the last report?

 According to JIRA, the project has added the following:

 * June: 29 new issues; 22 issues resolved.
 * July: 20 new issues; 15 issues resolved.
 * August: 7 new issues; 7 issues resolved.

 August activity was largely build and renaming activities, tracked under a
 few Jira issues.

 The name for the project was changed from Apache Quarks to Apache Edgent.
 The new name went through a suitable name search and was approved.  The
 infrastructure, code and documentation changes have been completed.

 A logo was voted on and chosen, and a wiki was set up for the Edgent
 community.

Date of last release:

 We have not created an Apache release as of yet.  We need to complete build
 changes and licensing work to create a release.

When were the last committers or PMC members elected?

 In May, we added two new committers and PPMC members, Kathy Saunders and
 Queenie Ma.

Signed-off-by:

 [ ](edgent) Daniel Debrunner
 [ ](edgent) Luciano Resende
 [X](edgent) Katherine Marsden
 [X](edgent) Justin Mclean

15 Jun 2016

Apache Quarks is a programming model 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 Pis or smart phones). Working in conjunction with
centralized analytic systems, Apache Quarks provides efficient and timely
analytics across the whole IoT ecosystem: from the center to the edge.

Quarks has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around Quarks project
 2. Create the first Apache release of Quarks
 3. Complete the product name search and select a suitable name

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

 Due to trademark concerns with "Quarks", the Quarks PPMC voted to change
 the project's name. A renaming discussion and public vote was held on the
 dev mailing list. The voting results are being discussed privately by the
 PPMC.

How has the community developed since the last report?

 We have added two new committers and PPMC members, Kathy Saunders and
 Queenie Ma. Kathy has taken the lead on the name search process for
 Quarks, and her positive attitude and helpfulness are an incredible asset
 for the Quarks community. Queenie has contributed content to the website
 and is a frequent participant in community discussions. The Quarks
 community is still small, as Quarks has just recently incubated, therefore
 we aim to continue growing our list in the near future.

How has the project developed since the last report?

 * According to JIRA, the project has added 27 new issues in May, and 22
   issues have been resolved.
 * On May 12, several Quarks contributors hosted an "Apache Quarks on
   Raspberry Pi" webcast where they showed how to use Quarks to work with
   real sensor data on a Raspberry Pi, and demonstrated a smart sprinkler
   application using Quarks.

Date of last release:

 Quarks is still new, so we haven't created an Apache release as of yet.

When were the last committers or PMC members elected?

 In May, we added two new committers and PPMC members, Kathy Saunders and
 Queenie Ma.


Signed-off-by:

 [ ](quarks) Daniel Debrunner
 [x](quarks) Luciano Resende
 [X](quarks) Katherine Marsden
 [X](quarks) Justin Mclean

18 May 2016

Apache Quarks is a programming model 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 Pis or smart phones). Working in conjunction with
centralized analytic systems, Apache Quarks provides efficient and timely
analytics across the whole IoT ecosystem: from the center to the edge.

Quarks has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around Quarks project
 2. Create the first Apache release of Quarks
 3. Complete migration of website to host all content at Apache (javadoc is
    still on Github).

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

 Nothing jumps to mind.

How has the community developed since the last report?

 We have added a new committer and PPMC member, Cazen Lee.  Cazen started
 making valuable contributions almost immediately when Quarks went into
 incubation. The Quarks community is still small, as Quarks has just
 recently incubated, therefore we aim to continue growing our list in the
 near future.


How has the project developed since the last report?

 * According to JIRA, the project has added 59 new issues in April, and 34
   issues have been resolved.
 * On April 13th, the committers hosted an "Introduction to Quarks" webcast
   where they presented a high-level overview of the project and demonstrated
   how to write, monitor and debug Quarks applications.

Date of last release:

 Quarks is still new, so we haven't created an Apache release as of yet.

When were the last committers or PMC members elected?

 In April we added a new committer and PPMC member, Cazen Lee.

Signed-off-by:

 [ ](quarks) Daniel Debrunner
 [x](quarks) Luciano Resende
 [X](quarks) Katherine Marsden
 [X](quarks) Justin Mclean

20 Apr 2016

Apache Quarks is a programming model 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 Pis or smart phones). Working in conjunction with
centralized analytic systems, Apache Quarks provides efficient and timely
analytics across the whole IoT ecosystem: from the center to the edge.

Quarks has been incubating since 2016-02-29.

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

 1. Create and expand a diverse community of contributors and committers
    around Quarks project
 2. Create the first Apache release of Quarks
 3. Complete migration of website to host all content at Apache (javadoc is
    still on Github).

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

 Nothing jumps to mind.

How has the community developed since the last report?

 The Quarks community is keeping dev-related conversations on the mailing
 list. Because of this, it's allowed for the participation of independent
 contributors in mailing list discussions. Although our list of independent
 contributors is small, Quarks is still very new as an Apache project and
 we aim to actively grow our list in the near future.

How has the project developed since the last report?

 * The project has successfully migrated from Github-based development to
   using the Apache git repo, Jira, and the mailing lists.

Date of last release:

 Quarks is still new, so we haven't created an Apache release as of yet.

When were the last committers or PMC members elected?

 No changes from the initial committers.

Signed-off-by:

 [ ](quarks) Daniel Debrunner
 [ ](quarks) Luciano Resende
 [X](quarks) Katherine Marsden
 [X](quarks) Justin Mclean