Re: renaming apache-mynewt-larva to apache-mynewt-os

[Sterling Hughes]

oh, and please specify your preferred option:

 [  ] apache-mynewt-mynewt
 [  ] apache-mynewt-os
 [  ] apache-mynewt-core
 [  ] apache-mynewt-main

Mine is apache-mynewt-mynewt, since this really is the "mynewt" portion 
of the mynewt project.


For efficiencies sake, unless noted otherwise, by +1 you are saying "I 
am fine with all of these options", and then expressing a preference for 
a particular one.  If you feel strongly about any of these, please call 
it out.


Sterling

On 3/3/16 5:38 PM, will sanfilippo wrote:

+1



On Mar 3, 2016, at 4:24 PM, marko kiiskila  wrote:

+1 for the rename. Sooner the better if we’re going to go ahead with this one.


On Mar 3, 2016, at 3:50 PM, Sterling Hughes  wrote:

:)

Hey all -

I wanted to get a few more opinions on this.  We're going to need to change 
some repositories around on the newt/newtmgr side (Chris/Todd, can you send a 
summary to the list?)

I'd like to get this all done at once.  I don't think we need a formal vote on this 
one, but just lazy consensus.  My suggestion is that Chris send a summary of the go 
changes, and we leave this open till Sunday. If anyone has objections before then, 
we can stop & vote.

Also, we have our last few features/changes coming in this week. So, we should 
uncharacteristically have a few days to poke around at the release prior to 
releasing B2.

Sterling


On 3/3/16 4:09 AM, Jim Jagielski wrote:

Maintaining the precedent also becomes more painful as
things move forward :)


On Mar 2, 2016, at 6:28 PM, Sterling Hughes  wrote:

Howdy,

Awhile ago we decided to be cute about naming things: eggs, eggshells, 
clutches, etc.  One holdover from this was larva: our main package repository, 
which includes the OS and most of the packages.

While its painful to rename the git repo: it's only going to get more painful 
as we move forward.  Do we think it makes sense to make it clearer, and rename 
this to apache-mynewt-os or apache-mynewt-main?

Sterling

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

[will sanfilippo]

+1. I dont really like author tags myself...

> On Mar 3, 2016, at 4:18 PM, Sterling Hughes  wrote:
> 
> 
> 
> On 3/3/16 4:02 PM, Justin Mclean wrote:
>> 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 via the commit 
>> history. Author tags in 3rd party code (i.e. code not developed at the ASF) 
>> should be left as it is.
>> 
> 
> +1 this was on my TODO for an email to send out.
> 
> For all standard packages, I think it should be Apache Mynewt as author, and 
> dev@ as the email address.  These fields are really more useful for 3rd party 
> packages that will be developed around the Apache Mynewt core.
> 
> Sterling

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

[Justin Mclean]

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 via the commit history. 
Author tags in 3rd party code (i.e. code not developed at the ASF) should be 
left as it is.

Thanks,
Justin

Re: renaming apache-mynewt-larva to apache-mynewt-os

[Sterling Hughes]

:)

Hey all -

I wanted to get a few more opinions on this.  We're going to need to 
change some repositories around on the newt/newtmgr side (Chris/Todd, 
can you send a summary to the list?)


I'd like to get this all done at once.  I don't think we need a formal 
vote on this one, but just lazy consensus.  My suggestion is that Chris 
send a summary of the go changes, and we leave this open till Sunday. 
If anyone has objections before then, we can stop & vote.


Also, we have our last few features/changes coming in this week. So, we 
should uncharacteristically have a few days to poke around at the 
release prior to releasing B2.


Sterling


On 3/3/16 4:09 AM, Jim Jagielski wrote:

Maintaining the precedent also becomes more painful as
things move forward :)


On Mar 2, 2016, at 6:28 PM, Sterling Hughes  wrote:

Howdy,

Awhile ago we decided to be cute about naming things: eggs, eggshells, 
clutches, etc.  One holdover from this was larva: our main package repository, 
which includes the OS and most of the packages.

While its painful to rename the git repo: it's only going to get more painful 
as we move forward.  Do we think it makes sense to make it clearer, and rename 
this to apache-mynewt-os or apache-mynewt-main?

Sterling

Re: Introduction and first contribution

[Sterling Hughes]

Welcome Neel!

On 3/3/16 12:19 PM, Neel Natu wrote:

Hi,

My name is Neel Natu and I recently started hacking on Apache Mynewt. I
have been lurking on the dev list, digesting the documentation, making
simple changes to the OS etc and its been a pleasant experience thus far.

My first contribution is adding wallclock time support to Mynewt:
https://github.com/apache/incubator-mynewt-larva/pull/8



Looks great, I see that you & Will are already discussing it.

Cheers,
Sterling

Re: the fs/nffs

[Sterling Hughes]

Hi Nges,

On 3/3/16 1:49 PM, Nges B wrote:

Hello,
I downloaded the the newt binary and placed it inside my lerva directory.
Now I have created my_app .
also ran the command
$ ./newt pkg search fs
and got the following output.

Installed package project/ffs2native@
Installed package fs/nffs@0.8.0
Installed package fs/fs@

I now  proceed to run the following command
 $ ./newt pkg install fs/nffs


In which directory did you run newt package install?  You would need to 
run it in the my_app directory in order to have it work.


When you do that, remember to make sure to add larva as a remote package 
list for the installation:


$ cd my_app
$ newt app add-pkg-list larva 
https://github.com/apache/incubator-mynewt-larva
Downloading pkg-list.yml from 
https://github.com/apache/incubator-mynewt-larva/master... ok!

Verifying pkg-list.yml format...
 ok!
Package list larva successfully installed to application.
$
$ newt pkg search fs
Package list larva has package project/ffs2native@0.0.0
Package list larva has package fs/nffs@0.8.0
Package list larva has package fs/fs@0.0.0

