Re: basically, I get an error when I do make

hello, i'm happy you resolved the issue and that you also helped me progress in my projects ! have a nice day. Justin Linotte Le 19-07-24 à 23:48, Alan C. Assis a écrit : PR submitted: https://github.com/apache/nuttx/pull/12736 Thank you Justin for finding this issue!!! You help

Re: basically, I get an error when I do make

-help mode   [C] Toggle show-name mode  [A] Toggle show-all mode [Q] Quit (prompts for save) [D] Save minimal config (advanced) Thanks you in advance, Justin Linotte Le 18-07-24 à 20:52, Alan C. Assis a écrit : Hi Linotte, Thanks for testing our tutorials, it is important to validate and find

basically, I get an error when I do make

hello, i hope my question doesn't bother you, i'm an amateur, not a pro with 40y of experience so it may be dumb for you. i'm also an amateur in english btw when i do make like advised here : https://nuttx.apache.org/docs/latest/quickstart/compiling_make.html#build-nuttx i get this : :~/pico

YOLO machine learning on nuttx and more

Hello, i do not master Nuttx deeply, but i want to create a system using Computer vision to naviguate I develop my system on a raspberry pi pico board with nuttx on it and i see in the docs that there is support for machine learning like YOLO (you only look once), but there is no more documentation

Re: Legal help to (Apache) NuttX RTOS: adding licenseed driver

project under the Apache license. Kind Regards, Justin > On 11 Dec 2023, at 1:54 am, Gregory Nutt wrote: > > On 12/10/2023 7:15 AM, Alan C. Assis wrote: >> I understand your point. And in fact I think the issue is not your >> contribution itself, but the future contributi

Bluetooth SIG and Bluetooth company Id

Hi, Something that may be of interest. I managed to get the ASF membership in the Bluetooth SIG and get a company id/manufacturer id (0x0B65) This also means anyone with an apache.org email address can sign up as a Bluetooth SIG user. [1] Kind Regards, Justin 1. https://apps.bluetooth.com

Re: mqtt library on NuttX?

de being talked about part of the original software grant? Thanks, Justin

Re: Raspberry Pi Pico a nice board for NuttX

e as they are unlikely to be under an open source license and NuttX would need to get permission to use them. May need to clarify on the legal discuss list. Thanks, Justin

Re: [VOTE] Apache NuttX 10.0.0 (incubating) RC0 release

Hi, > Did you intend to vote on the IPMC thread? I did I’ll move it there. Thanks, Justin

Re: [VOTE] Apache NuttX 10.0.0 (incubating) RC0 release

best to try and get the license terms changed. If that can’t be done I would do as suggested double check on legal discuss. Thanks, Justin

Re: Xiaomi Vela based on NuttX

Hi, Nice. Would be better if they called by it correct name - “Apache NuttX”. Thanks, Justin

Re: IP Clearance

part of the NuttX donation or is it BSD because it’s 3rd party code from somewhere else? Thanks, Justin 1. https://www.apache.org/legal/resolved.html#category-a 2. https://infra.apache.org/licensing-howto.html#permissive

Re: IP Clearance

official process, other than to ask the person/company to fill it it and sent it to the secretary. Thanks, Justin

Re: IP Clearance

icense as ALv2 or not? - How many other files do we hav from this author? > In the meantime, if I need to move code from a file to a new file (split > implementation) with BSD header, what header should appear on the new file? It should stay under the original BSD license. Thanks, Justin

Re: IP Clearance

Hi, For some context most project graduate at 1 1/2 t 2 years, but some take longer, it just depends on the project. The IP clearance is important and you would need to show progress on this before you could graduate. Thanks, Justin

Re: official nuttx-ci-linux image

HI, > This is a build environment we use for CI, it does not contain any NuttX > release code. Thanks for that perhaps make that clearer by adding a description? Thanks, Justin

Re: official nuttx-ci-linux image

