On 9/9/19 12:52 PM, Kevin Fenzi wrote:
On 9/7/19 12:54 PM, Dusty Mabe wrote:
> On 9/7/19 1:11 PM, Kevin Fenzi wrote:
>> On 9/6/19 10:45 AM, Dusty Mabe wrote:
>>> On 9/6/19 1:31 PM, Kevin Fenzi wrote:
>>>> On 9/5/19 9:30 AM, Dusty Mabe wrote:
>>>>> Could we send all of the unorphan, unretire, revive etc issues to a
>>>>> than https://pagure.io/releng/?
I like to follow and participate in
>>>>> but the number of those recently has been a bit unwieldy and they all
go to the mailing
>>>> Yeah, I'd be ok with this. I mean anyone who wants those can just
>>>> the project in pagure.
>>> Just to be clear, you'd be OK with creating a new repo for those types of
>> No, sorry, let me be more clear:
> I'm glad I asked for clarification :)
>> I'd be ok with NOT copying the rel-eng list on all the releng pagure
>> requests. I think moving those requests to another repo might be
>> confusing to people. Hopefully a number of them should go away when we
>> implement the plugins to handle orphan stuff.
> ehh. I'd be ok with not copying rel-eng list on all the releng pagure requests
> but then the releng list will pretty much be very very low volume so I don't
> know if it will really achieve any goals because anyone who wants to be involved
> will have to subscribe to the pagure repo AND the list.
Well, then I don't understand your goals. If we stop copying the list on
all pagure requests the list will be low volume and a place you can have
discussions, right? You only need to also subscribe to pagure issues if
you care about those, and you can also then filter them into a different
place more easily.
Basically what I'm saying is all pagure issues aren't created equal
and there is a class I think we can target to reduce noise (see below).
The current setup is not ideal for me because I get 2 copies of
everything in pagure (one from pagure and one to the list). It just
seems like duplication to me... and I agree lists posts are lost in the
sea of ticket copies.
Yes. This is a problem for me as well. I also get two copies.
Moving those things to another pagure repo doesn't seem like it would
help anything. It would just make me get a different copy of all those,
and interested people would need to subscribe there anyhow.
There are three communication streams I'm concerned with:
1. releng list posts
2. pagure repo ticket discussion not related to scm requests
3. pagure repo ticket discussion related to scm requests
I think 1+2 are representative of discussions about releng, relevant changes,
and potential future. 3. is kind of noise that drowns 1/2 out.
so, to me, the thing that makes the most sense is to stop copying all
the tickets to the list and let the list be usable for more discussions.
If you feel that way, then I'd support that decision. Sometimes it can be useful
to copy the list so that it's easier for people to follow releng (i.e. they only have
to sign up for one thing and they get all the discussions), but adding a "also
to the pagure repo" isn't too bad.