Intent to start ARC investigation git-forge replacement

[Tomas Hrcka]

Hello, Fedora community,

Following on from the Fedora Council's decision to investigate Forgejo
and GitLab as potential replacements[1], the Community Platform
Engineering team will start an ARC[2] investigation to compare
proposed alternatives for current pagure use cases.
The council has defined some broad requirements for the team to
consider during this investigation. But we would like inputs from all
gitforge user groups in our community.
So, if you have a specific use case or workflow, share it with us in
the form of a user story in this ticket[6], or consider joining the
ARC team for this investigation.

High-level overview of investigation requirements by the council:

 1. Suitability for dist-git and src.fedoraproject.org replacement

 2. Suitability for replacement of Bugzilla for packaging issues and
review process

 3. Suitability for replacement of Pagure and Bugzilla for release
issues (change process, blocker bugs, etc)
     * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
     * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

 4. Suitability for replacement of Pagure for SIG and Team ticket
tracking (e.g. FESCo tracker)

 5. Cost of hosting and maintenance (hardware + time and resources
from CPE and wider infrastructure team)

 6. Ease of migration from current Pagure, GitHub, and GitLab

 7. Ease of extension and enhancement — can we improve things
ourselves to add missing features/features that are cool and useful
like CI integration?

 8. New features like Asciidoc support, Online editor, and others to
make things easier for the Fedora teams and their workflows.

 9. Estimate Future risk for Fedora project and Infrastructure team
    1. Long-term project vision
    2. Platform SMEs in the Fedora Infrastructure team and the wider community

These requirements do not represent feature sets, but rather a
high-level overview of our current use cases.
CPE has already done some initial mapping of how our current
applications interact with distgit[3] and if we have missed anything,
please let folks know in a thread on discussions.fp.o[4].

The aim of this investigation will not be to pick one solution or the other,
but instead, focus on providing the Fedora Council and decision
makers[5] with an extensive comparison of the two.


For discussion about the purpose of this investigation please use the
discussions.fp.o thread[7]

The ARC investigation will commence in early May.



[1] - https://communityblog.fedoraproject.org/2024-git-forge-evaluation/
[2] - https://fedora-arc.readthedocs.io/en/latest/index.html
[3] - https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html#inte...
[4] - https://discussion.fedoraproject.org/t/dist-git-decoupling-investigation/...
[5] - https://pagure.io/Fedora-Council/tickets/issue/488
[6] - https://pagure.io/fedora-infra/arc/issue/164
[7] - https://discussion.fedoraproject.org/t/arc-git-forge-investigation/114018

Tomas Hrcka
Cat herder at Community Platform Engineering team
fas: humaton
libera.CHAT: jednorozec
matrix: @humaton:fedora.im
--
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
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/[e-mail]...
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Akashdeep Dhar]

Hello folks,

It has been a couple of weeks since Tomas announced the requirements gathering phase and
till now we have received about nine of those - all from Maxwell G (by the way, thanks for
your inputs) in the Fedora ARC issue ticket[1].

I want to bump this up to folks' attention and ensure we account for as many usecase
requirements as possible. Please take some time and let us know about it as comments under
the ticket - multiple comments are totally fine.

If you agree with the usecase requirements mentioned in someone else's comment, please
use the reactions to let us know of the importance of the same. Please take until 29th May
2024 to communicate your requirements with us.

As always, this thread can be responded to if you have any questions or concerns.

Index
[1] - https://pagure.io/fedora-infra/arc/issue/164

Regards,
Akashdeep Dhar (he/him),
Red Hat Community Platform Engineering
Elected Representative, Fedora Council
t0xic0der(a)fedoraproject.org
akashdeep(a)redhat.com
TZ = Asia/Kolkata (UTC+05:30)

[Stephen Smoogen]

On Wed, 8 May 2024 at 10:17, Akashdeep Dhar <akashdeep.dhar(a)gmail.com&gt;
wrote:

