Re: [VOTE] Retire Apache Edgent

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

Re: [VOTE] Retire Apache Edgent

Hi, +1 (binding) Sad to see but I can see the project graduating. Thanks, Justin

Re: Podling Report Reminder - May 2019

HI, > I'll take care of that later today. No rush it been extended a few days given it falls on a 1st this month. Thanks, Justin

Re: Access Twitter account

Hi, > @Chris or @Justin: what do you think of Dan's proposal? sounds fine to me. Thanks, Justin

Incubator Podling Report (Due 6th February)

Hi, The incubator PMC would appreciated if you could complete the podling report on time it's due on 6th February in a few days. It's best if you discuss the contents of the report on the list a week before it is due and work collaboratively on it before submitting it. It takes time to

Re: [DRAFT] November Podling Report Edgent

Hi, > I think we (as we-that-are-on-the-list) have to decide whether we want to > (re-)start the project, building a new PPMC (currently we have effectively > one with chris) and start to do some work in edgent. As far as PPMC (and mentor) duties I’m still around. The board likes a minimum of

Re: [DRAFT] May Podling Report Edgent

Hi, > Can someone post this to the incubator wiki? Its not complete. I can sign > off if you're missing sign off, but would prefer one of the active mentors > can. I can do this laster today. Thanks, Justin

Re: My Edgent and PLC4X Article on the Cover-Page

Hi, > today I bought the magazine with my Article and was totally amazed that it > has become one of the cover-page articles :- Really nice. Any chance of an english translation? Thanks, Justin

Re: request contribute permission

Hi, > You mean I do not need jira's "Assign" permission？ No but if you need that we can give you that without being committer. > Just sending discussions > to mailing list, if the community accepts my idea, I could contribute my > code then send my PR to apache/edgent repository? Yes that’s

Re: Podling Report Reminder - February 2018

Hi, This is due in a coupe of days - anyone have some bandwidth to work on it? Thanks, Justin

Re: [VOTE] Apache Edgent (Incubating) 1.2.0 RC1

Hi, +1 (binding) Here’s what I checked: - incubating in name - signatures and hash fine - LICENSE and NOTICE fine - no unexpected binaries in source release - can compile from source Thanks, Justin

Re: [VOTE] Apache Edgent (Incubating) 1.2.0 RC1

HI, > +1 (binding) > > (Am I allowed to vote “binding” on an incubating project PPMC or do only the > Incubator PMCs vote with binding? If this is the case, I vote “non binding” > ;-) ) Only IPMC votes are binding. I’ll have time to take a look at the release tomorrow. Thanks, Justin

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi, > Regarding the pgp issue i guess you have to Import my Key somehow. But i'm No > expert on that. My key should be valid judging from the number of Apaches > that signed it. Eventually there is no path of trust and you need to import > it manually. The warning is fine - it just means that

Re: [REVIEW] Edgent IPMC status report

Hi, > Oh, Justin and John, was I supposed to add checkmarks for your signoff or do > you do that? The mentors (i.e. us) should do that. Thanks, Justin

Re: maven: d3.legend.js mods

Hi, > So, I added this to the servlets LICENSE Perfect! Justin

Re: maven: d3.legend.js mods

Hi, > the license of the file is still MIT … we didn’t change anything with this. > And it is referenced in the LICENSE file as being MIT licensed. The only > thing I don’t quite know, is if it’s enough to reference the local path to > the file in the LICENSE file. Sounds fine to me. Thanks,

Re: maven: d3.legend.js mods

Hi, > having a deeper look into the differences, I decided to just put the original > file back in there. > In general, I think it’s a bad idea to include other licensed code and to > change its code. We should avoid things like that in the future. > Do we now have to add a part to the NOTICE

Re: maven: appended-resources/licenses

Hi, > I meant say/ask: Any bundled artifact that has applicable NOTICE info, not > typical, must have it added to the bundle’s NOTICE, regardless of the bundled > artifact's license type. > Hence a bundled ALv2 licensed artifact that has a non-default NOTICE needs to > have that added to the

Re: maven: appended-resources/licenses

HI, > A bundle’s LICENSE and NOTICE can only contain information relevant to > content present in the bundle. Yep. > I thought info for all bundled content (regardless of license type) must be > included. No - there’s no need to list ALv2 licensed bits for instance. > I believe NOTICE must

Re: maven: war LICENSE file

Hi, > Chris, while the enhancement to make the war’s > WEB-INF/classes/META-INF/DEPENDENCIES complete with info for bundled external > jars is great, I believe the war’s LICENSE still needs to have that info too… > or more sensibly the LICENSE needs to include a reference to that info. >

Re: maven-cvt: jar/war LICENSE/NOTICE files

