[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposal: add "packagers" field (list of strings (names)) to package
From: |
Florian Paul Schmidt |
Subject: |
Re: proposal: add "packagers" field (list of strings (names)) to package definition |
Date: |
Wed, 2 Dec 2015 23:16:00 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
-----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-----
- proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/01
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/01
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Leo Famulari, 2015/12/01
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Andy Wingo, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Thompson, David, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Andy Wingo, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Ricardo Wurmus, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Ludovic Courtès, 2015/12/03
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/03
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Andreas Enge, 2015/12/02
- Re: proposal: add "packagers" field (list of strings (names)) to package definition, Florian Paul Schmidt, 2015/12/02