>  Hello folks,
>
>  It has been a couple of weeks since Tomas announced the requirements
>  gathering phase and till now we have received about nine of those - all
>  from Maxwell G (by the way, thanks for your inputs) in the Fedora ARC issue
>  ticket[1].
>
>  I want to bump this up to folks' attention and ensure we account for as
>  many usecase requirements as possible. Please take some time and let us
>  know about it as comments under the ticket - multiple comments are totally
>  fine.
>
>  
It is going to be hard to make 'requirements' without knowing what is
being
done now and where with the current pagure system. A lot of functionality
has been built in over a decade or so of improvements, and would only show
up as 'oh we really required this' when comparing a built example of
GitForge2 to current GitForge. Only a couple of people are going to know
the internals of say fedpkg, pagure, packaging internals to speak to what
is a 'requirement'. Most people are going to expect that 'whoever knows
that' is going to answer, which then tends to be few answers at all. Having
some sort of framework around what is expected can help elicit clearer
input (especially when you leave out things and the usual suspects rattle
on about 'clearly you have no idea how this works because you forgot
about...')



>  If you agree with the usecase requirements mentioned in someone
> else's
>  comment, please use the reactions to let us know of the importance of the
>  same. Please take until 29th May 2024 to communicate your requirements with
>  us.
>
>  As always, this thread can be responded to if you have any questions or
>  concerns.
>
>  Index
>  [1] - https://pagure.io/fedora-infra/arc/issue/164
>
>  Regards,
>  Akashdeep Dhar (he/him),
>  Red Hat Community Platform Engineering
>  Elected Representative, Fedora Council
>  t0xic0der(a)fedoraproject.org
>  akashdeep(a)redhat.com
>  TZ = Asia/Kolkata (UTC+05:30)
>  --
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>  Do not reply to spam, report it:
>  https://pagure.io/fedora-infrastructure/new_issue
>  

-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren

[Kamil Paral]

On Wed, Apr 24, 2024 at 5:30 PM Tomas Hrcka <thrcka(a)redhat.com&gt; wrote:

>  So, if you have a specific use case or workflow, share it with us in
>  the form of a user story in this ticket[6], or consider joining the
>  ARC team for this investigation.
>  
Tomas, the email title and the referenced ticket only talk about "git
forge", but your description also talks about Bugzilla replacement. So
should we also mention Bugzilla-related requirements in that ticket? (As
QA, we might have a lot of those).

Also, what is the deadline for providing the requirements?

Should we separate the requirements into "must have" and "nice to
have"?

[Sérgio Basto]

On Tue, 2024-04-23 at 12:06 +0200, Tomas Hrcka wrote:
>   1. Suitability for dist-git and src.fedoraproject.org replacement
Can someone explain me what is the problem of pagure ? 

please join to 
https://discussion.fedoraproject.org/t/2024-git-forge-evaluation/111795/20

Thanks 
-- 
Sérgio M. B.

[Peter Robinson]

On Thu, 16 May 2024 at 13:29, Sérgio Basto <sergio(a)serjux.com&gt; wrote:
>  On Tue, 2024-04-23 at 12:06 +0200, Tomas Hrcka wrote:
>  >  1. Suitability for dist-git and src.fedoraproject.org replacement
>
>  Can someone explain me what is the problem of pagure ? 
There's been a lot of discussions about it. I believe some of the main
problems are is it's basically unmaintained, it's not adding useful
features and as a result is an overall burden for those running it.

> please join to
> https://discussion.fedoraproject.org/t/2024-git-forge-evaluation/111795/20
>
> Thanks
> --
> Sérgio M. B.
> --
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Robby Callicotte]

On Monday, May 20, 2024 7:40:51 AM CDT Peter Robinson wrote:
>  On Thu, 16 May 2024 at 13:29, Sérgio Basto <sergio(a)serjux.com&gt;
> wrote:
>  
>  >
>  >
>  > On Tue, 2024-04-23 at 12:06 +0200, Tomas Hrcka wrote:
>  > 
>  > >  1. Suitability for dist-git and src.fedoraproject.org replacement
>  >
>  >
>  >
>  > Can someone explain me what is the problem of pagure ?
>  
>  
>  There's been a lot of discussions about it. I believe some of the main
>  problems are is it's basically unmaintained, it's not adding useful
>  features and as a result is an overall burden for those running it.
>  
>  
>  > please join to
>  > https://discussion.fedoraproject.org/t/2024-git-forge-evaluation/111795/20
>  > 
>  >
>  >
>  >
>  > Thanks
>  > --
>  > Sérgio M. B.
>  > --
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > 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/[e-mail].o
>  > rg Do not reply to spam, report it:
>  > https://pagure.io/fedora-infrastructure/new_issue
>  --
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>  Do not reply to spam, report it:
>  https://pagure.io/fedora-infrastructure/new_issue 
Pagure is still under active development.  There was a flurry of commits in 
April.

--Robby