ARC: Git-forge investigation

Project Discussion
,
1

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)

  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.

1 Like
2

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.

It seems that references [3] and [5] are missing.

I understand the link before reference [4], but I wonder if that
reference meant another thing.

3

I would like to volunteer to help with this investigation, but I am unfamiliar with the process. How can I contribute?

I have a lot of experience with GitLab (as a user, administrator, consultant, …).

4

I too would like to be part of this investigation, or at least be able to voice my thoughts in a constructive way.

5

Hello all, sorry for the late reply but there was a whirl of planned and unplanned time off on my side.

I am not sure how edits work on this platform, but meanwhile, all the links can be found in the original message on mailing lists

We started the weekly sync meeting at 8:30 UTC on Wednesdays.
We have chosen this time because currently, people working on this are in the EU and Indian time zones.

If you are still interested in helping out please pick a time and day of the week. Times are in UTC.

  • 10:00
  • 11:00
  • 12:00
  • 13:00
  • 14:00
  • 15:00
  • 16:00
  • 17:00
  • 18:00
  • 19:00
0 voters

And the Day that suits you

  • Monday
  • Tuesday
  • Wednesday
  • Thursday
  • Friday
0 voters

Are you willing to use Google Meet?

  • Yes
  • Please use jitsi
0 voters