Re: [CALL for TOP Down workflow Requirements]

On Fri, Dec 20, 2019, 11:22 PM David Sidrane wrote: > All, > > Please help flesh this out. > > Proposed Workflow Requirements (REQ) and Derived Requirements (DREQ) > > REQ1) master is branches of apps and nuttx have to always build > REQ1.1) ALL development work is done on branches. >

RE: Apache NuttX website

+1 -Original Message- From: Brennan Ashton [mailto:bash...@brennanashton.com] Sent: Friday, December 20, 2019 8:54 PM To: dev@nuttx.apache.org Subject: Re: Apache NuttX website Could we create the repo for the website. http://www.apache.org/dev/project-site.html The one I created is

[CALL for TOP Down workflow Requirements]

All, Please help flesh this out. Proposed Workflow Requirements (REQ) and Derived Requirements (DREQ) REQ1) master is branches of apps and nuttx have to always build REQ1.1) ALL development work is done on branches. DREQ1.1.1) master is branch protected prevention pushes to it. REQ2)

RE: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

+1 -Original Message- From: Brennan Ashton [mailto:bash...@brennanashton.com] Sent: Friday, December 20, 2019 8:47 PM To: dev@nuttx.apache.org Subject: Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers) On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) wrote:

RE: Away for two weeks

Enjoy! -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Friday, December 20, 2019 5:07 PM To: dev@nuttx.apache.org Subject: Away for two weeks H, I’m off on a two week break, while I’ll have some time to answer questions, where I'm going for the first week

Re: Test Repository

Hi Justin, Great points. See below On 2019/12/21 00:42:58, Justin Mclean wrote: > Hi, > > You may need to think how this fits into releases. some things to consider: > - Do you want the release to contain test information or not? A lot of Apache > project do include that but some don’t - it

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

For me I do not think a jenkins job will stop others to try other solutions, like buildbot or travis CI or other CI tools. We can both provide our solutions, at least a POC, and then start to argue which one is better. And maybe both ways are fine, or we can find a way to them all in one. For

RE: Test Repository

Greg, -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Friday, December 20, 2019 4:32 PM To: dev@nuttx.apache.org Subject: Re: Test Repository > Looking at https://gitbox.apache.org/repos/, I see several projects, > perhaps most projects, that have a special

RE: Test Repository

+1 -Original Message- From: Gregory Nutt [mailto:spudan...@gmail.com] Sent: Friday, December 20, 2019 4:29 PM To: dev@nuttx.apache.org Subject: Test Repository Looking at https://gitbox.apache.org/repos/, I see several projects, perhaps most projects, that have a special repository just

Re: Apache NuttX website

Could we create the repo for the website. http://www.apache.org/dev/project-site.html The one I created is based off the Jekyll template as discussed here. https://incubator.apache.org/guides/sites.html#publishing_your_website

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

Same answer.  We need to clearly define how the workflow should behave first.  Then we will have a set of requirements that we can use to make trade-offs against the design options. With no requirements in hand, it is just people supporting their favorite tools or implementations they are

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

Thanks for your offer.  We really need to agree to an end-to-end workflow before we invest very much into implementation.  The implementation should not drive the workflow; the workflow requirements should drive the implementation. Unfortunately, the topic is now so poisoned that people don't

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

On Fri, Dec 20, 2019, 8:31 PM 张铎(Duo Zhang) wrote: > And I could help setting up the jenkins jobs on the asf infrastructure > against github PRs to test them automatically. The website is > https://builds.apache.org/ . Plan to work with Haitao together next week > on > this. > Could we please

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

And I could help setting up the jenkins jobs on the asf infrastructure against github PRs to test them automatically. The website is https://builds.apache.org/ . Plan to work with Haitao together next week on this. I saw the very long thread about workflow and seems David was on fire so due to my

Re: New Apache NuttX Repositories

