Re: segger jlink

Hi, > Well, I’m on mynewt.slack.com - if you care to be a guinea pig! :-) > > Invite link here: > https://join.slack.com/mynewt/shared_invite/MTkwMTg1ODM1NTg5LTE0OTYxNzQ4NzQtZTU1YmNhYjhkMg You might want to consider adding a room to https://the-asf.slack.com/ ? Thanks, Justin

Re: [VOTE] Graduation of podling Apache Mynewt to Top Level Project

Hi, +1 good luck (not that you need it) and congratulations Thanks, Justin

Re: [DISCUSS] Graduation of podling Apache Mynewt to Top Level Project

Hi, > Yes, will add that. Some are independent consultants and not affiliated with > any organization. Well I fit in that as well. I think Others (X) would be fine. > Do I need to send a new [VOTE] thread with the revisions? Or just do the > corrections before sending out to general@ ? IMO

Re: [DISCUSS] Graduation of podling Apache Mynewt to Top Level Project

Hi, > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Justin Mcclean > be appointed to the office of Vice President, Apache Mynewt It’s Mclean not Mcclean unless there’s another Justin on the project I don’t know about :-) Thanks, Justin

Re: [DISCUSS] Graduation of podling Apache Mynewt to Top Level Project

e and you need to add "Class Software (1)*”? > RESOLVED, that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache Mynewt Project: > *Justin Mclean” <jmcl...@apache.org> > *P. Taylor Goetz” <ptgo...@apache.org

Re: [DRAFT] April podling report for Mynewt

HI, Find my me. Anyone else think this project is near to graduation? Thanks, Justin

Re: [DISCUSS] [VOTE] Release Policy for Apache Mynewt

Hi, > I would like to propose and put to vote a release policy for Apache Mynewt. > As you all know, this is an important step towards graduation. Not a requirement for graduation but certainly a good thing to have. Looks good to me as long as the Apache voting rules are followed for releases

Re: [DISCUSS] Release Apache Mynewt 1.0.0-b2-incubating-rc1

Hi, > should the NOTICE files be updated with 2017? Yep but not a blocking issue for an incubator vote. 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 - January 2017

Hi, Ping? Is someone on the PPMC working on this? It was due on the 4th. Thanks, Justin

