Hi Rich,
Rich Freeman writes:
> Actually, I think it is more of a technical constraint. It is
> basically impossible to blacklist somebody on a mailing list, since
> all they need to do is roll up a new email address.
> I can think of various arguments for whitelisting or not whitelisting,
> b
Alec Warner posted on Wed, 21 Mar 2018 10:44:48 -0400 as excerpted:
> On Wed, Mar 21, 2018 at 1:36 AM, Eray Aslan wrote:
>
>> On Tue, Mar 20, 2018 at 10:28:48AM -0500, Matthew Thode wrote:
>> > While I personally do no agree with mailing list moderation infra has
>> > been tasked with moving for
On 22/03/18 00:33, Kristian Fiskerstrand wrote:
>
> Most contributions should happen via patches on b.g.o
>
Who was lamenting about the every-increasing bug queue on this Very list
recently?
And what about those 5+ year old bugs that are rotting for packages long
last-rited from the tree ?
sig
On 03/22/2018 12:56 AM, Chí-Thanh Christopher Nguyễn wrote:
> Rich Freeman schrieb:
>
>> Actually, I think it is more of a technical constraint. It is
>> basically impossible to blacklist somebody on a mailing list, since
>> all they need to do is roll up a new email address.
>>
>> I can think of
On 03/22/2018 12:56 AM, Chí-Thanh Christopher Nguyễn wrote:
> Michael Palimaka schrieb:
>> I see that in bug #650964[1] Council is pushing forward again with
>> implementing user whitelisting on this mailing list (ie. anyone that is
>> not "approved" will have their mail rejected).
>>
>> Could some
On 03/22/2018 12:56 AM, Chí-Thanh Christopher Nguyễn wrote:
> Kristian Fiskerstrand schrieb:
>
>> Switching to mailman might have some good merits on its own, but as I
>> understand it it isn't necessary for the proposal at hand, that can be
>> solved using access control lists in mlmmj-process?
>
Rich Freeman schrieb:
> Actually, I think it is more of a technical constraint. It is
> basically impossible to blacklist somebody on a mailing list, since
> all they need to do is roll up a new email address.
>
> I can think of various arguments for whitelisting or not whitelisting,
> but it se
Michael Palimaka schrieb:
> I see that in bug #650964[1] Council is pushing forward again with
> implementing user whitelisting on this mailing list (ie. anyone that is
> not "approved" will have their mail rejected).
>
> Could someone please explain how this doesn't directly contradict the
> core
Kristian Fiskerstrand schrieb:
> Switching to mailman might have some good merits on its own, but as I
> understand it it isn't necessary for the proposal at hand, that can be
> solved using access control lists in mlmmj-process?
I would advise caution that Council better not try to micro-manage
Hi everyone,
I'm planning to add a new category app-metrics, which is mainly (at
least for my own use case) going to be used for prometheus[0] and its
exporters providing endpoints for prometheus. It can be used for other
packages whose _main_ purpose is to provide metrics, transform or
consume th
John Levine, author of "The Internet For Dummies," once set up a robo-moderation
process for the Usenet newsgroup soc.religion.unitarian-univ
(Unitarian Universalists).
The group, along with most of Usenet, ultimately "died" due to lack of
attention from
the moderators, who failed to curb one of th
El mié, 21-03-2018 a las 10:51 +0200, Mart Raudsepp escribió:
> Ühel kenal päeval, L, 10.03.2018 kell 13:26, kirjutas Pacho Ramos:
> > From now Project:Lisp has no members... that doesn't seem an issue as
> > it
> > contains multiple subprojects that maintain relevant packages... but,
> > for the
>
On Wed, Mar 21, 2018 at 12:55 PM, R0b0t1 wrote:
>
> I can't tell, and I suspect other people can't either.
>
This is the crux of the issue. Decisions involving people issues are
made behind closed doors, which means that others are not free to
confirm for themselves whether those actions are cor
On Wed, Mar 21, 2018 at 9:44 AM, Alec Warner wrote:
> The community has a 'toxic people problem'
Maybe certain people who feel they are being attacked are idiots and
don't like hearing it? I can't tell, and I suspect other people can't
either.
Respectfully,
R0b0t1
On Wed, Mar 21, 2018 at 12:31 PM, Eray Aslan wrote:
> On Wed, Mar 21, 2018 at 10:44:48AM -0400, Alec Warner wrote:
> > [1] Which isn't to say that I would accept 'orders' to commit crimes, or
> > other obviously bad things.
>
> This is the crux of the problem. There are certain lines you will no
On Wed, Mar 21, 2018 at 10:44:48AM -0400, Alec Warner wrote:
> [1] Which isn't to say that I would accept 'orders' to commit crimes, or
> other obviously bad things.
This is the crux of the problem. There are certain lines you will not
cross. I am saying that my line is different and by voicing
On Wed, Mar 21, 2018 at 1:36 AM, Eray Aslan wrote:
> On Tue, Mar 20, 2018 at 10:28:48AM -0500, Matthew Thode wrote:
> > While I personally do no agree with mailing list moderation infra has
> > been tasked with moving forward on it.
>
> You can always resign from infra.
>
> That was a somewhat t
On 03/21/2018 03:33 AM, Kent Fredric wrote:
> On Wed, 21 Mar 2018 01:44:11 +
> Herb Miller Jr. wrote:
>
>> If I am, then yes, some kind of automation
>> would be the only sane way to keep up
> In my experience you can't *really* rely on automation 100% for this
> sort of thing. Not while achie
X dej writes:
> I did not find anything wannabe "g-pip" for python.
Check out app-portage/gs-pypi.
On Wed, Mar 21, 2018 at 1:36 AM, Eray Aslan wrote:
> On Tue, Mar 20, 2018 at 10:28:48AM -0500, Matthew Thode wrote:
>> While I personally do no agree with mailing list moderation infra has
>> been tasked with moving forward on it.
>
> That was a somewhat tongue-in-cheek comment but not wholly. Yo
2018-03-21 2:44 UTC+01:00, Herb Miller Jr. :
>>> When I did my homework on creating nodejs ebuilds (not nodejs itself
>>> but packages written in node), it seems the topic has come up a few
>>> times in the past but the time commitment and general disorganization
>>> of upstream has scared off any
Ühel kenal päeval, L, 10.03.2018 kell 13:26, kirjutas Pacho Ramos:
> From now Project:Lisp has no members... that doesn't seem an issue as
> it
> contains multiple subprojects that maintain relevant packages... but,
> for the
> case anyone wants to join the main project...
> https://wiki.gentoo.org
On Wed, 21 Mar 2018 01:44:11 +
Herb Miller Jr. wrote:
> If I am, then yes, some kind of automation
> would be the only sane way to keep up
In my experience you can't *really* rely on automation 100% for this
sort of thing. Not while achieving quality results.
Its viable for an overlay where
# Kent Fredric (21 Mar 2018)
# Not usable with versions of Bugzilla shipped by Gentoo since 2013,
# Dead upstream. Use dev-perl/BZ-Client instead.
# Removal in 30 days. Bug 651056
dev-perl/WWW-Bugzilla
pgpOQtW1bOeQa.pgp
Description: OpenPGP digital signature
24 matches
Mail list logo
