Thanks for a great meetup last night. I really appreciate you sharing the floor with me for a good chunk of time to try something new. For folks who missed it, here's a write up of the proposal I presented last night about dedicating some time as a group to learning about and contributing to core over the next few months.
The feedback I got on my proposal yesterday was overwhelmingly positive. (To be honest, much better than I anticipated.) The majority of people I spoke with (all but one) are supportive of spending the first hour of our next four meetups (that’s 6:30 - 7:30 in Nov., Dec., Jan., and Feb.) doing activities like we did this evening, then spending the second hour (7:30 - 8:30) doing lightening talks. I think this is awesome. But to be clear, this is only my proposal. It’s not my decision to make.
I have tried to be thorough about debriefing with people and soliciting feedback. Below is a write up of my notes from the evening, reflecting on the goals of our 1-hour exercise, and summarizing my one-on-one debriefs after the meetup. I hope the people I spoke with will feel I’ve done a good job summarizing and paraphrasing feedback.
If I didn't capture anyone's feedback, if you have feedback you didn’t share with me in person, or if you have any other thoughts or comments, please post it here.
Re. goals for this evening:
- For people without Drupal running locally: Get everyone set up.
OUTCOME: As far as I know, we got everyone with a laptop set up. Thanks Tim and Ben for helping get people set up.
- For people with Drupal running locally: Get everyone to make progress on one issue on some aspect of Drupal core they’re interested to learn more about. Specifically, reproduce and document a bug (http://bit.ly/drupalbugs).
OUTCOME: As far as I know, everyone with a laptop worked on an issue. Many people worked in pairs. 26 people opened the How To document with instructions on how to find bugs that need to be reproduced and documented. 10 people (or pairs of people) posted updates to core bugs they worked on for 30-40 minutes this evening. And three people told me on their way out, they had not posted an update, but intend to keep working on their bugs after wrapping up this evening.
- Get everyone to do #1 and #2 in under an hour.
OUTCOME: I presented my proposal, walked people through the How To document and demonstrated an example in 15 minutes. Then the group spent 40 minutes working on bugs.
Summary of feedback from debriefs:
(I did my best to talk to as many people as I could after wrapping up. I didn’t do a head-count, but I feel certain I was able to do one-on-one debriefs with at least two thirds of the people present. If these opinions are not representative of the people who didn’t stick around to give feedback, I hope those folks will chime in too.)
- The majority of people I spoke with (all but one) are in favor of spending the first hour (6:30 - 7:30 pm) of our next four meetups (Nov, Dec, Jan, Feb) doing activities like this, then spend the second hour (7:30 - 8:30 pm) doing lightening talks
- Three people suggested scheduling the ‘volunteer for Drupal hour’ from 6 - 7pm, and doing lightening talks from 7 - 8:30.
- One person suggested (and several supported) the idea of using an egg timer to time lightening talks and keep presentations moving. For example, give speakers up to 5 minutes for talk and then up to 5 minutes for Q&A. Each speaker sets the timer when they go up. When it dings, it’s the next person’s turn to present. This is especially appealing to people if we have less time allotted to lightening talks at the next few meetups.
- People who worked in pairs tended to have positive experiences with that setup. Newer Drupalists who didn’t have partners expressed interest in being paired with someone more experienced to work with.
- A number of people (including people who have reviewed and commented on contrib issues in the past) said this is the first time they’ve worked on any core issues.
- Not everyone had laptops. Most said they would like to do something like this again and they will bring their machines next time. But we will inevitably have people without machines, so it would be great to drum up a few spares.