Re: [RESULT][VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc1

Hi, Sorry but I just voted -1 on that release as it has a number of IMO significant issues. Given teh great work done on LICENSE/NOTICE initially I had assumed these were being kept upto date but that doesn’t seem to be the case. Apologies for not catching these issues sooner but with

Re: Nordic SDK license not Apache-compatible?

Hi, > Yes, these files are optional in the sense that Mynewt can still be > used without them. However, someone wishing to use Mynewt with a Nordic > MCU will probably won't get very far without them. As it optional (not everyone will use it on this platform) it is possible to have a

Re: Reminder to vote for 0.9.0-rc3 on the dev list

HI, > This is just a friendly reminder - if you are an IPMC member with a > binding vote, could you please carry your vote for 0.9.0-rc3 over to the > gen list? I’m just looking at it now. BTW sometime it can help to say what the difference from the last RC is, if for instance the only

Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc2

Hi, > For reference, the file that is being changed contains offsets to interrupt > vectors on ARM platforms. The new (correctly) licensed functions look > perfectly fine to me, and I think post release (and in develop) we should > replace these files. Sounds like a fine approach to me.

Re: [DISCUSS] A users@ mailing list for Apache Mynewt

Hi, > I agree 100% on the mail archive. If we could tee this off to a better > interface (more intuitive threading and search) and maintain sync, that would > help the community a lot. And that exists! [1] On Other project we’ve also set up forums to mirror the mailing lists at nibble [2].

Re: [DISCUSS] Release Apache Mynewt 0.8.0-incubating-rc1

Hi, > mynewt-core is a project, just like any project you create with newt new. So is a “newt build mynewt-core” expected to work? Thanks, Justin

Re: [DISCUSS] Release Apache Mynewt 0.8.0-incubating-rc1

HI, Perhaps a silly question but how do you compile mynewt core? There doesn’t seem to be any instructions in the package. I’m also run into an issue with compiling blinky on OSX and was getting this: Building target targets/my_blinky_sim Compiling main.c Error: In file included from

Re: [DISCUSS] Release Apache Mynewt 0.8.0-incubating-rc1

Hi, > I don't see the link? B2 (the link I see) was voted on, and released. This > is v0.8, full release... Sorry my mistake. I had expect the version number to not be the same as the previous release. Generally the version after 0.8.0 would be 0.8.1 (or similar). Thanks, Justin

Re: [DISCUSS] Release Apache Mynewt 0.8.0-incubating-rc1

Hi, Looks like there’s a up public link up to build that has not been voted on [1]? If so this is against Apache policy and the second time this has happened. What can we do to to fix this/avoid this happening again in the future? Justin 1. http://mynewt.apache.org/download/

Re: Problem Loading arduino_boot

Hi, > Please which USB cable Am I suppose to use to connect the Board to my > Computer??? Make sure it’s a data cable and not just a power cable, some cheap USB cable are missing the data lines. Thanks, Justin

Re: Using third-party Apache code

Hi, > I have pulled in some BLE security manager code from the Zephyr > project (www.zephyrproject.org). It is released under the Apache 2.0 > license, but not by the ASF. You’ll also have to consider their trademarks and also note the export compliance [1]. Does what you want to use contain

Re: Using third-party Apache code

Hi, > My understanding is that bundled Apache projects do not require a > pointer in the LICENSE file. My first question is: is this > understanding correct? Correct (for Apache 2.0 not for 1.1) that's what current policy states. Some projects do however list this in LICENSE even when there is

Re: April board report for Mynewt

Hi, > 1. Do a first Apache release capable of producing a downloadable RTOS image > with support for multiple peripherals and network connectivity. Do subsequent > releases to indicate thorough understanding, repeatability, and maturity of > process. As we already have made releases perhaps

Re: PWM API

Hi, > That¹s new information for me on the LEDs visuals. Are you talking about > PWM to control brightness or just visual blink rate? 16-bits seems large > to me for specifying a duty cycle for brightness, but I have no > experience. For comparison Arduino’s AnalogWrite takes a single byte

Hotspot anaysis

Hi, A little off topic but may be of interest. I did some hotspot analysis on mynewt core for a talk I’m giving and you can find the draft here: http://cssw.info.s3.amazonaws.com/Apache/hotspots/mynewt-core/index.html

Re: Release policy issue

Hi, Just in case it's not clear, under [1] it states: "Do not include any links on the project website that might encourage non-developers to download and use nightly builds, snapshots, release candidates, or any other similar package.” People subscribed to the dev list will know how to get

Release policy issue

Hi, I noticed there is a download link to unreleased software here [1]. I’m sorry but this is not allowed under Apache release policy. Can you please remove that link until the currently release candidate has been voted on. In future please only put up links to software only after it been

Re: [VOTE] Release Apache Mynewt 0.8.0-incubating-b2

Hi, > Blinky is a bit unusual in that it is not meant to be compilable nor > testable on its own Any reason it has unittest as a target then? (as shown by mynewt info) > Are subdirectories generally not considered to be included in such a > reference? All good I missed that subdirectory

Re: [VOTE] Release Apache Mynewt 0.8.0-incubating-b2

Hi, > We only officially vote on the source release so if you wanted to release > just the source artefacts here it would probably be OK (as I see nothing that > would block that) and I would change my vote. Sorry long day - I meant to say once the MPL was fixed. Justin

Re: [VOTE] Release Apache Mynewt 0.8.0-incubating-b2

Hi, > Darn, I failed to notice that the MPL is only valid in binary (not > source) releases. Always look at the Category A list on that legal FAQ page, if it’s in there it is comparable with the Apache license. If it’s Category B ( i.e. MPL or EPL) you can only included it in binary form and

Re: [VOTE] Release Apache Mynewt 0.8.0-incubating-b2

Hi, Sorry -1 binding as: - LICENSE, NOTICE and DISCLAIMER are missing from the convenience binary releases - Newt source release contains MPL code (hashicorp). This is a category B licence and can not be included in source form in an Apache release. - I’d also like to see instructions on how to

Re: incubator-mynewt-larva git commit: Fix some version discrepencies in pkg.yml files.

Hi, Just a minor thing I just noticed and certainly not an issue, but the ASF are not big on author tags. The PMC can of course discuss and decide what to do here, but you may want to remove or change them to be “ASF" or “Apache Mynewt". If they are removed you can see who worked on the file

Re: installing the Newt

Hi, > Nice! That seems to work. I guess I completely glossed over those > vanity URL emails. I will make the necessary changes to the develop > branch. Unfortunately, I'm afraid it is too late to fix 0.8.0-b1. Would be easy enough to release a 0.8.1 if people think the fix is important

Re: Analysis of our first release process

Hi, > What type of warnings do we want to provide in the Newt tool for non-ASF > compatible licenses. > > - Do we want to have a list of these 3rd party package repositories in the > official ASF documentation? General practice is to prompt the user when installing something that is not

Re: Analysis of our first release process

Hi, Great summary! > 0.8.0-b1 is exceptional in that it is our first release. In subsequent > releases we will want to specify what has been added or fixed since the > last release, as well as highlight known issues. JFYI this is usually done in a separate file call RELEASE_NOTES or similar.

Re: Tutorial topics for Apache Mynewt

Hi, > 1. How to create a custom LED blink pattern on the STM32F Discovery board > from STMicro Another (almost essential) beginners example would be how to drive a small servo motor. Thanks, Justin

Re: incubator-mynewt-site git commit: information to download newt tool executable added

Hi, Just double checking you're only putting up the source releases. There are a few policy issues around putting up the executables on the incubating site, i.e. before the incubating votes has passed and possible releasing unvoted on artefacts. Thanks, Justin

Re: README.md files

Hi, You may want to cancel the last vote before stating a new one by sending a ""[VOTE][CANCEL]” email. Thanks, Justin

Re: [VOTE] Release Mynewt 0.8.0-b1-incubating

Hi, > These are actually generated using sha512: > > gpg2 --print-md SHA512 larva-0.8.0-b1.tgz > larva-0.8.0-b1.tgz.sha Ah it's sha512. Looks like openssl is a bit more friendly: openssl dgst -sha512 larva-0.8.0-b1.tgz SHA512(larva-0.8.0-b1.tgz)=

Re: [3/3] incubator-mynewt-larva git commit: Add license to .gitignore file.

Hi, > I'll second that: Justin, and I say this knowing you're Australian: you've > earned as many beers as you can drink when we meet :-) I certainly drink beer. However I’ll pass on Fosters and Budwizer - they are not release quality IMO :-) Thanks, Justin

Re: [VOTE] Release Mynewt 0.8.0-b1-incubating

Hi, Sorry but it’s -1 (binding) from me. To be clear that doesn’t stop other people voting +1, and if you get 3+1 you can still put it up on the IPMC general list for a vote. You’re also welcome to try and change my mind, anyone can change their vote after initial voting. All the -1 means is

Re: [DISCUSS] Release Mynewt 0.8.0-b1-incubating

Hi, Part of the requirement for voting on a source artefact is that you can compile the package. With the current source releases how is that actually done? Thanks, Justin

Re: [DISCUSS] Release Mynewt 0.8.0-b1-incubating

Hi, See we already have an enthusiastic +1 vote. It is customary to list what was actually checked in the release and on what platform it was tested on. Being the first release I do suggest we double check everything just in case something has slipped through the cracks, other wise the vote

Re: [3/3] incubator-mynewt-larva git commit: Add license to .gitignore file.

Hi, Again no harm done but no required. JFYI - Files without any creative content don’t need a license header, .gitignore would fall under that. [1] Justin 1. http://www.apache.org/legal/src-headers.html#faq-exceptions

Re: LICENSE and NOTICE contents / headers

Hi, > These are both in tadpole and larva. Are you suggesting moving these prior > to release? Well it a little confusion as at first I though there was other Apache licensed software bundled and if that is you then need to look up their NOTICE files to see if that effects ours. Totally up

exe in repo

Hi, Just noticed this in the repo: https://github.com/apache/incubator-mynewt-newt/blob/master/newtvm/newtvm.exe It is intended that this go in the source release? That would be an issue and a source release can’t contain any executables or jars or the like. Thanks, Justin

RAT (release audit tool)

Hi, It quite likely that anyone reviewing the release on the incubator will use: 1) Apache rat [1] 2) Compliance Rocks We might want to put a rat exclusion file together to help people and cut down of the number of false positives it currently generates. At the very least yo shovel run the

