We are holding on this topic until the audit is complete.
We can setup initial GitLab pages. Split into new issue — Matthew
Matthew created issue for DrupalPod maintainership —
https://www.drupal.org/project/drupalpod/issues/3521853
💬
Offering to co-maintain DrupalPodActive
Darren has volunteered as well.
Next step is to reach out to Ofer.
Worried about a new tool prior to Vienna and writing documentation more than once.
Deadline in order to prepare writing documentation should be 1 month prior to Vienna.
DrupalForge setup is a bit longer and more involved than DrupalPod at the moment.
Matthew will get feedback from people at MidCamp.
Event planning lead - Chris
Rachel + James running first-time contributor workshop.
Document canonical first-time contributor workshop slides in the documentation issue.
Need more than one canonical slide deck
Mentored contribution room lead -
Communications lead - Igor volunteered
Novice issue triage lead - Rodrigo tentatively volunteered if he is able to attend.
Booth lead -
Tools lead - Matthew can help remotely, not on-site.
Chris: no particular update other than that we discussed getting those contrib tracks defined now and reaching out to the initiative leads now to get possible tables sorted out
That and they are moving a tonne of stuff out of D11 in D12 eg search module etc etc
So core will have less things that can be novice issues
We need to start including contrib. specially things that are in recipes.
Finding safe place to send people, is it a specific set of contrib modules and/or recipes. Is it fair to say whilst drupal cms is moving fast it's still a place to send people because governance is good.
Governance is a requirement for curated Novice issues.