Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Reminder: Please take attendance. Please paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits.
@Olamide Kolawole Dev team will update the module descriptor with list of env vars.
Environment variable RFC
@Olamide Kolawole has posted a timeline proposal on #folio-tc-internal
3 week public review span, then vote to approve / not approve the RFC.
Waiting for abstract to move forward. RFC to be submitted by @Oleksii Petrenko .
@Wayne Schneider Did they raise issues in Jira on affected projects? It may be done by the time the RFC gets to us.
@Olamide Kolawole Not aware of issues being raised in the repos, what work done/not done yet. Raised concerns in the doc, haven’t seen responses yet.
@Wayne Schneider Several dev teams might be asked to do something. Good to know if that will happen.
@Kevin Day Hoped for doc cleanup before reviews. Maybe should review what’s there even though not RFC?
@Olamide Kolawole Rather work on an RFC. They should be coming to TC, not us chasing. GA release deadline, not clear why that would be mandatory. Looking for a forum to discuss. If changes happen and RFC didn’t happen, then initial presentation was not necessary, would raise other questions. RMSG meeting said much work wouldn’t be on the teams.
@Maccabee Levine Can we just ask for estimated timeline on the RFC?
@Olamide Kolawole will.
@Olamide Kolawole If this shortened timeline should be standard for RFC? Not useful process if too long.
@Maccabee Levine TC did shorten the standard timeline a year+ back, but we haven’t tested in since. Should actually try an RFC before shortening the standard further.
@Kevin Day We do need time in an RFC for community input.
@Olamide Kolawole Shortened time to get the doc out to the community, 4 weeks to 3. Should still give community ample time to review, not < 3 weeks. A big change like Eureka should be even longer.
@Maccabee Levine The creation of the RFC has been the biggest delay for some prior RFCs.
0 min
Existing Module Evaluation
All
@Olamide Kolawole demonstrates Jira management of TCR project using parent tickets and subtasks
Can rank the modules as we want, within the board screen.
@Olamide Kolawole Parent task created, subtasks waiting to be picked up. There has not been much interest in precise ordering. We should create tickets for ui-export-manager for the channges to be made, and then approve the TCR Jira. Asking @Florian Gleixner and @Shelley Doljack to create the appropriate Jiras per the new process and move this one to Done. Go through the process and work through the kinks.
@Olamide Kolawole New module evals should take priority over existing module evals.
@Olamide Kolawole Not sure what we can do if we don’t have those dates yet
@Julian Ladisch Could assume some date and make some updates for technologies that are no longer OSS. I’ve updated it assuming next release will be this November.
@Olamide Kolawole Let’s come up with action items for specific things to change. Having a good date would help us, November is a good estimate given history. If the page looks good for November, that’s all we should change. Will review the page. Talk about MinIO not being OSS anymore, would be helpful to discuss as agenda item.