From Fedora Project Wiki

(Add announcements and Community Blog news)
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 34: Line 34:
 
*** #link https://fedoramagazine.org/fedora-24-released/
 
*** #link https://fedoramagazine.org/fedora-24-released/
 
*** #info We're in the middle of it today, team! Fedora 24 released hours ago. Today is a very busy day across Fedora. Check out upgrading your own system if you haven't already yet! :)
 
*** #info We're in the middle of it today, team! Fedora 24 released hours ago. Today is a very busy day across Fedora. Check out upgrading your own system if you haven't already yet! :)
 +
*** #link https://www.facebook.com/TheFedoraProject/posts/10154250457540480
 +
*** #link https://twitter.com/fedora/status/745255602121674754
 +
*** #link https://plus.google.com/+fedora/posts/5aqqppyVuHS
 +
*** #link https://fedoramagazine.org/upgrading-fedora-23-workstation-to-fedora-24/
 
** #info === "Fedora Cloud FAD 2016 Report" ===
 
** #info === "Fedora Cloud FAD 2016 Report" ===
 
*** #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016-report/
 
*** #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016-report/
 
*** #info The Fedora Cloud Working Group finished their Fedora Activity Day this past week. Learn all that was accomplished and what objectives are on the table for the Cloud WG in this article.
 
*** #info The Fedora Cloud Working Group finished their Fedora Activity Day this past week. Learn all that was accomplished and what objectives are on the table for the Cloud WG in this article.
 +
** #info === skamath's super cool statistic generation ===
 +
*** #link https://pagure.io/gsoc-stats
 +
*** #link https://docs.google.com/spreadsheets/d/1VatSWdON08MCLZIdJWRVYeFTMXxvo6HzE4GzrpQRdEo/edit#gid=776866005
 +
*** #link https://github.com/sachinkamath/fedstats-data/tree/master/interns-mid-term
 +
*** #info skamath's tool evaluates different parts of fedmsg activity to generate statistics about the contributions of specific contributors and where they spend their time in Fedora. You can see some of the data that he has collected so far in the above links. You can find the project source on Pagure!
 +
** #info === "Google's security princess talks cybersecurity" ===
 +
*** #link https://opensource.com/life/16/6/interview-parisa-tabriz-google
 +
*** #info decause recently published his latest work on Opensource.com where he interviewed Parisa Tabriz at PyCon 2016!
  
  
Line 66: Line 78:
 
* '''#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 #10 ===
*** #info ""
+
*** #info "CommOps vFAD 2016"
*** #link  
+
*** #link https://fedorahosted.org/fedora-commops/ticket/10
*** description
+
*** #link https://fedoraproject.org/wiki/FAD_CommOps_2016
** #info === Ticket #xx ===
+
*** #link http://goo.gl/forms/ck9Dcxb9vqo6jqh62
*** #info ""
+
*** Last meeting, we wanted to work on getting dates planned and getting input on when to host this. The options were this upcoming weekend (!!) or July 3-4. However, we received low responses on the form (only five responses), and the responses were received were 3 for July 3-4, 2 for June 25-26. This is making it difficult to agree on a specific timeframe for the event. Any thoughts?
*** #link  
+
** #info === Tickets #34, 49, 69 ===
*** description
+
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
** #info === Ticket #xx ===
+
*** #info #49: "[Onboarding Series] CommOps!"
*** #info ""
+
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link  
+
*** #link https://fedorahosted.org/fedora-commops/ticket/57
*** description
+
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
 +
*** skamath filed a ticket for the CommOps on-boarding badge series on the Badges Team Trac.
 +
*** #link https://fedorahosted.org/fedora-badges/ticket/464
 +
*** In the ticket, we have the needed criteria for the badge, as well as a full YAML file ready to be deployed as soon as artwork is available. Are there any other steps in the CommOps on-boarding badge that we want to revisit? Any other points to be brought up? Or is it once this badge is produced, our ticket is closed and we can move onto another sub-project?
 +
** #info === Ticket #71 ===
 +
*** #info "Centralizing Ambassadors / Events resources and utilities"
 +
*** #link https://fedorahosted.org/fedora-commops/ticket/71
 +
*** After last week's discussions, some more efforts were put forth to help make this topic easier to solve for the future (a Hubs ticket was filed for a "News" widget, the "why" aspect of something like FOSCo was explained a bit more, we looked at other newsy examples from Arch and Ubuntu). However, for the immediate, short-term solution to this problem, I believe a wiki page socialized across the project would take some of the *immediate* strain of the Design Team and Ambassadors, especially with F24 happening now and people possibly ordering new media sleeves and more items.
 +
*** #action jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later
  
  
Line 118: Line 138:
  
 
* '''#topic Open Floor'''
 
* '''#topic Open Floor'''
|summary=
+
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-06-21-15.57.html
|log=
+
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-06-21-15.57.log.html
 
|next-meeting=2016-06-28
 
|next-meeting=2016-06-28
 
}}
 
}}

Latest revision as of 18:27, 21 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-21

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-21)
  • #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-06-14/commops.2016-06-14-15.58.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 === decause review the vFAD goals/objectives/etc ===
    • #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
    • #info === decause nail down Flock arrangements and add to fedocal ===
    • #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
    • #info === decause Finish "final" version of F24 GA Release Announcement for review after go/no-go meeting on Thursday ===
    • #info === [COMPLETE] jflory7 Create a WhenIsGood and share with CommOps mailing list to decide on vFAD dates of July 2-3 or June 25-26 ===
    • #info === [COMPLETE] jflory7 Write YAML file for CommOps on-boarding badge based on FAS group sponsorship ===
    • #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
      • #action jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
    • #info === [COMPLETE] commops File a ticket on the Pagure repository for Fedora Hubs about creating a News widget that aggregates different sources of information and puts it together for easy consumption by a reader ===
    • #info === [COMPLETE] jflory7 Update Ticket #71 with the "WHY" perspective in relation to FOSCo ===
    • #info === decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
    • #info === [COMPLETE] jflory7 Look into filing a ticket on Pagure for CCing users / lists from a Pagure issue ===


  • #topic Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Ticket #10 ===
    • #info === Tickets #34, 49, 69 ===
      • #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
      • #info #49: "[Onboarding Series] CommOps!"
      • #link https://fedorahosted.org/fedora-commops/ticket/34
      • #link https://fedorahosted.org/fedora-commops/ticket/57
      • #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
      • skamath filed a ticket for the CommOps on-boarding badge series on the Badges Team Trac.
      • #link https://fedorahosted.org/fedora-badges/ticket/464
      • In the ticket, we have the needed criteria for the badge, as well as a full YAML file ready to be deployed as soon as artwork is available. Are there any other steps in the CommOps on-boarding badge that we want to revisit? Any other points to be brought up? Or is it once this badge is produced, our ticket is closed and we can move onto another sub-project?
    • #info === Ticket #71 ===
      • #info "Centralizing Ambassadors / Events resources and utilities"
      • #link https://fedorahosted.org/fedora-commops/ticket/71
      • After last week's discussions, some more efforts were put forth to help make this topic easier to solve for the future (a Hubs ticket was filed for a "News" widget, the "why" aspect of something like FOSCo was explained a bit more, we looked at other newsy examples from Arch and Ubuntu). However, for the immediate, short-term solution to this problem, I believe a wiki page socialized across the project would take some of the *immediate* strain of the Design Team and Ambassadors, especially with F24 happening now and people possibly ordering new media sleeves and more items.
      • #action jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later





  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting