Some things are broken with added items that Chris would like help with.
Maybe have to dechart and rechart to make it work.
Jess mentioned her expertise in Excel and could fix this up.
Default sort
Updated timeline documents based on with some new items.
Determining leads and mentors that can help leads who have larger roles.
Chris created the Event Layout / Spacing Planning document and mentoring leads reviewed.
Adjust room sizes for General / Mentored contribution
Document has been getting updated after discussion with event organizers.
From Meta meeting:
Chris: We are here to help provide any experience we can in terms of planning. We have already made documents with diagrams for spaces and layouts, and we can make more documents for other guidance. Will be good to flesh out the “mentoring event pack” that can be provided to organisers
We need to define what the definition of done is for fleshing out.
GitLab pages?
Vienna 2025
Igor was working on documentation for communications stuff
Need a tools channel to collaborate regardless of DrupalForge, DrupalPod, ddev, etc...
Even if working on separate solutions discussion and advisory discussion could end up there.
#contribution-tools
Proposal: any proposed solutions need to be presented (and tested) to mentoring leads by
date.
Needs to be tested 1 month prior to Vienna — 2025.09.18
We need to communicate a date when we focus on 1 solution?
First step is to contact Ofer.
Further discussion was made in the Mentor Meta and below in DrupalCon Vienna Planning section below.
Determine number of Mentor tickets available.
10 tickets available (but usually 8 so hush hush on that).
Ask Gábor about initiative / track topics for contribution.
This is in mentoring coordinators Slack channel.
Contribution tools platform is the main issue to get trained.
Mentor Orientation needs to mention tools docs, video, training.
Small changes can be done directly in GitLab merge requests / editor.
Proposal: If we (MWG + coordinators) do not have a good path forward by next month's meeting, then we won't have a specialist tool for Vienna 2025 (or Nara 2025).
The risk is getting to great.
Focus on how to work the issue queue
Triage novice issues that are Needs Issue Summary Update and train new contributors how to triage (novice) issues.
Get more issue touches as a new contributor is important to (sensitive) setting them up to getting spammed.
We won't teach the contribution tools, but other activities.
Pairs really well with BugSmash, Needs Review Queue Initiative, Major Issue Triage to have people focus on Needs Issue Summary Update and issue queue tags.
Divide people up who have tools already installed locally, and those who do not.
Though the research shows that "time to commit" matters a lot.
If we can get people to focus on issues that are more relevant to Starshot and other initiatives, then they are more likely to move.
Matthew is behind on things this ~~week~~ month and needs to reach out to Michael and Jimmy
Make event organizers channel modeled after Vienna channel and invite contribution event organizers and committee members.
Matthew was hoping to check-in with committee members and start meeting to share timeline documents, slide decks, etc... but we haven't been able to connect yet.
Communicate deadlines for contribution tools solutions
And propose for alternative to learning contribution tools at Vienna and focus on issue queue.
Update access on the FTCWS Themed slide deck and communicate the link in the issue and to relevant parties.
Create issue to change meeting time and date + merge request.