Re: [VOTE] Retire Apache Edgent

[William Marshall]

Thank you Christopher and Julian for keeping the project going until this
time! Sad to see it retire, but a highlight of this was seeing Edgent pop
up as a "preferred skill" on various job postings.

On Wed, Sep 11, 2019 at 8:33 AM Justin Mclean 
wrote:

> Hi,
>
> > Sad to see but I can see the project graduating.
>
> Can’t see the project graduating I mean to say.
>
> Thanks,
> Justin

Re: [ANNOUNCE] New Edgent PPMC member and committer: Julian Feinauer

[William Marshall]

Welcome, Julian!

On Thu, Nov 29, 2018 at 8:22 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hey all,
>
> first, big thanks to the PPMC!
> I feel honored and I am very motivated to help to get edgent back on track.
>
> Julian
>
> Am 29.11.18, 15:59 schrieb "Christofer Dutz" :
>
> All,
>
> Please welcome Julian as the newest member of the Edgent PPMC and
> committers group!
>
> Julian has recently been very helpful in helping get the Apache Edgent
> (incubating) project off the ground again.
>
> Chris
>
>
>
>
>

'emiritus' committer status

[William Marshall]

Hi all,

Apache has the concept of "emeritus" committers who have contributed to a
project in the past, but are not currently committing, writing docs, or
generally interacting with the project.
http://www.apache.org/dev/pmc.html#emeritus

Since I fit this description, I'm going to transition to an emeritus
committer. There's no formal process for this, but I expect it would help
when writing the monthly podling report to give an indication of active
committer diversity. Optionally, we could list this on whimsy or our
website.

Regards,

Will

Re: [DRAFT] May Podling Report Edgent

[William Marshall]

Although, I think John Ament resigned as a mentor to Edgent, not sure if he
is still required to sign off.

On Fri, May 4, 2018 at 3:19 PM, William Marshall <wcmar...@gmail.com> wrote:

> Looks good to me.
>
> On Fri, May 4, 2018 at 8:47 AM, Christofer Dutz <christofer.d...@c-ware.de
> > wrote:
>
>> Comments? I whipped this up by updating the last one …
>>
>> ===
>> 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 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. Attracting at least another independent committer/ppmc member.
>>   3. Finding further real world users of Edgent
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>>   Community participation, implying interest in Edgent, continues
>>   to be an issue.  One of the two active committer/PPMC members has
>>   retired at the end of February and the level of their continuing
>>   participation is has been significantly reduced since then. The second
>>   active committer was also very consumed with finishing his house-
>>   building, which is now finished. So we are hoping to see increased
>>   activity again.
>>
>> How has the community developed since the last report?
>>
>>   * An article on Apache Edgent has been published as cover-story in the
>> German JavaSPEKTRUM magazine in March
>> (https://bc-v3.pressmatrix.com/de/profiles/4967c6d5eae1/edit
>> ions/138b1a28747149541fb0)
>>   * At the Techcamp.Hamburg in April we had one well attended talk about
>>  Apache Edgent
>>   * Total, we have 76 subscribers to our mailing list, an increase
>> of 4 since the last report.
>>   * We have seen a new name on the list, which seems to be interested in
>> contributing. Especially in the Kafka area. We are hoping to see more
>> activity in the near future.
>>
>> How has the project developed since the last report?
>>
>>   * We have updated the Kafka module to the latest Kafka version
>>   * According to JIRA, 2 new issues were added and none were resolved
>> in the last 90 days
>>   * 12 commits were made in the last 90 days.
>>
>> How would you assess the podling's maturity?
>>
>>   Edgent is making slow but consistent progress towards graduation. While
>> we
>>   don't yet meet the diversity requirements, we put emphasis on community
>>   growth through outreach which will ultimately pave the way for
>> additional
>>   committers and contributors.
>>
>>   Additionally, before we graduate it is important that we find users
>>   outside of IBM. As most Edgent committers are employed by IBM, external
>>   stakeholders help ensure long term contribution to the project.
>>
>>   [ ] Initial setup
>>   [ ] Working towards first release
>>   [X] Community building
>>   [ ] Nearing graduation
>>   [ ] Other:
>>
>> Date of last release:
>>
>>   2017-12-14  Apache Edgent 1.2.0
>>
>> When were the last committers or PPMC members elected?
>>
>>   In August 2017, we added Christofer Dutz as a new committer
>>   and PPMC member.
>>
>>
>> Signed-off-by:
>>
>>   [ ](edgent) Daniel Debrunner
>>  Comments:
>>   [ ](edgent) Luciano Resende
>>  Comments:
>>   [ ](edgent) Justin Mclean
>>  Comments:
>>   [ ](edgent) John D. Ament
>>  Comments:
>>
>> IPMC/Shepherd notes:
>>
>>
>> =
>>
>>
>>
>>
>

Re: [DRAFT] May Podling Report Edgent

[William Marshall]

Looks good to me.

On Fri, May 4, 2018 at 8:47 AM, Christofer Dutz 
wrote:

> Comments? I whipped this up by updating the last one …
>
> ===
> 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 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. Attracting at least another independent committer/ppmc member.
>   3. Finding further real world users of Edgent
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   Community participation, implying interest in Edgent, continues
>   to be an issue.  One of the two active committer/PPMC members has
>   retired at the end of February and the level of their continuing
>   participation is has been significantly reduced since then. The second
>   active committer was also very consumed with finishing his house-
>   building, which is now finished. So we are hoping to see increased
>   activity again.
>
> How has the community developed since the last report?
>
>   * An article on Apache Edgent has been published as cover-story in the
> German JavaSPEKTRUM magazine in March
> (https://bc-v3.pressmatrix.com/de/profiles/4967c6d5eae1/
> editions/138b1a28747149541fb0)
>   * At the Techcamp.Hamburg in April we had one well attended talk about
>  Apache Edgent
>   * Total, we have 76 subscribers to our mailing list, an increase
> of 4 since the last report.
>   * We have seen a new name on the list, which seems to be interested in
> contributing. Especially in the Kafka area. We are hoping to see more
> activity in the near future.
>
> How has the project developed since the last report?
>
>   * We have updated the Kafka module to the latest Kafka version
>   * According to JIRA, 2 new issues were added and none were resolved
> in the last 90 days
>   * 12 commits were made in the last 90 days.
>
> How would you assess the podling's maturity?
>
>   Edgent is making slow but consistent progress towards graduation. While
> we
>   don't yet meet the diversity requirements, we put emphasis on community
>   growth through outreach which will ultimately pave the way for additional
>   committers and contributors.
>
>   Additionally, before we graduate it is important that we find users
>   outside of IBM. As most Edgent committers are employed by IBM, external
>   stakeholders help ensure long term contribution to the project.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [X] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   2017-12-14  Apache Edgent 1.2.0
>
> When were the last committers or PPMC members elected?
>
>   In August 2017, we added Christofer Dutz as a new committer
>   and PPMC member.
>
>
> Signed-off-by:
>
>   [ ](edgent) Daniel Debrunner
>  Comments:
>   [ ](edgent) Luciano Resende
>  Comments:
>   [ ](edgent) Justin Mclean
>  Comments:
>   [ ](edgent) John D. Ament
>  Comments:
>
> IPMC/Shepherd notes:
>
>
> =
>
>
>
>

Re: My first article about Apache Edgent was accepted :-)

[William Marshall]

Fantastic! Could could you post a link to the articles when when they
become available?

On Mon, Feb 19, 2018 at 6:22 AM, Dale LaBossiere 
wrote:

> Nice!
>
> > On Feb 18, 2018, at 7:10 AM, Christofer Dutz 
> wrote:
> >
> > Hi all,
> >
> > I just got notified, that the article I submitted for an IT Magazines
> IoT Special Edition (JavaSPEKTRUM) was accepted and is currently being
> prepared for being printed. I also added all information needed to come
> back to this list … will definitely do a dev-list subscription count before
> it’s released. It’s mainly focused on Edgent with a little bit (about 25%)
> about Apache PLC4X.
> >
> > A second Article for another Magazine IoT Special Edition is also
> submitted and will follow a few weeks after that. That however will be the
> other way around 75% about PLC4X and 25% about Edgent …
> >
> > Keep your fingers crossed ☺ Hopefully both will help get some life back
> to this list and specially spread the Word about both projects (Most people
> I talk to have never heard of both) …
> >
> > Chris
>
>

Re: [DISCUSS] Release Apache Edgent 1.2.0 (incubating)

[William Marshall]

+1, I like the process.

If I understand correctly, all development work is now happening on the
develop branch, and therefore master is only ever updated when a new
release is created.

On Mon, Nov 6, 2017 at 10:39 AM, Susan Cline  wrote:

> +1 - thanks for all the hard work on this!
>
> Susan
>
> > On Nov 6, 2017, at 12:20 AM, Christofer Dutz 
> wrote:
> >
> > Hi all,
> >
> > after finally merging back all changes we did in the last few months, I
> think it would be a good time to do a first release using Maven. This way
> we can give the Maven build its final and ultimate test and hopefully start
> releasing a lot more often.
> >
> > Even if I think the current development speed is still quite low, I
> would propose to start doing releases the following way:
> >
> >
> >  *   The intention to release is indicated by a “[DISCUSS]” Thread in
> which the intention for a new release is communicated
> >  *   After there is a general consensus on doing a new release a release
> branch is created and the version develop is incremented (In this case, I
> would create a “release/1.2” branch in which the version remains unchanged
> and the version of develop is incremented to “1.3.0-SNAPSHOT”
> >  *   As soon as this is done a “[LAST CALL]” Thread is started asking
> everyone to check the release branch, bring in last changes and fixes.
> >  *   As soon as the “[LAST CALL]” thread implies all are ready, a
> Release Candidate is created. We’ll be using the maven-release-plugin for
> that. This will create a so-called staging repository in Apache’s Nexus
> (This is like a maven repository, but it contains only the artifacts of the
> release candidate)
> >  *   As soon as the RC is staged, a “[VOTE]” Thread is started
> containing a link to the staging repository.
> >  *   As soon as the Vote passes, the staging repo is set to “release”
> and the artifacts automatically go to Apache’s public maven repo and get
> synced to Maven Central.
> >  *   Now the state of the release gets merged to “master” so now
> “master” represents the state of the last release done by the project.
> >  *   If there were any bugfixes, patches etc. applied to the release
> branch, these changes need to be merged to the develop branch too.
> >
> > What do you think? Should we start the games?
> >
> > Chris
>
>

Re: Do we want Edgent stickers?

[William Marshall]

Little late in replying here, but I'd love Edgent stickers :)

Hm, I don't think we have a SVG formatted logo.

On Mon, Aug 14, 2017 at 7:13 AM, Christofer Dutz 
wrote:

> Hi,
>
> I’m currently finishing the work on a 3 day Apache track at a conference
> in Hamburg. Right now we can order project stickers for our projects. I was
> thinking of requesting some Edgent stickers.
> Any objections?
>
> Do we have the logo in some SVG like (vector) format?
>
> I always love sticking stickers on things ;-)
>
> Chris
>

Re: Podling Report Draft

[William Marshall]

As there are no new comments, I've posted the report to the wiki. Would the
mentors please sign off?

https://wiki.apache.org/incubator/August2017#preview

Will

On Tue, Aug 1, 2017 at 12:47 PM, William Marshall <wcmar...@gmail.com>
wrote:

