From Fedora Project Wiki

(Update ticket comments)
No edit summary
Line 53: Line 53:
** #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
** #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
** #info === decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push ===
** #info === decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push ===
** #info === skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :) ===
** #info === [INCOMPLETE] skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :) ===
*** #action skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded
** #info === [COMPLETE] jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71 ===
** #info === [COMPLETE] jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71 ===
*** #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/OGHF2254VRUWUJTE36X3S5X5EQX5MQ5I/
*** #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/OGHF2254VRUWUJTE36X3S5X5EQX5MQ5I/
Line 127: Line 128:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
** #info skamath Introduce the summer-coding stats tool
|summary=
|summary=
|log=
|log=
|next-meeting=2016-06-14
|next-meeting=2016-06-14
}}
}}

Revision as of 15:54, 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 Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Ticket #10 ===
      • #info "CommOps vFAD 2016"
      • #link https://fedorahosted.org/fedora-commops/ticket/10
      • #link https://fedoraproject.org/wiki/FAD_CommOps_2016
      • In December, we began discussing the idea of a CommOps vFAD but were going to shelf until we grew some more and after the summer began. Now that we're getting into June, we began discussing this at our last meeting. A wiki page template was started for our vFAD. The next steps should be deciding the objectives and what we wish to accomplish for the CommOps vFAD.
    • #info === Tickets #34, 49, 69 ===
    • #info === Ticket #71 ===
      • #info "Centralizing Ambassadors / Events resources and utilities"
      • #link https://fedorahosted.org/fedora-commops/ticket/71
      • Feedback was asked for on the Design Team, and a few replies were given back this morning. Some efforts were already started to centralize the resources, but the Design Team has a strong preference on Ambassadors consulting with Design Team members first before printing (as compared to self-producing). This helps ensure the quality of the final product and that it properly represents the Fedora brand. Maybe an alternative to original problem in the ticket is making a more clear and guided process for what Ambassadors should do to request design assets?
      • #link https://pagure.io/designassets/tree/master





  • #topic Open Floor
    • #info skamath Introduce the summer-coding stats tool

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=449466"