Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Matthew Miller
On Tue, Mar 31, 2020 at 09:30:57AM -0500, Bruno Wolff III wrote: > It's more than that. While the community edition of gitlab (assuming > we don't get stuck with the proprietary version) is technically open > source, the main fork is run by Gitlab who have a conflict of > interest in adding feature

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Bruno Wolff III
On Tue, Mar 31, 2020 at 10:33:46 -0400, Matthew Miller wrote: I understand the attachment we have as a project to Pagure -- someone in our community made it, after all, and lots of others have made direct and indirect contributions. I feel that too! But, we all know that it needs significant d

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Matthew Miller
On Mon, Mar 30, 2020 at 10:20:00AM +0200, Miro Hrončok wrote: > The original proposal promised Fedora Council involvement. I wonder > where that happened, I could not found any Pagure ticket nor a > Council mailing list thread about this. We were asked to help collect the user stories and requirem

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Leigh Griffin
On Tue, Mar 31, 2020 at 1:23 PM Ian McInerney wrote: > Leigh, > > >> Do you know how many >>> existing integrations with pagure there are? >> >> >> No. Our analysis will tell us that in due course >> > > I am concerned by this approach to the decision-making. In many of your > replies, you mentio

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Ian McInerney
Leigh, > Do you know how many >> existing integrations with pagure there are? > > > No. Our analysis will tell us that in due course > I am concerned by this approach to the decision-making. In many of your replies, you mention wanting to get feature-parity with the current tooling and systems,

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Leigh Griffin
On Tue, Mar 31, 2020 at 11:28 AM Till Maas wrote: > Hi Leigh, > > On Tue, Mar 31, 2020 at 09:56:10AM +0100, Leigh Griffin wrote: > > On Mon, Mar 30, 2020 at 10:13 PM Till Maas wrote: > > > > > Hi, > > > > > > On Mon, Mar 30, 2020 at 11:28:59AM +0100, Leigh Griffin wrote: > > > > > > > No singula

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Till Maas
Hi Leigh, On Tue, Mar 31, 2020 at 09:56:10AM +0100, Leigh Griffin wrote: > On Mon, Mar 30, 2020 at 10:13 PM Till Maas wrote: > > > Hi, > > > > On Mon, Mar 30, 2020 at 11:28:59AM +0100, Leigh Griffin wrote: > > > > > No singular Forge satisfied every single User Story. Any feature gaps > > will >

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 10:13 PM Till Maas wrote: > Hi, > > On Mon, Mar 30, 2020 at 11:28:59AM +0100, Leigh Griffin wrote: > > > No singular Forge satisfied every single User Story. Any feature gaps > will > > land on the Backlog of Gitlab for voting and prioritisation as their > > Engineering te

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-31 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 7:17 PM clime wrote: > I thought CPE ("Community Platform Engineering") is a part of the > community. We are part of the CentOS and Fedora Communities, correct. > But no, because you want to hand over pagure.io to "the > Community", so what community is that...People t

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Till Maas
Hi, On Mon, Mar 30, 2020 at 11:28:59AM +0100, Leigh Griffin wrote: > No singular Forge satisfied every single User Story. Any feature gaps will > land on the Backlog of Gitlab for voting and prioritisation as their > Engineering teams see fit. this sounds very disturbing. Please clarify this. Fe

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Alex Scheel
- Original Message - > From: "Neal Gompa" > To: "Development discussions related to Fedora" > > Cc: "Alex Scheel" , "Leigh Griffin" > Sent: Monday, March 30, 2020 3:30:20 PM > Subject: Re: The Git forge decision (was CPE Weekly:

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Bruno Wolff III
On Mon, Mar 30, 2020 at 15:30:20 -0400, Neal Gompa wrote: I barely remember plague (it was going away when I started as a packager). Plague was free software, but the build system for Fedora Core was not. That and Plague were both replaced with Koji in 2007. It was a great day, indeed. Thank

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Neal Gompa
On Mon, Mar 30, 2020 at 3:26 PM Bruno Wolff III wrote: > > On Mon, Mar 30, 2020 at 14:42:33 -0400, > Alex Scheel wrote: > > > >Have you tried to use Pagure as a development based git forge? And not > >just as a dist-git hosting location? It needs a lot of help! More than the > >current resource

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Bruno Wolff III
On Mon, Mar 30, 2020 at 14:42:33 -0400, Alex Scheel wrote: Have you tried to use Pagure as a development based git forge? And not just as a dist-git hosting location? It needs a lot of help! More than the current resources provide. I've used the PR features a bit in a dist-git context. I tri

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Alex Scheel
- Original Message - > From: "Martin Kolman" > To: "Development discussions related to Fedora" > > Cc: "Leigh Griffin" > Sent: Monday, March 30, 2020 3:05:54 PM > Subject: Re: The Git forge decision (was CPE Weekly: 2020-03-28) >

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Martin Kolman
- Original Message - > From: "Alex Scheel" > To: "Development discussions related to Fedora" > > Cc: "Leigh Griffin" > Sent: Monday, March 30, 2020 8:42:33 PM > Subject: Re: The Git forge decision (was CPE Weekly: 2020-03-28) > &g

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Alex Scheel
- Original Message - > From: "Bruno Wolff III" > To: "Leigh Griffin" > Cc: "Development discussions related to Fedora" > > Sent: Monday, March 30, 2020 2:08:21 PM > Subject: Re: The Git forge decision (was CPE Weekly: 2020-03-28) >

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Bruno Wolff III
On Mon, Mar 30, 2020 at 17:20:04 +0100, Leigh Griffin wrote: On Mon, Mar 30, 2020 at 5:06 PM David Kaufmann wrote: We are trying to reduce the total ownership of the team to allow us to provide value on initiatives that are requested of us by our stakeholders. Pagure has value beyond Fedora

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread clime
I thought CPE ("Community Platform Engineering") is a part of the community. But no, because you want to hand over pagure.io to "the Community", so what community is that...People that don't have hardware? It seems that the whole proposal is trying to make src.fp.o and git.centos.org part of a cor

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Miro Hrončok
On 30. 03. 20 17:55, David Kaufmann wrote: What I don't understand is, why a decision this big is not taken by FESCo (or Council) and the CentOS Governing Board itself. FESCo cannot actually make anyone do anything. So even if FESCo says: "The dist-git will run on Pagure", CPE can say: "Whatev

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 5:06 PM David Kaufmann wrote: > Hi, > > On Mon, Mar 30, 2020 at 12:38:16PM +0100, Leigh Griffin wrote: > > The decision is made and we are proceeding to engage with Gitlab and > > unfortunately that won't be reversed as a decision. > > I haven't expected this situation, so

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread David Kaufmann
Hi, On Mon, Mar 30, 2020 at 12:38:16PM +0100, Leigh Griffin wrote: > The decision is made and we are proceeding to engage with Gitlab and > unfortunately that won't be reversed as a decision. I haven't expected this situation, so I've read up a bit on the whole thing. From the outside it looks t

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 1:13 PM Julen Landa Alustiza < jla...@fedoraproject.org> wrote: > > > 20/3/30 13:43(e)an, Leigh Griffin igorleak idatzi zuen: > > > > > > On Mon, Mar 30, 2020 at 12:24 PM Iñaki Ucar > > wrote: > > > > On Mon, 30 Mar 2020 at 13:10, Leigh

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Neal Gompa
On Mon, Mar 30, 2020 at 8:13 AM Nicolas Mailhot via devel wrote: > > Le dimanche 29 mars 2020 à 23:47 -0400, Neal Gompa a écrit : > > > > > As a General User > > > I want to access repos fully over https > > > For environments where SSH is blocked > > > > I would be really curious if the Red Hat I

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Nicolas Mailhot via devel
Le dimanche 29 mars 2020 à 23:47 -0400, Neal Gompa a écrit : > > > As a General User > > I want to access repos fully over https > > For environments where SSH is blocked > > I would be really curious if the Red Hat Infrastructure Security guys > have changed their opinion on this after four year

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Julen Landa Alustiza
20/3/30 13:43(e)an, Leigh Griffin igorleak idatzi zuen: > > > On Mon, Mar 30, 2020 at 12:24 PM Iñaki Ucar > wrote: > > On Mon, 30 Mar 2020 at 13:10, Leigh Griffin > wrote: > > > > On Mon, Mar 30, 2020 at 10:29 AM Iña

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Solomon Peachy
On Mon, Mar 30, 2020 at 12:45:59PM +0100, Leigh Griffin wrote: > We done that as a Management team and with our Product Owner among other > stakeholders. We did evaluate the merit of the requirements from a > practicality perspective but we did not question or force our opinion on > the validity of

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 12:31 PM Neal Gompa wrote: > On Mon, Mar 30, 2020 at 7:27 AM Iñaki Ucar > wrote: > > > > On Mon, 30 Mar 2020 at 13:20, Neal Gompa wrote: > > > > > > On Mon, Mar 30, 2020 at 7:02 AM Leigh Griffin > wrote: > > > > > > > >> > > > >> I was really looking forward to reading

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 12:24 PM Iñaki Ucar wrote: > On Mon, 30 Mar 2020 at 13:10, Leigh Griffin wrote: > > > > On Mon, Mar 30, 2020 at 10:29 AM Iñaki Ucar > wrote: > >> > >> So I was also waiting for those open discussions about the > >> requirements gathered. > > > > We had several threads on

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 12:10 PM Neal Gompa wrote: > On Mon, Mar 30, 2020 at 7:02 AM Leigh Griffin wrote: > > > >> > >> I was really looking forward to reading what > >> Neal (as he's doing now) and others had to say about the requirements > >> *before* any decision was taken, and how each tool

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Neal Gompa
On Mon, Mar 30, 2020 at 7:27 AM Iñaki Ucar wrote: > > On Mon, 30 Mar 2020 at 13:20, Neal Gompa wrote: > > > > On Mon, Mar 30, 2020 at 7:02 AM Leigh Griffin wrote: > > > > > >> > > >> I was really looking forward to reading what > > >> Neal (as he's doing now) and others had to say about the requ

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Iñaki Ucar
On Mon, 30 Mar 2020 at 13:20, Neal Gompa wrote: > > On Mon, Mar 30, 2020 at 7:02 AM Leigh Griffin wrote: > > > >> > >> I was really looking forward to reading what > >> Neal (as he's doing now) and others had to say about the requirements > >> *before* any decision was taken, and how each tool co

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Iñaki Ucar
On Mon, 30 Mar 2020 at 13:10, Leigh Griffin wrote: > > On Mon, Mar 30, 2020 at 10:29 AM Iñaki Ucar wrote: >> >> So I was also waiting for those open discussions about the >> requirements gathered. > > We had several threads on them from the Fedora perspective on both devel and > council lists.

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Neal Gompa
On Mon, Mar 30, 2020 at 7:02 AM Leigh Griffin wrote: > >> >> I was really looking forward to reading what >> Neal (as he's doing now) and others had to say about the requirements >> *before* any decision was taken, and how each tool covers them or not, >> and what kind of effort would require to c

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 10:29 AM Iñaki Ucar wrote: > On Mon, 30 Mar 2020 at 09:15, Julen Landa Alustiza > wrote: > > > > 20/3/30 08:40(e)an, James Cassell igorleak idatzi zuen: > > > > > > On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: > > >> On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 8:08 AM Julen Landa Alustiza < jla...@fedoraproject.org> wrote: > > > 20/3/30 08:40(e)an, James Cassell igorleak idatzi zuen: > > > > On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: > >> On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney > wrote: > >>> > >>> ### Other Upda

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Leigh Griffin
On Mon, Mar 30, 2020 at 4:48 AM Neal Gompa wrote: > On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: > > > > ### Other Updates > > > > GitForge Decision > > * After evaluating over 300 user stories from multiple stakeholders we > > have aligned on a decision for the Gitforge that CPE wi

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Julen Landa Alustiza
20/3/30 11:27(e)an, Iñaki Ucar igorleak idatzi zuen: > On Mon, 30 Mar 2020 at 09:15, Julen Landa Alustiza > wrote: >> >> 20/3/30 08:40(e)an, James Cassell igorleak idatzi zuen: >>> >>> On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote:

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Iñaki Ucar
On Mon, 30 Mar 2020 at 09:15, Julen Landa Alustiza wrote: > > 20/3/30 08:40(e)an, James Cassell igorleak idatzi zuen: > > > > On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: > >> On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: > >>> > >>> ### Other Updates > >>> > >>> GitForge Deci

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Miro Hrončok
On 30. 03. 20 5:47, Neal Gompa wrote: On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: ### Other Updates GitForge Decision * After evaluating over 300 user stories from multiple stakeholders we have aligned on a decision for the Gitforge that CPE will operate for the coming years. We

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-30 Thread Julen Landa Alustiza
20/3/30 08:40(e)an, James Cassell igorleak idatzi zuen: > > On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: >> On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: >>> >>> ### Other Updates >>> >>> GitForge Decision >>> * After evaluating over 300 user stories from multiple stakeholde

Re: The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-29 Thread James Cassell
On Sun, Mar 29, 2020, at 11:47 PM, Neal Gompa wrote: > On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: > > > > ### Other Updates > > > > GitForge Decision > > * After evaluating over 300 user stories from multiple stakeholders we > > have aligned on a decision for the Gitforge that CPE

The Git forge decision (was CPE Weekly: 2020-03-28)

2020-03-29 Thread Neal Gompa
On Sat, Mar 28, 2020 at 4:12 PM Aoife Moloney wrote: > > ### Other Updates > > GitForge Decision > * After evaluating over 300 user stories from multiple stakeholders we > have aligned on a decision for the Gitforge that CPE will operate for > the coming years. We are opting for Gitlab for ou