Re: LICENSE and NOTICE contents / headers

Hi, Also a few extra LICENSE file sin tadpole? ./hw/bsp/native/LICENSE ./libs/os/LICENSE ./libs/testutil/LICENSE Thanks, Justin

Re: LICENSE and NOTICE contents / headers

Hi, I’m still noticing a few files with multiple license headers in tadpole: ./libs/os/src/arch/cortex_m0/m0/HAL_CM0.s ./libs/os/src/arch/cortex_m0/m0/SVC_Table.s ./libs/os/src/arch/cortex_m4/m4/HAL_CM4.s ./libs/os/src/arch/cortex_m4/m4/SVC_Table.s ./libs/os/src/os_mbuf.c ./libs/util/src/base64.c

Re: LICENSE and NOTICE contents / headers

HI, > OK, I believe I have removed the Apache license from all the > "otherwise-licensed" files, and added corresponding pointers to the > larva LICENSE file. Still missing a few things I’ll add them. > Larva's LICENSE file has become quite a monster, I’m afraid. Yep but I’ve seen worse. It's

Re: incubator-mynewt-larva git commit: Updated version of system_stm32f4xx with more permissive license.

Hi, Would it be correct to assume this is a different version of the file by STMicroelectronics issued under a different license by them? Thanks, Justin > On 20 Feb 2016, at 9:55 am, ccoll...@apache.org wrote: > > Repository: incubator-mynewt-larva > Updated Branches: > refs/heads/master