Hi, This is a little bit of a concern.[1] "Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages” Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#publication

Changing headers

limitations under the License. Thanks, Justin

Re: About license headers

eaders we would need permission from the copyright owner who many not be the person who contributed the file. Thanks, Justin

Re: Markdown READMEs?

ay need to make sure that nothing with an incomparable license sneaks in. Thanks, Justin

Re: Markdown READMEs?

Hi, > asciidoctor requires ruby You can use it that way yes but it not required. One other ways of doing so including javascript for displaying markdown content on a website. Justin

Re: Markdown READMEs?

Hi, You might want to look at https://asciidoctor.org It an improved markdown with a few more features and multiple outputs. Thanks, Justin

Re: [RESULT] [VOTE] Release Apache NuttX (Incubating) 9.1.0 [RC2]

it’s board report time I think people are just busy with other things right now. I’ll take a look and vote when I can. Thanks, Justin

ApacheCon @Home 2020 call for papers closes in 2 days!

So far (with a couple of months to go) more than 900 people have signed up for the conference. Thanks, Justin

Re: Help with Apache Github Invite

HI, You need to wait until you have been added to the ASF gitHub account before doing the last step. The usual issue is not setting up 2FA. Thanks, Justin

Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release

HI, > I confirmed that the latest releases/9.1 branch fixes the problems. A vote need to be on a static code base / a release artefact not what is in a branch. It can’t change as the hashes and signatures would be different for starters. Thanks, Justin

Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release

at one point. I ‘m not sure how often it checks or if that is still the case. Thanks, Justin

Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release

” email address. Thanks, Justin

Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release

thread may just means there’s a few less RC’s and less conversation in the VOTE thread. Thanks, Justin

Re: mbedtls

committers have access. If this is just to avoid licensing issues then I suggest that is also not the best way to deal with that and let’s discuss what those issue are and see if there are other ways of resolving them. Thanks, Justin

Re: what to do with this?

Hi, > Is it really "All rights reserved.”? And looking through the rest of your code I can see it common practice. AFAIK it's not needed and has no legal standing. [1] Thanks, Justin 1. https://en.wikipedia.org/wiki/All_rights_reserved

Re: what to do with this?

Hi, Is it really "All rights reserved.”? Even with the MIT license below there may be some question raised about this. Thanks, Justin

Re: [NOMINATION] Self nominate to be a mentor of Apache NuttX

HI, > Welcome! Are there any formalities that we need to do (vote etc)? Only if you want them. I would say a lazy consensus applies i.e. if there no objections then just make it happen. Thanks, Justin

Re: Building on macOS [was: [VOTE] Release Apache NuttX (Incubating) 9.0.0 [RC1]]

-nconf.gui.o Thanks, Justin

Re: STM32H7 FDCAN driver

e all of these issues as they a) started at the ASF or b) have all committers sign ICLA or similar c) changed the license (and all contributors agreed on that) before coming to the ASF. Thanks, Justin

Re: STM32H7 FDCAN driver

d generalize in this case well. I > would think that the solution would be to bring the CAN file in with the > existing BSD header. But let's get confirmation on that. That is a good way to approach it (but not the only one). Thanks, Justin

Re: [ANNOUNCEMENT] Call for Validation of Apache NuttX 9.0.0 (incubating) RC0

sier to get IPMC votes on releases. This also make it easier for everyone else as well. Thanks, Justin

Re: [ANNOUNCEMENT] Call for Validation of Apache NuttX 9.0.0 (incubating) RC0

would help. Remember to get +1 votes a IPMC member will need to be able to compile it and some needed votes may need to come from people who are not familiar with your project. Thanks, Justin

Re: [ANNOUNCEMENT] Call for Validation of Apache NuttX 9.0.0 (incubating) RC0

Hi, > For the DISCLAIMER, does anyone have any ideas what should be included? Just list the thing that are not in line with ASF policy, missing ASF headers would be the main one. Thanks, Justin

