public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages
Date: Fri, 21 Jun 2019 09:03:41 +0300	[thread overview]
Message-ID: <20190621090341.2eccb0714f23bbf78a4c90c7@gentoo.org> (raw)
In-Reply-To: <8d6601e6-a295-778e-5dc8-5d9f01701c7d@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

Hi!

On Thu, 20 Jun 2019 09:53:46 -0400 Brian Evans wrote:
> > +
> > +Before adding a new user and/or group, the developer must send a RFC
> > +to the ``gentoo-dev`` mailing list.
> 
> This paragraph should go away.  It is a complete waste of time.

> > +Requiring mailing list RFC
> > +--------------------------
> > +
> > +The policy explicitly requires RFC-es for new users and groups, as they
> > +have global scopes and effects of mistakes while adding them are hard
> > +to fix.  Wider review should decrease the risk of major design mistakes.
> > +
> > +To provide one example, right now we have two different packages
> > +creating ``git`` user and requiring a different home directory for
> > +the user.  As a result, the first package being installed defines
> > +the actual home directory, and both technically can not be installed
> > +at the same time.
> 
> This section should go away.  It is a complete waste of time.

Mail list discussion may make sense only if users or groups and
intended to be shared between different applications (e.g. ftp,
mail, ntp). If user or group are intended to be application
specific, there is no need for such discussions as they will just
hinder development process.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-06-21  6:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 11:39 [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages Michał Górny
2019-06-13  2:21 ` Michael Orlitzky
2019-06-13  5:37   ` Michał Górny
2019-06-20 13:53 ` Brian Evans
2019-06-20 14:15   ` Michael Orlitzky
2019-06-20 14:32   ` Michał Górny
2019-06-21  5:59     ` Andrew Savchenko
2019-06-21  7:18       ` David Seifert
2019-06-21 12:02         ` Andrew Savchenko
2019-06-21 12:18           ` David Seifert
2019-06-21 13:09           ` Michał Górny
2019-06-21  8:31       ` Jaco Kroon
2019-06-21  6:03   ` Andrew Savchenko [this message]
2019-06-22 17:34   ` Andrey Utkin

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=20190621090341.2eccb0714f23bbf78a4c90c7@gentoo.org \
    --to=bircoph@gentoo.org \
    --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