Re: Git Forge Requirements: Please see the Community Blog

Heya, Currently we have two different pagure instances that hosts different use cases on them, and different use cases means different requirements, so first of all, about what use cases we are talking about? we have src.fp.o for distgit, some pagure.io projects that hosts actual code

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 12:20 PM Neal Gompa wrote: > > On Wed, Jan 22, 2020 at 6:06 AM Aleksandra Fedorova > wrote: > > > > On Wed, Jan 22, 2020 at 9:48 AM Clement Verna > > wrote: > > > > > > > > > > > > On Tue, 21 Jan 2020 at 22:32, Michael Catanzaro > > > wrote: > > >> > > >> On Tue, Jan

Re: Git Forge Requirements: Please see the Community Blog

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 there. We can use it as an opportunity to show what we do, but

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 22 Jan 2020 at 11:02, Neal Gompa wrote: > On Wed, Jan 22, 2020 at 1:05 AM Peter Robinson > wrote: > > > > On Wed, Jan 22, 2020 at 4:59 AM Dan Čermák > > wrote: > > > > > > Felix Schwarz writes: > > > > > > > Am 21.01.20 um 21:48 schrieb Guido Aulisi: > > > >> I totally agree with

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 6:06 AM Aleksandra Fedorova wrote: > > On Wed, Jan 22, 2020 at 9:48 AM Clement Verna > wrote: > > > > > > > > On Tue, 21 Jan 2020 at 22:32, Michael Catanzaro > > wrote: > >> > >> On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: > >> > And any discussion of GitHub

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 6:04 AM 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 > > > > developers in

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 9:48 AM Clement Verna wrote: > > > > On Tue, 21 Jan 2020 at 22:32, Michael Catanzaro wrote: >> >> On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: >> > And any discussion of GitHub isn't going to involve self-hosted, it's >> > going to involve GitHub.com, which means

Re: Git Forge Requirements: Please see the Community Blog

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 > > > developers in comparison to Python developers, so implementing something > > >

Re: Git Forge Requirements: Please see the Community Blog

* 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 a ptoential Fedora Github service would

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 1:05 AM Peter Robinson wrote: > > On Wed, Jan 22, 2020 at 4:59 AM Dan Čermák > wrote: > > > > Felix Schwarz writes: > > > > > Am 21.01.20 um 21:48 schrieb Guido Aulisi: > > >> I totally agree with Fabio, I can’t think of a single reason we should > > >> dismiss > > >>

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 10:01 +0100, Pierre-Yves Chibon wrote: > > IIRC phabricator does not issue tracking which mean it would not fit the > use-case of FESCo, FPC and other groups that are mostly using pagure as a > ticketing system. Sure it does, we used to use it for this. It calls them

Re: Git Forge Requirements: Please see the Community Blog