Re: LICENSE and NOTICE contents / headers

Hi, > OK, thanks for the heads up. Is this something we should deal with > immediately, or can we fix it between now and our next release? Best to fix now IMO, otherwise the incubator release may not pass. I’d say the risk is low but it’s there. That being said an incubating release doesn’t

Re: LICENSE and NOTICE contents / headers

Hi, > The rest of them are from files which contain the Apache license text at > the top of the file. In these files, we retained the original copyright > notice below the Apache license. Do you think this is problematic? That's incorrect.while you can license the whole as Apache, each file

Re: incubator-mynewt-newt git commit: LICENSE, NOTICE, and KEYS files for newt.

HI, > Since we won't be releasing binaries this time around, the only > artifacts are: 1) the source tgz files Perhaps a silly question. But how are those tgz files generated? Thanks, Justin

LICENSE and NOTICE contents / headers

Hi, I’m not 100% sure what’s in the release files but from a quick look (rushing out t the door) I’m guessing it still needs a tiny bit of work: Newt repo still has: ./.git/hooks/pre-rebase.sample And a number of files (mostly .go files) still have "Copyright 2015 Runtime Inc.” Larval has a

Re: incubator-mynewt-newt git commit: LICENSE, NOTICE, and KEYS files for newt.

Hi, >> Would you like me to give the various LICENSE and NOTICE files a once >> over before you make an official RC? > > Oops, I am not sure how I missed this. Yes, that would be extremely > helpful. I assume they are in the top of each repo? I can’t get to this right now (just about to go

Re: incubator-mynewt-newt git commit: LICENSE, NOTICE, and KEYS files for newt.

Hi, Another thought - releasing all 3 products make sense for the first release. After that you may want to consider releasing and voting on each one separately - less to review / less moving pieces to foul up :-) Thanks, Justin

Re: incubator-mynewt-newt git commit: LICENSE, NOTICE, and KEYS files for newt.

Hi, > No - the binaries certainly *do* contain LGPL code. I take it that is a > problem :). I think we can refrain from releasing the binaries until we > get the LGPL issue sorted out. If others disagree with this, please > chime in. Having a source only release would make it easier. Just be

Re: Kicking off a release

Hi, > Good question: I nominate Chris. Well as long as Chris want to take on that role that’s fine :-) Here’s some links on the process / publishing a release: http://www.apache.org/dev/release.html http://www.apache.org/dev/release-publishing.html

Re: Wiki / Confluence

Hi, > Is there ASF infrastructure to support a Wiki? Would someone mind putting > together a ticket for infrastructure, so we can start capturing this stuff > there? You can ask for it here [1] under 3 wiki request. You need to know the admin and initial contributors and a few other things.

Re: Kicking off a release

Hi, Who is going to act as release manager? > The latter, I think, has been successfully resolved on dev@mynewt and > general@incubator Yep agreed. > - Add release notes to the mynewt distribution > - Tag the tree with a B1 release tag (mynewt_0_8_0_b1_tag) > - Start a [VOTE] thread to [VOTE]

Release dependant on LGPL

Hi, Apache Mynewt [1] is moving towards making it’s first release. We found that one of the libraries we depend on, viper which is MIT licensed [2], in turn depends on a library that is LGPLv3 licensed (go-yaml) [3]. It is intended to replace the viper/yaml libraries with ones comparable with

Re: Request committer access

Hi, > It looks like other Apache projects do pull requests using github, but mynewt > isn't doing > that. You can create git patches on ttp://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git or pull requests on the github mirrors of the mynewt repos

Re: Request committer access

Hi, > Oh, cool. I find it easier to keep track of proposed changes using the > dedicated pull requests page than searching through email. Usual practise is to add the patch to a JIRA. > Could you setup a mirror for > http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git? You’ll

