From: Eric Wong <e@80x24.org>
To: Julien Moutinho <julm+public-inbox@sourcephile.fr>
Cc: meta@public-inbox.org
Subject: Re: Difficulty following the AGPL for example systemd units
Date: Sat, 7 May 2022 00:57:06 +0000 [thread overview]
Message-ID: <20220507005706.M664745@dcvr> (raw)
In-Reply-To: <20220506203223.xhp3ipbt4isp4tty@sourcephile.fr>
Julien Moutinho <julm+public-inbox@sourcephile.fr> wrote:
> Le jeu. 28 avril 2022 10h53 +0000, Eric Wong a ??crit??:
> > Jason Yundt <jason@jasonyundt.email> wrote:
> > > Now that I look at it, the top-level README only says that the program is
> > > under the GNU AGPL. Does that mean that those units don???t have a license?
> >
> > I suppose there's no license, or just CC0/public-domain.
> > I mean, we sometimes post config snippets in emails w/o licenses, too;
> > and same happens on git@vger and various other development lists/forums/etc..
> >
> > *shrug*
> You may want to use https://reuse.software to clarify this :
>
> $ reuse init
Interesting, though I'm trying to have less software installed
on my system(s)...
<snip>
> $ cat .reuse/dep5
> > Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> > Upstream-Name: public-inbox
> > Upstream-Contact: Eric Wong <e@80x24.org>
> > Source: https://public-inbox.org/public-inbox.git
Would prefer upstream contact to be something along the lines of:
all contributors <meta@public-inbox.org>
...To emphasize that it's a community project.
As an aside, I've always been a shy introvert, so I always get
uncomfortable when seeing my name in "official-looking" places.
I'm even less comfortable as I age, and believe the acronym
expansion I added to the AUTHORS file is rather appropriate ;>
> > # Sample paragraph, commented out:
> > #
> > # Files: src/*
> > # Copyright: $YEAR $NAME <$CONTACT>
> > # License: ...
> >
>
> And after editing .reuse/dep5:
>
> $ git rm COPYING
> $ git add LICENSES .reuse/dep5
> $ reuse lint
Anyways, I'll think about it; though I'm not sure if I want to
be an early adopter of this and put more .dotfiles into the
source tree.
Thanks.
prev parent reply other threads:[~2022-05-07 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 22:01 Difficulty following the AGPL for example systemd units Jason Yundt
2022-04-25 23:22 ` Eric Wong
[not found] ` <20220426222705.GA30933@dcvr>
2022-04-27 22:50 ` Jason Yundt
2022-04-28 10:53 ` Eric Wong
2022-05-06 20:32 ` Julien Moutinho
2022-05-07 0:57 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220507005706.M664745@dcvr \
--to=e@80x24.org \
--cc=julm+public-inbox@sourcephile.fr \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).