> (ignore the lingering "Groovy", it's been fixed)
>
> On Tue, Aug 1, 2017 at 12:46 PM, William Marshall <wcmar...@gmail.com>
> wrote:
>
>> The changes have been made. The updated draft follows:
>>
>> 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 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. Attracting at least another independent committer/ppmc member.
>>   3. Finding further real world users 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?
>>
>> * Total, we have 70 subscribers to our mailing list, an improvement
>> of 5 since the last report.
>> * We have had a noticeable increase in the number of
>> information-seeking
>> emails on the mailing list from new Edgent developers.
>> * A San Francisco meetup has been scheduled for the 20th of September
>> to demonstrate an Edgent video analytics application which was
>> initially presented at ApacheCon 2017 (Video Analytics at the Edge:
>> Fun with Apache Edgent, OpenCV and a Raspberry Pi).
>> * In addition to Chris Dutz, we have had one non-committer PR merged.
>>
>>
>> How has the project developed since the last report?
>>
>>   * With the contributions of Christoper Dutz and Dale LaBossiere, the
>> Edgent build system is undergoing an overhaul to Maven from Groovy.
>> Maven provides benefits over Gradle, including a more rigid build
>> structure, and the Maven package system.
>>   * According to JIRA, 13 new issues were added to the project and 6
>> issues have been resolved or closed between May 2017 and August 2017.
>>
>> How would you assess the podling's maturity?
>> Edgent is making slow but consistent progress towards graduation. While we
>> don't yet meet the diversity requirements, we put emphasis on community
>> growth through outreach which will ultimately pave the way for additional
>> committers and contributors.
>>
>> Additionally, before we graduate it is important that we find users
>> outside of IBM. As most Edgent committers are employed by IBM, external
>> stakeholders help ensure long term contribution to the project.
>>
>>   [ ] 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:
>>   [ ](edgent) Luciano Resende
>>  Comments:
>>   [ ](edgent) John Ament
>>  Comments:
>>   [ ](edgent) Justin Mclean
>>  Comments:
>>
>> IPMC/Shepherd notes:
>>
>> On Tue, Aug 1, 2017 at 12:39 PM, William Marshall <wcmar...@gmail.com>
>> wrote:
>>
>>> > I don't believe a course was ever created.
>>> Actually, you are correct. I was confusing the Edgent course with a
>>> different course which is currently in the works.
>>>
>>> > I would avoid mentioning about this DeveloperWorks piece due to
>>> $corporateBacking.
>>> All the more reason :)
>>>
>>> > Nit:   it’s Maven from **Gradle**   :-)
>>> Thanks, Dale. The mind thinks one thing, the fingers type another.
>>>
>>> > We also received

Re: Podling Report Draft

[William Marshall]

The changes have been made. The updated draft follows:

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 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. Attracting at least another independent committer/ppmc member.
  3. Finding further real world users 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?

* Total, we have 70 subscribers to our mailing list, an improvement
of 5 since the last report.
* We have had a noticeable increase in the number of information-seeking
emails on the mailing list from new Edgent developers.
* A San Francisco meetup has been scheduled for the 20th of September
to demonstrate an Edgent video analytics application which was
initially presented at ApacheCon 2017 (Video Analytics at the Edge:
Fun with Apache Edgent, OpenCV and a Raspberry Pi).
* In addition to Chris Dutz, we have had one non-committer PR merged.


How has the project developed since the last report?

  * With the contributions of Christoper Dutz and Dale LaBossiere, the
Edgent build system is undergoing an overhaul to Maven from Groovy.
Maven provides benefits over Gradle, including a more rigid build
structure, and the Maven package system.
  * According to JIRA, 13 new issues were added to the project and 6
issues have been resolved or closed between May 2017 and August 2017.

How would you assess the podling's maturity?
Edgent is making slow but consistent progress towards graduation. While we
don't yet meet the diversity requirements, we put emphasis on community
growth through outreach which will ultimately pave the way for additional
committers and contributors.

Additionally, before we graduate it is important that we find users
outside of IBM. As most Edgent committers are employed by IBM, external
stakeholders help ensure long term contribution to the project.

  [ ] 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:
  [ ](edgent) Luciano Resende
 Comments:
  [ ](edgent) John Ament
 Comments:
  [ ](edgent) Justin Mclean
 Comments:

IPMC/Shepherd notes:

On Tue, Aug 1, 2017 at 12:39 PM, William Marshall <wcmar...@gmail.com>
wrote:

> > I don't believe a course was ever created.
> Actually, you are correct. I was confusing the Edgent course with a
> different course which is currently in the works.
>
> > I would avoid mentioning about this DeveloperWorks piece due to
> $corporateBacking.
> All the more reason :)
>
> > Nit:   it’s Maven from **Gradle**   :-)
> Thanks, Dale. The mind thinks one thing, the fingers type another.
>
> > We also received PR submission from another new contributor
> Absolutely worth mentioning, thanks.
>
> On Tue, Aug 1, 2017 at 12:36 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
>> Unless its something this team has specifically built and is part of the
>> ASF project, I would avoid mentioning about this DeveloperWorks piece due
>> to $corporateBacking.
>>
>> On Tue, Aug 1, 2017 at 3:29 PM Queenie Ma <queeni...@apache.org> wrote:
>>
>> > Regarding this item, "An online course on Edgent was developed on
>> > DeveloperWorks, providing further material for new users to familiarize
>> > themselves with Edgent", I don't believe a course was ever created. I
>> know
>> > one was in the works earlier this year, but it was never completed. Am I
>> > off base?
>> >
>> > The rest looks great, thanks!
>> >
>> > --
>> > Queenie
>> >
>> > On Tue, Aug 1, 2017 at 11:13 AM, William Marshall <wcmar...@gmail.com>
>> > wrote:
>> >
>> > > Hi All,
>> > >
>> > > The following is the initial draft of the podling report. If you have
>> any
>> > > comments, please make them 

Re: Podling Report Draft

[William Marshall]

> I don't believe a course was ever created.
Actually, you are correct. I was confusing the Edgent course with a
different course which is currently in the works.

> I would avoid mentioning about this DeveloperWorks piece due to
$corporateBacking.
All the more reason :)

> Nit:   it’s Maven from **Gradle**   :-)
Thanks, Dale. The mind thinks one thing, the fingers type another.

> We also received PR submission from another new contributor
Absolutely worth mentioning, thanks.

On Tue, Aug 1, 2017 at 12:36 PM, John D. Ament <johndam...@apache.org>
wrote:

