From Fedora Project Wiki

(Add action items, Community Blog, release schedule)
(Ad more announcements and tickets)
Line 34: Line 34:
*** #link https://flocktofedora.org/
*** #link https://flocktofedora.org/
*** #info The annual Fedora contributor conference, Flock, begins on August 2 and lasts to August 5 next week in Kraków, Poland. Stay tuned in IRC and on the [[Community Blog]] for more news and updates about the happenings starting next week!
*** #info The annual Fedora contributor conference, Flock, begins on August 2 and lasts to August 5 next week in Kraków, Poland. Stay tuned in IRC and on the [[Community Blog]] for more news and updates about the happenings starting next week!
** #info === Fedora elections come to an end ===
** #info === "July 2016 Elections - Result announcement" ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/5CNNSJT5JGJFSH7PZNGXSMFET4HFUUDB/
*** #info
*** #link https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/U4LYT24W53L4EE3CT7AKJAF2THPPY2CT/
** #info === "" ===
*** #info The elections for FESCo and Fedora Council, July 2016, have concluded, and the results are available in the above two email threads. Congratulations to all winning candidates and thanks all candidates for running!
*** #link  
*** #info  




Line 58: Line 56:
* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://fedorahosted.org/fedora-commops/report/9
** #link https://fedorahosted.org/fedora-commops/report/9
** #info === Ticket #xx ===
** #info === Ticket #79 ===
*** #info ""
*** #info "Flock 2016 CommOps Workshop"
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
*** #link https://fedorahosted.org/fedora-commops/ticket/79
*** description
*** #link https://fedoraproject.org/wiki/CommOps/Flock_2016
** #info === Ticket #xx ===
*** #info More planning and brainstorming targeted for the next 48 hours. As a workshop, the schedule or preparation doesn't have to be as rigid as a talk, but some general organization and plotting of final details should be wrapped up in the next couple of days (Flock is next week, after all)... :)
*** #info ""
*** #link https://etherpad.gnome.org/p/flock-2016-commops-workshop
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
** #info === Ticket #25 ===
*** description
*** #info "Begin initiative to consolidate subgroup wiki pages"
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/25
*** #info ""
*** In January, we began discussing ways the wiki's overall readability and disorganization could be resolved. In the ticket, there are some questions put out to try to best understand the successes and failures of the wiki so we can devise the best solution. We can do some brainstorming about this now.
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
** #info === Tickets #34, 49 ===
*** description
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** #info #49: "[Onboarding Series] Infrastructure"
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** Update on any developments with regards to blocking issues for usernames vs. email issues?
*** #link https://fedorahosted.org/fedora-badges/ticket/434
*** #link https://fedorahosted.org/fedora-badges/ticket/441
*** #link https://fedorahosted.org/fedora-badges/ticket/442





Revision as of 15:40, 26 July 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-07-26

Meeting Time

Participants

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

  • 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-07-26)
  • #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 Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-07-19/commops.2016-07-19-15.57.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 === [IN PROGRESS] commops Interested attendees for Flock 2016 workshop (either in-person or remote), please add yourselves to the "Attendees" section on the wiki page ===
      • #action commops Interested attendees for Flock 2016 workshop (either in-person or remote), please add yourselves to the "Attendees" section on the wiki page
    • #info === [COMPLETE] skamath / jflory7 Work on creating the YAML rules files for fedbadges#441 (Hot Topic) and fedbadges#442 (Licensed to Push) ===
    • #info === [IN PROGRESS] commops Review ticket #25, add any feedback / ideas / thoughts towards reorganizing the wiki by subgroups / time periods ( https://fedorahosted.org/fedora-commops/ticket/25 ) ===
      • #info This ticket is on the discussion agenda for today as well.
    • #info === [INCOMPLETE] jflory7 Work on drafting an article about the Flock 2016 CommOps workshop for Community Blog ===
      • #action jflory7 Work on drafting an article about the Flock 2016 CommOps workshop for Community Blog






  • #topic Open Floor
    • No meeting next week due to Flock?

Meeting summary and action items

Full meeting log

Next Meeting