Closed drnikki closed 7 years ago
Including #27 , #37
After today's conversation I think # 11 - CWG recommendation could have some interest.
Another topic: do we want to bring this work to a venue (or venues) beyond DrupalCon? Local camps, etc?
Should we move the issue queue to drupal.org so that we're in the same ecosystem as the rest of the projects and can leverage people's existing knowledge of tickets there. Is it unfair to expect that people are familiar with Github?
Question - will we take & publish minutes from this meeting? Should we do that for all of our meetings? I feel like transparency is the key to trust in our community right now.
We do take and publish notes (of varying quality) on all of our meetings. They're not full transcripts - though I suppose they could be, but I do want people to be able to speak freely - but are usually quick high-level things.
I don't think we need full transcripts - I think maybe we could organize/publicize that repo a little better (just realized it exists and is public), and have some more details. This may be where having more "positions" in the org comes, in (like a secretary) so someone is always on top of it and it's not the person running the meeting!
Yeah, details like this are not my personal strength, so figuring out someone who can take notes/do minutes would be really great.
Should we move the dd&i site to drupal (this has come up a few times)? If so can we sprint on it in Baltimore?
@drnikki are working groups usually on d.o?
@sugaroverflow - I don't know. My guess is yes, though it's important to be clear that we're not a part of the DA. I just don't want to exclude people who are familiar with d.o issues but not github issues.
2017-03-31 14:19 GMT-07:00 Fatima Sarah Khalid notifications@github.com:
@drnikki https://github.com/drnikki are working groups usually on d.o?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/drupaldiversity/administration/issues/28#issuecomment-290832924, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPj2zF5xh5xXAt3VFpWJ_ExSuizWViMks5rrW30gaJpZM4MYZ6x .
-- @drnikki 619 808 1057
To make it easier can we add a quick guide to using github issues to our "welcome/getting started" thing?
Referencing #51 Mentoring new or first time speakers to our strategy.
Based on convo in slack on 4.18 -
Would be great to put things onto a calendar. Some things we can focus on in the time leading up to CFPs so that we can schedule initiatives.
Here are the notes from the strategy meeting we had in Baltimore
John’s company has been looking at ways to bring it to underserved communities.
Lead by: Heather.
General consensus: yes
Lead by: Nikki, Tara, and Ruby
DDI has the same problem as the community. Should we lead by example? Consensus: yes
Initial Teams:
Initial Members:
Solidification By: Ruby and Alana
These will be listed in meeting notes and will manifest in issues shortly.
(comment updated by @sugaroverflow to fix markdown syntax)
Collecting items to meet and discuss at DrupalCon for the DD&I's 2017-18 strategy. Meeting times will be posted when we're closer to the con and all of the sessions have been scheduled.
There's a doodle poll for scheduling that strategy meeting here: http://doodle.com/poll/a47szfwsguqm47xa
You can also list things you'd like us to sprint on during the week. We'll be doing that sprinting using issues here in this queue. You can also make issues and link them here. :)