Re: Edgent report for Feb - Apr 2017

[Katherine Marsden]

On 4/25/17 1:38 PM, Victor Dogaru wrote:


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

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

I would say ppmc members instead of just members as it might be confused 
with Apache members.


I think the template has changed a bit especially this section:

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

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

I would say we are in Community Building.

https://wiki.apache.org/incubator/May2017

Re: Edgent report for Feb - Apr 2017

[Dale LaBossiere]

LGTM

— Dale

> On Apr 25, 2017, at 4:38 PM, Victor Dogaru  wrote:
> 
> Hi All,
> 
> The following is the proposed report for the months of February, March, and
> April. As this needs to be submitted by May 1, please respond with comments
> soon.
...

Edgent report for Feb - Apr 2017

[Victor Dogaru]

Hi All,

The following is the proposed report for the months of February, March, and
April. As this needs to be submitted by May 1, please respond with comments
soon.

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:

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

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

Date of last release:

  * The most recent release of Apache Edgent was 1.1.0 on 17 March 2017.

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.

[jira] [Closed] (EDGENT-410) Update the Apache Incubator logo to the new logo

[Queenie Ma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Queenie Ma closed EDGENT-410.
-
Resolution: Resolved

> Update the Apache Incubator logo to the new logo
> 
>
> Key: EDGENT-410
> URL: https://issues.apache.org/jira/browse/EDGENT-410
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> The Incubator has recently selected a new logo. We need to update the logo on 
> our website to use the new logo (the first image in Press Kit for Podlings 
> page at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EDGENT-410) Update the Apache Incubator logo to the new logo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983256#comment-15983256
 ] 

ASF GitHub Bot commented on EDGENT-410:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/95


> Update the Apache Incubator logo to the new logo
> 
>
> Key: EDGENT-410
> URL: https://issues.apache.org/jira/browse/EDGENT-410
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> The Incubator has recently selected a new logo. We need to update the logo on 
> our website to use the new logo (the first image in Press Kit for Podlings 
> page at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-edgent-website pull request #95: [EDGENT-410] Update Apache Incuba...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/95


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EDGENT-410) Update the Apache Incubator logo to the new logo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983255#comment-15983255
 ] 

ASF GitHub Bot commented on EDGENT-410:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/95

[EDGENT-410] Update Apache Incubator logo

Also add the footer to the rest of the site.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-410

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent-website/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #95






> Update the Apache Incubator logo to the new logo
> 
>
> Key: EDGENT-410
> URL: https://issues.apache.org/jira/browse/EDGENT-410
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> The Incubator has recently selected a new logo. We need to update the logo on 
> our website to use the new logo (the first image in Press Kit for Podlings 
> page at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-edgent-website pull request #95: [EDGENT-410] Update Apache Incuba...

[queeniema]

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/95

[EDGENT-410] Update Apache Incubator logo

Also add the footer to the rest of the site.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-410

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent-website/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #95






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EDGENT-410) Update the Apache Incubator logo to the new logo

[Queenie Ma (JIRA)]

Queenie Ma created EDGENT-410:
-

 Summary: Update the Apache Incubator logo to the new logo
 Key: EDGENT-410
 URL: https://issues.apache.org/jira/browse/EDGENT-410
 Project: Edgent
  Issue Type: Task
  Components: Web Site
Reporter: Queenie Ma
Assignee: Queenie Ma


The Incubator has recently selected a new logo. We need to update the logo on 
our website to use the new logo (the first image in Press Kit for Podlings page 
at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: How to add Edgent as a dependency using gradle

[Samantha Chan]

Thanks!  will do!

Samantha

On Mon, Apr 24, 2017 at 8:36 AM, Dale LaBossiere 
wrote:

> I now noticed the mavenLocal info is mentioned in DEVELOPMENT.md [1]  :-)
>
> The Overview doc [2] (scroll to the bottom) describes what you need to add
> to a classpath to but doesn’t generally describe how to achieve that for
> different build environments.
> Still, maybe it’s worth providing a link to that gradle info there?  An
> opportunity to contribute! :-)
>
> Additionally, seems like it would be nice if there was some doc/help on
> how to populate a mavenLocal repo from a binary-release - e.g., include a
> gradle script in the binary release that will do that. Or maybe provide
> some gradle script that a project could just include that essentially just
> defines a “repository” (jars and metadata) so that the project can express
> the dependency in the normal way but not have to populate a mavenLocal
> repository.  Don’t know if that sort of thing is possible :-)
>
> Feel free to file a JIRA [3] requesting enhancements.
>
> Regardless pls share what you eventually came up with.
>
> Thanks,
> — Dale
>
> [1] https://github.com/apache/incubator-edgent/blob/master/
> DEVELOPMENT.md#publish-to-maven-repository
> [2] https://edgent.apache.org/javadoc/latest/  javadoc/latest/>
> [3] https://issues.apache.org/jira/browse/EDGENT
>
> > On Apr 24, 2017, at 8:56 AM, Dale LaBossiere 
> wrote:
> >
> > Hi,
> >
> > Edgent does not publish to MavenCentral.
> >
> > A while ago someone contributed changes to support publishing into
> mavenLocal.
> >
> > $ ./gradlew publishToMavenLocal
> >
> > Then…
> >
> > repositories {
> >  mavenLocal()
> > }
> >
> > And specify dependencies like: org.apache.edgent:edgent.api.
> topology:1.1.0
> >
> > Alternatively you can specify a dependency on a local jar.  Something
> like this I think
> >
> > dependencies {
> >  compile files(‘path-to-jar’)
> > }
> >
> > Hope that helps
> > — Dale
> >
> >> On Apr 22, 2017, at 9:56 AM, Samantha Chan 
> wrote:
> >>
> >> Hi -
> >>
> >> I am building an application that uses Apache Edgent.  I am trying to
> use
> >> Gradle to build my application.  In Gradle, one can specify dependencies
> >> like this:
> >>
> >> repositories {
> >>   mavenCentral()
> >> }
> >>
> >> dependencies {
> >>   compile group 'ca.uhn.hapi', name: 'hapi-base', version: '2.2'
> >> }
> >>
> >> This will download my dependency from Maven and I can use it to build my
> >> project.
> >>
> >> Is Apache Edgent published to Maven Central?  What's the best way to
> >> include Apache Edgent dependency in my gradle build script?
> >>
> >> Thanks...
> >> Samantha
> >
>
>