Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 5:40 PM Leigh Griffin wrote: > Hey Everyone, > > On behalf of the CPE team I want to draw the communities attention to a > recent blog post which you may be impacted by: > https://communityblog.fedoraproject.org/git-forge-requirements/ > > We will be seeking input and

Re: Git Forge Requirements: Please see the Community Blog

On Fri, 7 Feb 2020 at 03:32, Michal Konecny wrote: > > > On 06/02/2020 22:13, Till Maas wrote: > As a package maintainer, I can easily request commit/admin access for > >a specific branch or dist-git repo. > I add one more requirement based on my own workflow: > - As fedora user, I want to

Re: Git Forge Requirements: Please see the Community Blog

On 06/02/2020 22:13, Till Maas wrote: On Tue, Jan 21, 2020 at 04:34:37PM +, Leigh Griffin wrote: On behalf of the CPE team I want to draw the communities attention to a recent blog post which you may be impacted by: https://communityblog.fedoraproject.org/git-forge-requirements/ We

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Feb 6, 2020, 21:14 Till Maas wrote: > On Tue, Jan 21, 2020 at 04:34:37PM +, Leigh Griffin wrote: > > > On behalf of the CPE team I want to draw the communities attention to a > > recent blog post which you may be impacted by: > >

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Feb 6, 2020 at 4:14 PM Till Maas wrote: > > On Tue, Jan 21, 2020 at 04:34:37PM +, Leigh Griffin wrote: > > > On behalf of the CPE team I want to draw the communities attention to a > > recent blog post which you may be impacted by: > >

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 04:34:37PM +, Leigh Griffin wrote: > On behalf of the CPE team I want to draw the communities attention to a > recent blog post which you may be impacted by: > https://communityblog.fedoraproject.org/git-forge-requirements/ > > We will be seeking input and

Re: Git Forge Requirements: Please see the Community Blog

On Fri, 2020-01-31 at 10:35 -0500, Neal Gompa wrote: > > > And talking about the git forge, what is Red Hat using internally as git > > forge? And then the above questions applies. > > > > It was mentioned in a different part of this thread that Red Hat is > using pagure internally. Well, it's

Re: Git Forge Requirements: Please see the Community Blog

On Sat, Feb 01, 2020 at 11:15:43AM +0100, Dan Čermák wrote: > Dan Čermák writes: > > > Rahul Sundaram writes: > > > >> Hi > >> > >> On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: > >> > >>> > >>> Welcome to our lives! > >>> If it was mathematically possible to go above 100% that's

Re: Git Forge Requirements: Please see the Community Blog

On Fri, Jan 31, 2020 at 10:02:36AM +0100, Petr Pisar wrote: > On Thu, Jan 30, 2020 at 06:01:22PM -0800, Kevin Fenzi wrote: > > I am with you on open source, but I don't understand the 'self-hosted' > > requirement. I guess I agree that self hosting should be possible, in > > case someone wants to

Re: Git Forge Requirements: Please see the Community Blog

On Sat, Feb 1, 2020 at 10:16 AM Dan Čermák wrote: > Dan Čermák writes: > > > Rahul Sundaram writes: > > > >> Hi > >> > >> On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: > >> > >>> > >>> Welcome to our lives! > >>> If it was mathematically possible to go above 100% that's how much >

Re: Git Forge Requirements: Please see the Community Blog

First requirement: As a Fedora community member, I'm able to self-organize my personal and team work by creating projects and group of projects, by defining different access levels, and by having basic contribution allowed for everyone by default, so that I can contribute in full autonomy. As

Re: Git Forge Requirements: Please see the Community Blog

Dan Čermák writes: > Rahul Sundaram writes: > >> Hi >> >> On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: >> >>> >>> Welcome to our lives! >>> If it was mathematically possible to go above 100% that's how much >>> agreement you >>> would have from us. >>> >> >> If Red Hat is using

Re: Git Forge Requirements: Please see the Community Blog

Rahul Sundaram writes: > Hi > > On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: > >> >> Welcome to our lives! >> If it was mathematically possible to go above 100% that's how much >> agreement you >> would have from us. >> > > If Red Hat is using Pagure internally, it is really odd to

Re: Git Forge Requirements: Please see the Community Blog

