From: Florian Paul Schmidt <mista.tapas@gmx.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: proposal: add "packagers" field (list of strings (names)) to package definition
Date: Wed, 2 Dec 2015 23:16:00 +0100 [thread overview]
Message-ID: <565F6DA0.9040609@gmx.net> (raw)
In-Reply-To: <20151201173518.GA18163@jasmine>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/01/2015 06:35 PM, Leo Famulari wrote:
> All the contributors do get attribution in the copyright notice at
> the top of each file, although that information is not linked to
> their actual contributions except through git.
If they feel their contribution is significant enough to even warrant
an entry there.
[snip]
> Plus I can see some "political" issues in the future where people
> lay claim to parts of the code base and justify it based on their
> name being in the packager field. Personally, I think we should
> avoid creating these sorts of bureaucracies if its not necessary.
Sure, there's a tradeoff there. If the intended semantics are
communicated clearly I don't see that problem.
> I noticed that the NixOS github has a "mention-bot" that
> automatically contacts people based on `git blame` if their old
> code is subject to a pull request. You can see it in action here:
> https://github.com/NixOS/nixpkgs/pull/11329
>
> I think we should let the git repository be the single source of
> truth for figuring out who is responsible for the code. If
> necessary, we can build some automation around the git repo.
Yeah, I like the nixos workflow quite a bit. github is a pretty nice
tool, but sadly nonfree, thus a machina non grata for guix. The nixos
devs actively encourage people to add themselves to the maintainer
fields btw..
Flo
- --
https://fps.io
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWX22gAAoJEA5f4Coltk8Zb+8H/3qprqfKFCzK6049IGMm5EZl
+RVZICpFcvZQH8QLsNeBrkiDfqEq/lTDg7A6emW38GttxSTE4OCy8rUNy9y73TDB
WdSaglazbYHH3HKv4vIZQSTmkODDkuHS0HtTjgTxqicOSwZBChyhEP2jW04rvMCg
ihSigW/MvASkLSwUH2ridL5kHyfDCzdipOy9WnysLsAlTVJi7SUwLvk6hAx2IP3l
km7qm0ZDFSwglM5NeUHitYHr8eZ0GJLTXNi+lhucXucg+OgpR3pozTkTpX5XjEUG
TnhxnlNhLCt2tGL9LWpRVqE80va8SHON96q8HX3XYy2RxIzpG2mds7ue5RNQcJM=
=IUiM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-02 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 8:12 proposal: add "packagers" field (list of strings (names)) to package definition Florian Paul Schmidt
2015-12-01 12:59 ` Florian Paul Schmidt
2015-12-01 17:35 ` Leo Famulari
2015-12-01 18:46 ` Leo Famulari
2015-12-02 22:16 ` Florian Paul Schmidt [this message]
2015-12-02 13:43 ` Andy Wingo
2015-12-02 14:09 ` Thompson, David
2015-12-02 14:59 ` Florian Paul Schmidt
2015-12-02 16:12 ` Andy Wingo
2015-12-02 18:43 ` Florian Paul Schmidt
2015-12-02 19:54 ` Ricardo Wurmus
2015-12-03 10:36 ` Ludovic Courtès
2015-12-03 21:18 ` Florian Paul Schmidt
2015-12-02 16:50 ` Andreas Enge
2015-12-02 18:43 ` Florian Paul Schmidt
2015-12-03 16:46 ` Pjotr Prins
2015-12-03 21:15 ` Florian Paul Schmidt
2015-12-03 10:40 ` Ludovic Courtès
2015-12-03 10:57 ` Taylan Ulrich Bayırlı/Kammer
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=565F6DA0.9040609@gmx.net \
--to=mista.tapas@gmx.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.