On Tue, Oct 29, 2019 at 6:30 AM Clement Verna <[email protected]>
wrote:

>
>
> On Mon, 28 Oct 2019 at 18:42, Kevin Fenzi <[email protected]> wrote:
>
>> On Fri, Oct 25, 2019 at 02:33:02PM -0400, Randy Barlow wrote:
>> > On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote:
>> > > I think the main reason why we don't already have it on Pagure is
>> > > that we don't want to be dependent of our own infrastructure to host
>> > > this repo. It currently lives on the batcave01 host which is the box
>> > > we use to deploy our infrastructure. So to me if we are going to host
>> > > this repository on a git forge I think using an external service
>> > > would make sense.
>>
>> I don't agree, unless we move/have all/more of our presense there.
>>
>
>> ie, I don't want to move just the fedora infrastructure ansible repo to
>> say gitlab and have it there by itself. I think thats really poor for
>> discoverability, etc.
>>
>
> Yes I agree with you.
>

Please forgive the "new guy" ignorance, but I'm trying to understand why
Fedora Infrastructure wouldn't want to host its project on Fedora Pagure.
Shouldn't we eat our own dog food?

>
>
>>
>> ...snip...
>>
>> > > After I am not really interested in a long debate in regards of where
>> > > that repo should be hosted, to me what matters is that we should have
>> > > the Fedora Community in only one place be it GitLab like the Gnome
>> > > community or GitHub where we already have fedora-infra, fedora-cloud,
>> > > fedora CoreOS.
>>
>> Yeah, but any such move will be a long debate I fear.
>>
>
And open debate is just one of the benefits of open source. I'm learning
from this discussion which is why I joined the project.

>
>> >
>> > Yeah GitHub and GitLab are both great.
>>
>> Well, from a end user perspective, yes.
>>
>> There are ideological issues with both, github isn't open source, gitlab
>> is open core and has been making odd decisions of late (see the 'we are
>> going to collect metrics on everything" and "we don't drop customers due
>> to their political views").
>>
>> But to get back to the initial question here...
>>
>> It sounds like adding the hook now as things are doesn't make too much
>> sense? Althought we could run a daily report or something that points
>> out issues after they have been commited (so at least we fix it).
>>
>
+1

>
>> Short term, I'm very keen to have ansible repo PR's. So, perhaps we
>> could work something to move it to pagure soon (either repospanner if we
>> can handle the performance, or just git on pagure we mirror some way)?
>> Happy to discuss this in our meeting thursday? or some other time.
>>
>
> +1
>
 +1

>
>> Longer term, yeah, we may want to move to gitlab/github, but I don't
>> think the ansible repo is something I want to be a scout or outlyer, I'd
>> want us to have a plan and move things in a coordinated way. I think
>> thats a bigger discussion we need to have.
>>
>
> +1
>
+1

>
>
>> kevin
>> _______________________________________________
>> infrastructure mailing list -- [email protected]
>> To unsubscribe send an email to
>> [email protected]
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/[email protected]
>>
> _______________________________________________
> infrastructure mailing list -- [email protected]
> To unsubscribe send an email to
> [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
>
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to