Thank you for doing this recap of the checkins @Dean !
I’ll go through the list, ahead of discussing it during the contributors meetup.
Calls/offers for help
Upstreaming course - call for contributions / Sprint 2022 remote sprint
We need more contributing writers and proofreaders with actual experience contributing – our knowledge about this is something to share, it’s a really good way to communicate this to new contributors.
Missing permission
Looks closed now – thanks @BbrSofiane ! @pdpinch Would it make sense for you to get that missing permission for next time, by nominating yourself to get it assigned?
Tutor deployment at scale & Kubernetes - Collaboration
There is an ongoing discussion on this, on the following thread: Tech talk/demo: Deploying multiple Open edX instances onto a Kubernetes Cluster with Tutor – if we pull together around a common architecture & project to handle this, we can share the maintenance and help each other?
Frontend
@arbrandes Any comment on this?
Improvements & blockers
Availability
@Andres.Aulasneo Which time and workforce are you talking about, yours? What could help you to obtain more of it to dedicate to the project?
Nutmeg - Need contributors for Tutor plugins!
This is a good way to help with a release ^
Btw, one additional way which would improve this would be to make the Tutor maintainer program compatible with or part of the core contributors & maintainers program of Open edX – this way the count of time spent on the Tutor maintainer program would be counting towards the Open edX Core contributor, and provide more time from the time budget pool dedicated to it by organizations to Open edX. There is an ongoing discussiong with @regis about applying OEP-55 to it on TEP: rethinking the Tutor maintainers program - #10 by antoviaque - Tutor Enhancement Proposals (TEPs) - Overhang.IO which would help with this.
@xitij2000 Has this been fixed? The repository being non-supported, this will likely happen more and more. Do we have plans to deprecate the branch builds?
Other improvements
And there were a few of the improvements from the checkins not included above, so adding it here:
Need to continue discussions from the conference
Our points converge about the need to not let go of those discussions from the conference, and make sure we do things as a community. I’ll bring this up for discussion during the contributor meetup later today. Do we need to schedule specific follow-up sync meetings? Which ones? What can we do async?
It would also be worth having more people posting their impressions, comments and hope in the public feedback thread – that could help sparkle some of the discussions. : ) Open edX Conference 2022 - Feedback Thread
Assigning issues
@pdpinch Sometimes it can help to ask specific people – maybe see in the list of core contributors who would have the right skills/experience to handle it, then maybe starting with the ones who have contributed less so far so have more contributions to plan for?
Working group communication
@ali_hugo Note that the sprint checkin can be a good way to do this – if you prepare the update on your progress, you can send it at the same time to the UX team? The UX team could also post updates there, if that helps you?
Data working group
Glad to hear! 