2025-02-26 15:05:09 <@amoloney:fedora.im> !startmeeting Fedora Council 
2025-02-26 15:05:10 <@meetbot:fedora.im> Meeting started at 2025-02-26 15:05:09 UTC
2025-02-26 15:05:10 <@meetbot:fedora.im> The Meeting name is 'Fedora Council '
2025-02-26 15:05:38 <@amoloney:fedora.im> !topic roll call
2025-02-26 15:05:40 <@amoloney:fedora.im> !hi
2025-02-26 15:05:40 <@mattdm:fedora.im> !hi
2025-02-26 15:05:42 <@zodbot:fedora.im> Aoife Moloney (amoloney)
2025-02-26 15:05:42 <@zodbot:fedora.im> Matthew Miller (mattdm) - he / him / his
2025-02-26 15:05:43 <@dcantrell:fedora.im> !hi
2025-02-26 15:05:45 <@zodbot:fedora.im> David Cantrell (dcantrell) - he / him / his
2025-02-26 15:05:52 <@jonatoni:fedora.im> !hi
2025-02-26 15:05:53 <@zodbot:fedora.im> Jona Azizaj (jonatoni) - she / her / hers
2025-02-26 15:06:17 <@jbrooks:matrix.org> !hi jasonbrooks
2025-02-26 15:06:19 <@zodbot:fedora.im> Jason Brooks (jasonbrooks) - he / him / his
2025-02-26 15:07:42 <@asamalik:fedora.im> hi!
2025-02-26 15:07:43 <@asamalik:fedora.im> !hi
2025-02-26 15:07:44 <@zodbot:fedora.im> Adam Samalik (asamalik) - he / him / his
2025-02-26 15:08:41 <@amoloney:fedora.im> I think were waiting on JWW (@jflory7) [away until 2025-02-25] and bookwar 
2025-02-26 15:08:49 <@amoloney:fedora.im> They will join when they can Im sure :)
2025-02-26 15:08:54 <@amoloney:fedora.im> !topic Agenda
2025-02-26 15:09:21 <@amoloney:fedora.im> !topic Hackfest Summaries Check-in
2025-02-26 15:09:59 <@amoloney:fedora.im> some of us have some summary writing to do, this is a reminder moreso https://discussion.fedoraproject.org/t/council-meeting-2025-02-26/146104
2025-02-26 15:10:15 <@mattdm:fedora.im> we should probably actually include the agenda? :)
2025-02-26 15:10:34 <@amoloney:fedora.im> Its in the discussion post, but fiiiiine :d
2025-02-26 15:10:38 <@amoloney:fedora.im> Its in the discussion post, but fiiiiine :p
2025-02-26 15:11:08 <@mattdm:fedora.im> it will make the meetbot summary nicer
2025-02-26 15:12:06 <@amoloney:fedora.im> !info The agenda topics today are a check in on the hackfest summaries, the git forge update, and any other business council members want to discuss
2025-02-26 15:12:14 <@jflory7:fedora.im> !hi
2025-02-26 15:12:18 <@zodbot:fedora.im> Justin W. Wheeler (jflory7) - he / him / his
2025-02-26 15:12:20 <@jflory7:fedora.im> Sorry, had a brief internet outage
2025-02-26 15:13:40 <@amoloney:fedora.im> The 'how we work' summary is published https://discussion.fedoraproject.org/t/council-f2f-hackfest-2025-summaries-how-the-council-works/145310
2025-02-26 15:14:20 <@zodbot:fedora.im> jflory7 has already given cookies to amoloney during the F41 timeframe
2025-02-26 15:14:37 <@amoloney:fedora.im> The AI policy draft is also out https://discussion.fedoraproject.org/t/ai-policy-in-fedora-wip/144297/4
2025-02-26 15:15:02 <@amoloney:fedora.im> I have an action to write up one covering the other policy conversations - Legal DEI Event, etc
2025-02-26 15:15:14 <@amoloney:fedora.im> mattdm: you are on strategy
2025-02-26 15:15:20 <@amoloney:fedora.im> JWW (@jflory7) [away until 2025-02-25]: you are on budget
2025-02-26 15:15:34 <@amoloney:fedora.im> Sumantro Mukherjee: is taking mindshare
2025-02-26 15:15:35 <@jflory7:fedora.im> Is there a deadline?
2025-02-26 15:15:43 <@amoloney:fedora.im> and afaik they are the big ticket items covered
2025-02-26 15:15:58 <@amoloney:fedora.im> Ideally we have these all written up over the next 2-3 weeks max
2025-02-26 15:16:06 <@mattdm:fedora.im> I intend to have at least a useful draft by the end of the week. You can quote me on that.
2025-02-26 15:16:14 <@amoloney:fedora.im> were in week 3 since we met so its getting stale otherwise
2025-02-26 15:16:41 <@mattdm:fedora.im> yeah. guilty as charged :)
2025-02-26 15:16:47 <@amoloney:fedora.im> I also have an action to create action items for everyone who put their hand up for things in individual tickets. I have not forgotten, I just have not done it yet 
2025-02-26 15:16:50 <@jflory7:fedora.im> I will probably have to punt mine until March, I have a lot of family health issues going on and I also am trying to keep up with Flock and routine budgeting work
2025-02-26 15:17:13 <@jbrooks:matrix.org> At Scale there's a Fedora/CentOS classroom Shaun and I are doing, and I'm set to talk about Fedora for like 10 min to start -- I'd like to touch on the 4 strategic initiatives in that
2025-02-26 15:17:56 <@jflory7:fedora.im> Might also consider asking some of the Fedora Ambassadors in #event-scale:fedoraproject.org if they want to get involved, but I know this is off-topic for this meeting right now. The four initiatives sound good to me
2025-02-26 15:18:05 <@amoloney:fedora.im> As a reminder, these are summaries of the conversations we had, and not when the work we identified as being needed to be done should be completed by
2025-02-26 15:18:24 <@amoloney:fedora.im> When is Scale?
2025-02-26 15:18:32 <@jflory7:fedora.im> Next week πŸ™‚ 
2025-02-26 15:18:50 <@amoloney:fedora.im> mattdm:  you up for the challenge to have a summary in place for then??
2025-02-26 15:18:54 <@jbrooks:matrix.org> That's just to say, I'll be paying attn to mattdm's end of week πŸ™‚
2025-02-26 15:19:05 <@mattdm:fedora.im> Sounds fair!
2025-02-26 15:19:40 <@amoloney:fedora.im> then i will make an agreed statement that the next summary is on strategy items and itll go on discourse by the end of this week?
2025-02-26 15:19:44 <@mattdm:fedora.im> I will start the draft from the end and work backwards, so the pragmatic initiative summaries are first priority
2025-02-26 15:20:17 <@mattdm:fedora.im> I will commit to a decent draft in the working space by the end of the week. not necessarily publication
2025-02-26 15:21:26 <@amoloney:fedora.im> !agreed mattdm will draft a summary of the strategy conversation by the end of February (Friday 28th) for review on discourse
2025-02-26 15:21:50 <@amoloney:fedora.im> !topic Git Forge Update
2025-02-26 15:22:20 <@amoloney:fedora.im> We now have an official proposal for the git forge replacement as a community initiative
2025-02-26 15:22:27 <@amoloney:fedora.im> !info We now have an official proposal for the git forge replacement as a community initiative
2025-02-26 15:22:33 <@amoloney:fedora.im> !link https://pagure.io/Fedora-Council/tickets/issue/485
2025-02-26 15:22:47 <@dcantrell:fedora.im> yes, but have we really given enough consideration to going back to cvs?
2025-02-26 15:23:07 <@mattdm:fedora.im> is that the right link?
2025-02-26 15:23:18 <@amoloney:fedora.im> no its not :(
2025-02-26 15:23:27 <@amoloney:fedora.im> !link https://pagure.io/Fedora-Council/tickets/issue/525
2025-02-26 15:23:46 <@mattdm:fedora.im> Nice.
2025-02-26 15:23:53 <@amoloney:fedora.im> Sweet baby jebas this is hard work today
2025-02-26 15:23:55 <@jflory7:fedora.im> Pagure is working for me
2025-02-26 15:24:04 <@jflory7:fedora.im> !link https://pagure.io/Fedora-Council/tickets/issue/525
2025-02-26 15:24:07 <@amoloney:fedora.im> https://fedoraproject.org/wiki/Objectives/Git_Forge_Initiative_2025
2025-02-26 15:24:16 <@jflory7:fedora.im> !link https://fedoraproject.org/wiki/Objectives/Git_Forge_Initiative_2025
2025-02-26 15:24:49 <@amoloney:fedora.im> Im requesting we vote on approving this proposal....or not (?)
2025-02-26 15:25:20 <@jflory7:fedora.im> I may have just renamed the wiki page πŸ˜› https://fedoraproject.org/wiki/Initiatives/Git_Forge_Initiative_2025
2025-02-26 15:25:22 <@amoloney:fedora.im> If approved, I volunteer as executive sponsor for the initiative for the council
2025-02-26 15:25:38 <@amoloney:fedora.im> ryanlerch: is initiative lead
2025-02-26 15:25:46 <@mattdm:fedora.im> In keeping with our "be more strict with initiatives" outcome from the hackfest, do we feel that the plan and milestones are detailed enough here?
2025-02-26 15:25:56 <@jflory7:fedora.im> They are not
2025-02-26 15:26:20 <@jflory7:fedora.im> I don't think we need to force something into a logic model if it does not make sense, but the the plan section and the milestones and timeframe section need to be more tightly bound
2025-02-26 15:26:21 <@amoloney:fedora.im> No, they need more work for sure, so I can take that back to the initiative lead and team to request they refine it more
2025-02-26 15:26:51 <@mattdm:fedora.im> _after_ I'm done with the other thing I committed to, I can help with the logic model part if necessary
2025-02-26 15:26:56 <@amoloney:fedora.im> i don have two clarifications needed from the team for us council people though as well
2025-02-26 15:27:08 <@jflory7:fedora.im> When will Forgejo be deployed? Is F42 GA release, or is it initial availability? When will dist-git packages be migrated approximately? Is there a window planned for testing? Have we talked about doing Test Weeks for different milestones?
2025-02-26 15:27:10 <@mattdm:fedora.im> But we should also give some better guidance than "make it better"
2025-02-26 15:27:14 <@jflory7:fedora.im> When is Pagure decommissioned?
2025-02-26 15:27:21 <@jflory7:fedora.im> What are the backend tools being developed?
2025-02-26 15:27:27 <@amoloney:fedora.im> This is very good
2025-02-26 15:27:30 <@jflory7:fedora.im> What about fedora-messaging?
2025-02-26 15:27:34 <@jflory7:fedora.im> Will Badges be supported?
2025-02-26 15:27:41 <@jflory7:fedora.im> We should make sure the broken Pagure badges are ported over to Forgejo
2025-02-26 15:27:48 <@jflory7:fedora.im> It will be an added incentive for people to adopt the new platform
2025-02-26 15:27:58 <@dcantrell:fedora.im> https://www.youtube.com/watch?v=Dg7P5nVAvjA
2025-02-26 15:28:33 <@jflory7:fedora.im> I am -1 to the proposal as written because it gives me more questions than answers. Of course, I want this to be a successful proposal and I want to see it go through, so I just want to see a revision with some of these key questions addressed
2025-02-26 15:28:46 <@farchord:fedora.im> JWW (@jflory7) [away until 2025-02-25]: "_What exactly_ will get migrated over to Forgejo?"
2025-02-26 15:28:50 <@jflory7:fedora.im> Otherwise, we will lose a lot of time answering these questions in the community.
2025-02-26 15:28:59 <@mattdm:fedora.im> Maybe -- Justin and Aoife, can you collaborate on "what more we need?" to take to Ryan (and to work on!), hopefully so we can approve by next week's meeting?
2025-02-26 15:28:59 <@jflory7:fedora.im> Yep, breaking it down into smaller pieces is key
2025-02-26 15:29:17 <@jflory7:fedora.im> I really have to say no because I am overburdened right now and might have to take additional days off in the coming weeks
2025-02-26 15:29:20 <@amoloney:fedora.im> In the earlier meeting, I and the folks doing the work were talking about how to roll out this initiative better so this is very good feedback to get and bring back to the team
2025-02-26 15:29:28 <@mattdm:fedora.im> fair
2025-02-26 15:29:42 <@amoloney:fedora.im> I can take it, Justin did a lot of the work already with the prompts :D
2025-02-26 15:30:02 <@mattdm:fedora.im> Anyone else want to help?
2025-02-26 15:30:12 <@amoloney:fedora.im> Ill pull the questions JWW (@jflory7) [away until 2025-02-25] asked from this meeting to be addressed
2025-02-26 15:30:49 <@farchord:fedora.im> We may need a place to submit bugs/issues with Forgejo (There might already be one)
2025-02-26 15:30:58 <@farchord:fedora.im> may it be in Matrix or in pagure/forgejo
2025-02-26 15:31:02 <@jflory7:fedora.im> I also think a logic model might not fit for _every_ Initiative. Like, I really want a clearly documented roadmap more than I want to understand the logic. We have been talking about the logic for maybe five years now πŸ˜› 
2025-02-26 15:31:08 <@mattdm:fedora.im> definitely
2025-02-26 15:31:11 <@jflory7:fedora.im> I want a roadmap with clear deadlines, milestones, and a tight timeline
2025-02-26 15:31:18 <@jflory7:fedora.im> Room for flexibility, of course
2025-02-26 15:31:21 <@farchord:fedora.im> Agreed
2025-02-26 15:31:21 <@jflory7:fedora.im> But like, give us some dates pls
2025-02-26 15:31:41 <@jflory7:fedora.im> Or even Fedora release cycles
2025-02-26 15:31:49 <@farchord:fedora.im> I'm assuming F44+ lol
2025-02-26 15:31:54 <@dcantrell:fedora.im> dates and specifically the order of operations, but also contingency  plans.  what happens if a step fails or encounters a major problem
2025-02-26 15:31:59 <@jflory7:fedora.im> An Initiative can run for maximum three Fedora release cycles
2025-02-26 15:32:04 <@jflory7:fedora.im> So that is something to consider too
2025-02-26 15:32:18 <@mattdm:fedora.im> I expect that a lot of the specific work will be executed as a series of Changes. It would be nice to list the anticipated proposals and their timing.
2025-02-26 15:32:21 <@jflory7:fedora.im> (in terms of building a roadmap and timeline, because I understand absolute dates are very hard for a complex project like this)
2025-02-26 15:32:23 <@amoloney:fedora.im> So in the proposal, points 2 - 5 are going to be change proposals to FESCo
2025-02-26 15:32:41 <@jflory7:fedora.im> Yesssss, I would love it so much if this included Change proposal proposals πŸ˜› 
2025-02-26 15:32:44 <@dcantrell:fedora.im> ok, good
2025-02-26 15:32:52 <@jflory7:fedora.im> Really, this is how technical work in the distro should be driven, through a series of Changes
2025-02-26 15:32:56 <@dcantrell:fedora.im> the change proposals can get in to the weeds then
2025-02-26 15:32:58 <@jflory7:fedora.im> The Initiative is just like a big container bin to catch them all
2025-02-26 15:33:04 <@conan_kudo:matrix.org> does that mean the bootc initiative is ending then?
2025-02-26 15:33:06 <@mattdm:fedora.im> exactly!
2025-02-26 15:33:12 <@farchord:fedora.im> Before those changes are submitted, you prolly also need to delegate teams/people to each tasks so they're not just a bunch of empty promises XD
2025-02-26 15:33:21 <@dcantrell:fedora.im> but not an immutable container
2025-02-26 15:33:25 <@amoloney:fedora.im> Point 1 is a deployment and is not touching fedora linux as we know it, but the rest all need  more planing and sign off 
2025-02-26 15:33:30 <@mattdm:fedora.im> yes. we need to wrap that up, and plan to have something related to replace it.
2025-02-26 15:33:31 <@jflory7:fedora.im> I defer this one to Jason Brooks πŸ™‚ Or you could ask him at SCaLE for the full scoop next week
2025-02-26 15:33:44 <@jflory7:fedora.im> +1
2025-02-26 15:33:54 <@jbrooks:matrix.org> It was set to be one year, and that'll be in May
2025-02-26 15:33:56 <@farchord:fedora.im> You'Re assuming that neal is going to scale! :P
2025-02-26 15:34:01 <@nhanlon:beeper.com> wooo scale!
2025-02-26 15:34:16 <@jflory7:fedora.im> Hahah. No, Initiatives definitely need to be mutable. An immutable Initiative would never survive the Fedora Project πŸ˜› 
2025-02-26 15:34:47 <@jflory7:fedora.im> I am, but precedent gives me some added weight in that assumption πŸ˜› 
2025-02-26 15:34:47 <@conan_kudo:matrix.org> considering I spent all the money for plane tickets and hotel, I sure as heck hope I'm going
2025-02-26 15:35:01 <@jflory7:fedora.im> Anywayssssss…
2025-02-26 15:35:05 <@farchord:fedora.im> lol
2025-02-26 15:35:05 <@jbrooks:matrix.org> ppl can weigh in at https://gitlab.com/fedora/bootc/tracker/-/issues/62
2025-02-26 15:35:05 <@amoloney:fedora.im> I need to pull us back to the topic at hand please  - Git forge proposal
2025-02-26 15:35:07 <@jflory7:fedora.im> Not to get too far off the Git Forge Initiative path here
2025-02-26 15:35:15 <@jflory7:fedora.im> Aoife Moloney: Any next steps here other than the feedback?
2025-02-26 15:35:30 <@amoloney:fedora.im> yes i have some feedback from the team for US to guide please
2025-02-26 15:35:32 <@jflory7:fedora.im> I would love if the Initiative owners could give us changes by the next Council meeting in 2 weeks
2025-02-26 15:35:39 <@jflory7:fedora.im> That is my wish list
2025-02-26 15:35:49 <@jflory7:fedora.im> These meetings are good forums to discuss and get wider feedback on Initiative proposals
2025-02-26 15:36:00 <@jflory7:fedora.im> And of course, log an official vote
2025-02-26 15:36:13 <@amoloney:fedora.im> Thats somewhat doable. The change proposals may not be available all  together though as they will take time to architecturally create
2025-02-26 15:36:28 <@amoloney:fedora.im> but a more fleshed out initiative proposal is doable
2025-02-26 15:36:54 <@amoloney:fedora.im> once I fix the page to describe what are the requirements for initiatives to meet when submitting
2025-02-26 15:36:54 <@jflory7:fedora.im> Yep, that is all I want
2025-02-26 15:36:58 <@amoloney:fedora.im> its one big loop ha
2025-02-26 15:37:22 <@jflory7:fedora.im> Happy to review a MR. I am slowly iterating on some of the old docs tickets we have, ahead of our own move to Forgejo
2025-02-26 15:37:33 <@jflory7:fedora.im> (which BTW, we should totally be one of the first groups to migrate and be a leader in using the new platform)
2025-02-26 15:37:40 <@jflory7:fedora.im> (when the time is right)
2025-02-26 15:37:54 <@jflory7:fedora.im> This is also related to my other agenda topic I hope we can cover today πŸ™‚ 
2025-02-26 15:38:13 <@amoloney:fedora.im> so speaking of that....here is the first clarification the forgejo development team needs from council
2025-02-26 15:39:03 <@amoloney:fedora.im> It has been said we (fedora) will *not* offer general project hosting. Instead, in order to host your project on our git platform, your project must serve the Fedora Project in some way
2025-02-26 15:39:08 <@amoloney:fedora.im> is this a true statement?
2025-02-26 15:39:35 <@jflory7:fedora.im> Oh, great question
2025-02-26 15:39:38 <@conan_kudo:matrix.org> whoa, what?
2025-02-26 15:39:48 <@jflory7:fedora.im> I have an opinion
2025-02-26 15:40:02 <@mattdm:fedora.im> I don't think we want to get into the business of strictly policing that 
2025-02-26 15:40:04 <@jflory7:fedora.im> Hard and firm policy? No, we do not want the job of deciding whether something is Fedora-related or not
2025-02-26 15:40:16 <@jflory7:fedora.im> Guidelines and advice? Yes. Projects should serve the Linux ecosystem in some form.
2025-02-26 15:40:28 <@amoloney:fedora.im> I like this sentiment
2025-02-26 15:40:29 <@jflory7:fedora.im> We should be clear that projects that serve the needs of Fedora and upstream Linux are the priority
2025-02-26 15:40:47 <@mattdm:fedora.im> Yeah that 
2025-02-26 15:40:50 <@jflory7:fedora.im> We are not going to prioritize an open source Windows game's needs for a git hosting platform
2025-02-26 15:41:04 <@jflory7:fedora.im> But we would want to listen to say, NetworkManager or the Design Team as stakeholders
2025-02-26 15:41:25 <@mattdm:fedora.im> Upstream Linuxy software, to be clear. Not strictly Linux Kernel 
2025-02-26 15:41:30 <@jflory7:fedora.im> Also, maybe we _should_ say FOSS only?
2025-02-26 15:41:37 <@jflory7:fedora.im> That one could be spicy
2025-02-26 15:41:42 <@jflory7:fedora.im> But seems easy and practical for Fedora
2025-02-26 15:41:43 <@jflory7:fedora.im> IDL
2025-02-26 15:41:45 <@jflory7:fedora.im> IDK
2025-02-26 15:41:46 <@conan_kudo:matrix.org> that one was already the rule
2025-02-26 15:41:50 <@jflory7:fedora.im> Maybe the FPCA covers this sufficiently
2025-02-26 15:41:53 <@jflory7:fedora.im> Oh.
2025-02-26 15:41:55 <@jflory7:fedora.im> TIL πŸ˜› 
2025-02-26 15:42:07 <@jbrooks:matrix.org> This might work better as a written proposal to process and discuss
2025-02-26 15:42:13 <@jflory7:fedora.im> Now is a good opportunity to reaffirm whether we want a rule or not
2025-02-26 15:42:18 <@jflory7:fedora.im> Actually, yes
2025-02-26 15:42:32 <@jflory7:fedora.im> Could the Initiative owners be put to task on drafting this as part of the Initiative?
2025-02-26 15:42:33 <@conan_kudo:matrix.org> it wasn't enforced because we didn't force FPCA flow for pagure.io
2025-02-26 15:42:38 <@mattdm:fedora.im> Good call β€” this is down in the details. 
2025-02-26 15:42:39 <@conan_kudo:matrix.org> but it was already a rule
2025-02-26 15:42:42 <@jflory7:fedora.im> I don't think the Council should own drafting this, but we should review this
2025-02-26 15:43:24 <@amoloney:fedora.im> this is why I am asking, to both debunk any notions that might accidentally become canon, and reaffirm what we expect from our new project hosting service
2025-02-26 15:44:00 <@jbrooks:matrix.org> I don't see any rules at pagure.io
2025-02-26 15:44:07 <@amoloney:fedora.im> No I dont think thats fair on them
2025-02-26 15:44:19 <@mattdm:fedora.im> I kind of think the Council should own it, to shield the initiative from arguing about it 
2025-02-26 15:44:21 <@amoloney:fedora.im> They are asking council for guidance
2025-02-26 15:44:30 <@amoloney:fedora.im> we should own it, 100%
2025-02-26 15:44:37 <@amoloney:fedora.im> this is literal project governance
2025-02-26 15:45:01 <@jflory7:fedora.im> Also, we are not Forgejo experts and it would be nice to have the context about features like license scanning or what tools could enforce this for us
2025-02-26 15:45:08 <@conan_kudo:matrix.org> they were present several iterations of the UI ago :/
2025-02-26 15:45:13 <@amoloney:fedora.im> I like Jason Brooks idea of creating a draft though for feedback
2025-02-26 15:45:16 <@jflory7:fedora.im> I would prefer a draft from the Initiative owners that covers 50% and the Council addresses the final 50%
2025-02-26 15:45:24 <@jflory7:fedora.im> I just think giving us this task of owning it is biting off more than we can chew
2025-02-26 15:45:30 <@jflory7:fedora.im> We have soooo many follow-ups from the Council hackfest
2025-02-26 15:45:33 <@jflory7:fedora.im> We need to delegate more somehow
2025-02-26 15:45:54 <@jflory7:fedora.im> I don't want these to suffer because git forge takes us off the rails yet again
2025-02-26 15:45:55 <@amoloney:fedora.im> This is literally the councils job though
2025-02-26 15:46:18 <@jflory7:fedora.im> Then we need to set a realistic deadline on when we think we can deliver it. I am not confident for F42, this is not that far away
2025-02-26 15:46:34 <@conan_kudo:matrix.org> then push back the deployment and migration dates
2025-02-26 15:46:37 <@conan_kudo:matrix.org> it's not that big of a deal to wait
2025-02-26 15:46:59 <@amoloney:fedora.im> tbh we dont even have to do that
2025-02-26 15:47:20 <@amoloney:fedora.im> we can continue with the deployment if we really want to, and bring in the project hosting guidance at a later stage
2025-02-26 15:47:35 <@jflory7:fedora.im> We _could_ submit something for Flock, like a roundtable or BoF
2025-02-26 15:47:40 <@jflory7:fedora.im> I mean, the CFP is open for one more week πŸ˜› 
2025-02-26 15:47:45 <@jflory7:fedora.im> Or, just roll it into the Council panel
2025-02-26 15:47:50 <@jflory7:fedora.im> As a discussion topic
2025-02-26 15:48:01 <@amoloney:fedora.im> I dont see why we cant just take what we use for pagure, make some edits, propose it for feedback and see what comes back and agree to something
2025-02-26 15:48:12 <@amoloney:fedora.im> I do like this idea
2025-02-26 15:48:14 <@jflory7:fedora.im> I also admit to never knowing about these guidelines for Pagure
2025-02-26 15:48:21 <@jflory7:fedora.im> I would contend that they are not as understood as we think they are
2025-02-26 15:48:29 <@jflory7:fedora.im> And I have been here 10 years and I am saying that πŸ˜› 
2025-02-26 15:48:42 <@jbrooks:matrix.org> that's a good start, the trick is finding those rules
2025-02-26 15:48:48 <@conan_kudo:matrix.org> the guidelines for gitlab.com/fedora are basically the same rules for pagure.io
2025-02-26 15:48:56 <@jflory7:fedora.im> Where are these rules though??
2025-02-26 15:49:04 <@conan_kudo:matrix.org> I dunno, you told me them :P
2025-02-26 15:49:13 <@jflory7:fedora.im> Me??? O.O
2025-02-26 15:49:18 <@conan_kudo:matrix.org> yup
2025-02-26 15:49:24 <@conan_kudo:matrix.org> when the gitlab.com/fedora namespace launched
2025-02-26 15:49:24 <@amoloney:fedora.im> yeah lets not reinvent things from scratch, lets pull together what we can find and see what works
2025-02-26 15:49:25 <@jbrooks:matrix.org> I'm trolling through the wayback machine, and I can't find them
2025-02-26 15:49:28 <@mattdm:fedora.im> I think the policy is just a matter of drafting and getting feedback. 
2025-02-26 15:49:51 <@amoloney:fedora.im> So, my previous statement is NOT TRUE (phew)
2025-02-26 15:49:57 <@conan_kudo:matrix.org> oof
2025-02-26 15:50:17 <@mattdm:fedora.im> Aoife I can help after my otherwise homework :) 
2025-02-26 15:50:20 <@conan_kudo:matrix.org> I think the only place it's currently written is actually copr πŸ˜…
2025-02-26 15:50:24 <@jflory7:fedora.im> Yeah, I mean, we can find the details as we move forward
2025-02-26 15:50:30 <@conan_kudo:matrix.org> everywhere else seems to be gone
2025-02-26 15:50:33 <@jflory7:fedora.im> It is not urgent to discuss it now
2025-02-26 15:50:39 <@amoloney:fedora.im> We, council, have some work to do on making sure we have project hosting guidelines in place for when Forgejo becomes a 'big deal'
2025-02-26 15:50:42 <@jflory7:fedora.im> But good to take inventory of this topic and register it as an important detail
2025-02-26 15:50:53 <@jflory7:fedora.im> +1, #agreed
2025-02-26 15:51:28 <@amoloney:fedora.im> mattdm: @amoloney and Jason Brooks will cobble together an initial draft of guidelines we feel could be suitable, and publish them for rounds of feedback on discourse
2025-02-26 15:51:45 <@amoloney:fedora.im> We expect this wont happen until mid-March or April realistically
2025-02-26 15:52:09 <@amoloney:fedora.im> does that sound ok? sorry Jason Brooks I pulled you in as you had some practical approaches :)
2025-02-26 15:52:31 <@amoloney:fedora.im> anyone else would like to have a hand in this, please let me know
2025-02-26 15:53:09 <@amoloney:fedora.im> Im going to make an agreed statement in a minute, so if anyone has any last minute objections please type them now
2025-02-26 15:54:07 <@jflory7:fedora.im> 🌊
2025-02-26 15:57:14 <@amoloney:fedora.im> !agreed The Fedora Council will draft a guidance policy on project hosting in Fedoras new git platform. mattdm @amoloney and Jason Brooks will take existing policies from other project hosting sites such as gitlab, pagure, etc and publish something for feedback from the wider Fedora Community by April 2025. We are aiming for early April.
2025-02-26 15:57:27 <@amoloney:fedora.im> !topic Open Floor
2025-02-26 15:57:45 <@amoloney:fedora.im> I actually had another git forge thing, but thats enough excitement for one day :D
2025-02-26 15:58:13 <@jflory7:fedora.im> I would really like votes on this PR: https://pagure.io/Fedora-Council/council-docs/pull-request/244
2025-02-26 15:58:27 <@jflory7:fedora.im> I have been addressing community feedback all week, and I think it is a really good principle/philosophy doc
2025-02-26 15:58:33 <@jflory7:fedora.im> I hoped to get your votes on it today
2025-02-26 15:58:47 <@mattdm:fedora.im> Did we announce that the Flock cfp is extended? I saw the 23rd somewhere this morning still. 
2025-02-26 15:58:56 <@jflory7:fedora.im> Aoife is helping me with this
2025-02-26 15:59:15 <@amoloney:fedora.im> Announcement coming later today πŸ‘οΈ
2025-02-26 15:59:24 <@amoloney:fedora.im> Closing date is now Monday March 3rd
2025-02-26 15:59:36 <@amoloney:fedora.im> and I will add my +1 vote to that ticket now JWW (@jflory7) [away until 2025-02-25] 
2025-02-26 15:59:45 <@jflory7:fedora.im> TY TY
2025-02-26 15:59:54 <@jbrooks:matrix.org> I still need to read it -- is it just in screenshot format?
2025-02-26 16:00:06 <@jflory7:fedora.im> I can make a new screenshot if it helps
2025-02-26 16:00:09 <@jflory7:fedora.im> The changes are in AsciiDoc
2025-02-26 16:00:21 <@jflory7:fedora.im> https://pagure.io/fork/jflory7/Fedora-Council/council-docs/blob/b2bf857e2e481feae8818a960a7052351bead406/f/project/modules/ROOT/pages/upstream-first.adoc
2025-02-26 16:01:14 <@mattdm:fedora.im> Sheesh we need some kind of useful preview functionality. Screenshots are not a good way! 
2025-02-26 16:01:39 <@jflory7:fedora.im> GitLab has this with CI 🌚
2025-02-26 16:01:43 <@jflory7:fedora.im> Pagure was always a pain
2025-02-26 16:01:57 <@jflory7:fedora.im> And I did ask about moving the Council docs to GitLab three years ago πŸ˜› 
2025-02-26 16:02:06 <@jflory7:fedora.im> But I hope we can do this in Forgejo
2025-02-26 16:02:09 <@jflory7:fedora.im> 🀞
2025-02-26 16:03:46 <@salimma:fedora.im> mattdm: JWW (@jflory7) [away until 2025-02-25] hi folks, are you going to be on much longer? I think Hyperscale has the meeting room now
2025-02-26 16:03:50 <@salimma:fedora.im> (we might want to relocate ours)
2025-02-26 16:03:58 <@amoloney:fedora.im> oops were done
2025-02-26 16:04:00 <@amoloney:fedora.im> !endmeeting