From Fedora Project Wiki

(First draft of the agenda)
(Add more links for actions)
Line 42: Line 42:


* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-31/commops.2016-05-31-15.56.html
** #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
** #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
** #info === decause Follow up with tatica and diversity team about LimeSurvey availability ===
** #info === decause Follow up with tatica and diversity team about LimeSurvey availability ===
Line 61: Line 61:
*** #link https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/
*** #link https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/
** #info === [COMPLETE] jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session ===
** #info === [COMPLETE] jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session ===
*** #link  
*** #link https://apps.fedoraproject.org/calendar/meeting/3918/




Line 79: Line 79:
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** This tickets are all currently blocking on Badges proposals. The next logical steps to get this in motion will be to propose the badge series creation on the Fedora Badges Trac. After that, these badges can be tackled at the Design + CommOps hack session or another convenient time. With this week being PyCon, it might be a slow start at the beginning of this week, but there are Fedora sprints at PyCon, so this might be a good time to try to coordinate a hack session or something similar. It will be worth checking in with decause about when the hack sessions are so we can maybe try to work around those times. Would anyone be interested in proposing the badges on the Fedora Badges Trac?
*** <!-- This tickets are all currently blocking on Badges proposals. The next logical steps to get this in motion will be to propose the badge series creation on the Fedora Badges Trac. After that, these badges can be tackled at the Design + CommOps hack session or another convenient time. With this week being PyCon, it might be a slow start at the beginning of this week, but there are Fedora sprints at PyCon, so this might be a good time to try to coordinate a hack session or something similar. It will be worth checking in with decause about when the hack sessions are so we can maybe try to work around those times. Would anyone be interested in proposing the badges on the Fedora Badges Trac? -->
*** #link https://fedorahosted.org/fedora-badges/
*** #link https://fedorahosted.org/fedora-badges/
** #info === Ticket #71 ===
** #info === Ticket #71 ===

Revision as of 14:04, 7 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-07

Meeting Time

Participants

This week's CommOps Meeting will be led by decause.

  • The participants will be posted after the meeting.

Meeting Protocol

  • To help improve the flow of the meeting, using the IRC Meeting Protocol is encouraged, as modeled by the EMEA Ambassadors.
  • Please follow the Meeting Protocol where possible.

Agenda

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-06-07)
  • #meetingname commops
  • #nick commops
  • #chair <given to approved members of FAS group at meeting>



  • #topic Roll Call / Q&A
    • #info Name; Timezone; Sub-projects/Interest Areas
    • If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.








  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:CommOps_2016-06-07&oldid=449448"