#79 Flock 2016 CommOps Workshop
Closed: Fixed None Opened 6 years ago by jflory7.

= Phenomenon =

[https://flocktofedora.org/ Flock 2016] is happening from August 2-5, 2016, in Krakow, Poland. At Flock, there are several [https://flock2016.sched.org/ talks and workshops] scheduled. There is a [https://flock2016.sched.org/event/6ypN/commops-workshop CommOps Workshop] scheduled On Thursday, August 4, 2016, from 13:30 to 15:30 (Polish local time).

= Background Analysis =

decause was originally the owner of this workshop, but since his departure, I will take ownership of the event.

Based on previous discussions in channels or on mailing lists, we want to make the CommOps workshop a collaborative space to work on some of the existing objectives and tasks we're working on already. We also want this to be a place for the community to bring ideas and wishes for things they would like to see that we can work on together to build a better project.

= Implementation Recommendation =

The [https://fedoraproject.org/wiki/CommOps/Flock_2016 wiki page] for the workshop will be the planning pad for most of the details about the workshop. I hope to bring this ticket up at the next CommOps meeting to get some others' thoughts on this and see what others would like to see and get out of this event.

'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-07-05-15.56.html 2016-07-05 meeting].'''

= Workshop is a go =

With the wiki page created, planning efforts on the workshop are starting to come together now. I'll be working on getting an itinerary together of some sort for how it should flow and begin compiling resources together. This is an ultra-high-priority item for jflory7 this month.

= Collaboration == open =

As mentioned in the meeting, feedback, discussion, ideas, planning, and everything else about this workshop is intended to be '''''open'''''. As the details begin coming together, I'd love to hear feedback from others about what's on the agenda, what we can or should focus on, and what resources might be helpful. This ticket will largely serve as the planning / discussion space for the workshop, and the wiki page will be for the more finalized-ish details.

= Add yourselves! =

For now, something everyone can do is add themselves to the attendees part of the wiki page. If you're going to be at Flock either as a CommOps member or someone from another part of the project, this will be super helpful for planning! And if you want to participate virtually, it will be very helpful for me to have an idea of who will try to be around for the workshop so we can utilize time wisely with the number of people available.

== [https://fedoraproject.org/wiki/CommOps/Flock_2016#Attendees Add yourself here!] ==

As mentioned in today's CommOps IRC meeting, I'm interested to participate however I can (I guess remotely) and maybe can provide some newcomer perspective. :-) Since I'm not CLA+1 yet I can't log in to the wiki to add my name, but we'll get that sorted out eventually!

= Workshop completed =

This ticket is being closed as Flock 2016 has ended. I went through the wiki page, updated information, and added a link to my [https://blog.justinwflory.com/2016/08/fedora-flock-2016/ Flock 2016 report], which has a fair amount of comments and feedback on the workshop.

I would still like to work on a separate report / write-up of the workshop to share on the Community Blog in the coming week or two, but that's something definitely already on my radar. Bee and I will definitely be collaborating on that one.

Sorry for the difficulties in setting up remote participation on this one. I think I have some ideas for how we could make it better for next year… will reflect on this some in the CommBlog post. Hope we'll get to do this again at the next Flock!

Serious big thanks to Bee (bee2502++) for all of the help in putting the final touches on this. We did a lot of the work together on Tuesday and Wednesday for preparing the workshop (it definitely helps being in the same room as someone for this kind of thing).

Login to comment on this ticket.