Neal Gompa writes: > Michal Konecny wrote: >> Vít Ondruch wrote: >>> Neal Gompa napsal(a): Randy Barlow wrote: > Vít Ondruch wrote: > >> cough cough errata cough cough >> >> Honestly, sometimes the disconnect between what is going on in >> Fedora and internally in

Re: Git Forge Requirements: Please see the Community Blog

On Fri, Jan 31, 2020 at 3:53 PM Rahul Sundaram wrote: > Hi > > On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: > >> >> Welcome to our lives! >> If it was mathematically possible to go above 100% that's how much >> agreement you >> would have from us. >> > > If Red Hat is using Pagure

Re: Git Forge Requirements: Please see the Community Blog

Hi On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: > > Welcome to our lives! > If it was mathematically possible to go above 100% that's how much > agreement you > would have from us. > If Red Hat is using Pagure internally, it is really odd to discuss replacing Pagure with something

Re: Git Forge Requirements: Please see the Community Blog

On Fri, Jan 31, 2020 at 12:11:08PM +0100, Vít Ondruch wrote: > > Of course, there is a lot of business logic specific to Red Hat projects > backed into Errata, but ultimately, it does not help to anybody if > Fedora release process is using different tools then Red Hat internally. > What Red Hat

Re: Git Forge Requirements: Please see the Community Blog

On Fri, Jan 31, 2020 at 10:23 AM Michal Konecny wrote: > > > > On 31/01/2020 12:11, Vít Ondruch wrote: > > Dne 31. 01. 20 v 1:43 Neal Gompa napsal(a): > >> On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow > >> wrote: > >>> On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > cough cough

Re: Git Forge Requirements: Please see the Community Blog

On 31/01/2020 12:11, Vít Ondruch wrote: Dne 31. 01. 20 v 1:43 Neal Gompa napsal(a): On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow wrote: On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: cough cough errata cough cough Honestly, sometimes the disconnect between what is going on in

Re: Git Forge Requirements: Please see the Community Blog

Dne 31. 01. 20 v 1:43 Neal Gompa napsal(a): > On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow > wrote: >> On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: >>> cough cough errata cough cough >>> >>> Honestly, sometimes the disconnect between what is going on in Fedora >>> and internally in Red

Re: Git Forge Requirements: Please see the Community Blog

Dne 30. 01. 20 v 18:45 Adam Williamson napsal(a): > On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: >>> My point is that we have to dedicate a team to work on Pagure, I would >>> rather have these people working on improving the infrastructure so >>> that we don't need these heroics to

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 06:01:22PM -0800, Kevin Fenzi wrote: > I am with you on open source, but I don't understand the 'self-hosted' > requirement. I guess I agree that self hosting should be possible, in > case someone wants to fork our distro and use our tools, but if we can > convince a open

Re: Git Forge Requirements: Please see the Community Blog

Am 31.01.20 um 03:01 schrieb Kevin Fenzi: > I am with you on open source, but I don't understand the 'self-hosted' > requirement. I guess I agree that self hosting should be possible, in > case someone wants to fork our distro and use our tools, but if we can > convince a open source project to

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 11:01:59PM +0100, Felix Schwarz wrote: > > Am 21.01.20 um 22:31 schrieb Michael Catanzaro: > > Well since we have a request for requirements: I propose requirements #1 and > > #2 are to be self-hosted and open source. > > +1 I am with you on open source, but I don't

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow wrote: > > On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > > cough cough errata cough cough > > > > Honestly, sometimes the disconnect between what is going on in Fedora > > and internally in Red Hat is intriguing. > > I did think about Errata

Re: Git Forge Requirements: Please see the Community Blog

On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > cough cough errata cough cough > > Honestly, sometimes the disconnect between what is going on in Fedora > and internally in Red Hat is intriguing. I did think about Errata tool* a bit back when I worked on Bodhi. I like the idea of sharing

Re: Git Forge Requirements: Please see the Community Blog

On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: > > > My point is that we have to dedicate a team to work on Pagure, I would > > rather have these people working on improving the infrastructure so > > that we don't need these heroics to happen. If we don't put people to > > work on Pagure

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 10:40:05AM +0100, Vít Ondruch wrote: >Dne 29. 01. 20 v 23:22 Pierre-Yves Chibon napsal(a): > > On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote: > > Julen Landa Alustiza [1] writes: > > > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak

Re: Git Forge Requirements: Please see the Community Blog