Then you can use newt package install.  You'll also want to install the 
fs/fs package, which provides an abstraction of filesystem access 
routines for nffs, which is a specific implementation of the file system.


Cheers,
Sterling

the fs/nffs

[Nges B]

Hello,
I downloaded the the newt binary and placed it inside my lerva directory.
Now I have created my_app .
also ran the command
$ ./newt pkg search fs
and got the following output.

Installed package project/ffs2native@
Installed package fs/nffs@0.8.0
Installed package fs/fs@

I now  proceed to run the following command
$ ./newt pkg install fs/nffs
 and instead of getting the installation of the fs/nffs I get and
error saying the packages were not found.
please where am I going wrong??

Introduction and first contribution

[Neel Natu]

Hi,

My name is Neel Natu and I recently started hacking on Apache Mynewt. I
have been lurking on the dev list, digesting the documentation, making
simple changes to the OS etc and its been a pleasant experience thus far.

My first contribution is adding wallclock time support to Mynewt:
https://github.com/apache/incubator-mynewt-larva/pull/8

Let me know if there are any concerns with the design or coding style and I
can iterate on it.

If not, then please commit :-)

best
Neel

Re: installing the Newt

[todd mitton]

I should have said that new users will be able to 'go get
mynewt.apache.org/newt/...' once Chris's changes have been merged onto
master.

On Thu, Mar 3, 2016 at 10:53 AM, todd mitton  wrote:

> Sorry.  I was waiting to switch to the vanity import domain until all the
> other rename changes were done.  I didn't realize we were ready.
>
> New users can now do this:
>
> go get mynewt.apache.org/newt/newt
> go get mynewt.apache.org/newt/newtmgr
> go get mynewt.apache.org/newt/newtvm
>
> The user won't need to manually clone the repo.  go get will clone it into
> $GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
> master branch. If the user wishes to be on develop, they can:
>
> cd $GOPATH/src/mynewt.apache.org/newt
> git checkout develop
>
> -Todd
>
> On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins 
> wrote:
>
>> I have committed the changes to the develop branch.  Now all go imports
>> use the vanity domain.
>>
>> Unfortunately, this is going cause a bit of pain for the current users
>> because the newt sources are now in the wrong directory.  To correct
>> this problem, you will need to move the old newt path to the new one:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   mv $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> If you plan on building older versions of newt, you should link the path
>> rather than move it:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   ln -s $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> Sorry for the hassle.  Yes, we definitely need to include convenience
>> binaries in the next release :).
>>
>> Chris
>>
>> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
>> > 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.
>> >
>> > Chris
>> >
>> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
>> > >
>> > > >
>> > > > When pointed at the apache server, on the other hand, "go get"
>> seems to
>> > > > require the ".git" suffix.  An I mentioned earlier, this results in
>> the
>> > > > creation of a directory that also has the ".git" suffix.
>> > > >
>> > > > The problem is: the behavior of "git clone" is in conflict with the
>> > > > behavior of "go get", at least with regards to the apache git
>> server.
>> > > > At one point the installation documentation was accurate, but it
>> seems
>> > > > we have since opted for git-friendliness rather than
>> > > > go-get-friendliness.
>> > > >
>> > > > We will need to find a simpler workaround.  In the meantime, we
>> should
>> > > > at least update the documentation.  Also, soon newt binaries will be
>> > > > available for download which help to alleviate problems with go.
>> > > >
>> > >
>> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
>> > > that would point to the proper Apache git repository?   I thought this
>> > > would solve that problem?
>> > >
>> > > Sterling
>>
>
>

Re: installing the Newt

[todd mitton]

Sorry.  I was waiting to switch to the vanity import domain until all the
other rename changes were done.  I didn't realize we were ready.

New users can now do this:

go get mynewt.apache.org/newt/newt
go get mynewt.apache.org/newt/newtmgr
go get mynewt.apache.org/newt/newtvm

The user won't need to manually clone the repo.  go get will clone it into
$GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
master branch. If the user wishes to be on develop, they can:

cd $GOPATH/src/mynewt.apache.org/newt
git checkout develop

-Todd

On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins 
wrote:

> I have committed the changes to the develop branch.  Now all go imports
> use the vanity domain.
>
> Unfortunately, this is going cause a bit of pain for the current users
> because the newt sources are now in the wrong directory.  To correct
> this problem, you will need to move the old newt path to the new one:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   mv $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
> "$GOPATH"/src/mynewt.apache.org/newt
>
> If you plan on building older versions of newt, you should link the path
> rather than move it:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   ln -s $GOPATH/src/
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
> mynewt.apache.org/newt
>
> Sorry for the hassle.  Yes, we definitely need to include convenience
> binaries in the next release :).
>
> Chris
>
> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
> > 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.
> >
> > Chris
> >
> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
> > >
> > > >
> > > > When pointed at the apache server, on the other hand, "go get" seems
> to
> > > > require the ".git" suffix.  An I mentioned earlier, this results in
> the
> > > > creation of a directory that also has the ".git" suffix.
> > > >
> > > > The problem is: the behavior of "git clone" is in conflict with the
> > > > behavior of "go get", at least with regards to the apache git server.
> > > > At one point the installation documentation was accurate, but it
> seems
> > > > we have since opted for git-friendliness rather than
> > > > go-get-friendliness.
> > > >
> > > > We will need to find a simpler workaround.  In the meantime, we
> should
> > > > at least update the documentation.  Also, soon newt binaries will be
> > > > available for download which help to alleviate problems with go.
> > > >
> > >
> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
> > > that would point to the proper Apache git repository?   I thought this
> > > would solve that problem?
> > >
> > > Sterling
>