From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Organization requirements
Date: Fri, 24 Apr 2020 17:25:09 +0200 [thread overview]
Message-ID: <20200424152509.3LeILdd8id52qRP7sYcLlfQKmhG6Az_ktf4jjALbwcU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21299@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Closed issue by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/issues/21299
Description:
I think the current state of void related to who decides what to push or not is a tragedy. This needs to be improved for the sake of us and all users.
I really think that before someone pushes a change there need to be some requirements:
- For package updates being updated by the current maintainer, no review necessary.
- For package updates without soname bumps, at least get the change reviewed by 2 people.
- For new packages at least get change reviewed by 2 people.
- For package updates with soname bumps, at least get the changes reviewed by 5 people.
- For xbps-src changes, at least get the changes reviewed by 5 people.
- For reverts, at least get the ok from 5 people.
Otherwise this is just anarchy...
@void-linux/pkg-committers
next prev parent reply other threads:[~2020-04-24 15:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 11:32 [ISSUE] " xtraeme
2020-04-24 11:39 ` xtraeme
2020-04-24 11:45 ` Duncaen
2020-04-24 11:46 ` Duncaen
2020-04-24 11:48 ` xtraeme
2020-04-24 11:48 ` xtraeme
2020-04-24 11:49 ` xtraeme
2020-04-24 11:50 ` leahneukirchen
2020-04-24 11:51 ` xtraeme
2020-04-24 11:52 ` xtraeme
2020-04-24 11:57 ` xtraeme
2020-04-24 11:57 ` leahneukirchen
2020-04-24 11:59 ` xtraeme
2020-04-24 12:01 ` xtraeme
2020-04-24 12:01 ` xtraeme
2020-04-24 12:08 ` sgn
2020-04-24 12:11 ` sgn
2020-04-24 12:11 ` xtraeme
2020-04-24 12:12 ` xtraeme
2020-04-24 12:21 ` xtraeme
2020-04-24 12:22 ` xtraeme
2020-04-24 13:07 ` pullmoll
2020-04-24 13:09 ` pullmoll
2020-04-24 13:13 ` xtraeme
2020-04-24 14:05 ` Vaelatern
2020-04-24 14:27 ` xtraeme
2020-04-24 14:34 ` q66
2020-04-24 15:09 ` xtraeme
2020-04-24 15:15 ` xtraeme
2020-04-24 15:16 ` Anachron
2020-04-24 15:25 ` xtraeme
2020-04-24 15:25 ` xtraeme [this message]
2020-04-24 15:33 ` Anachron
2020-04-24 19:02 ` Mothrakk
2020-04-24 19:32 ` rugalash
2020-04-24 19:33 ` the-maldridge
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=20200424152509.3LeILdd8id52qRP7sYcLlfQKmhG6Az_ktf4jjALbwcU@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).