Greg, On a tangental note, what will become of our remaining repos: buildroot I’m preparing a PR to upgrade binutils and gcc! Can you still accept updates on Bitbucket? tools nxwidgets Regards, -david > On Dec 20, 2019, at 2:24 PM, Gregory Nutt wrote: > > [Cross posting to both the

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

The sync is bidirection. See this page: https://gitbox.apache.org/setup/ On https://id.apache.org/ , fill your github username and then there will be an invitation sent to you on github to let you join the apache organization on github. And once the MFA status on

Re: Test Repository

You may need to think how this fits into releases. some things to consider: - Do you want the release to contain test information or not? A lot of Apache project do include that but some don’t - it may be size dependant. - Do you wan users to be able to easy test releases? (Not providing test

Re: Away for two weeks

Hi, > ?? Apache has backup right? I thought ruling out one person failure was the > reason for bringing it to Apache ?? Or am I mistaking here? The PMC and ASF > can chip in ? Maybe I am getting it wrong. There are several other mentors (3) who can help, so there's need for concern, (

Re: Away for two weeks

?? Apache has backup right? I thought ruling out one person failure was the reason for bringing it to Apache ?? Or am I mistaking here? The PMC and ASF can chip in ? Maybe I am getting it wrong. Have a good holiday then Justin! Verstuurd vanaf mijn iPhone > Op 21 dec. 2019 om 02:07

Away for two weeks

H, I’m off on a two week break, while I’ll have some time to answer questions, where I'm going for the first week has limited internet access, no mobile phone reception and no mains electricity. I may be able to check messages once a day so I may be slow in responding to any questions that

Re: Test Repository

Hi, You may need to think how this fits into releases. some things to consider: - Do you want the release to contain test information or not? A lot of Apache project do include that but some don’t - it may be size dependant. - Do you wan users to be able to easy test releases? (Not providing

Re: Transferring Repositories

Hi, > Well that answers a question that was asked earlier: Which repository is a > mirror of the other? Either gitbox.apache.org is a mirror of > github.com/apache or two two URLs are linked to the same repository in some > fashion. The gitbox is the primary repo and any change to it are

Re: [nuttx] New Apache NuttX Repositories

HI, > And also here (but not for contributions): > > https://gitbox.apache.org/repos/asf?p=incubator-nuttx.git > > https://gitbox.apache.org/repos/asf?p=incubator-nuttx-apps.git >

Re: Test Repository

Looking at https://gitbox.apache.org/repos/, I see several projects, perhaps most projects, that have a special repository just to contain testing logic.  Often this is named -testing and often is has other names (like integration and others). So there is a precedence for a nuttx-testing

Re: Transferring Repositories

Hi Greg, On 12/20/19, Gregory Nutt wrote: > hould decide. >> >> The Apache repository started out 3 commits behind the Bitbucket >> repository: >> >> commit 54d6a0768ccd0e386b67723cc1a24e9e9fff902a >> Author: Daniel Pereira Volpato >> Date: Fri Dec 20 13:07:31 2019 -0600 >> >>

Re: Testing the new repository

This looks progress!! Good job!! Verstuurd vanaf mijn iPhone > Op 20 dec. 2019 om 23:10 heeft Alan Carvalho de Assis het > volgende geschreven: > > On 12/20/19, Gregory Nutt wrote: >> >>> We you can see the new repository is working fine. >>> >>> I submitted the i2C driver for

Re: Transferring Repositories

Hi, They should be in sync now. Those were probably created just after the transfer. On Fri, Dec 20, 2019 at 9:28 PM Gregory Nutt wrote: > > >> I don't know if there are any problems with doing this with tags, but > >> we cannot do this which commits without eventually really mucking up > >>

Re: Testing the new repository

On 12/20/19, Gregory Nutt wrote: > >> We you can see the new repository is working fine. >> >> I submitted the i2C driver for STM32G070/NUCLEO-G070RB that was added >> to bitbucket. >> >> As a rules of thumb, please don't commit directly to the "master". >> >> I created a brash called "stage"

Re: Testing the new repository

We you can see the new repository is working fine. I submitted the i2C driver for STM32G070/NUCLEO-G070RB that was added to bitbucket. Tomorrow I will do a get fetch from apache and force bitbucket to exactly match the apache repository (after verifying that the recent histories are the

Re: Testing the new repository

We you can see the new repository is working fine. I submitted the i2C driver for STM32G070/NUCLEO-G070RB that was added to bitbucket. As a rules of thumb, please don't commit directly to the "master". I created a brash called "stage" that we could use before merging in to "master", this

Testing the new repository

Hi Guys, We you can see the new repository is working fine. I submitted the i2C driver for STM32G070/NUCLEO-G070RB that was added to bitbucket. As a rules of thumb, please don't commit directly to the "master". I created a brash called "stage" that we could use before merging in to "master",

Re: Transferring Repositories

I don't know if there are any problems with doing this with tags, but we cannot do this which commits without eventually really mucking up the history. Commits must go in on direction.  For the time being, I think it must work like this: * There must be no changes directly to the apache

Are you failure with the HAM Story?

All, This is one of my favorite Lessons that I learned... reposted from Private Are you failure with the HAM Story? A husband and his wife were in their kitchen. The husband was sitting at the kitchen table reading the newspaper while his wife was preparing a ham for dinner. The husband watched

Re: Transferring Repositoies (Was Re: Masayuki Ishikawa added to NuttX committers)

[This conversation belongs on the dev list] Which way is the mirrors? I believe I read somewhere, it's apache --> github. But I could be wrong. I recall Duo saying that you can set this up either way.

Re: Images did not make it - I bet it is in [need auth]

Great! Thanks! On 12/20/19, Nathan Hartman wrote: > On Fri, Dec 20, 2019 at 1:12 PM Alan Carvalho de Assis > wrote: >> >> Hi David, >> >> Strange, let's to test sending a PNG image. >> >> It work? >> >> BR, >> >> Alan >> >> On 12/20/19, David Sidrane wrote: >> > Hi Alan, >> > >> > I Sent with

Re: Attachment test Photo

Lookin in the site archive, his PNG was just a white square. On 12/20/19, Nathan Hartman wrote: > On Fri, Dec 20, 2019 at 1:32 PM Gregory Nutt wrote: >> > How about this >> > >> Looks fine > > Was there a picture attachment? Hmm, I don't see it for some reason. >

Re: Images did not make it - I bet it is in [need auth]

On Fri, Dec 20, 2019 at 1:12 PM Alan Carvalho de Assis wrote: > > Hi David, > > Strange, let's to test sending a PNG image. > > It work? > > BR, > > Alan > > On 12/20/19, David Sidrane wrote: > > Hi Alan, > > > > I Sent with an image. I do not see the post here.It must be stuck in the > >

Re: Attachment test Photo

On Fri, Dec 20, 2019 at 1:32 PM Gregory Nutt wrote: > > How about this > > > Looks fine Was there a picture attachment? Hmm, I don't see it for some reason.

Re: [PATCH] This is a test! Please DON'T commit!

On Fri, Dec 20, 2019 at 1:41 PM David Sidrane wrote: > > https://lists.apache.org/list.html?dev@nuttx.apache.org > > LOL - the list does list nor archive attachments. Attachments sent to the mailing list are archived. See Alan's above message with test attachment here:

Re: [PATCH] This is a test! Please DON'T commit!

https://lists.apache.org/list.html?dev@nuttx.apache.org LOL - the list does list nor archive attachments. On 2019/12/20 17:56:42, Alan Carvalho de Assis wrote: > Testing attachments. > > Greg, please confirm you can receive attachments. > > BR, > > Alan >

Re: Attachment test Photo

How about this Looks fine

Re: Images did not make it - I bet it is in [need auth]

Hi David, Strange, let's to test sending a PNG image. It work? BR, Alan On 12/20/19, David Sidrane wrote: > Hi Alan, > > I Sent with an image. I do not see the post here.It must be stuck in the > approval queue. We need to to request access to the moderation page. > > David >

Attachment test Photo

Got it! How about this. Never got your GitHub invitation? Visit github.com/apache to see if you have an invitation pending. Apache Account:Authed Welcome back, David! *Not David? Log out then!* GitHub Account:Authed You are currently

[PATCH] This is a test! Please DON'T commit!

Testing attachments. Greg, please confirm you can receive attachments. BR, Alan From 05eadfbfb75074c97390d6625c1c226f356b4ae4 Mon Sep 17 00:00:00 2001 From: Alan Carvalho de Assis Date: Fri, 20 Dec 2019 14:54:46 -0300 Subject: [PATCH] This is a test! Please DON'T commit! --- testing.txt | 1

Re: [DISCUSS - NuttX Workflow]

Buildbot is written in python and the configuration is very flexible, you can do whatever you want, even make a coffee after a git event, the server keep the configurations and can both poll or react to events from the git server. In my configuration there is an AWS buildbot server with a build

RE: [DISCUSS - NuttX Workflow]

I am not familiar with buildbot ore this sort of setup so please forgive for some simple minded questions. Is this SW CI or HW CI or both? How does the RPi/BBB/Laptop fit into the picture. Any Pictures? David -Original Message- From: Fabio Balzano [mailto:fa...@elfarolab.com] Sent:

Making a robot controller from scratch

Interesting NuttX presentation coming up: Making a robot controller from scratch With NuttX, IoT.js, WebThing and more https://fosdem.org/2020/schedule/event/iotnuttx/ Alan found that and posted this in the LinkedIn group.  Worth re-posting here. Greg

Re: [DISCUSS - NuttX Workflow]

2 hours is a configured parameter, it is to allow burst of commits, it can reduced to 0 if you need real time building, then the buildbot server can also provision remote testing of the builds. > On 20 Dec 2019, at 13:09, David Sidrane wrote: > > Hi Fabio, > > What are the capabilities? > >

Re: [DISCUSS - NuttX Workflow]

you can connect as many boards you want via USB, it all depends by the processing power and required deadline time, personally I use an old laptop so I can provision and automate a fresh build of Nuttx at every new git commit for 15 boards in 2 hours. > On 20 Dec 2019, at 13:09, David Sidrane

Re: [DISCUSS - NuttX Workflow]

You may want to consider separate levels of scrutiny for MCU's than boards. Acknowledged. The issue with boards and MCUs is that the pool of contributors for these areas is much thinner than the pool of contributors for some of the more heavily exercised areas. Depends on the popularity of

RE: [DISCUSS - NuttX Workflow]

Hi Fabio, What are the capabilities? It this 1 RPi/BBB per board nuttx board? David -Original Message- From: Fabio Balzano [mailto:fa...@elfarolab.com] Sent: Friday, December 20, 2019 5:06 AM To: dev@nuttx.apache.org Subject: Re: [DISCUSS - NuttX Workflow] Hello, yes the buildbot

Re: [DISCUSS - NuttX Workflow]

Hello, yes the buildbot server is down, later today I will bring it up. Yes you can do remote builds using a RPI/BBB or similars or local builds performed by the server itself. I can setup and maintain the server for the Nuttx project in case you think it is useful. Thank you so much Fabio

Re: [DISCUSS - NuttX Workflow]

Hi David, Sorry for scolding you in public as well, but I think we don't need to find guilt. So, I got the impression you were doing it to promote PX4 test workflow as the best solution for all the NuttX issues. And although 300K drones are a lot, there are many commercial products using NuttX.

Re: [DISCUSS - NuttX Workflow]

Hi Alan, Sorry if my intent was misunderstood. I am merely stating facts on were we are and how got there.I am not assigning blame. I am not forcing anything I am giving some examples of how we can make it the project complete and better. We can use all of it, some of it none of it. The is a

Re: [DISCUSS - NuttX Workflow]

I think we can learn the good practice from PX4, but shouldn't take all without any justification. PX4 has the mature workflow, maybe we can extract the core OS part as our base to boost the initial setup. The important thing now is to define the high level workflow and vote in the community. Then

Re: [DISCUSS - NuttX Workflow]

Hi David, On 12/20/19, David Sidrane wrote: > Hi Nathan, > > On 2019/12/20 02:51:56, Nathan Hartman wrote: >> On Thu, Dec 19, 2019 at 6:24 PM Gregory Nutt wrote: >> > >> ] A bad build system change can cause serious problems for a lot of >> people around the world. A bad change in the core OS

Re: [DISCUSS - NuttX Workflow]

Hi Nathan, On 2019/12/20 02:51:56, Nathan Hartman wrote: > On Thu, Dec 19, 2019 at 6:24 PM Gregory Nutt wrote: > > >> ] A bad build system change can cause serious problems for a lot of > people around the world. A bad change in the core OS can destroy the good > reputation of the OS. > > >

Re: [DISCUSS - NuttX Workflow]

Hi Nathan, You Rock! On 2019/12/20 05:31:37, Nathan Hartman wrote: > On Thu, Dec 19, 2019 at 4:40 PM David Sidrane wrote: > > > Changes to code in MCU architectural support, board support, or features > > > in the periphery of the OS should be at the discretion of the > > > committer.

Re: Apache NuttX website

Hi, A totally different can be found here. [1] Thanks, Justin 1. https://plc4x.apache.org/developers/website.html

Re: Apache NuttX website

On Fri, Dec 20, 2019, 1:13 AM Justin Mclean wrote: > Hi, > > This may also help [1]. Jekyll is supported as well, there’s a good > example here [2] and many other projects use Jekyll. > Yes I used the Apache Jekyll template for incubating projects to create a NuttX one I posted.

Re: Apache NuttX website

Hi, This may also help [1]. Jekyll is supported as well, there’s a good example here [2] and many other projects use Jekyll. Thanks, Justin 1. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405038 2. https://github.com/apache/beam/tree/beam-site/website

Re: [nuttx] Wiki Backup

Hi, > In the past nuttx.org was just the wiki, but I see that there is a standard > template that we are recommended to start > from. I have used Jekyll in the past, so happy to get something for > comment. I am not a commiter or sure what our > git repo is for the website (seemed like it could

Apache NuttX website

Took a stab tonight at putting a minimal site together from the template Apache provides. We do not seem to have the website repos yet, so for now here is what I have. Note that I opened a couple issues on it that need to be resolved before it could go live.