> Unless its something this team has specifically built and is part of the
> ASF project, I would avoid mentioning about this DeveloperWorks piece due
> to $corporateBacking.
>
> On Tue, Aug 1, 2017 at 3:29 PM Queenie Ma <queeni...@apache.org> wrote:
>
> > Regarding this item, "An online course on Edgent was developed on
> > DeveloperWorks, providing further material for new users to familiarize
> > themselves with Edgent", I don't believe a course was ever created. I
> know
> > one was in the works earlier this year, but it was never completed. Am I
> > off base?
> >
> > The rest looks great, thanks!
> >
> > --
> > Queenie
> >
> > On Tue, Aug 1, 2017 at 11:13 AM, William Marshall <wcmar...@gmail.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > The following is the initial draft of the podling report. If you have
> any
> > > comments, please make them by 12:00 PM PST tomorrow to leave sufficient
> > > time for the mentors to sign off on the wiki.
> > >
> > >
> > > 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 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. Attracting at least another independent committer/ppmc member.
> > >   3. Finding further real world users 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?
> > >
> > > * Total, we have 70 subscribers to our mailing list, an improvement
> > > of 5 since the last report.
> > > * We have had a noticeable increase in the number of
> > > information-seeking
> > > emails on the mailing list from new Edgent developers.
> > > * An online course on Edgent was developed on DeveloperWorks,
> > providing
> > > further material for new users to familiarize themselves with
> Edgent
> > > * A San Francisco meetup has been scheduled for the 20th of
> September
> > > to demonstrate an Edgent video analytics application which was
> > > initially presented at ApacheCon 2017 (Video Analytics at the Edge:
> > > Fun with Apache Edgent, OpenCV and a Raspberry Pi).
> > >
> > >
> > > How has the project developed since the last report?
> > >
> > >   * With the contributions of Christoper Dutz and Dale LaBossiere, the
> > > Edgent build system is undergoing an overhaul to Maven from Groovy.
> > > Maven provides benefits over Groovy, including a more rigid build
> > > structure, and the Maven package system.
> > >   * According to JIRA, 13 new issues were added to the project and 6
> > > issues have been resolved or closed between May 2017 and August
> 2017.
> > >
> > > How would you assess the podling's maturity?
> > > Edgent is making slow but consistent progress towards graduation. While
> > we
> > > don't yet meet the diversity requirements, we put emphasis on community
> > > growth through outreach which will ultimately pave the way for
> additional
> > > committer

Podling Report Draft

[William Marshall]

Hi All,

The following is the initial draft of the podling report. If you have any
comments, please make them by 12:00 PM PST tomorrow to leave sufficient
time for the mentors to sign off on the wiki.


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 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. Attracting at least another independent committer/ppmc member.
  3. Finding further real world users 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?

* Total, we have 70 subscribers to our mailing list, an improvement
of 5 since the last report.
* We have had a noticeable increase in the number of information-seeking
emails on the mailing list from new Edgent developers.
* An online course on Edgent was developed on DeveloperWorks, providing
further material for new users to familiarize themselves with Edgent
* A San Francisco meetup has been scheduled for the 20th of September
to demonstrate an Edgent video analytics application which was
initially presented at ApacheCon 2017 (Video Analytics at the Edge:
Fun with Apache Edgent, OpenCV and a Raspberry Pi).


How has the project developed since the last report?

  * With the contributions of Christoper Dutz and Dale LaBossiere, the
Edgent build system is undergoing an overhaul to Maven from Groovy.
Maven provides benefits over Groovy, including a more rigid build
structure, and the Maven package system.
  * According to JIRA, 13 new issues were added to the project and 6
issues have been resolved or closed between May 2017 and August 2017.

How would you assess the podling's maturity?
Edgent is making slow but consistent progress towards graduation. While we
don't yet meet the diversity requirements, we put emphasis on community
growth through outreach which will ultimately pave the way for additional
committers and contributors.

Additionally, before we graduate it is important that we find users
outside of IBM. As most Edgent committers are employed by IBM, external
stakeholders help ensure long term contribution to the project.

  [ ] 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:
  [ ](edgent) Luciano Resende
 Comments:
  [ ](edgent) John Ament
 Comments:
  [ ](edgent) Justin Mclean
 Comments:

IPMC/Shepherd notes:

Re: Podling Report Reminder - August 2017

[William Marshall]

Hi John,

Yes, I am drafting the report.

Will

On Sun, Jul 30, 2017 at 12:25 PM, John D. Ament 
wrote:

> All,
>
> Just wanted to check in to see if any report were planned?
>
> John
>
> On 2017-07-30 10:23, 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, 16 August 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, August 02).
> >
> > 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/August2017
> >
> > 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: Alternate solution for hardware portion of Water Sprinkler Use Case

[William Marshall]

Also, I'd recommend subscribing to the mailing list before sending
messages, just send a message to dev-subscr...@edgent.apache.org.

-Will

On Fri, Jul 7, 2017 at 11:24 AM, William Marshall <wcmar...@gmail.com>
wrote:

> Hi Aarushi,
>
> I am assuming that your Grove sensor is similar to this one.
> <http://wiki.seeed.cc/Grove-Moisture_Sensor/>
>
> The code in the Water Conservation Demo which reads from a real,
> non-simulated, sensor assumes that the sensor is a Mod My Pi Soil
> Moisture Sensor
> <https://www.modmypi.com/electronics/sensors/soil-moisture-sensor>. Your
> Grove sensor returns moisture readings as values between 0-950. In
> contrast, the digital output of the Pi Soil Moisture Sensor give only a
> simple "on" or "off" for whether moisture is present.
>
> I'm not sure which method for connecting your Grove sensor to the
> Raspberry PI is best, but whichever you choose, you can modify the
> SprinklerSimulatorWithSensor code
> <https://github.com/IBMStreams/streamsx.waterConservation.starterKit/blob/master/com.ibm.streamsx.smartsprinkler.edgent/src/com/ibm/streamsx/smartsprinkler/edgent/SprinklerSimulatorWithSensor.java>
> to read from your Grove sensor instead of the Mod My Pi Soil Moisture
> Sensor. Just change the constructor to initialize communication with your
> sensor, and then change the getMoisture method to read from your sensor and
> set the moisture value.
>
> You can run the Water Conservation Demo on any IoT board that has a Java7
> or Java8 JVM, assuming you remove the parts of SprinklerSimulatorWithSensor
> that directly depend on the Raspberry PI (such as reading from GPIO pins).
>
> Let me know if any of this is unclear, or if you need help modifying the
> code.
>
> -Will
>
>
>
> On Wed, Jul 5, 2017 at 2:44 AM, MITTAL Aarushi <
> aarushi.mit...@soprasteria.com> wrote:
>
>> Hi Samantha,
>>
>>
>>
>> I have successfully launched an application on bluemix following your
>> tutorial for Smart Water Sprinkler:
>>
>> https://github.com/IBMStreams/streamsx.waterConservation.sta
>> rterKit/blob/master/com.ibm.streamsx.smartsprinkler.edgent/README.md
>>
>>
>>
>> I have successfully been able to receive simulated readings.
>>
>>
>>
>> Now , I want to get real readings from a moisture sensor.
>>
>>
>>
>> There are 2 problems here :
>>
>> 1)  I have a Grove moisture sensor that maybe difficult to connect
>> to a Pi. But the I am not sure if the Edgent application can be written on
>> any other iot board ,except a Pi.
>>
>> Though I have found a way to directly connect the grove sensor to Pi, I
>> am not too confident with this approach.
>>
>> http://www.switchdoc.com/2016/02/tutorial-grove-connector-pr
>> oject-examples-for-raspberry-pi-arduino/
>>
>>
>>
>> 2)  I have an Arduino base shield on which many grove sensors can be
>> connected.
>>
>> I can mount my shield(having the grove sensor connected ) on my Arduino
>> uno .
>>
>> After that , I can connect this entire Arduino setup to my raspberry Pi 3
>> via Serial Communication.
>>
>>
>>
>> Please guide me if it would be a good idea , to get the sensor readings
>> from the Arduino to the pi and then send them to the Edgent application(on
>> the Pi) for Edge computing.
>>
>>
>>
>> I have to submit this solution by 7th July 2017.
>>
>> Please help.
>>
>>
>>
>> Regards,
>>
>> *Aarushi Mittal*
>>
>> *IOT, Digital Transformation Team*
>>
>> *[image: cid:image001.png@01D2C80A.F0430D40]*
>>
>> Sopra Steria
>> A-67, Sector 64
>> Noida 201301 - U.P. India
>>
>> Mobile: +91-7065508866 <+91%2070655%2008866>
>> aarushi.mit...@soprasteria.com - www.soprasteria.in
>>
>>  [image: cid:image002.gif@01CF42C0.CFE0E450]
>>
>> The content of this message may be confidential, legally privileged and
>> protected by law. Unauthorized use, copying or disclosure of any of it may
>> be unlawful. If you are not the intended recipient please notify the sender
>> and remove it from your system. While attachments to this e-mail are
>> checked for viruses, we do not accept any liability for any damage
>> sustained by viruses.
>> Before printing, think about the environment.
>>
>>
>>
>
>

Re: Alternate solution for hardware portion of Water Sprinkler Use Case

[William Marshall]

Hi Aarushi,

I am assuming that your Grove sensor is similar to this one.


The code in the Water Conservation Demo which reads from a real,
non-simulated, sensor assumes that the sensor is a Mod My Pi Soil Moisture
Sensor .
Your Grove sensor returns moisture readings as values between 0-950. In
contrast, the digital output of the Pi Soil Moisture Sensor give only a
simple "on" or "off" for whether moisture is present.

I'm not sure which method for connecting your Grove sensor to the Raspberry
PI is best, but whichever you choose, you can modify the
SprinklerSimulatorWithSensor code

to read from your Grove sensor instead of the Mod My Pi Soil Moisture
Sensor. Just change the constructor to initialize communication with your
sensor, and then change the getMoisture method to read from your sensor and
set the moisture value.

You can run the Water Conservation Demo on any IoT board that has a Java7
or Java8 JVM, assuming you remove the parts of SprinklerSimulatorWithSensor
that directly depend on the Raspberry PI (such as reading from GPIO pins).

Let me know if any of this is unclear, or if you need help modifying the
code.

-Will



On Wed, Jul 5, 2017 at 2:44 AM, MITTAL Aarushi <
aarushi.mit...@soprasteria.com> wrote:

> Hi Samantha,
>
>
>
> I have successfully launched an application on bluemix following your
> tutorial for Smart Water Sprinkler:
>
> https://github.com/IBMStreams/streamsx.waterConservation.
> starterKit/blob/master/com.ibm.streamsx.smartsprinkler.edgent/README.md
>
>
>
> I have successfully been able to receive simulated readings.
>
>
>
> Now , I want to get real readings from a moisture sensor.
>
>
>
> There are 2 problems here :
>
> 1)  I have a Grove moisture sensor that maybe difficult to connect to
> a Pi. But the I am not sure if the Edgent application can be written on any
> other iot board ,except a Pi.
>
> Though I have found a way to directly connect the grove sensor to Pi, I am
> not too confident with this approach.
>
> http://www.switchdoc.com/2016/02/tutorial-grove-connector-
> project-examples-for-raspberry-pi-arduino/
>
>
>
> 2)  I have an Arduino base shield on which many grove sensors can be
> connected.
>
> I can mount my shield(having the grove sensor connected ) on my Arduino
> uno .
>
> After that , I can connect this entire Arduino setup to my raspberry Pi 3
> via Serial Communication.
>
>
>
> Please guide me if it would be a good idea , to get the sensor readings
> from the Arduino to the pi and then send them to the Edgent application(on
> the Pi) for Edge computing.
>
>
>
> I have to submit this solution by 7th July 2017.
>
> Please help.
>
>
>
> Regards,
>
> *Aarushi Mittal*
>
> *IOT, Digital Transformation Team*
>
> *[image: cid:image001.png@01D2C80A.F0430D40]*
>
> Sopra Steria
> A-67, Sector 64
> Noida 201301 - U.P. India
>
> Mobile: +91-7065508866 <+91%2070655%2008866>
> aarushi.mit...@soprasteria.com - www.soprasteria.in
>
>  [image: cid:image002.gif@01CF42C0.CFE0E450]
>
> The content of this message may be confidential, legally privileged and
> protected by law. Unauthorized use, copying or disclosure of any of it may
> be unlawful. If you are not the intended recipient please notify the sender
> and remove it from your system. While attachments to this e-mail are
> checked for viruses, we do not accept any liability for any damage
> sustained by viruses.
> Before printing, think about the environment.
>
>
>