Re: [ANNOUNCEMENT] Call for Validation of Apache NuttX 9.0.0 (incubating) RC0

. Some of the above also applies to for the app package as well. What a good board to try on OSX? I tried a few at random that are popular or that I know but couldn't get the config script to work. Thanks, Justin 1. ./boards/arm/sama5/sama5d3-xplained/boot/uImage

Re: What should we we do with SocketCAN

changes here might be too small for a SGA. Thanks, Justin

Re: What should we we do with SocketCAN

anges here and do we have ICLAs from them? Thanks, Justin 1. https://cwiki.apache.org/confluence/display/NUTTX/License+Clearing 2. https://github.com/apache/dubbo/wiki/CLA-signing-status

Re: What should we we do with SocketCAN

speaking only of the legal rights as state in the license of the file. ASF policy goes beyond (for good reasons) what is just legally possible. Thanks, Justin

Re: What should we we do with SocketCAN

e nothing is needed. A CCLA would be a show of good faith or something else official from them to say there are no issues with using their code. Thanks, Justin

Re: What should we we do with SocketCAN

cense may say) IMO if that is the case we should remove the code. Thanks, Justin

Re: What should we we do with SocketCAN

cts. Mynewt made a lot of effort to get permission to use code and in some cases change licensing with 3rd parties. Thanks, Justin

Re: What should we we do with SocketCAN

Hi, > Given that we have been trying unsuccessfully to get an SGA from NXP This I think in the issue why are they not willing to do this? Thanks, Justin

Re: Start of the NuttX 9.0 release cycle

Hi, > The tarballs should be uploaded to [1] and/or [2] right? Correct. I’ve created them for you. Thanks, Justin

Re: The new Apache NuttX Logo

HI, https://apache.org/logos/ prefers svg, eps, ai or pdf. If you submit something else they will likely vectorise it for you and make them the right size. Central services can also help if it needed. Thanks, Justin

Re: The new Apache NuttX Logo

Hi, It would be easy to put the image on your wiki / confluence. Justin

Re: Approvals for Critical Changes

this to make it clear who owns the code. # Global owners * @apache/nuttx-committers Thanks, Justin

Re: Podling Nuttx Report Reminder - April 2020

Hi, I would suggest you report this month otherwise you’ll be asked to report again next month. Thanks, Justin

Re: The Release

Hi, I would make a check list like so [1], this one assumes you are using the ordinary disclaimer. I’ve reviewed hundreds and hundreds of releases so can help out. I also know what the IPMC looks out for and I’m currently the VP of the Incubator. Thanks, Justin 1. https://cwiki.apache.org

Re: Apache 2.0 License headers in source files

Hi, > For the Sony contributions I will change the license in all contributed > files as soon as I get clearance from our department They would need to submit a SGA to the ASF for this to happen. Thanks, Justin

Re: Apache 2.0 License headers in source files

, Justin 1. https://www.chicagotribune.com/news/ct-xpm-2002-08-05-0208050013-story.html

Re: Podling Nuttx Report Reminder - April 2020

wn this track it is on I will have no choice but to resign as a mentor. Thanks, Justin

Re: Podling Nuttx Report Reminder - April 2020

ght be good for it to report again this month. Thanks, Justin

Re: Question of PR Etiquette

ng not work on the code. All contribution are generally valuable even if they need some minor tweaks and you want to encourage people to contribute. Apache often says "community over code”. Thanks, Justin

Re: Question of PR Etiquette

al case, > for example the owner don't response PR for a long time. If they don’t respond it mean you have driven them away, and that teh best time to ask yourself what could you have done differently to keep them involved? Thanks, Justin

Re: committers-only files under sched/

(In some cases your employment contract may prohibit you from doing this.) For small contributions an ICLA is all we need. An SGA is used to donate an sizeable amount of existing code Thanks, Justin 1. https://www.apache.org/licenses/contributor-agreements.html

Re: Should we relax precheck a little bit?

