#3248 Git Forge Evaluation FESCo Rep(s)
Closed: Accepted by sgallagh. Opened by amoloney.

Hi FESCo,

I along with @humaton are nailing down the Git Forge Evaluation project work this week in order to:

  • Have up to date information to share with Fedorans at the Git Forge talk @ Flock on the project details
  • Be able to build on momentum (hopefully) gained at Flock and execute on a project plan with milestones to work against

FESCo is one of the main stakeholder groups (yes, arguably all of Fedora is a stakeholder, but thats too big a group so I need to have a smaller set of folks to represent wider needs) and I would like you to nominate someone, or someones, to be a point of contact for FESCo in a RACI matrix for the project.

I would suggest someone other than @humaton , as he is already heavily involved and leading the main investigation.

QA have nominated someone to be a point of contact for their group, and I will be requesting council and packaging committee nominate someone also.

Expected engagement is not set, but the minimum would be that this person, or persons, would take a keen interest in the investigation work and its outputs (coming v.soon) for FESCo, be available to work with the investigation team from time to time when they have questions, and be a point of contact/reference on the public project plan I am working on for the overall evaluation.

This is not a decision-maker request. This is a point of contact/link person request.

Thanks!
Aoife


We should probably discuss this at the weekly meeting

Metadata Update from @salimma:
- Issue tagged with: meeting

I'll volunteer for this, though I'll note up-front that I have a bit of a built-in bias towards Gitlab because I've been administering it for CentOS Stream for the last few years. I'll try to keep an open mind about alternatives, though.

This will be discussed during today's meeting.

AGREED: Stephen Gallagher is approved as FESCo rep for the Git Forge Evaluation project (+8, 0, 0)

Metadata Update from @zbyszek:
- Issue untagged with: meeting
- Issue tagged with: document it

Folks, I set document it label, but looking into this, I don't think we should do that. Looking at our docs, the only position we document, is Fedora Council Engineering Rep, which is a permanent position with a bunch of additional policy. Stephen's delegation is temporary, since the evaluation project is temporary. Thus, I propose to just close this as "accepted".

Metadata Update from @zbyszek:
- Issue untagged with: document it

Metadata Update from @sgallagh:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Metadata