On Mon, Mar 30, 2020 at 3:07 PM Fabio Valentini <decathorpe@xxxxxxxxx> wrote:
On Mon, Mar 30, 2020 at 4:00 PM Leigh Griffin <lgriffin@xxxxxxxxxx> wrote:
>
>
>
> On Mon, Mar 30, 2020 at 2:01 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
>>
>> On 30. 03. 20 14:13, Neal Gompa wrote:
>> > And unlike Alioth, we have*serious*
>> > integration across the board with Pagure, and a good chunk of it is
>> > not possible to implement in GitLab. Features we have in here were
>> > designed to meet the needs of Fedorans that we will be forced to give
>> > up.
>>
>> I want to stress out that recently we even got more of it. Several years after
>> the PackageDB sunset, we are finally getting to a matching packager experience.
>>
>> (For example with the Bugzilla default assignee or the unorphan/unretire buttons.)
>>
>> Is this going to be possible with GitLab?
(snip)
>
>
> I don't have an answer to this as we haven't done that deep level of tooling analysis and integration analysis yet.
So you're basically saying that you've decided for GitLab (despite the
fedora community obviously preferring pagure - whether you received
that message or not),
It was not a formal requirement.
and you have not even looked at what that will
mean?
We have looked into the capabilities of it to inform our decision but not at a granular tooling level.
And if it turns out that GitLab can't deliver some features you
want, and not satisfy some "stakeholder user stories"?
Not all requirements can be satisfied in totality, we knew this before we began and Gitlab satisfies the majority of the requirements needed.
Am I crazy, or shouldn't have those problems have been taken into
account *before* such a big decision is made?
Your responses sound like "we made our decisions, and now we'll stick
to them no matter what happens".
Like any technology decision that we as a team choose, we can revert our decision if the service is not working as intended and not satisfying our needs. Right now, we are proceeding with Gitlab as our choice.
And honestly, I shouldn't have expected anything else from this "kill
pagure project".
Pagure was a viable choice and several hundred person hours went into informing us of this decision because of how critical it was to get right.
The way the fedora community - and the pagure project - are and were
treated here is shameful, and you're going to lose fedora contributors
because of it.
Fabio
>
>>
>> Will CPE implement this before we
>> switch, or will GitLab be dumped on us and we will do toothless FESCo approved
>> statements, such as "Missing Pagure features should be re-implemented in
>> GitLab"?
>
>
> CPE will take on a lot of the tooling work to ease the migration.
>
>>
>> What measures will be taken to prevent yet another "open a releng
>> ticket and a human will do this while we automate stuff" era?
>>
>> --
>> Miro Hrončok
>> --
>> Phone: +420777974800
>> IRC: mhroncok
>> _______________________________________________
>> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> --
>
> Leigh Griffin
>
> Engineering Manager
>
> Red Hat Waterford
>
> Communications House
>
> Cork Road, Waterford City
>
> lgriffin@xxxxxxxxxx
> M: +353877545162 IM: lgriffin
>
> @redhatjobs redhatjobs @redhatjobs
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Leigh Griffin
Engineering Manager
Communications House
Cork Road, Waterford City
lgriffin@xxxxxxxxxx
M: +353877545162 IM: lgriffin
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