Re: add edit perms for Apache Mynewt in Jira

Hi, > “p...@runtime.io” I’ve added you to the contributors group. If there something you need do do and it doesn’t let you just ask. Thanks, Justin

Re: Request committer access

Hi, > I'm a backend engineer at runtime.io. I'd like to become a committer so I > can help with infrastructure and website related tasks. The way to become a committer is by showing merit by contributing to the project. The peddling PMC then needs to vote or decides on making your a

Review of tadpole licenses

Hi, Here’s the licenses in tadpole. BSD - KEIL ARM Germany GmbH ./libs/os/src/arch/cortex_m4/m4/HAL_CM4.s ./libs/os/src/arch/cortex_m4/m4/SVC_Table.s BSD - The Regents of the University of California ./libs/os/src/os_mbuf.c (BTW You’ll notice that clause 3 is missing I think that this was

Re: [2/2] incubator-mynewt-larva git commit: Simpler linker script for STM32F3 discovery board.

Hi, > Re [2] - What defines major? :-) I ask this because of libjson. The (P)PMC i.e. you. (see point 5 in that last link). > We've taken microjson (http://www.catb.org/esr/microjson/), and are doing > some fairly major surgery to it: > - conversion into our coding standards (tabs to spaces,

Re: Automate http://mynewt.incubator.apache.org generation

Hi, >> +echo Remove unwanted html templates >> +find site -name "*.html" | xargs grep '{%.*%}' -l | xargs rm Nice didn’t think of doing it that way, I had forgotten about xargs I would normally do: find site -name "*.html" -exec rm {} \; Or even: find site -name “*.html” -delete Thanks,

Re: Mailing lists

done

Getting LICENSE and NOTICE read for a release

Hi, I just noticed we were missing NOTICE files in newt [1] and lava [2] so added one. Please feel free to alter the Realtime Inc line if you feel it needs it. Is there any reason for the LICENSE in newt repo to not be at the top level? Tadpole [3] is missing a top level LICENSE and NOTICE

Re: Larva content review for license

Hi, > If you'd like to create an overall shout-out, then go for it. The > Subversion project does this, and uses the same file to track partial > commit (as Mynewt has adopted). See: > http://svn.apache.org/repos/asf/subversion/trunk/COMMITTERS Apache Flex does this a little differently and

Re: Vanity import domain

Hi, > We (runtime) have purchased and set this up, because we are lazy and don't > like typing things. Sure understand that, but it lacks a bit of transparency to me. Also (while unlikely) what if it was hacked and pointed to download something malicious? > We'd be happy to gift this to the

Re: Taskstats display on newtmgr

Hi, You may want to add as an option a format that a little more parseable by computers? i.e. JSON or CSV or similar. That way various tools (IDEs, logging) etc could take advantage of it. Thanks, Justin

Re: Draft of January report for Mynewt

Hi, > count tomorrow morning (instead of 150+). Rough counts are fine - the exact stats don’t matter. > 3. Develop a roadmap and release schedule for the Mynewt Operating System Not a big deal but I’d remove this one. Apache projects are volunteer based, and while some projects do have

Re: January 2016 Report

Hi, Anyone free to do this? Thanks, Justin

Re: Incubator PMC/Board report for Nov 2015 ([ppmc])

Hi, > Hi, I posted the status report and marked it as being signed off by three > mentors: > > Sterling Hughes > Justin Mclean > P.Taylor Goetz Usually it’s up to the mentors to sign it off (and they may want to add a note), but no objections from me. Thanks, Justin

Re: JIRA

Hi, It’ all been set up and good to go [1]. I’ve been made an administrator, if anyone else want to be one just ask. Thanks, Justin 1. https://issues.apache.org/jira/browse/MYNEWT

Minute Incubation web site

Hi, Currently our web site gives a Not Found page [1]. There are several options for creating an Apache web site [2] which do we want to go with? I think I’ve also seen content pulled from github, but would need to double check that. Thanks, Justin 1. http://mynewt.incubator.apache.org 2.

Re: JIRA

Hi, > Hi, sorry I didn't catch this earlier, but the original plan was to have all > notifications including JIRA to be sent to notifications@mynewt. Isn’t that normally for notifications rather than issues? i.e. We can keep both use issues for JIRA and notifications for release announcement

Re: Mynewt Incubation web site

Hi, > I need my ASF account (as a committer) set up before I can get started with > their CMS. I believe your account has been created. > We want to put up a basic Mynewt incubator project website as soon as > possible. I was thinking of using the Apache CMS to publish the documentation >