From: "Erik Närström" <erik.narstrom@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] meson.eclass third draft
Date: Fri, 5 May 2017 18:20:43 +0000 [thread overview]
Message-ID: <CACzQBmnQb708Fk0NKsv2-xnOHuo_PWq4DeMCk-fDCOJFcpThsw@mail.gmail.com> (raw)
In-Reply-To: <assp.02983c6d06.20170505133134.2399f717@o-sinc.com>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
I'snt copyright deth of author +70yrs?
On 5 May 2017 20:06, "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> On Fri, 5 May 2017 13:18:58 -0400
> "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
>
> > On Fri, 05 May 2017 18:55:41 +0200
> > Michał Górny <mgorny@gentoo.org> wrote:
> >
> > > On pią, 2017-05-05 at 10:35 -0500, William Hubbs wrote:
> > > > # Copyright 2017 Gentoo Foundation
> > >
> > > Aren't we supposed to use the full range of years here?
> >
> > It applies when something comes into existing. If this eclass did not
> > exist in 2016, a copyright for that year would not be correct.
> >
> > This maybe different for ebuilds, as that could be considered derived
> > from the original ebuild. First one ever written. I am not sure the
> > same applies to eclasses, but it might. In that case the year of the
> > first eclass would be correct.
> >
> > I guess it is safe to always use the oldest year.
>
> It may not be good to use the oldest year. Rather the first year
> something came into existence.
>
> "If the copyright duration depends on the date of first publication
> and the year given in the notice is earlier than the
> actual publication date, protection may be shortened by
> beginning the term on the date in the notice"
> https://www.copyright.gov/circs/circ03.pdf
>
> That means if you author something in 2017, and put down say 1999-2017.
> You are starting at 1999, and not 2017. Losing 16 years for no reason.
>
> --
> William L. Thomson Jr.
>
[-- Attachment #2: Type: text/html, Size: 2161 bytes --]
next prev parent reply other threads:[~2017-05-05 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 15:35 [gentoo-dev] meson.eclass third draft William Hubbs
2017-05-05 16:24 ` Mike Gilbert
2017-05-05 16:31 ` William Hubbs
2017-05-05 16:55 ` Michał Górny
2017-05-05 17:18 ` William L. Thomson Jr.
2017-05-05 18:05 ` William L. Thomson Jr.
2017-05-05 18:20 ` Erik Närström [this message]
2017-05-05 18:31 ` William L. Thomson Jr.
2017-05-05 18:55 ` Erik Närström
[not found] ` <20170505143117.13b54da3@o-sinc.com>
2017-05-05 18:38 ` [gentoo-dev] OT Copyright -> " William L. Thomson Jr.
2017-05-05 19:13 ` Erik Närström
2017-05-05 18:31 ` [gentoo-dev] " William L. Thomson Jr.
2017-05-21 1:07 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACzQBmnQb708Fk0NKsv2-xnOHuo_PWq4DeMCk-fDCOJFcpThsw@mail.gmail.com \
--to=erik.narstrom@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox