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/regi

Re: mqtt library on NuttX?

Hi, > Espressif has already signed an SGA, licensing shouldn't be an issue. I know this is a very late reply, and sorry for that. I just want to clear something up in general a software grant is for a single bit of software, it doesn’t cover all software from that company. Was this code being

Re: Raspberry Pi Pico a nice board for NuttX

Hi, > Copyright © 2020 Raspberry Pi (Trading) Ltd. The documentation of the RP2040 > microcontroller is licensed under a Creative Commons > Attribution-NoDerivatives 4.0 International (CC BY-ND). Portions Copyright © > 2019 Synopsys, Inc. All rights reserved. Used with permission. Synopsys & >

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

Hi, +1 (binding) but a lot more needs to be done on the LICENSE and headers I checked: - incubating in name - DISCLAIMER exists - a good start have been made on LICENSE - NOTICE looks fine - No unexpected binary files - More work needs to be done on adding ASF headers I not sure that using key w

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

HI, > "something like this" you mean because of the license or because of the small > number of files? Because of the license and it’s a small amount of code, it's regarded at Category A [1]. However do take care not to fork existing projects if possible. > If the latter, my question is always

Re: IP Clearance

Hi, > Well, I suppose any new contribution should always be in ALv2, so yes. If you want it to be ALv2 then it is best to: a) Ask the author to relicense it to ALv2 b) Ask them to sign an ICLA (assuming they are the copyright owner not their employer. In most cases it will be their employer.) c)

Re: IP Clearance

Hi, > I was about to edit a file and saw it was BSD licensed with Copyright to > company and author which does not to appear to be an active commiter. What is > the procedure to start asking for ICLAs/SGAs? Should I just email the author? Depends on a few things: - Do you want to relicense as A

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

Hi, I noticed a couple of times recently 3rd party headers have been changed. Please stop doing this. No one on the project can change the headers on a file without the correct process being followed. Doing so will just make IP province harder and graduating the project much more difficult. In

Re: About license headers

Hi, > I will convert all files contributed from Xiaomi(Pinecone) in the next > release. Masayuki, does Sony have any plan? Developers who already sign ICLA > can start the conversion now. Just because people have signed ICLA doesn’t mean you can change the headers. To change the headers we wou

Re: Markdown READMEs?

Hi, > I also love having the docs in the repository and releases, and versioned > along with the code. It makes things so much easier. That's a great idea, but it may have some impact on teh LICENSE file depending on what libraries, fonts etc are bundled with the documentation. You may need to

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]

Hi, > It appears under the same [RESULT][VOTE] thread in my email too, but > they are two different threads. Maybe gmail is trying to be smart? It's a gmail issue it groups all email by subject lines ignoring things inside “[]”. It’s extremely annoying. Given ApacheCon@home and it’s board repo

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

Hi, Only a couple of days to go before to call for papers closes for ApacheCon @Home 2020 on Monday. The Incubator will be running a track at this online conference, so if you're thinking of submitting something, please don't delay. We'll accept talks on the Apache incubator itself, and talks

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

Hi, > This key is not expired and has been signed by my apache.org email address as > well Thanks for that I must of had an old cached key. Setting your expiry dates to the near future may not be a good idea as I seem to recall releases with expired key were removed from the mirrors at one poi

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

Hi, I’ve not done a full check (which I will do) but I would be -1 on this release as it looks like it’s been signed with an expired key: gpg: Good signature from "Brennan Ashton " [expired] gpg: Note: This key has expired! It's also a good idea to sign with an “@apache.org” email address. Tha

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

Hi, > Does this mean that if you do not validate anything, you lose your right as a > PPMC member to vote? No, merit once gained isn’t lost, but it could be a little embarrassing if a critical issue is found after the release has been made. In that case another release is needed to correct it,

Re: mbedtls

Hi, I’m concerned that you are discussion doing work outside of the Apache repositories. Why is the main issue here? Greg mentions that the apache report are not properly controlled and verified but I’m not 100% sure what he means by that. The PMC has control of them and only verified committe

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]]

Hi, Something may be different with my setup or perhaps I’m missing something as I’m getting a number of linker errors. Undefined symbols for architecture x86_64: "_current_item", referenced from: _conf in frontends_nconf_kconfig_nconf-nconf.o _do_match in frontends_nconf_kconfig_n