Hi, Sorry late here - what I should have said is “may NOT 100% agree with it.”. Justin

Re: Should we relax precheck a little bit?

100% agree with it. People may not agree, but collectively everyone thinks this is the best way forward. Getting consensus can sometimes be difficult and involve a lot of discussion. Thanks, Justin

Re: Should we relax precheck a little bit?

nsus and when called teh outcome is already known. I would not suggest having a vote on this in such a short time frame. Thanks, Justin

Re: Should we relax precheck a little bit?

over code. Thanks, Justin

Re: Should we relax precheck a little bit?

ild is better than the last one. We would prefer that project make frequent releases, gradually improving things, and not put off a release trying to make it perfect. One path leads to community growth, the other to community decline, I’ll let you guess which is which. Thanks, Justin [*] The p

Re: Apache 2.0 License headers in source files

Hi. I wold also read [1][2]. I have also given talks at ApacheCon on this, see [3][4] for examples. Both [3] and I think [4] predate the work in progress disclaimer, which makes it easier for you. Thanks, Justin 1. https://www.apache.org/legal/resolved.html 2. http://www.apache.org/dev

Re: Apache 2.0 License headers in source files

construct a rat exclusion file to filter out any 3rd party code or other known issues. Having a documented rat exclusion file would help teh incubator review your releases. Once that is done it will pick up any new issues quite easily. It can also be used to replace licenses headers. Thanks, J

Re: Apache 2.0 License headers in source files

r release checks. Thanks, Justin 1. https://creadur.apache.org/rat/

Re: Apache 2.0 License headers in source files

. Thanks, Justin 1. https://lists.apache.org/list.html?dev@nuttx.apache.org

Re: Apache 2.0 License headers in source files

will be harder to detect downtime track, these changes shouldn’t have been merged. Why is this project ignore good advice from it's mentors? Thanks, Justin

Re: Apache 2.0 License headers in source files

as well. > I think we should get an SGA from Xiaomi and Sony ASAP. A software grant is not required but it may make the licensing situation a little easier, but there’s about 150+(?) different copyright holders so that still need to be dealt with. Thanks, Justin

Re: Apache 2.0 License headers in source files

do not comply with existing ASF policy and their original header will need to be added back. I would suggest you don’t do a bulk replacements and they will cause many issues. Please read [1] Thanks, Justin 1. https://www.apache.org/legal/src-headers.html#3party

Re: Podling Nuttx Report Reminder - March 2020

Hi, Looking at the report this question needed to be answered, you need to include a date. "### When were the last committers or PPMC members elected?" Thanks, Justin

Re: Podling Nuttx Report Reminder - March 2020

Hi, > It's due by end of the day, right? It best if it submitted before it due so if there are any issues they can be corrected. Thanks, Justin

Re: Podling Nuttx Report Reminder - March 2020

Hi, This is due today is the PPMC working on it? Thanks, Justin

Re: Progress on making a release

should be aware of. These issues are things that are not in line with ASF release or license policy. > I moved both "FAT long file names" and tools/ under NOTICE. Or do you > think we should remove the "tools" note all together? If it not in the release it doesn’t need to be mentioned. Thanks, Justin

Re: nightly build failures

pam folders. Who is the email sent from, we can add that sender to the subscribers list. Thanks, Justin

Re: Progress on making a release

ase we are making so I’m not sure the “tools” section will apply. The note about "drivers/video/ov2640” is concerning as this may mean that’s under a GPL license and not compatible. Thanks, Justin

Re: Progress on making a release

)PMC member votes are counted. The release candidate has to be signed. This is usually done by the release manager, but others can sign it if they want. Thanks, Justin

Progress on making a release

Hi, Where is the project at in moving forward to make it’s next release? Thanks, Justin

nightly build failures

liugu...@gmail.com, wouldn’t it be better to send email to the list? Thanks, Justin 1. https://builds.apache.org/job/NuttX-Nightly-Build/

