[libcamera-devel,PATCH/RFC,05/11] licenses: Move developer's certificate of origin to Documentation/

Message ID 20200213153635.27953-6-laurent.pinchart@ideasonboard.com
State Accepted
Headers show
Series
  • Improve license information
Related show

Commit Message

Laurent Pinchart Feb. 13, 2020, 3:36 p.m. UTC
The developer's certificate of origin isn't a license, move it from
LICENSES/ to Documentation/.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 {LICENSES => Documentation}/developer-certificate-of-origin.txt | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename {LICENSES => Documentation}/developer-certificate-of-origin.txt (100%)

Comments

Kieran Bingham Feb. 13, 2020, 3:43 p.m. UTC | #1
Hi Laurent,

On 13/02/2020 15:36, Laurent Pinchart wrote:
> The developer's certificate of origin isn't a license, move it from
> LICENSES/ to Documentation/.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  {LICENSES => Documentation}/developer-certificate-of-origin.txt | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename {LICENSES => Documentation}/developer-certificate-of-origin.txt (100%)
> 
> diff --git a/LICENSES/developer-certificate-of-origin.txt b/Documentation/developer-certificate-of-origin.txt
> similarity index 100%
> rename from LICENSES/developer-certificate-of-origin.txt
> rename to Documentation/developer-certificate-of-origin.txt

Hrm, ok, This is fine in principle, but it leaves an orphaned single
file under Documentation, while all other files there are part of an
html generation.

Feels like this dumps it as a single file currently ...

Of course the html generation could just link to the DCO site ...

Is there an 'official' RST/MD impelmentation of this file that can be
directly tied into our Documentation rather than being a lone
otherwise-unreferenced file in a directory?
Laurent Pinchart Feb. 13, 2020, 4:22 p.m. UTC | #2
Hi Kieran,

On Thu, Feb 13, 2020 at 03:43:49PM +0000, Kieran Bingham wrote:
> On 13/02/2020 15:36, Laurent Pinchart wrote:
> > The developer's certificate of origin isn't a license, move it from
> > LICENSES/ to Documentation/.
> > 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >  {LICENSES => Documentation}/developer-certificate-of-origin.txt | 0
> >  1 file changed, 0 insertions(+), 0 deletions(-)
> >  rename {LICENSES => Documentation}/developer-certificate-of-origin.txt (100%)
> > 
> > diff --git a/LICENSES/developer-certificate-of-origin.txt b/Documentation/developer-certificate-of-origin.txt
> > similarity index 100%
> > rename from LICENSES/developer-certificate-of-origin.txt
> > rename to Documentation/developer-certificate-of-origin.txt
> 
> Hrm, ok, This is fine in principle, but it leaves an orphaned single
> file under Documentation, while all other files there are part of an
> html generation.

The change was prompted by "reuse lint" complaining that the
developer-certificate-of-origin license wasn't used by any file.

> Feels like this dumps it as a single file currently ...
> 
> Of course the html generation could just link to the DCO site ...
> 
> Is there an 'official' RST/MD impelmentation of this file that can be
> directly tied into our Documentation rather than being a lone
> otherwise-unreferenced file in a directory?

Not that I know of, but it's copied in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst,
so I think we could copy it in contributing.rst.

Patch

diff --git a/LICENSES/developer-certificate-of-origin.txt b/Documentation/developer-certificate-of-origin.txt
similarity index 100%
rename from LICENSES/developer-certificate-of-origin.txt
rename to Documentation/developer-certificate-of-origin.txt