Mentor Meeting 17 May 2023
This meeting is the start of our weekly meetings leading up to the event.
This meeting is on 17 May in the #mentoring channel on Drupal Slack at 2000 UTC. This meeting is text-only, no audio or video, and is asynchronous so everyone can join in as they're available for about 24 hours. After that’ll we'll capture notes from the threads.
Please add agenda items by editing this issue summary or commenting below.
Draft Agenda
:drupal-mentoring: :drupal-mentoring: :drupal-mentoring:
Hello everyone. Welcome to the Drupal Core Mentoring Meta Meeting! This meeting is a bit informal and we're hoping to bust out some action items.
➤ is text only!
➤ happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously.
➤ refers to various issues and plans tracking in the mentoring project on d.o:
https://www.drupal.org/project/issues/mentoring →
➤ :star: Please comment on the meeting agenda [
https://www.drupal.org/project/mentoring/issues/3361088] →
so we can grant you credit for attending/contributing!
:zero: Roll Call! Who’s here today? Comment in a thread here to introduce yourself, include your drupal.org name, and if you're up to it, what did you eat for lunch yesterday?
:one: :zero: Action item one. Spreading the word about mentoring at DrupalCon. Issues have been created. Each issue has a link to a google doc that can be improved and used as a space for collaboration
:one: :one: [META] Create copy for DrupalCon NA 2023 mentoring program:
https://www.drupal.org/project/mentoring/issues/3358612
📌
[META] Create copy for DrupalCon NA 2023 mentoring program
Fixed
:one: :two: Create social media copy for DrupalCon NA 2023 mentors:
https://www.drupal.org/project/mentoring/issues/3361023
📌
Create social media copy for DrupalCon NA 2023 mentors
Fixed
:one: :three: Create newsletter copy for DrupalCon NA 2023 mentoring program:
https://www.drupal.org/project/mentoring/issues/3361024
📌
Create newsletter copy for DrupalCon NA 2023 mentoring program
Fixed
:one: :four: Distribute copy for DrupalCon NA 2023 mentoring program to the social media managers:
https://www.drupal.org/project/mentoring/issues/3361026
📌
Distribute copy for DrupalCon NA 2023 mentoring program to the social media managers
Fixed
:Two: Please review these roles and see if there's a good fit, if you can co-lead, or would like to be mentored for a specific role.
Mentoring lead opportunities.
- [planning lead](
https://www.drupal.org/community/contributor-guide/role/mentored-contrib... →
)
- [mentored contribution room leads](
https://www.drupal.org/community/contributor-guide/role/mentoring-room-lead →
)
- [novice issue triage leads](
https://www.drupal.org/community/contributor-guide/role/novice-issue-tri... →
)
- [booth leads](
https://www.drupal.org/community/contributor-guide/role/mentoring-booth-... →
)
- [communications leads](
https://www.drupal.org/community/contributor-guide/role/mentor-communica... →
)
- [first-time workshop leads](
https://www.drupal.org/community/contributor-guide/role/first-time-contr... →
)
- [community tools leads](
https://www.drupal.org/community/contributor-guide/role/community-tools-... →
)
- mentored contribution welcome area leads
:three: BoFs are scheduled. Please add them to your schedule. If you would like to lead a BoF and be mentored on how to, please comment.
- Mentor orientation 1: Monday, 5 June at 3p-4p in RM 326 at tables 1 & 2
- Mentor orientation 2: Tuesday, 6 June at 9a-10a in RM 326 tables 1 & 2
- Issue queue triage: Tuesday, 6 June at 3p-4p in RM 326 tables 1 & 2
:four: Open floor/other topics. Please start a new thread.
That's it for now! Continue the conversation in the threads above or below and in issues. Remember to post in the meeting issue or in the roll call thread! And volunteer!!!!
Slack link:
https://drupal.slack.com/archives/C4K9UPX9P/p1684353565002219
Meetings notes from slack:
:drupal-mentoring: :drupal-mentoring: :drupal-mentoring:Hello everyone. Welcome to the Drupal Core Mentoring Meta Meeting!This meeting is a bit more informal than usual and we're hoping to bust out some action items.➤ is text only!➤ happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously.➤ refers to various issues and plans tracking in the mentoring project on d.o:
📌
Mentor Meeting 17 May 2023
Fixed
] so we can grant you credit for attending/contributing!
0️⃣ Roll Call! Who’s here today? Comment in a thread here to introduce yourself, include your drupal.org name, and if you're up to it, what did you eat for lunch yesterday?
1️⃣ . 0️⃣ Spreading the word about mentoring at DrupalCon. Issues have been created. Each issue has a link to a google doc that can be improved and used as a space for collaboration. (edited)
3️⃣ BoFs are scheduled. Please add them to your schedule. If you would like to lead a BoF and be mentored on how to, please comment.Mentor orientation 1: Monday, 5 June at 3p-4p in RM 326 at tables 1 & 2Mentor orientation 2: Tuesday, 6 June at 9a-10a in RM 326 tables 1 & 2Issue queue triage: Tuesday, 6 June at 3p-4p in RM 326 tables 1 & 2
So one should show up on Wednesday and check in? First time mentoring but am pretty involved with #bugsmash and #needs-review-queue-initiative so hoping to help in those areas
4️⃣ . 2️⃣ I guess this is more anecdote than thread, but there was some discussion at the committer onsite about the "Novice" issue tag, where other committers were discussing the problem of the novice tag being on not-novice things, and I explained both that there was an entire handbook page dedicated to explaining what is/isn't a good novice issue, and that every DrupalCon has a pre-sprint session that is basically untagging as many badly tagged novice issues as possible. :joy:The specific example given was the novice tag being added to issues for arbitrary CSS changes. Back in 2011, small CSS changes might have been novice issues, but they are definitely not anymore because:They have to be manually tested in multiple browsers with multiple breakpoints.A single change can have very wide-ranging impacts on completely different pages than the one covered in the issue, and it requires knowledge about the theme and about Drupal to know where that might happen.Modern CSS is a fully-fledged language with its own architectural paradigmsD10's default themes use PostCSS, which adds a layer of complexityEven if the contributor is familiar with modern CSS architectures, they would also have to understand Drupal-specific things like the Stable base theme and the restrictions on which changes to which themes are allowed in which branches.Etc.Examples of novice tasks related to CSS might be:Manual testing in a single browser, or for a breakpoint that wasn't taken into account in previous manual testingCorrecting a specific coding standard that doesn't have a functional impactEtc.(edited)
4️⃣ .3️⃣ Remote contribution during DrupalCon NA
So? No takers on the action items?