Re: STM32H7 FDCAN driver

HI, It’s not that every file that gets submitted needs to have an Apache license. It's only files developed at the ASF by people who have signed ICLAs. If it done by people who have not signed ICLA and it’s a new file, it should also have a ASF headers, but whoever accepts that PR is ensuring t

Re: STM32H7 FDCAN driver

HI, > We did do something similar when we created the arch/arm/src/armv8-m port. > It started as a clone of the armv8-m port. We changed all of the headers > with only my copyright to Apache 2.0. And all questionable headers we copied > over with no change. So I suppose we could generalize

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

Hi, > This is linked in the Documentation under "Getting Started" here: > https://cwiki.apache.org/confluence/display/NUTTX/Documentation Is there anything for OSX? It is mentioned as a supported platform. You may have to do some more work on make the compilation process easier to get IPMC vo

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

Hi, > Did you put untar the 'nuttx' and 'apps' tarballs to get a directory > structure like this: > > some_directory/ > |-nuttx > |-apps Yes I did. > Could you share the error message(s), if there were any? ./tools/configure.sh -m -a ../apps teensy-2.0:hello make sh: avr-nuttx-elf-gcc: command

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

Hi, I checked: - incubating in artefact names - signatures and hashes fine - LICENSE and NOTICE are OK - Found an unexpected comped fine in the source release [1] - ASF files don’t have correct headers - Had some issues compiling From the ASF side there some minor things, most of them are likely

Re: What should we we do with SocketCAN

Hi , comparing the changes between the branches and looking at the authors I only see 3: Gregory Nutt Jari van Ewijk Peter van der Perk One solution would be to get Jari and Peter to sign ICLA (I see none on file) and get a CCLA or SGA from VW (who I assume they work for). The amount of change

Re: What should we we do with SocketCAN

Hi, Here would would be the ideal from an ASF point of view: 1. All large pieces of 3rd party code is donated to the ASF via SGAs 2. If not, anyone who worked on large contributors have a signed ICLA. 3. Remove the 3rd party code if it has an active community elsewhere and can be used as an exter

Re: What should we we do with SocketCAN

HI, > Is that the official Apache position? Yes ASF policy is in line with that. If it “offical” is a matter of interpretation but as VP Incubator and an ASF board member I would consider it so. > It this discussion, I think it depends on which rights you are referring to. > I am speaking on

Re: What should we we do with SocketCAN

Hi, > I know that both VW and NXP is okay with incoporating into NuttX. In fact, > they are enthusiastic about it. What kind of documentation would we need > just to get permission without changing the licensing? An interesting question. Legally nothing is needed and ASF policy wise nothing

Re: What should we we do with SocketCAN

