incubator-nuttx/boards/sim/sim/sim/include/board.h
board.h consists only of 3 line:
1
/
2 * boards/sim/sim/sim/include/board.h
3
If we start adding them, can we also start adding SPDX headers as well.
This will make it a whole lot easier to audit going forward. This is kind
of an industry standard now and makes the legal people in companies a lot
happier as well.
--Brennan
On Sun, Jan 19, 2020 at 12:30 PM Gregory Nutt
Let's not get too sucked into how to apply the header. I'm just trying to
clarify what we need to get headers on where we are missing data.
Here are more files that are missing license information:
H files over 0 bytes no license detected
incubator-nuttx/boards/sim/sim/sim/include/board.h
Then maybe
find . -name Kconfig | xargs sed -i -e "' 1i \
Licensed to the Apache Software Foundation (ASF) under one\
or more contributor license agreements. See the NOTICE file\
distributed with this work for additional information\
regarding copyright ownership. The ASF
Then maybe
find . -name Kconfig | xargs sed -i -e "' 1i \
Licensed to the Apache Software Foundation (ASF) under one\
or more contributor license agreements. See the NOTICE file\
distributed with this work for additional information\
regarding copyright ownership. The ASF
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
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
I share this opinion as well. What should we do about getting license
information on the Kconfig files?
If we used SPDX one-liner, it could be done with a simple find and sed.
Maybe like:
find . -name Kconfig | xargs sed -i -e "' 1i \
# SPDX blablabla"
This could handle a multiple
I share this opinion as well. What should we do about getting license
information on the Kconfig files?
--Brennan
On Sun, Jan 19, 2020, 11:01 AM Gregory Nutt wrote:
>
> > What about the Kconfig files and the defconf files?
>
> I see Linux now has license information (but not copyrights) in
What about the Kconfig files and the defconf files?
I see Linux now has license information (but not copyrights) in their
Kconfig files. For example
https://elixir.bootlin.com/linux/latest/source/Kconfig :
# SPDX-License-Identifier: GPL-2.0
#
# For a description of the syntax of
After looking into this more with Fossology I think I would be a good idea
to use it to track all of this rather than relying on home grown greps.
It's probably better to do the tracking not on my installation, but on
something run by INFRA (mine is backed up for what it's worth).
Justin, how
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
In general, BSD licensed files with "Copyright (C) 20XX Gregory Nutt” would
have the ASF header on them, but we may need to double check that they are not a 3rd
party file that’s just had some changes to it or been reformatted.
That is kind of offensive. I would never do something like
Hi,
In general, BSD licensed files with "Copyright (C) 20XX Gregory Nutt” would
have the ASF header on them, but we may need to double check that they are not
a 3rd party file that’s just had some changes to it or been reformatted.
Thanks,
Justin
Hi,
> So for the OS BSD headers we would need to keep them on the file as well as
> include it in the NOTICE file?
No you would generally not add to NOTICE, only some things are added to NOTICE.
See [1]
> What happens when someone modifies one of these old files once the project
> makes the
On Sat, Jan 18, 2020, 7:11 PM Justin Mclean
wrote:
> Hi,
>
> > Is there some docs to guide us in making this licencing transition? I
> would
> > be happy to start the processing of adding spdx headers based on what is
> in
> > the code if that would help, but I don't know how to transition files
Hi,
> Is there some docs to guide us in making this licencing transition? I would
> be happy to start the processing of adding spdx headers based on what is in
> the code if that would help, but I don't know how to transition files to
> Apache 2 under this project.
It’s easy enough:
- Add ASF
Justin,
Is there some docs to guide us in making this licencing transition? I would
be happy to start the processing of adding spdx headers based on what is in
the code if that would help, but I don't know how to transition files to
Apache 2 under this project.
I also know that while most of the
Hi,
It would be great if some people start working on these issues otherwise it
will hold up making a release. I raised a couple of Github issues for the most
urgent ones e.g having a LICENSE, NOTICE and DISCLAIMER and putting ASF headers
on files.
Thanks,
Justin
I'm also willing to take this on or help someone else for the first
release. Can't rush the code, but it would be nice to get the other bits
in place for a release.
--Brennan
On Wed, Jan 15, 2020, 3:37 PM Justin Mclean
wrote:
> HI,
>
> > I cannot determine what the capabilities are that are
HI,
> I cannot determine what the capabilities are that are needed and what the
> impact in hours will be?
Hard to estimate hours but it should be more than a few hours week, the first
release generally take some time to get together 2 to 4 weeks is typically, but
some projects do it quicker
Is anyone willing to be the first release manager?
My understanding is that the release manager does not necessarily do the
release, but is the point of contact and coordinator for releases and
needs to sign releases. Is that true?
So the job should not sound as scary as the title
I have been reading:
http://www.apache.org/dev/release-publishing.html
Verstuurd vanaf mijn iPhone
> Op 15 jan. 2020 om 23:52 heeft Justin Mclean het
> volgende geschreven:
>
> Hi,
>
> Is anyone willing to be the first release manager?
>
> Thanks,
> Justin
Hello Justin,
I cannot determine what the capabilities are that are needed and what the
impact in hours will be? And I would need guidance I have a strong passion
about Nuttx, but maybe thats not enough...
Ben
Verstuurd vanaf mijn iPhone
> Op 15 jan. 2020 om 23:52 heeft Justin Mclean
Hi,
Is anyone willing to be the first release manager?
Thanks,
Justin
Hi,
If the PPMC want to get started making a release I suggest they do the
following:
1. Someone puts up their hand up to be the release manager. Do we have any
takers?
2. Add LICENSE and NOTICE and DISCLAIMER to the repo. COPYING may need to be
modified/removed.
3. Decide on approach to take
26 matches
Mail list logo