20/1/29 18:19(e)an, Clement Verna igorleak idatzi zuen: > > Things that I would in my opinion improve Pagure PRs : > > * In the PR diff should start from the correct line number, not always > 1. (https://pagure.io/pagure/issue/724) > * Every time a branch is forced pushed you loose the

Re: Git Forge Requirements: Please see the Community Blog

On Thu, Jan 30, 2020 at 6:40 AM Iñaki Ucar wrote: > > On Wed, 29 Jan 2020 at 23:23, Leigh Griffin wrote: > > > > I suspect that a bulk of our users are similar to you. Given that you are > > engaged on the thread (thank you!) what is your day to day needs? What > > features are part of your

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 23:23, Leigh Griffin wrote: > > I suspect that a bulk of our users are similar to you. Given that you are > engaged on the thread (thank you!) what is your day to day needs? What > features are part of your usage and interaction? What's missing or what would > you like

Re: Git Forge Requirements: Please see the Community Blog

Dne 29. 01. 20 v 23:22 Pierre-Yves Chibon napsal(a): > On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote: >> Julen Landa Alustiza writes: >> >>> (snip) >>> >>> 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: To me that's the all point of this process, let's put

Re: Git Forge Requirements: Please see the Community Blog

Dne 29. 01. 20 v 17:37 Clement Verna napsal(a): > > > On Wed, 29 Jan 2020 at 16:18, Pierre-Yves Chibon > wrote: > > On Wed, Jan 29, 2020 at 03:56:08PM +0100, Clement Verna wrote: > >    On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > >   

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 12:52:53PM -0500, Robbie Harwood wrote: > Julen Landa Alustiza writes: > > > (snip) > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > >> To me that's the all point of this > >> process, let's put down what we *really* *really* need and  then look at > >>

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020, 17:19 Iñaki Ucar wrote: > On Wed, 29 Jan 2020 at 16:23, Leigh Griffin wrote: > > > > On Wed, Jan 29, 2020 at 10:35 AM Iñaki Ucar > wrote: > >> > >> On Wed, 29 Jan 2020 at 00:08, Leigh Griffin > wrote: > >> > > >> > On Tue, Jan 28, 2020, 22:06 Iñaki Ucar > wrote: > >> >>

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 18:26, Stephen John Smoogen wrote: > On Wed, 29 Jan 2020 at 11:38, Clement Verna > wrote: > > > > > > > > On Wed, 29 Jan 2020 at 16:18, Pierre-Yves Chibon > wrote: > >> > > >> these heroics related to pagure? > >> > >> If not, I'm not sure what is the point you were

Re: Git Forge Requirements: Please see the Community Blog

Julen Landa Alustiza writes: > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: >> To me that's the all point of this >> process, let's put down what we *really* *really* need and  then look at >> the different options. >> > > Do we *really* *really* need to compete with

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 16:56, Adam Williamson wrote: > On Wed, 2020-01-29 at 15:56 +0100, Clement Verna wrote: > > On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza < > jla...@fedoraproject.org> > > wrote: > > > > > (snip) > > > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > >

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 11:38, Clement Verna wrote: > > > > On Wed, 29 Jan 2020 at 16:18, Pierre-Yves Chibon wrote: >> >> these heroics related to pagure? >> >> If not, I'm not sure what is the point you were trying to make for this >> thread. > > > My point is that we have to dedicate a team

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 16:18, Julen Landa Alustiza wrote: > > > 2020(e)ko urtarrilaren 29(a) 15:56:08 (CET)-(e)an, Clement Verna < > cve...@fedoraproject.org>-(e)k hau idatzi zuen: > >On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > > > >wrote: > > > >> (snip) > >> > >> 20/1/29 14:49(e)an,

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 16:23, Leigh Griffin wrote: > > On Wed, Jan 29, 2020 at 10:35 AM Iñaki Ucar wrote: >> >> On Wed, 29 Jan 2020 at 00:08, Leigh Griffin wrote: >> > >> > On Tue, Jan 28, 2020, 22:06 Iñaki Ucar wrote: >> >> >> >> On Tue, 28 Jan 2020 at 20:58, Leigh Griffin wrote: >> >> > >>

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 16:18, Pierre-Yves Chibon wrote: > On Wed, Jan 29, 2020 at 03:56:08PM +0100, Clement Verna wrote: > >On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > > wrote: > > > > (snip) > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > > To

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-29 at 16:17 +0100, Julen Landa Alustiza wrote: > > 2020(e)ko urtarrilaren 29(a) 15:56:08 (CET)-(e)an, Clement Verna > -(e)k hau idatzi zuen: > > On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > > > > wrote: > > > > > (snip) > > > > > > 20/1/29 14:49(e)an, Clement Verna

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-29 at 15:56 +0100, Clement Verna wrote: > On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > wrote: > > > (snip) > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > > To me that's the all point of this > > > process, let's put down what we *really* *really* need

Re: Git Forge Requirements: Please see the Community Blog

* Neal Gompa: > On Wed, Jan 29, 2020 at 10:07 AM Julen Landa Alustiza > wrote: >> >> Per git ref acls is not a common thing on git forges. If this is a final >> requirement, we should start analyzing the viability of implementing and >> maintain it on the different forges (and it should be

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 3:30 PM Pierre-Yves Chibon wrote: > On Wed, Jan 29, 2020 at 04:06:22PM +0100, Julen Landa Alustiza wrote: > >Per git ref acls is not a common thing on git forges. If this is a > final > >requirement, we should start analyzing the viability of implementing > and >

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 10:07 AM Julen Landa Alustiza wrote: > > Per git ref acls is not a common thing on git forges. If this is a final > requirement, we should start analyzing the viability of implementing and > maintain it on the different forges (and it should be feasible with all of >

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 04:06:22PM +0100, Julen Landa Alustiza wrote: >Per git ref acls is not a common thing on git forges. If this is a final >requirement, we should start analyzing the viability of implementing and >maintain it on the different forges (and it should be feasible with

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 03:56:08PM +0100, Clement Verna wrote: >On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > wrote: > > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > To me that's the all point of this > > process, let's put down what we

Re: Git Forge Requirements: Please see the Community Blog

2020(e)ko urtarrilaren 29(a) 15:56:08 (CET)-(e)an, Clement Verna -(e)k hau idatzi zuen: >On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza > >wrote: > >> (snip) >> >> 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: >> > To me that's the all point of this >> > process, let's put down what

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 10:35 AM Iñaki Ucar wrote: > On Wed, 29 Jan 2020 at 00:08, Leigh Griffin wrote: > > > > On Tue, Jan 28, 2020, 22:06 Iñaki Ucar wrote: > >> > >> On Tue, 28 Jan 2020 at 20:58, Leigh Griffin > wrote: > >> > > >> > This thread is serving as a source of requirements

Re: Git Forge Requirements: Please see the Community Blog

Per git ref acls is not a common thing on git forges. If this is a final requirement, we should start analyzing the viability of implementing and maintain it on the different forges (and it should be feasible with all of the rest of our strange ACLs on dist-git) On pagure side, now that our

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020, 15:23 Julen Landa Alustiza wrote: > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > To me that's the all point of this > > process, let's put down what we *really* *really* need and then look at > > the different options. > > > > Do we *really*

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 09:37:36AM -0500, Neal Gompa wrote: > On Wed, Jan 29, 2020 at 9:29 AM Pierre-Yves Chibon > wrote: > > > > On Wed, Jan 29, 2020 at 03:22:25PM +0100, Julen Landa Alustiza wrote: > > > (snip) > > > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > > >To me

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 9:29 AM Pierre-Yves Chibon wrote: > > On Wed, Jan 29, 2020 at 03:22:25PM +0100, Julen Landa Alustiza wrote: > > (snip) > > > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > > >To me that's the all point of this process, let's put down what we > > >*really*

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 29, 2020 at 03:22:25PM +0100, Julen Landa Alustiza wrote: > (snip) > > 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: > >To me that's the all point of this process, let's put down what we > >*really* *really* need and  then look at the different options. > > > > Do we

Re: Git Forge Requirements: Please see the Community Blog

(snip) 20/1/29 14:49(e)an, Clement Verna igorleak idatzi zuen: To me that's the all point of this process, let's put down what we *really* *really* need and  then look at the different options. Do we *really* *really* need to compete with other full featured git forges on features? The

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 11:36, Iñaki Ucar wrote: > On Wed, 29 Jan 2020 at 00:08, Leigh Griffin wrote: > > > > On Tue, Jan 28, 2020, 22:06 Iñaki Ucar wrote: > >> > >> On Tue, 28 Jan 2020 at 20:58, Leigh Griffin > wrote: > >> > > >> > This thread is serving as a source of requirements (although

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 29 Jan 2020 at 00:08, Leigh Griffin wrote: > > On Tue, Jan 28, 2020, 22:06 Iñaki Ucar wrote: >> >> On Tue, 28 Jan 2020 at 20:58, Leigh Griffin wrote: >> > >> > This thread is serving as a source of requirements (although it has >> > meandered dramatically away from that) >> >> When I

Re: Git Forge Requirements: Please see the Community Blog

Le mardi 21 janvier 2020 à 16:34 +, Leigh Griffin a écrit : Hi, > On behalf of the CPE team I want to draw the communities attention to > a recent blog post which you may be impacted by: > https://communityblog.fedoraproject.org/git-forge-requirements/ Requirements: 1. the url to the

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 28, 2020, 22:06 Iñaki Ucar wrote: > On Tue, 28 Jan 2020 at 20:58, Leigh Griffin wrote: > > > > This thread is serving as a source of requirements (although it has > meandered dramatically away from that) > > When I first read the post, my thought was: wow, what a convoluted and >

Re: Git Forge Requirements: Please see the Community Blog

On Tue, 28 Jan 2020 at 20:58, Leigh Griffin wrote: > > This thread is serving as a source of requirements (although it has meandered > dramatically away from that) When I first read the post, my thought was: wow, what a convoluted and abstruse way of saying "we want to abandon Pagure". Probably

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 28, 2020, 15:58 Adam Saleh wrote: > Way we were discussing this, I think there were several points I didn't > really see here. > > a) we are gathering requirements for Git Forge, but we need a good Dist > Git as well. > > There might be difference in requirements and tooling for Dist

Re: Git Forge Requirements: Please see the Community Blog

On Tue, 28 Jan 2020 at 12:17, Martin Kolman wrote: > > On Wed, 2020-01-22 at 13:28 -0500, Neal Gompa wrote: > > On Wed, Jan 22, 2020 at 12:58 PM Milan Crha wrote: > > > On Wed, 2020-01-22 at 11:37 -0600, Michael Catanzaro wrote: > > > > they all picked GitLab CE. > > > > > > Hi, > > > I

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 13:28 -0500, Neal Gompa wrote: > On Wed, Jan 22, 2020 at 12:58 PM Milan Crha wrote: > > On Wed, 2020-01-22 at 11:37 -0600, Michael Catanzaro wrote: > > > they all picked GitLab CE. > > > > Hi, > > I do not want to pollute this thread with unrelated information, > >

Re: Git Forge Requirements: Please see the Community Blog

Way we were discussing this, I think there were several points I didn't really see here. a) we are gathering requirements for Git Forge, but we need a good Dist Git as well. There might be difference in requirements and tooling for Dist Git compared to generic fully featured Git Forge. It might

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 11:37 am, Michael Catanzaro wrote: It doesn't have as many features as github.com, Sorry, this was a typo. I meant: it doesn't have as many features as gitlab.com. ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: Git Forge Requirements: Please see the Community Blog

On 2020-01-23 11:26, Bruno Wolff III wrote: On Wed, Jan 22, 2020 at 10:28:52 -0500,  Neal Gompa wrote: We don't need to. There are improvements that people would like, and that does take development effort. That's the piece that requires manpower to go faster. In my opinion, I think this is

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 10:28:52 -0500, Neal Gompa wrote: We don't need to. There are improvements that people would like, and that does take development effort. That's the piece that requires manpower to go faster. In my opinion, I think this is where Red Hat should be helping. Pagure has

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 12:04:15PM +0100, Adam Williamson wrote: > On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote: > > > > > > On top of that Gitlab is a huge Ruby on Rails application and (at least > > > > I have the feeling that) the Fedora community doesn't have so many Ruby > > > >

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 5:21 PM Felix Schwarz wrote: > > > Am 22.01.20 um 11:00 schrieb Neal Gompa: > > Yes, but neither of those communities actually have terribly special > > requirements. In fact, those communities either had *nothing* in terms > > of infrastructure (FreeDesktop/Xorg) or were

Re: Git Forge Requirements: Please see the Community Blog

Am 22.01.20 um 11:00 schrieb Neal Gompa: > Yes, but neither of those communities actually have terribly special > requirements. In fact, those communities either had *nothing* in terms > of infrastructure (FreeDesktop/Xorg) or were willing to throw > everything away for GitLab (GNOME). We would

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 12:58 PM Milan Crha wrote: > > On Wed, 2020-01-22 at 11:37 -0600, Michael Catanzaro wrote: > > they all picked GitLab CE. > > Hi, > I do not want to pollute this thread with unrelated information, > but for what it worth, I only recently realized that GitLab CE,

Re: Git Forge Requirements: Please see the Community Blog

Alexander Bokovoy writes: > On ti, 21 tammi 2020, Alex Scheel wrote: > >> For a period of time, IDM tried using Pagure for FreeIPA development. >> They filed a huge number of issues. Now we host issues on Pagure, and >> have moved development to GitHub. [*] I think we've mostly quit >> filing

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 11:37 -0600, Michael Catanzaro wrote: > they all picked GitLab CE. Hi, I do not want to pollute this thread with unrelated information, but for what it worth, I only recently realized that GitLab CE, the one hosted on GNOME, does not have searching working properly.

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 9:12 am, Neal Gompa wrote: I followed it pretty closely. In the GNOME case, you were willing to throw away Bugzilla, CGit, and older CI infrastructure to replace it with GitLab. To be clear, getting rid of Bugzilla was the goal, not a compromise. cgit is a nice

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 10:46 AM Michael Catanzaro wrote: > > On Wed, Jan 22, 2020 at 5:00 am, Neal Gompa wrote: > > And there's this worry that GitLab will go the same path Transifex > > did. They have a ton of incentives to do so, and they already are > > starting to with the consideration of

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 5:00 am, Neal Gompa wrote: And there's this worry that GitLab will go the same path Transifex did. They have a ton of incentives to do so, and they already are starting to with the consideration of injecting nonfree JavaScript in all variants. Terrifying. Do you have a

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 13:51 +0100, Florian Weimer wrote: > * Miro Hrončok: > > > On 22. 01. 20 13:12, Aleksandra Fedorova wrote: > > > I think that it would be more productive if you try to rationalize this > > > opinion. > > > I don't want to argue about the feeling you have, but I would be > >

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 10:22 AM Michael Watters wrote: > > > On 1/22/20 1:56 AM, Michal Konecny wrote: > > If we go this way, in a few years we will end up in the same situation > > as with Pagure today. We will have many custom patches (which we need > > to take care of) and we will not have

Re: Git Forge Requirements: Please see the Community Blog

On 1/22/20 1:56 AM, Michal Konecny wrote: > If we go this way, in a few years we will end up in the same situation > as with Pagure today. We will have many custom patches (which we need > to take care of) and we will not have manpower to compete with the > features of other major git forges.

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 3:43 PM Clement Verna wrote: > > > > On Wed, 22 Jan 2020 at 15:37, Ernestas Kulik wrote: >> >> On Wed, 2020-01-22 at 09:12 -0500, Neal Gompa wrote: >> > On Wed, Jan 22, 2020 at 9:08 AM Ernestas Kulik >> > wrote: >> > > On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote:

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 22 Jan 2020 at 15:37, Ernestas Kulik wrote: > On Wed, 2020-01-22 at 09:12 -0500, Neal Gompa wrote: > > On Wed, Jan 22, 2020 at 9:08 AM Ernestas Kulik > > wrote: > > > On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote: > > > > > > And then there's the issue that we are not upstream and

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 09:12 -0500, Neal Gompa wrote: > On Wed, Jan 22, 2020 at 9:08 AM Ernestas Kulik > wrote: > > On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote: > > > > > And then there's the issue that we are not upstream and might > > > > > have to > > > > > maintain the integration as a

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 9:08 AM Ernestas Kulik wrote: > > On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote: > > > > And then there's the issue that we are not upstream and might > > > > have to > > > > maintain the integration as a downstream patch forever as > > > > upstream might > > > > not

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 05:00 -0500, Neal Gompa wrote: > > > And then there's the issue that we are not upstream and might > > > have to > > > maintain the integration as a downstream patch forever as > > > upstream might > > > not want it. > > > > They've provided pretty good support to various

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 2:21 PM Miro Hrončok wrote: > > On 22. 01. 20 14:03, Aleksandra Fedorova wrote: > > can we have the power, scalability and feature-richness of a platform > > like Gerrit, but (optionally) hidden under the hood so that there is a > > "simple mode" for people who just need a

Re: Git Forge Requirements: Please see the Community Blog

* Miro Hrončok: >> The red X isn't a relevant indicator. This commit was merged and has it, >> too: >> >> > > The red X doesn't mean “CLA not signed”, it means any CI has > failed. CPython allows merges with some CI failed, they

Re: Git Forge Requirements: Please see the Community Blog

On 22. 01. 20 14:03, Aleksandra Fedorova wrote: can we have the power, scalability and feature-richness of a platform like Gerrit, but (optionally) hidden under the hood so that there is a "simple mode" for people who just need a one-time contribution? I won't go there, becasue I don't think

Re: Git Forge Requirements: Please see the Community Blog

On 22. 01. 20 14:12, Florian Weimer wrote: * Miro Hrončok: On 22. 01. 20 11:21, Florian Weimer wrote: * Felix Schwarz: Personally I guess github would attract most contributions for Fedora from new contributors but it is closed source so I'd prefer gitlab for Fedora. I don't think Github

Re: Git Forge Requirements: Please see the Community Blog

* Miro Hrončok: > On 22. 01. 20 11:21, Florian Weimer wrote: >> * Felix Schwarz: >> >>> Personally I guess github would attract most contributions for Fedora >>> from new contributors but it is closed source so I'd prefer gitlab for >>> Fedora. >> >> I don't think Github allows disabling pull

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 1:25 PM Miro Hrončok wrote: > > On 22. 01. 20 13:12, Aleksandra Fedorova wrote: > > I think that it would be more productive if you try to rationalize this > > opinion. > > I don't want to argue about the feeling you have, but I would be > > interested in comparing notes

Re: Git Forge Requirements: Please see the Community Blog

On 22. 01. 20 11:21, Florian Weimer wrote: * Felix Schwarz: Personally I guess github would attract most contributions for Fedora from new contributors but it is closed source so I'd prefer gitlab for Fedora. I don't think Github allows disabling pull requests for projects. This means that

Re: Git Forge Requirements: Please see the Community Blog

* Miro Hrončok: > On 22. 01. 20 13:12, Aleksandra Fedorova wrote: >> I think that it would be more productive if you try to rationalize this >> opinion. >> I don't want to argue about the feeling you have, but I would be >> interested in comparing notes on what exactly "Gerrit workflow" means >>

Re: Git Forge Requirements: Please see the Community Blog

* Aleksandra Fedorova: >> I even think sending patches over e-mail is probably better. > > I think that it would be more productive if you try to rationalize > this opinion. Gerrit makes it really hard to figure out your open tasks. You can see a list of the reviews you have “started”

Re: Git Forge Requirements: Please see the Community Blog

Hello, Thanks for the thread. Lots of good stuff there. Would it be also OK to add a non technical requirement into the mix: - whatever we do choose, we stick to it for N years. I add this because an important reason for moving away from Pagure seems to be that we don't have the man-power to

Re: Git Forge Requirements: Please see the Community Blog

On 22. 01. 20 13:12, Aleksandra Fedorova wrote: I think that it would be more productive if you try to rationalize this opinion. I don't want to argue about the feeling you have, but I would be interested in comparing notes on what exactly "Gerrit workflow" means to you, and whether or not it is

Re: Git Forge Requirements: Please see the Community Blog

* Aleksandra Fedorova: > If we go for splitting up use cases, than I'd like to highlight one thing: > > src.fedoraproject.org is not a GitForge, it is a centrally managed > code-review platform > > Git Forges play a lot with the idea of users being able to create > their own forks of the

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 12:38 PM Miro Hrončok wrote: > > On 22. 01. 20 12:19, Neal Gompa wrote:>> We do need a better discoverability > and > visibility in the generic > >> development community. But it is a solvable task: we can create a > >> read-only mirror of our code on every common

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 22 Jan 2020 at 12:38, Miro Hrončok wrote: > On 22. 01. 20 12:19, Neal Gompa wrote:>> We do need a better > discoverability and > visibility in the generic > >> development community. But it is a solvable task: we can create a > >> read-only mirror of our code on every common platform out

  1   2   >