Hi, > My take on it, surely previously told that by a mentor :-), is each jar > requires LICENSE/NOTICE that are appropriate for it… no more… no less. Yep 100% it must reflect what is contained within that jar [1] and the notice need to be keep at short as possible. [2] Thanks, Justin 1.

Re: maven and distribution bundles with transitive deps: licensing

Hi, > As I understand it / ASF policy, the newly generated distribution bundles > lack the necessary > license/notice info for transitive deps contained in the bundle. In general dependancies don’t modify LICENSE or NOTICE files only what is bundled in an artefact does. Thanks, Justin

Re: Understanding the snapshot and release process

Hi, While not a requirement prefixing with apache may add some legal protection and is good from a branding point of of view. Thanks, Justin

Re: Proposal: release Apache Edgent 1.1.0-incubating

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: Edgent status report updates

Hi, > I would be interested to hear from the committers whether they think we > should pursue graduation by explaining rather than checking off this item. It has caused some discussion in the past on the incubator ist so that would be best. > We have this page for How to become a committer.

Re: Edgent status report updates

Hi, > 1) *Are there three or more independent committers?*(The legal definition of > independent is long and boring, but basically it means that there is no > binding relationship between the individuals, such as a shared employer, that > is capable of overriding their free will as

Re: Podling Report Reminder - February 2017

Hi, I notice the report has been submitted it’s always a good idea to post it here first before submitting IMO. RE point 2 on the maturity model, it just a useful guideline not policy so it’s not required for graduation. Thanks, Justin

IoT summit at ApacheCon

Hi, There’s going to be an IoT summit at ApacheCon. Is anyone thinking of submitting a talk? It would be a good opportunity to get the word out about the project and see what other Apache projects are doing in this space. Thanks, Justin

Re: Podling Report Reminder - February 2017

Hi, Just checking who on the PPMC is working on this as it due in a day. With the first release and a few other things there’s something to report :-) Thanks, Justin

Re: please help - can’t announce release until the website is updated

Hi, > The release needs to be published here [1] BTW it best to publish them with an svn mv command from the currently dev voted on artefacts. Thanks, Justin

Re: please help - can’t announce release until the website is updated

HI, > Does we have md5/sha/asc files? Or needs to be create from a release? The release needs to be published here [1] and you can link the hash / signatures files there. For the artefacts you need to wait 24 hours for the mirrors to catchup [2], and use the mirror script and not link directly

Re: [VOTE] Apache Edgent 1.0.0 Release RC2

Hi, +1 binding I checked: - incubating in name - signatures and hashes correct - DISCLAIMER exists - LICENSE good - Source NOTICE fine. The binary NOTICE is a little odd in it refers to external files but we can fix that in a later release. - No unexpected binaries in source release - All

[DISCUSS] Apache Edgent 1.0.0 RC2

HI, Just wondering what are the steps needed to build RC2 as it seem to be missing the gradle build file. Thanks, Justin

Re: Podling Report Reminder - November 2016

Hi, Is anyone of the PPMC working on this? It would be good to post a draft to the dev list first. Thanks, Justin

Re: [VOTE] Apache Edgent 1.0.0 release

Hi, Great! Might be best to start a new thread for the VOTE. Justin

Re: [DISCUSS] Apache Edgent 1.0.0 release

Hi, > I see that Kafka avoids bundling gradle-wrapper.jar by requiring the user to > perform a “bootstrap gradle” step using an installed version of gradle. You may also want to look at Groovy, Tapestry, Zest, Usergrid or Geode. I can see that a couple do have the jar in git but IMO would be

Re: [VOTE] Apache Edgent 1.0.0 release

Hi, BTW you do have 3 +1 vote and only one -1 vote, that is still enough to make a release if you were a top level project. A -1 is not a veto on a release. But with the binaries in the source release I don’t think this would pass an incubator vote so it probably best IMO to cancel this vote,

Re: [VOTE] Apache Edgent 1.0.0 release

Hi, I’ve been on holiday and only just had a chance to take a look at the release. Sorry but it’s -1 (binding) from me due to the artefact names missing incubating and we have unexpected binaries in the source release I checked: - incubating is not in name. See 3.1 of [1] - signatures and

Re: got karma to create edgent release areas?

Hi, > As per [1], I’m querying if anyone on the list has the karma to create the > Edgent release areas below. > If not I’ll just file a infra request. > > https://dist.apache.org/repos/dist/dev/incubator/edgent > https://dist.apache.org/repos/dist/release/incubator/edgent Done. Justin

[jira] [Commented] (EDGENT-284) Check all source files have license headers