Hi, > From my understanding, it is just the slow wheels of corporate legal > departments. In my experience, legal departments just see no win to giving > up rights. If they don’t want to give the rights to us to use it, do we actually have the rights to use it? (Despite what the license may

Re: What should we we do with SocketCAN

Hi, > There is a LOT of third party code in the Mynewt repositories. Having 3rd party code that is under a compatible license is OK, but the ASF likes to go a step further and know that the owner is OK with this. The ASF doesn’t take code without permission or make hostile forks of projects. M

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

Hi, The only project I know that does something similar (successfully) is subversion and it's by social convention. Please consider not using CODEOWNERS as people don’t own the parts of the code at the ASF. It can also cause long term issues and discourage contribution.Tjhere are other issues,

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/co

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

Hi, INAL but the copyright notice in the header is just a claim and may not reflect who actually has copyright. It doesn’t mean that that person or company owns the copyright on the entire file. With a company it’s usually easier as employment contracts say the company owns the copyright of wor

Re: Podling Nuttx Report Reminder - April 2020

Hi, > Will this help us make progress? If you don’t want to report then that’s up to you. > We've been more or less repeating the same thing for the past two reports. Which is a concern. > Technically the project is making progress Which the ASF is not so concerned about, what you need to sho

Re: Podling Nuttx Report Reminder - April 2020

Hi, > My understanding is that new podlings report monthly for the first 3 months > then quarterly after that. That’s correct it looks like the group attribute may of been set incorrectly in podlings.xml I’ll double check and fix it, but given this podlings lack of progress I think it might be

Re: Question of PR Etiquette

Hi, > So what you suggest it that we as committer don't need disscuss > anything with the contributor, we just need take his PR and do what we > think the right modification then merge directly. You could either discuss it with them or accept the PR and improve it. What you do may be decided on

Re: Question of PR Etiquette

Hi, > Yes, this is last resort. It's better to discuss PR in the github and > let the contributor fix the problem by self. The collaboration model > can decrease the divergence and improve the community health. In my experience this has the opposite effect, it discourages newcomers from contribu

Re: committers-only files under sched/

Hi, > I am guessing (?) that everyone listed there has an Apache Software Grant > Agreement filed, or at > least is willing to file one. If we got SGAs from everyone on the list, one > step in the license clearing would be to find all the files

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?

Hi, > How much time should we wait before starting a vote? When you know the vote will be in favour of your position is the time to call a vote. Actually in favour is probably too strong a position to take, it’s more that no-one would be against this course of action even if they may 100% agree

Re: Should we relax precheck a little bit?

Hi, > I basically agree with most of the things you say here, but in an Apache > project, you cannot set rules unilaterally. No one person has that authority > over the project. We all all equals. Decisions can only be made with > concurrence from other team members and we can only get concu

Re: Should we relax precheck a little bit?

Hi, > But how we measure the release become better and better? Very simply you succeeded if you attract more users and committers. Being welcoming to new committers and having a simple process which that are able to take part helps that. I think you are looking though this from a technical lens

Re: Should we relax precheck a little bit?

Hi, > Yes, this is the key point why I am asking this question: we need > stable the mainline and make the first apache release. Apache doesn’t actually care if your release works or not [*], it not an ASF requirement that a build must pass all tests. What matters is that the next build is be

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/licensi

Re: Apache 2.0 License headers in source files

Hi, > I tried using the mailing list search link you provided, but couldn't find > any previous discussions. It defaults to 1 month old, try change to greater than 0 days or up the months to 4. Use advanced search and type “license" into the subject line. One of the first hits is [1]. Brennan h

Re: Apache 2.0 License headers in source files

Hi, > Does Apache have a recommended way to use the Fossology tool as part of a > project? In general no but your setup is complex. > Or how a podling should use it? Generally they use RAT but that is defined for simpler situations. [1] It still good idea too use it as part of your release che

Re: Apache 2.0 License headers in source files

HI, Rather than having this discussion yet again, please look back through the archives [1] and see what has already been said on this subject (just search for license). Apache also has tools to help you with this, although given the complexity of what you have they may be of limited use. Than

Re: Apache 2.0 License headers in source files

HI, > Brennan has made the initial report here: > https://fossology.brennanashton.com/repo/?mod=browse&show=quick&folder=2 > We can run Adam's tools and fossology iteratively utils all copyright > issue get resolved. Adam tool as it currently is will induce issues that will be harder to detect d

Re: Apache 2.0 License headers in source files

Hi, > For now, I think I think that you could just find all files that contain my > Copyright (grep -rl "Gregory Nutt" *), and then make sure the word Copyright > appears only once in the file (count=`grep Copyright $file1`; if [ $count -eq > 1 ]; then …) I would take care with this, copyright

Re: Apache 2.0 License headers in source files

Hi, Your cannot change the license header without the owners permission and it’s ASF policy to not change any copyright notices without permission. Greg has given his permission via a software grant but there is still a large amount of 3rd party code in the repo.. Is some cases existing files d

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

HI, > Some of the information are kind of overlapping in all three files, > I'm a little confused what to add where. > All the incenses information are in the LICENSE file, what should go > to the DISCLAIMER? DISCLAIMER include the disclaimer and lists any issues that the user should be aware of

Re: nightly build failures

Hi, > But the dev maillist hasn't got the jenkins fail email notice. Could you > please help look into this or should we ask help from Apache Infra? The email would be moderated because the sender of the email is not subscribed to this list. That moderated email may of ended up in spam folders.

Re: Progress on making a release

Hi, > First thing is to created DISCLAIMER, LICENSE and NOTICE files. > I created a draft PR > (https://github.com/apache/incubator-nuttx/pull/392) where I added > these files. > Please check it and share your thoughts. I’d like to see more than just "* Releases may have incomplete licensing con

Re: Progress on making a release

Hi, The release process is: - Create an release candidate and vote on the release on this list - If that vote passes then ask the IPMC to vote on the release on the general@incubator list A vote passes if you get 3 or +1 votes and more +1 votes than -1 votes. A -1 vote is not a veto. Only (P)PM

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

HI, I’m unclear on how progress on the build system is going but I can see there a large number of failure on the jenkins job [1]. Is anyone looking into this? I have seen little discussion on list about this. I notice it's only configured to send email to xiaoxiang781...@gmail.com liugu...@gm

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 that just cont

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

HI, > - Is it possible to mention the count of commits, contributors in the report. > > - Also can we mentions who many discussions happened in the mailing list and > how many people participated in the discussion. Only if it adds something to the report. > These are the non-technical deta

Re: Podling Nuttx Report Reminder - February 2020

Hi, > I just submitted it. Thanks for that, it looks fine and I’ve signed dit off. In future please follow the formatting guidelines at the top of the page and don’t change the spacing from the template, I’ve fixed it this time. In particular: • Keep all lines under 76 characters long

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

Hi, > Yet another great argument for github actions. A number of projects are experimenting with this but there no official ASF support for it yet. [1] There’s a thread I cannot find on making that support more “official”. Also note this thread on broken build taking up resources. [2] Thank

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

Hi, >> 1) Historically, we have put the file name at the top of each file. This >> form would retain that convention. Is this acceptable? >> 2) The line length in the coding standard is 78 bytes. The longest line in >> the same is 62 bytes. That looks weird. Can we use the 78 character line

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