Re: Setting up an ASF Jenkins?

[William Marshall]

Hey Chris,

Would this create a SNAPSHOT for every pull request? Where would snapshots
be hosted?

I like the idea of changing the website workflow. Currently we manually
generate the html using jekyll, commit the changed html to the asf-site
branch, and then push that to origin.

-Will

On Fri, Jun 16, 2017 at 9:47 AM, Dale LaBossiere 
wrote:

> Does this tell you what you need to know?
>
> https://github.com/apache/incubator-edgent-website/blob/master/README.md <
> https://github.com/apache/incubator-edgent-website/blob/master/README.md>
>
> — Dale
>
>
> > On Jun 16, 2017, at 9:03 AM, Christofer Dutz 
> wrote:
> >
> > That depends on your current setup. If you could describe that, I could
> go a little more into details.
> >
> > Chris
> >
> > Am 16.06.17, 14:45 schrieb "Dale LaBossiere" :
> >
> >+1 from me.  Could you elaborate on the website updating?  What is
> updated under what conditions?
> >
> >Thanks,
> >— Dale
> >
> >> On Jun 16, 2017, at 4:58 AM, Christofer Dutz 
> wrote:
> >>
> >> Hi guys,
> >>
> >> I was thinking, if you would be interested in me setting up ASF Jenkins
> for Edgent?
> >> The way Travis is currently used to automatically test pull requests is
> really good. I would like to additionally setup Jenkins Jobs on ASF Infra
> to publish SNAPSHOTS in the near future. Also, it would allow automating
> the process of updating the Edgent website.
> >>
> >> I don’t know if I would need additional permissions to do this, but I
> wanted to make sure you guys would like me to take care of this.
> >>
> >> Chris
> >
> >
> >
>
>

Blog Ideas/Edgent Use Cases

[William Marshall]

Hi All,

I'm writing a series of articles for the Edgent blog. The goal is to have
one, or several, use cases to be walked through step-by-step. Edgent's
strength is in reducing the amount of streaming data sent over a network,
so my current blog idea is to walk through a "smart microphone" example
where a Raspberry Pi only transmits sound if the decibel level is above a
threshold.

But that's just one idea.

I want to invite the Edgent community to comment on possible Edgent use
cases. Hopefully, these could be used as the basis for future articles/blog
posts, and can serve as a way of drawing in new developers to the project.

How can Edgent be used?

-Will

Edgent Blog now Live

[William Marshall]

Hi All,

I asked INFRA to create an Apache blog page for Edgent. It can be found
here:

https://blogs.apache.org/edgent/

Currently, I am the only one with write access and admin privileges, but if
you create an account here, I can add you
https://blogs.apache.org/roller-ui/login-redirect.rol as an admin or
blogger.

I plan to make some sample applications with Edgent integrating with other
Apache projects. Let me know if you would like to submit a post!

-Will

Re: Improving the Edgent message

[William Marshall]

Replied

tl;dr, I think the Spark website does a lot of things right, and we should
take a sentence to explain datastreaming and link to the "Streaming
Concepts" page.

On Wed, May 24, 2017 at 8:33 AM, Dale LaBossiere 
wrote:

> If you have additional thoughts on improving our message
> I encourage you to chime in here or on [1]
>
> [1] https://issues.apache.org/jira/browse/EDGENT-415
>
> — Dale

Re: Moving Edgent Forward

[William Marshall]

Hi John,

Thanks for agreeing to become a mentor for Edgent. I agree that we should
focus on a demo which shows an Edgent use case without relying on Watson,
since it seems to have left the impression that Watson is needed to run
Edgent.

Regarding the "branding" issue with the website:
> the fact that there's two different color schemes makes it feel like two
different sites

This is very nearly true! The landing page was developed independently from
the documentation pages, so even though they're hosted in the same
directory on the same webserver, they have a very different look and feel.

Will

On Thu, May 18, 2017 at 8:08 AM, Queenie Ma  wrote:

> Hi John,
>
> Thanks for your interest in Edgent. It would be wonderful to have you as a
> mentor for our project! I can tell you have great ideas already :)
>
> I can't speak to the first and last items you mentioned, but I'm glad you
> brought up the second point. I agree that the website should be more
> cohesive... perhaps by merging the home page into the documentation page.
>
> Thanks,
> Queenie
>
> On Wed, May 17, 2017 at 7:49 PM, John D. Ament 
> wrote:
>
> > Hi All,
> >
> > Wanted to summarize some of what Dale, Will and I chatted about this
> > evening with regard to Edgent and some ideas on how to move Edgent
> forward.
> >
> > I'll be honest, when I read the conflicting info from Kathey and in
> person
> > description from Justin I thought there was something awry, so I did want
> > to dig in further to having a full in depth dump of ideas.  It seems to
> me
> > that the disconnect is around past contributors vs active contributors.
> > From what was described the only active contributor is Dale, whereas
> others
> > have contributed to the project in different ways (Will seems to be doing
> > some evangelism, Kathey's helped with documentation to name it a bit).
> In
> > the past there was a bit more outside delivery but at the end of day its
> > not even a single company but a single contributor doing most of the
> work.
> > While its clear to me that the project gets The Apache Way, until
> there's a
> > bigger developer community I would be hesitant to say the podling is
> > completely ready to go.
> >
> > Looking across Edgent, there's some clear areas of improvement for the
> > podling.  I'll list them below in no particular order, and ignoring that
> > I've already spoken in person about some of these (just to make it clear
> > that it's also happening on list):
> >
> > - Downloads are an issue.  First problem is that the links from
> > http://edgent.apache.org/docs/downloads are pointing to directories on
> > dist.a.o instead of the direct downloads makes it harder for a user to
> > leverage Edgent.  Even then, the fact that the project is not distributed
> > in a repository manager (e.g. Maven) makes leveraging it even harder.
> >
> > - There's some website branding issues, but not issues in the "this is
> > wrong" sense but more "this is weird" sense.  For instance, there's two
> > different themes from what I can tell, comparing
> > http://edgent.apache.org/docs/downloads and the main
> > http://edgent.apache.org/ the fact that there's two different color
> > schemes
> > makes it feel like two different sites. The same color scheme, logos etc
> > should be in use.
> >
> > - Figure out a way to build synergy with existing ASF projects over
> demoing
> > with commercial entities.  I threw out the idea to use Apache ActiveMQ
> > Artemis for MQTT based communication over leveraging Watson IoT - it
> builds
> > a more common use case (many people will already know ActiveMQ, and its
> > embeddable).  It would also be good to have an end to end sample that
> > demonstrates using Edgent in an all Apache way, no third parties
> required.
> >
> > I believe if these start to get addressed, the project may start to see
> > more users with new use cases.  It is still a niche market.  I have
> > volunteered to mentor you.  If you'll accept me, I would like to:
> >
> > - Be added to the roster in Whimsy
> > https://whimsy.apache.org/roster/ppmc/edgent
> > - Access to your JIRA
> > - Access to your Confluence
> >
> > Regards,
> >
> > John
> >
>

Re: Looking for additional mentor for Edgent with community growth ideas/focus

[William Marshall]

Hi John, I'm glad you enjoyed the presentation, ApacheCon was a great
forum.

All mentors are currently active, and right now the way in which Edgent
most needs mentorship is in its outreach to developers. From a technical
perspective, I think Edgent is mature for its age and number of committers,
but to date we've only seen a few users actually adopt it in an
application. This is strange, given the amount of initial interest, but I
sense this is in part due the the name change from Quarks to Edgent.

Since Kathey is likely stepping down soon, you would be the 4th mentor (not
the there's any hard limit, as far as I'm aware). Given your experience
with podlings I think you would fit the role well. Any thoughts on the
outreach problem?

-Will

On Tue, May 16, 2017 at 3:21 PM, Katherine Marsden 
wrote:

> On 5/16/17 2:17 PM, John D. Ament wrote:
>
>> William,
>>
>> Great presentation this afternoon.
>>
>> I'd like offer to help you guys as a mentor, you do currently have 4
>> mentors.  Are all 4 mentors active in the project?
>>
>>
> Hi John, I am not involved in the project from a technical perspective,
> except I helped initially setting up the website and have done some release
> testing and filed a few bugs.
>
> As mentor I have been mostly just offering solicited and unsolicited
> advice and maintaining the project status page (hmmm haven't looked at that
> in a while, better check), posting the maturity model to the wiki and
> reviewing and signing off on reports, etc.
>
> I would be happy to commit to continuing  with this minimal role as
> mentor  or step aside if that makes more sense given the number of mentors
> if you will take over maintaining the project status page.  I think the
> project needs your help a lot more than mine right now as the folks working
> on the project seem to totally have a handle on everything on which I could
> provide guidance.  If anyone on the project has questions that I could
> answer,  I still certainly would be available to answer.  One ppmc member
> requested I stay on for my "timely advice" [1] but I certainly am never shy
> about giving  advice no matter my formal role.  I am sure she wouldn't mind
> if I stepped down in my formal mentor role if I stuck around on the dev
> list which I plan to.
>
> Best
>
> Kathey
>
>
> [1] https://mail-search.apache.org/members/private-arch/edgent-
> private/201704.mbox/%3c7f0611ab-b983-4398-8977-9ec99d662...@yahoo.com%3E
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling Shark Tank Sessions next week

[William Marshall]

Hi Roman,

Thanks for getting in touch. I missed your direct message which I've now
read and understand. I can confirm that Edgent will participate in Podling
Shark Tank! I will come prepared with a 10 minute ST presentation on Tue
5/16 at 4:40.

Thanks again,

-Will Marshall

On Mon, May 8, 2017 at 12:17 PM, Roman Shaposhnik  wrote:

> Hi!
>
> my apologies for reaching out directly to the dev@ mailing
> lists, but since both Edgenet and Rya volunteered to present
> at Podling Shark Tank Sessions next week I'd like to make
> sure it happens. More details here:
> https://wiki.apache.org/apachecon/ACNA17PodlingSharkTank
>
> I tried to reach out to Will and Adina directly but without much
> luck so I'm trying to see if the rest of the community can help
> me find them.
>
> All I need at this point is for Will and Adina to contact me off-list
> so I can make sure they come to the session prepared.
>
> Thanks,
> Roman.
>

Re: [VOTE] Publish Apache Edgent 1.1.0-incubating (RC1)

[William Marshall]

+1

On Thu, Mar 16, 2017 at 5:11 AM, Dale LaBossiere  wrote:

> Hey buddy, can you spare a VOTE?  :-)
>
> Just another ping.  I appreciate that folks may have a lot of things on
> their plate at this time.
>
> Thanks in advance for your help in getting this release out the door.
> — Dale
>
> > On Mar 5, 2017, at 7:58 AM, Dale LaBossiere  wrote:
> >
> > The Apache Edgent community approved a vote to release
> > Apache Edgent 1.1.0-incubating from RC1.
> >
> > Per [1] we are requesting IPMC approval to publish the
> > release bundles on the distribution site [2].
> >
> > This vote will be open for 120 hours (I’m on vacation :-)
> >
> > - 1.1.0-incubating-RC1 vote results / thread [3]
> > - Git hash and tag for the release
> >  commit: 4744f56
> >  tag: 1.1.0-incubating-RC1
> >  link to RC1 source in the git repository [4]
> > - links to RC1 artifacts [5]
> >
> > [ ]  +1 accept
> > [ ]  -1 reject (explanation required)
> >
> > Thanks for your assistance in achieving this milestone!
> >
> > [1] policy http://incubator.apache.org/incubation/Incubation_Policy.
> html#Releases
> > [2] distribution https://dist.apache.org/repos/
> dist/release/incubator/edgent/
> > [3] rc1 vote https://www.mail-archive.com/dev@edgent.apache.org/
> msg01477.html
> > [4] rc1 src repo https://github.com/apache/incubator-edgent/tree/1.1.0-
> incubating-RC1
> > [5] rc1 artifacts https://dist.apache.org/repos/
> dist/dev/incubator/edgent/1.1.0-incubating/rc1/
>
>