On Wed, 2020-01-22 at 08:40 +, Peter Oliver wrote: > On Tue, 21 Jan 2020, 21:32 Michael Catanzaro, wrote: > > So if we can agree on that much, then we can avoid wasting time by > > including GitHub in the list of options. That would bring us to a > > choice between GitLab CE and Pagure. (Are

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 08:40:54AM +, Peter Oliver wrote: >On Tue, 21 Jan 2020, 21:32 Michael Catanzaro, <[1]mcatanz...@gnome.org> >wrote: > > So if we can agree on that much, then we can avoid wasting time by > including GitHub in the list of options. That would bring us to

Re: Git Forge Requirements: Please see the Community Blog

On Tue, 21 Jan 2020 at 22:32, Michael Catanzaro wrote: > On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: > > And any discussion of GitHub isn't going to involve self-hosted, it's > > going to involve GitHub.com, which means we're talking about losing > > more of our independence as a

Re: Git Forge Requirements: Please see the Community Blog

On Tue, 21 Jan 2020, 21:32 Michael Catanzaro, wrote: So if we can agree on that much, then we can avoid wasting time by > including GitHub in the list of options. That would bring us to a > choice between GitLab CE and Pagure. (Are there any other serious > options?) In the blog post they

Re: Git Forge Requirements: Please see the Community Blog

On Tue, 2020-01-21 at 17:04 -0500, Michael Watters wrote: > On 1/21/20 4:59 PM, Felix Schwarz wrote: > > (Though > > I somehow got used to pagure and getting the gitlab integration to the same > > level as pagure currently will be a lot of work for sure.) > > Maybe I'm just a grumpy old system

Re: Git Forge Requirements: Please see the Community Blog

On 21/01/2020 23:13, John M. Harris Jr wrote: On Tuesday, January 21, 2020 2:31:47 PM MST Michael Catanzaro wrote: On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: And any discussion of GitHub isn't going to involve self-hosted, it's going to involve GitHub.com, which means we're talking

Re: Git Forge Requirements: Please see the Community Blog

On Wed, Jan 22, 2020 at 4:59 AM Dan Čermák wrote: > > Felix Schwarz writes: > > > Am 21.01.20 um 21:48 schrieb Guido Aulisi: > >> I totally agree with Fabio, I can’t think of a single reason we should > >> dismiss > >> pagure. > > > > Gitlab is used by many free software communities like

Re: Git Forge Requirements: Please see the Community Blog

On Tuesday, January 21, 2020 9:57:59 PM MST Dan Čermák wrote: > Felix Schwarz writes: > > Am 21.01.20 um 21:48 schrieb Guido Aulisi: > >> I totally agree with Fabio, I can’t think of a single reason we should > >> dismiss pagure. > > > > Gitlab is used by many free software communities like

Re: Git Forge Requirements: Please see the Community Blog

Felix Schwarz writes: > Am 21.01.20 um 21:48 schrieb Guido Aulisi: >> I totally agree with Fabio, I can’t think of a single reason we should >> dismiss >> pagure. > > Gitlab is used by many free software communities like Freedesktop, Gnome, > Debian. Using the same tools could help to

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 3:13 pm, John M. Harris Jr wrote: Both Gitea and Gogs are potential options, in my opinion, both are lightweight and easy to extend. I have some experience with Gogs. I don't recommend it. ___ devel mailing list --

Re: Git Forge Requirements: Please see the Community Blog

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 bugs; the Pagure team has done a good job

Re: Git Forge Requirements: Please see the Community Blog

> >> And any discussion of GitHub isn't going to involve self-hosted, it's > >> going to involve GitHub.com, which means we're talking about losing > >> more of our independence as a project. This is one of those things > >> that I'm not sure is a wise move. > > > > Well since we have a request

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 5:14 PM John M. Harris Jr wrote: > > On Tuesday, January 21, 2020 2:31:47 PM MST Michael Catanzaro wrote: > > On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: > > > > > And any discussion of GitHub isn't going to involve self-hosted, it's > > > going to involve

Re: Git Forge Requirements: Please see the Community Blog

On Tuesday, January 21, 2020 2:31:47 PM MST Michael Catanzaro wrote: > On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: > > > And any discussion of GitHub isn't going to involve self-hosted, it's > > going to involve GitHub.com, which means we're talking about losing > > more of our

Re: Git Forge Requirements: Please see the Community Blog

On 1/21/20 4:59 PM, Felix Schwarz wrote: > (Though > I somehow got used to pagure and getting the gitlab integration to the same > level as pagure currently will be a lot of work for sure.) Maybe I'm just a grumpy old system admin but it sounds like a lot of work for little, if any, gain.

Re: Git Forge Requirements: Please see the Community Blog

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 Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

Re: Git Forge Requirements: Please see the Community Blog

Am 21.01.20 um 21:48 schrieb Guido Aulisi: > I totally agree with Fabio, I can’t think of a single reason we should dismiss > pagure. Gitlab is used by many free software communities like Freedesktop, Gnome, Debian. Using the same tools could help to facilitate inter-process/inter-distro

Re: Git Forge Requirements: Please see the Community Blog

On Tuesday, January 21, 2020 2:33:11 PM MST Neal Gompa wrote: > Unfortunately, this is very difficult to manage with GitLab Omnibus > based deployments The new plugin interface makes it so that this is not the case. I make use of it on git.splentity.com, for example. -- John M. Harris, Jr.

Re: Git Forge Requirements: Please see the Community Blog

- Original Message - > From: "Michael Catanzaro" > To: "Development discussions related to Fedora" > > Sent: Tuesday, January 21, 2020 4:31:47 PM > Subject: Re: Git Forge Requirements: Please see the Community Blog > > On Tue, Jan 21, 2020 a

Re: Git Forge Requirements: Please see the Community Blog

On 1/21/20 4:31 PM, Michael Catanzaro wrote: > On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: >> And any discussion of GitHub isn't going to involve self-hosted, it's >> going to involve GitHub.com, which means we're talking about losing >> more of our independence as a project. This is one

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 4:18 PM John M. Harris Jr wrote: > > On Tuesday, January 21, 2020 2:04:33 PM MST Neal Gompa wrote: > > Aside from GitLab being very anti-integration > > This is no longer the case, by the way. GitLab has recently made it easier to > add plugins, with the new method not

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: And any discussion of GitHub isn't going to involve self-hosted, it's going to involve GitHub.com, which means we're talking about losing more of our independence as a project. This is one of those things that I'm not sure is a wise move.

Re: Git Forge Requirements: Please see the Community Blog

On Tuesday, 21 January 2020 17:34:37 CET 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

Re: Git Forge Requirements: Please see the Community Blog

On Tuesday, January 21, 2020 2:04:33 PM MST Neal Gompa wrote: > Aside from GitLab being very anti-integration This is no longer the case, by the way. GitLab has recently made it easier to add plugins, with the new method not requiring patching the source tree. Even before that change, webhook

Re: Git Forge Requirements: Please see the Community Blog

I had replied to Fabio on IRC but... :-) - Original Message - > From: "Guido Aulisi" > To: "Development discussions related to Fedora" > > Sent: Tuesday, January 21, 2020 3:48:31 PM > Subject: Re: Git Forge Requirements: Please see the Community Blog

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 10:02 PM Leigh Griffin wrote: > > > > On Tue, Jan 21, 2020, 20:02 Fabio Valentini wrote: >> >> On Tue, Jan 21, 2020 at 8:30 PM Leigh Griffin wrote: >> > >> > >> > >> > On Tue, Jan 21, 2020, 17:17 Fabio Valentini wrote: >> >> >> >> On Tue, Jan 21, 2020 at 5:40 PM Leigh

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 3:01 PM Fabio Valentini wrote: > > On Tue, Jan 21, 2020 at 8:30 PM Leigh Griffin wrote: > > > > > > > > On Tue, Jan 21, 2020, 17:17 Fabio Valentini wrote: > >> > >> On Tue, Jan 21, 2020 at 5:40 PM Leigh Griffin wrote: > >> > > >> > Hey Everyone, > >> > > >> > On behalf

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020, 20:02 Fabio Valentini wrote: > On Tue, Jan 21, 2020 at 8:30 PM Leigh Griffin wrote: > > > > > > > > On Tue, Jan 21, 2020, 17:17 Fabio Valentini > wrote: > >> > >> On Tue, Jan 21, 2020 at 5:40 PM Leigh Griffin > wrote: > >> > > >> > Hey Everyone, > >> > > >> > On behalf

Re: Git Forge Requirements: Please see the Community Blog

> Il giorno 21 gen 2020, alle ore 18:15, Fabio Valentini > ha scritto: > > 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

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020 at 8:30 PM Leigh Griffin wrote: > > > > On Tue, Jan 21, 2020, 17:17 Fabio Valentini wrote: >> >> 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

Re: Git Forge Requirements: Please see the Community Blog

On Tue, Jan 21, 2020, 17:17 Fabio Valentini wrote: > 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: > >

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

Git Forge Requirements: Please see the Community Blog

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 requirements in an open and transparent manner on the future of a git

<    1   2