Re: Address Randomization in net/nimble

[will sanfilippo]

Not sure if this was answered, but I do think the simple form of random 
addresses is either close to being there or not alot of work. Would have to 
look into this a bit more to be sure.


> On Feb 6, 2016, at 1:04 PM, Sterling Hughes  wrote:
> 
> Howdy:
> 
> How hard is it to get address randomization in the net/nimble stack?  I 
> realize that full Bluetooth security is probably a month or two away, but 
> would it be possible to just provide the randomization component of it, for 
> privacy and tracking considerations?
> 
> Sterling

Re: Request committer access

[Justin Mclean]

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 
https://github.com/apache/incubator-mynewt-larva.

Thanks,
Justin

Bye Bye Eggs :-(

[Sterling Hughes]

Hey,

I have implemented the bug report here: 
https://issues.apache.org/jira/browse/MYNEWT-71


I think everyone has noticed that on-boarding new users becomes 
difficult because we use custom terms for packages, package lists and 
repositories.  While I personally like these terms (I named them that 
way), I think we wan the package and build system to be as easy to use 
as possible, and keeping track of these seems to be creating too much of 
a hurdle.


So, I have a bunch of mondo commits to rename these.  They are low risk, 
and I've tested them.


When I commit, in order to maintain your existing targets, you will need 
to do the following:


- rename .nest in larva to .repo (this is custom per install, so I 
can't move this for you)


- rename nest.db to repo.db in .repo

- rename clutches/ directory pkg-lists/ in .repo

Everything else should operate well, unless you have changes to egg.yml 
files that are uncommitted.  You will need to manually port those over.


Also, as a part of this commit, I've removed .git from the newt import 
path.  It seems like the majority of people are able to go get this 
without the .git, and it was causing conflicts with newtmgr.  (*)


I'll push these to origin master this evening if nobody has objections.

Sterling

(*) These will eventually be moved, again, when Todd adds 
mynewt.apache.org support.

Re: Request committer access

[Justin Mclean]

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 need to raise a JIRA for infra like this one:
https://issues.apache.org/jira/browse/INFRA-11212

This can be done though this:
https://issues.apache.org/jira/servicedesk/customer/portal/1

Thanks,
Justin

Re: Request committer access

[todd mitton]

Oh, cool.  I find it easier to keep track of proposed changes using the
dedicated pull requests page than searching through email.  Could you setup
a mirror for
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site.git?  Let me
know if I should submit a request ticket someplace.

Thanks Justin,
-Todd


On Tue, Feb 9, 2016 at 1:28 PM, Justin Mclean 
wrote:

> 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
> https://github.com/apache/incubator-mynewt-larva.
>
> Thanks,
> Justin

Re: Bye Bye Eggs :-(

[marko kiiskila]

+1.

This will have effect on pending work. When do you think you’ll do this?
IMHO sooner is better.

> On Feb 9, 2016, at 3:56 PM, Sterling Hughes  wrote:
> 
> Hey,
> 
> I have implemented the bug report here: 
> https://issues.apache.org/jira/browse/MYNEWT-71
> 
> I think everyone has noticed that on-boarding new users becomes difficult 
> because we use custom terms for packages, package lists and repositories.  
> While I personally like these terms (I named them that way), I think we wan 
> the package and build system to be as easy to use as possible, and keeping 
> track of these seems to be creating too much of a hurdle.
> 
> So, I have a bunch of mondo commits to rename these.  They are low risk, and 
> I've tested them.
> 
> When I commit, in order to maintain your existing targets, you will need to 
> do the following:
> 
> - rename .nest in larva to .repo (this is custom per install, so I can't move 
> this for you)
> 
> - rename nest.db to repo.db in .repo
> 
> - rename clutches/ directory pkg-lists/ in .repo
> 
> Everything else should operate well, unless you have changes to egg.yml files 
> that are uncommitted.  You will need to manually port those over.
> 
> Also, as a part of this commit, I've removed .git from the newt import path.  
> It seems like the majority of people are able to go get this without the 
> .git, and it was causing conflicts with newtmgr.  (*)
> 
> I'll push these to origin master this evening if nobody has objections.
> 
> Sterling
> 
> (*) These will eventually be moved, again, when Todd adds mynewt.apache.org 
> support.