public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Bugzilla package list editing
Date: Wed, 10 May 2017 15:08:40 -0400	[thread overview]
Message-ID: <CAGfcS_n4dtS1GdjsWg+t1Ch86rcnxvZZSBju-QAckwfM8X+X8Q@mail.gmail.com> (raw)
In-Reply-To: <CABfmKSJiYHXnAbBXxiUdyStp694VNe=FpbDRL7CB8t=UThsBLw@mail.gmail.com>

On Wed, May 10, 2017 at 2:17 PM, Michael Jones <gentoo@jonesmz.com> wrote:
> From a non-gentoo developer who seriously looked at joining the community
> over the last few years as a new developer, this entire conversation thread
> is absurd, and is a wonderful example of why I decided to not bother.
>
> If you don't want people to edit the field such that it's usable with the
> official package manager of the distribution, then change the formatting
> rules for the field!
>
> If you don't want people editing a field, then change the software such that
> groups who aren't allowed to edit the field aren't even capable of editing
> it!
>
> Either officially document the expected formatting and permissions, or put
> automated enforcement rules into place. Throwing accusations of wrongdoing
> around simply because the action in question generates an email is, again,
> absurd.
>

While the situation is indeed absurd, and this email will no doubt
only fuel your shock, the solution isn't quite that simple.

Validations probably would help, assuming they can be implemented in bugzilla.

Permissions are a touchy situation, because the person who is being
accused of incorrectly editing the field is also our main bug
wrangler, who probably does more bug editing than just about anybody
else.  So, removing their permissions also removes one of their main
areas of contribution to Gentoo.

One of the issues that keeps coming up is around just how
decentralized we are, and that has pros and cons.  We're pretty
reluctant to actually enforce just about anything, or sometimes we're
inconsistent (we let somebody post on the mailing lists, but not
github, and so on).

-- 
Rich


  reply	other threads:[~2017-05-10 19:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 10:29 [gentoo-dev] Bugzilla package list editing Mart Raudsepp
2017-05-02  0:31 ` Andreas K. Huettel
2017-05-02 10:20   ` Paweł Hajdan, Jr.
2017-05-02 11:05     ` Chí-Thanh Christopher Nguyễn
2017-05-02 12:32       ` Ulrich Mueller
2017-05-02 16:19         ` Andreas K. Huettel
2017-05-04 15:42         ` Jeroen Roovers
2017-05-04 16:07           ` Mike Gilbert
2017-05-05  6:02           ` Ulrich Mueller
2017-05-02 12:36       ` Lars Wendler
2017-05-02 16:27       ` Andreas K. Huettel
2017-05-02 16:30         ` Andreas K. Huettel
2017-05-04 15:26       ` Jeroen Roovers
2017-05-10 15:22   ` Mart Raudsepp
2017-05-10 15:33     ` David Seifert
2017-05-10 15:45       ` Kristian Fiskerstrand
2017-05-10 18:17         ` Michael Jones
2017-05-10 19:08           ` Rich Freeman [this message]
2017-05-10 19:24             ` William L. Thomson Jr.
2017-05-10 20:10               ` Rich Freeman
2017-05-10 19:20           ` Mart Raudsepp

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=CAGfcS_n4dtS1GdjsWg+t1Ch86rcnxvZZSBju-QAckwfM8X+X8Q@mail.gmail.com \
    --to=rich0@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