Re: Podling Nuttx Report Reminder - February 2020

Hi, > I personally deliberately avoided number of commits/PRs in the report > as I saw Justin giving the same remark in his review to other reports > that did that, and I believe he has a good argument. I’s not just my point, the board frequently gives the same feedback on reports

Re: Podling Nuttx Report Reminder - February 2020

HI, > Instead of giving absolute numbers, why not say there was an increase of x% > in the number of PRs applied, etc Which is slightly better but without context or explanation to why this happened it’s mostly meaningless for people outside the project. Thanks, Justin

Re: Podling Nuttx Report Reminder - February 2020

e non-technical details but it will help to keep a track on the > health of the community. On their own they are meaningless, you need to explain why they are significant if you put them in a report. Remember people who read this report are not involved in your project. Thanks, Justin

Re: Podling Nuttx Report Reminder - February 2020

sign off reports. Thanks, Justin

Re: Podling Nuttx Report Reminder - February 2020

Hi, Don't forget the report is due today. Thanks, Justin

Re: [GitHub] [incubator-nuttx-testing] davids5 commented on issue #2: Multibranch pipeline job example

[2] Thanks,. Justin 1. https://lists.apache.org/search.html 2. https://lists.apache.org/thread.html/r5b37643fce90c6560308958ac48ea4387b8ee8ae7dbeb265ad1f8527%40%3Cbuilds.apache.org%3E

Re: [incubator-nuttx] 02/02: sched/sched/sched_getcpu.c: Add file needed by previous commit.

we use the 78 character line >> width? I used Apache Rat to check this and it doesn’t complain, it still clear how the file is licensed, so both should be fine. Thanks, Justin

Re: [incubator-nuttx] 02/02: sched/sched/sched_getcpu.c: Add file needed by previous commit.

gt; width? Same here, doing so may stuff up some license checkers. Thanks, Justin

Re: [incubator-nuttx] 07/10: sendto should always call send if to == NULL || tolen <= 0

Hi, Wrong header here as well - please fix. Thanks, Justin

Re: [incubator-nuttx] branch master updated: sched/sched/sched_getcpu.c: Implement non-standard interface.

Hi,\ Same issue with the headers here. Thanks, Justin

Re: [incubator-nuttx] 02/02: sched/sched/sched_getcpu.c: Add file needed by previous commit.

Hi, Any new files developed at the ASF should have ASF headers [1] you also note it down;t have a copyright line. Thanks, Justin 1. https://www.apache.org/legal/src-headers.html#headers

Re: Podling Nuttx Report Reminder - February 2020

oked into. But just about all podlings have that issue at this stage. Thanks, Justin 1. https://whimsy.apache.org/board/minutes/Incubator.html

Re: Podling Nuttx Report Reminder - February 2020

Hi, it a good idea to start working on the report early so people can give feedback on it, a week before it is due is the suggestion. Who on the PPMC would like to try getting a draft together first? Thanks, Justin

Re: NuttX at FOSDEM 2020

Hi, > Being the large opensource conference that it is, I was curious if anyone > in this project or Apache was planning on attending. There's lots of Apache people going, pop by their booth and say hi. I will not be there. Thanks, Justin

Re: Jenkins CI

Hi, > Thanks, good to know. I am asking my employer about including me in a > corporate one (CCLA [1]), but if it is too much paperwork I guess I can > just submit the ICLA. You would need to submit an ICLA. The CCLA is for more for your employer benefit not ours. Thanks, Justin

Re: License Analysis with Fossology

ations don’t reach me/are filtered out. Thanks, Justin

Re: License Analysis with Fossology

HI, So how are we with this, are we any closer to start considering making a release? Thanks, Justin

Re: Jenkins CI

n account. Thanks, Justin

Re: Jenkins CI

n access but they need to be in LDAP. [1] that means you need to be a committer or PPMC member. Thanks, Justin 1. https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount?

  1   2   3   >