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

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 06:18:19PM +1100, Justin Mclean wrote: > 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? Oh, I see. No, not silly at all. I used

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

2016-02-18 Thread Justin Mclean
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

2016-02-18 Thread Justin Mclean
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.

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 06:05:20PM +1100, Justin Mclean wrote: > What the process for generating the release artefacts? Since we won't be releasing binaries this time around, the only artifacts are: 1) the source tgz files, 2) the ascii signature files, and 3) the SHA checksums. Or maybe you are

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

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 05:54:11PM +1100, Justin Mclean wrote: > 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

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

2016-02-18 Thread Justin Mclean
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.

2016-02-18 Thread Justin Mclean
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.

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 04:19:57PM +1100, Justin Mclean wrote: > 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. Thanks, Chris

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

2016-02-18 Thread Justin Mclean
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: incubator-mynewt-newt git commit: LICENSE, NOTICE, and KEYS files for newt.

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 04:19:57PM +1100, Justin Mclean wrote: [convenience binaries] > And are we 100% sure that they don’t contain the LGPL code (source or > compiled) ? No - the binaries certainly *do* contain LGPL code. I take it that is a problem :). I think we can refrain from releasing

Re: hal organization and multiple smaller packages

2016-02-18 Thread Sterling Hughes
Paul - I think you make a number of good points here, but I'm not sure all of them argue for re-organizing the HAL, but perhaps just improving the existing structure. The purpose of the HAL is to abstract MCU peripheral functions, and make that portable across various MCU architectures.

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

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 01:43:59PM +1100, Justin Mclean wrote: > If you’re going to be RM, you should sign up to that list and/or take > a look previous incubating release votes so you know what to expect. Good idea. I have subscribed to that list. Now... :) I am afraid I'm going to have to nag

[BLE] Questions about BLE on Apache Mynewt

2016-02-18 Thread Huynh Minh Quang
Dear Sir/Madam, First, I see that Apache Mynewt is the excellent RTOS and I would like to use Apache Mynewt for my BLE module using Nordict NRF51822 IC (this already working with mbed contribution). So, I wonder where can I find the documentation, user manual, tool-chain, complier or something

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

2016-02-18 Thread Christopher Collins
On Fri, Feb 19, 2016 at 01:18:19PM +1100, Justin Mclean wrote: > Hi, > > > Thanks, Justin. If we remove this from the distribution (i.e., don't > > bundle it), do we still need to mention it in LICENSE or NOTICE? > > No only things that are bundled need to be mentioned in LICENSE and > NOTICE,

hal organization and multiple smaller packages

2016-02-18 Thread p...@wrada.com
Just wanted to pass on some thoughts I had today about the hal ... I was thinking about how much is in a hal, how it will grow over time and how to tell "how complete" a given hal is. And more importantly how to provide simple stuff that does basic HW (like polling GPIO) while allowing

Re: Kicking off a release

2016-02-18 Thread Justin Mclean
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: Kicking off a release

2016-02-18 Thread Christopher Collins
Sounds good. I will act as the release manager. Chris On Thu, Feb 18, 2016 at 01:48:43PM -0800, Sterling Hughes wrote: > > > On 2/16/16 5:07 PM, Justin Mclean wrote: > > Hi, > > > > Who is going to act as release manager? > > > > Good question: I nominate Chris. > > > > >> - Add release

Re: Kicking off a release

2016-02-18 Thread Sterling Hughes
On 2/16/16 5:07 PM, Justin Mclean wrote: Hi, Who is going to act as release manager? Good question: I nominate Chris. - 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] on the Mynewt release (along