Plan a workshop session with CommOps team members to run at Flock 2018, preferably by June 15
For the past two years, CommOps runs a session at Flock to either update the community on what we're working on or to help bring new contributors into the team. This year, like last year, Flock is taking a more hands-on approach. A workshop is a preferred format for us to focus and deliver.
CommOps has a limited number of core contributors, so we should identify team members who are making plans to attend Flock and then identify one strong proposal for a workshop submission. We should aim to apply by June 15, 2018 for Round 1 preferential review. Proposals are accepted in the Flock Pagure repo.
We had a brief discussion in IRC today (June 3). The two ideas that came up:
This list is not exhaustive, but these are the two ideas we had initially. @dhanesh95 is starting an Etherpad to collect and brainstorm these ideas and new ideas further.
Submit a proposal by June 15, plan out how we will run the workshop over June and July, execute the workshop at Flock in August
I've added the two ideas to the Etherpad here.
I'm also adding questions below the ideas to help understand how much work will be required to achieve the goal.
As a reminder, per the discussion in #110 from the CommOps FAD this year, we wanted to promote Appreciation Week and contributor stories at Flock. We'll need to brainstorm further on how we want to do that too.
Because of the looming deadline tomorrow for Flock sessions, I submitted a half-day hackfest proposal for the CommOps team in the Flock CFP Pagure (flock#51).
I think this format is more useful for our team and allows us flexibility to address many of the topics listed above. We also have the flexibility to make more decisions about what we want to focus on and include in July based on the information we have available. This measure ensures we will be reviewed during the first selection round for Flock; however, over the next two months, we should establish better scope of what we want to accomplish at Flock.
I will start working on adding more sources to the dashboard I already setup. I did not write any documentation for setting it up (/me hides in a corner). Once I have something up and running, I can do a quick tutorial during our hacksessions on how to setup the Grimoirelab suite.
@dhanesh95 Are you working on something related to the dashboard?
@skamath Thanks for chiming in. Do you think there's any possibility of writing documentation for creating mailing list panels by Flock? I would consider it a success if we could go to Flock with documentation in-hand to help other sub-projects and teams build simple visualizations of their mailing list activity in a staging instance of Grimoire.
This would be a valuable opportunity to get early feedback from users about what is useful or most insightful for different teams for visualizations.
I'm going to remove this from the meeting agenda. For now, since we have the mini-hackfest proposed at Flock, I think we can focus our efforts in on making that session successful. Later in July, we should revisit this ticket for prep work based on where things stand as we get closer to Flock.
Metadata Update from @jflory7: - Issue untagged with: help wanted, needs info, next meeting - Issue priority set to: normal (1-2 weeks) (was: minor (3-4 weeks))
Metadata Update from @jflory7: - Issue assigned to jflory7
Metadata Update from @jflory7: - Issue tagged with: team - commops
This was done successfully. Once new tickets and/or a blog post are published about our session, this ticket can be closed.
Metadata Update from @jflory7: - Issue tagged with: next meeting
Discussed in 2018-09-03 meeting.
This ticket was added to the meeting agenda to give a brief recap of Flock to remote team members. In addition to the notes below, also see the transcript and note-taking Etherpad.
@jflory7 If possible, a CommBlog article summarizing CommOps @ Flock by Monday, October 17
Metadata Update from @jflory7: - Issue untagged with: next meeting
Metadata Update from @jflory7: - Issue priority set to: waiting on assignee (was: next meeting)
I was sorting through pictures and found this. Thought it would be useful to share.
<img alt="Whiteboard / sticky note pad from CommOps team sprint at Flock 2018" src="/fedora-commops/issue/raw/files/e5e629beded7068bde5f08bc7608464c0f32a6fb3422b6db6f461faff5960a3d-IMG_20180810_162448.jpg" />
An article is scheduled for Tuesday, October 16th. A final preview is available here. The final, published URL will be here:
https://communityblog.fedoraproject.org/commops-takeaways-flock-2018/
Closing ticket as complete. :clapper:
Metadata Update from @jflory7: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.