Hi, >> The NuttX coding standard would add to this in .C and C++ files:= Which should be fine. > 1) Historically, we have put the file name at the top of each file. This > form would retain that convention. Is this acceptable? I would put it after the header, but it may be OK. I would need t

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

Hi, > There already is a draft: > https://cwiki.apache.org/confluence/display/NUTTX/February+2020 > We would appreciate your usual feedback. No major feedback but it seems a little light on for detail. Have a look at some of the previous incubator reports [1], you see some piddling reports are

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

Hi, > Brennan is asking for some clarifications in Github > (https://github.com/apache/incubator-nuttx/issues/128) > I thought about bringing it here to get more attention. > Sorry if you saw that already. Probably better to discuss on the mailing list those “@justinmclean” notifications don’t r

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

Hi, > Oh, I did check that wiki page but I was not aware that it was a > requirement to be a comitter or PPMC member to have an LDAP account, but it > makes sense, thanks anyway. We probably can get infra to add you, submitting an ICLA might help as that could be used to create an account. Than

Re: Jenkins CI

Hi, > Also, a request: maybe it would be good to test if Jenkins in > builds.apache.org support pipelines or any Jenkins plugin is missing, so if > I could get the rights to access create a proof-of-concept pipeline to > check everything is available. I can give people Jenkin admin access but the

Re: Jenkins CI

Hi, > so good you liked the idea. I tried to create the page in Confluence, but > it seems I don't have enough rights. You should have permission now. Kind Regards, Justin

Re: Towards making your first Apache release

Hi, > If we used SPDX one-liner, it could be done with a simple find and sed. That would be against current ASF policy on headers. [1] We could ask for an exception if the project wanted to do this. Thanks, Justin 1. https://www.apache.org/legal/src-headers.html#headers

Re: Towards making your first Apache release

HI, > I tend to agree with the way Linux does things. Kconfig files require manual > effort to generate and maintain and are a work that should be protected. > defconfig files, on the other hand, are auto-generated and you want people to > be free to use them. In general copyright doesn’t a

Re: Towards making your first Apache release

HI, > I would never do something like that. I have never intentionally violated a > license. All OS licenses allow you to take code and modify it, including ALv2. ASF policy goes a little further in how your handle the headers, that all. Does that make it clearer? Thanks, Justin

Re: Towards making your first Apache release

Hi, > That is kind of offensive. I would never do something like that. I have > never intentionally violated a license. I always give credit when credit is > due. You're misunderstanding me, I’m describing the conditions under which we can change the headers to ALv2. In some cases you have t

  1   2   3   >