Re: Proposal: release Apache Edgent 1.1.0-incubating

[William Marshall]

+1

On Tue, Feb 14, 2017 at 4:59 PM, Justin Mclean 
wrote:

> Hi,
>
> > I absolutely agree, but think if nobody else is volunteering right now,
> it is definitely worthwhile for you to go through it again and get another
> release out.
>
> Yep +1 to that.
>
> Thanks,
> Justin

Re: What do we still need to be ready for graduation?

[William Marshall]

>What do you as a community feel we still need to do to be ready?

To mirror previous concerns, I agree that we need a larger and more diverse
community. I see healthy projects composed of many individual contributors
from universities, corporate entities, or personal projects. Currently, we
only have one non-IBM committer.

Meetups, conferences, and articles might be a good way to spur growth.

-Will

Proposed Podling Report

[William Marshall]

Hi All,

The following is the proposed podling report for the months of November,
December, and January. As this needs to be submitted by EOD today, please
respond with comments asap.

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

Edgent meetup

[William Marshall]

Hi All,

I will be running an Edgent meetup this Wednesday at 6:00 PM PST at
Galvanize in San Francisco.

Hope you can make it!

https://www.meetup.com/SF-Data-Science/events/236682354/

-Will

Re: Edgent website analytics

[William Marshall]

Thanks Justin & Dan.

We could potentially proceed as follows


   - Create an Edgent Google Analytics account, e.g. apacheedg...@gmail.com
   - Set up Analytics using Edgent account
   - Post the account info to the PPMC



   -  Publish the monthly reports publicly.



On Thu, Jan 5, 2017 at 1:58 PM, Justin Mclean 
wrote:

> Hi,
>
> > I'd like to have a discussion about:
> > A) Should we include analytics on our site?
>
> You can if you want to, a number of other Apache projects do so.
>
> > B) On what account should the data be stored, and how should access be
> > controlled?
>
> I would post the credentials to the private list to let the PPMC manage it.
>
> > C) Are there more general concerns? Dan brought up that both Apex and
> > Apache include privacy disclaimers and linked to this JIRA:
> > https://issues.apache.org/jira/browse/APEXCORE-553
>
> Yes add a privacy policy, here’s another example [1].
>
> Thanks,
> Justin
>
> 1. http://flex.apache.org/about-privacy.html

Edgent website analytics

[William Marshall]

Hi All,

In the interest of learning more about how users interact with the Edgent
site, I added a google analytics snippet to our landing and documentation
pages. This was hasty, and should have been discussed on the mailing list
first, so I have since backed out the changes.

I'd like to have a discussion about:
A) Should we include analytics on our site?
B) On what account should the data be stored, and how should access be
controlled?
C) Are there more general concerns? Dan brought up that both Apex and
Apache include privacy disclaimers and linked to this JIRA:
https://issues.apache.org/jira/browse/APEXCORE-553

It should have been discussed here first, and I apologize for committing
the changes without consulting the mailing list.

-Will

Re: test mail after trouble migrating subscription from quarks

[William Marshall]

I'd be happy to be a moderator of the dev mailing list. Let me know if
there's any step I need to take.

-Will

On Tue, Dec 6, 2016 at 12:58 PM, Katherine Marsden <kmars...@apache.org>
wrote:

> On 12/6/16 12:37 PM, William Marshall wrote:
>
> Given that I encountered this issue, it's possible that others on the
>> mailing list have also encountered this issue. I would recommend sending
>> direct emails to each member of the mailing list, and informing them that
>> they may not have been receiving all (or any) mail from this list. If a
>> mailing list member is able to see this and other edgent-dev emails after
>> the name change, then they likely are not affected.
>>
>> I am happy to craft the email, unless someone else would prefer to. If so,
>> where can I find a list of everyone subscribed to the dev@mailing list?
>>
>
> Thanks Will for volunteering to send the mail. I think that is smart as we
> may have lost some of the community in the switch and I did not see any
> distinction in the list that might give us a clue of who has this problem.
> Direct mail is our best bet.
>
> Probably a moderator should send the mails.
> Are you willing also to become a moderator of the dev and private lists?
> That way you can send email to -l...@edgent.apache.org to get the
> lists and unsubscribe the problem accounts.
>
> Moderator responsibilities (outside this problem) are light.
> You, just occasionally get a MODERATE or CONFIRM email when someone not
> subscribed to the list sends email. You then just respond to let the
> legitimate ones through.
>
> Let us know. If you don't have bandwidth, maybe another volunteer would
> like to do it or I would be happy to.
>
> Best
>
> Kathey
>
>
>
>
>

Re: test mail after trouble migrating subscription from quarks

[William Marshall]

Since I've received this email, the issue seems to have been resolved after
Kathy manually removed me from the list so I could resubscribe via
dev-subscr...@edgent.apache.org.

Given that I encountered this issue, it's possible that others on the
mailing list have also encountered this issue. I would recommend sending
direct emails to each member of the mailing list, and informing them that
they may not have been receiving all (or any) mail from this list. If a
mailing list member is able to see this and other edgent-dev emails after
the name change, then they likely are not affected.

I am happy to craft the email, unless someone else would prefer to. If so,
where can I find a list of everyone subscribed to the dev@mailing list?

-Will

On Tue, Dec 6, 2016 at 11:53 AM, Katherine Marsden 
wrote:

>  Will pinged me off line regarding a problem getting edgent emails after
> the switch from quarks to edgent. He showed up on the subscription list but
> was not getting emails and could not unsubscribe.
>
> To correct this I unsubscribed him as moderator by sending mail to
> dev-unsubscribe-wcmarsha=gmail@edgent.apache.org
>
> per the instructions at
> http://apache.org/foundation/mailinglists.html
>
> and he was able to successfully resubscribe himself by sending mail to
> dev-subscr...@edgent.apache.org.  Hopefully this fixes it.
>
> Will, please let us know.
>
> Best
>
> Kathey
>