[ https://issues.apache.org/jira/browse/EDGENT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664291#comment-15664291 ] Justin Mclean commented on EDGENT-284: -- You might also want to try http://compliance.rocks > Ch

Re: [GitHub] incubator-edgent pull request #231: [Edgent-272] source: conform to license&...

Hi, > Is there some acceptable way to reduce the bloat / duplication in LICENSE for > MIT / BSD licenses that differ only in copyrights for different files? Usual way is to use the short form, i.e. put some pointer text in LICENSE referring to the full license in a seperate file. [1] Here

Re: [GitHub] incubator-edgent pull request #231: [Edgent-272] source: conform to license&...

HI, > So it sounds like those copyright notices should be kept with their license > text that's been added to LICENSE. Yes that's the usual way. Thanks, Justin

[jira] [Commented] (EDGENT-292) Update CONTRIBUTORS

[ https://issues.apache.org/jira/browse/EDGENT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15649395#comment-15649395 ] Justin Mclean commented on EDGENT-292: -- You can make it how every you want ;-) Not that I care

[jira] [Comment Edited] (EDGENT-292) Update CONTRIBUTORS

[ https://issues.apache.org/jira/browse/EDGENT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648975#comment-15648975 ] Justin Mclean edited comment on EDGENT-292 at 11/8/16 10:28 PM: Another

[jira] [Commented] (EDGENT-292) Update CONTRIBUTORS

[ https://issues.apache.org/jira/browse/EDGENT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648975#comment-15648975 ] Justin Mclean commented on EDGENT-292: -- Another way is to not have this files at all and make sure

[jira] [Commented] (EDGENT-292) Update CONTRIBUTORS

[ https://issues.apache.org/jira/browse/EDGENT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648804#comment-15648804 ] Justin Mclean commented on EDGENT-292: -- What I generally do is look at VC and see who checked in any

[jira] [Commented] (EDGENT-306) With edgent Tester, failed to read file content from the newly appeared files from a directory

[ https://issues.apache.org/jira/browse/EDGENT-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623573#comment-15623573 ] Justin Mclean commented on EDGENT-306: -- Note this was the same test that failed when testing

[jira] [Commented] (EDGENT-280) Make sure README and RELEASE_NOTES are up to date

[ https://issues.apache.org/jira/browse/EDGENT-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623564#comment-15623564 ] Justin Mclean commented on EDGENT-280: -- Not a blocking issue just may causes some confusion

Re: [DISCUSS] Apache Edgent 1.0.0 release

Hi, I also getting two tests failing. Is this expected? I’m on OSX if it matters. I’m actually not sure what platforms are supported, perhaps this should be mentioned in README? org.apache.edgent.test.connectors.file.FileStreamsTextFileWriterGlobalTest > testRetainAggSizeBased FAILED

[jira] [Commented] (EDGENT-268) Change licensing header in gradle files

[ https://issues.apache.org/jira/browse/EDGENT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571191#comment-15571191 ] Justin Mclean commented on EDGENT-268: -- See also http://www.apache.org/legal/src-headers.html#headers

Re: I'll volunteer for release manager this go-round

Hi, > Thanks so much Dale for volunteering! > > Here is some information on making a release > http://www.apache.org/dev/release-publishing.html It a good idea to document it as you go makes it a lot easier for future release managers. e.g. [1] JIRA can also be used to track everything that

Re: binary release license info - some cause for concern?

HI, > Is it allowable to compile against the pi4j jar? LGPL/GPL is not allowed as a dependancy in most cases so it not allowed if we bundle it or not. Category X [1] can be used in a few cases, if it an optional dependancy [2] or a build tools [3], but I think in this case it wouldn’t be

Re: the license headers in the gradle files?

Hi, > The gradle files have ASF license headers but they are of the form specified > in [1]. The rest of the source files (java, shell) use the form specified in > [2]. Are the gradle files OK or do they need to be changed to use [2]? I would go with [2]. Thanks, Justin

Re: need to adjust "Edgent is released under the Apache License Version 2.0"?

Hi, > Does the statement need to be adjusted in light of EDGENT-262? …the Edgent > repository (console servlet code) includes MIT and BSD-3-Clause licensed > content. No the bundle as a whole is license under ASLv2. There terms of the MIT and BSD licenses are compatible with ASLv2 and allow

Re: binary release license info - some cause for concern?

Hi, > - javax.servlet-api-3.1.0.jar is CDDL-2 and GPL. > See [4] and https://glassfish.java.net/nonav/public/CDDL+GPL.html > > > - javax.websocket-api-1.0.jar is CDDL-1.1 and GPL-2 > See [5] and

Re: [jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

Hi, > For where I got d3.min.js, it is available here now, but it no longer seems > to have a BSD license. > > https://github.com/d3/d3/releases/tag/v3.5.9 Looks like 3 clause BSD to me [1], but even it it changes to/from MIT that’s fine as both are permissive licenses. Just make sure you use