From Fedora Project Wiki

(Create outline for next meeting)
 
(Add minutes and logs)
 
(3 intermediate revisions by the same user not shown)
Line 6: Line 6:
|MINUTE=00
|MINUTE=00
|CHANNEL=#fedora-meeting
|CHANNEL=#fedora-meeting
|CHAIR=decause
|CHAIR=jflory7
|agenda=* '''#startmeeting Fedora CommOps (2016-06-28)'''
|agenda=* '''#startmeeting Fedora CommOps (2016-06-28)'''
* '''#meetingname commops'''
* '''#meetingname commops'''
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Friends. Features. Freedom. First. Forever." ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/CG5JS4DQ3G2TVA5YZX7LBOSXVNCUPTIB/
*** #info  
*** #info On Friday, decause announced on the mailing list that he will be leaving his position at Red Hat to become the Open Source Campaign Manager for a candidate in the US elections. We wish decause well in his future endeavors and will always be happy to see him in Fedora whenever he has the time to stop by. For the time being, the Fedora Community Lead position will remain open.
** #info === "" ===
** #info === "Behind the new Fedora Developer Portal" ===
*** #link  
*** #link https://fedoramagazine.org/behind-new-fedora-developer-portal/
*** #info  
*** #info The Developer Portal for developers using Fedora or wanting to contribute to Fedora has had some new changes. Read up on what's new in the Developer Portal and a little bit of background behind its inception in the Fedora Magazine article.
** #info === "" ===
** #info === Google Summer of Code midterm evaluations ended ===
*** #link  
*** #link https://summerofcode.withgoogle.com/how-it-works/
*** #info  
*** #info Google Summer of Code 2016 midterm evaluations ended yesterday. Students received a pass/fail rating from their mentor(s) on their project status so far and are moving on the final period of their project proposals. Students, make sure to reach out on the mailing lists, communicate with blog posts, and participate in IRC discussions for the final phase of your projects!




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-06-21-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 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 === ===
** #info === [CHANGED] decause review the vFAD goals / objectives / etc. ===
** #info === ===
*** #action jflory7 Move forward with making final plans for vFAD or reconsider plans for Flock workshop (???)
** #info === ===
** #info === [CHANGED] decause nail down Flock arrangements and add to fedocal ===
** #info === ===
*** #info Further Flock arrangements will be handled by the Flock staff for now, as far as I can tell? --[[User:Jflory7|Jflory7]] ([[User talk:Jflory7|talk]]) 03:29, 28 June 2016 (UTC)
** #info === ===
** #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
*** #action jflory7 jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
** #info === [INCOMPLETE] decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
*** #info Red Hat Summit happening now.
** #info === [INCOMPLETE] 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 ===
*** #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
** #info === [IN PROGRESS] jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response ===
*** #action jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response
** #info === [COMPLETE] jflory7 Create a placeholder article for F22 EoL article in CommBlog so we keep on the agenda ===
*** #link https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5cd19f98b
** #info === [COMPLETE] jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article ===




* '''#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 ===
*** We agreed for the vFAD to be July 3 - 4, but organizing this now may have some unexpected challenges with the decause's departure. I was trying to think about the vFAD in relation to the CommOps workshop at Flock, but I'm wondering now if it might be better to change focus on the CommOps workshop since it no longer has a lead (and I don't know if I want to see it slip off the schedule). :) Maybe it would be better to refocus efforts for planning for our Flock workshop? Thoughts?
*** #info ""
** #info === Tickets #34, 57 ===
*** #link  
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** description
*** #info #49: "[Onboarding Series] CommOps!"
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #info ""
*** #link https://fedorahosted.org/fedora-commops/ticket/57
*** #link  
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** description
*** #link https://fedorahosted.org/fedora-badges/ticket/464
*** Once artwork is designed for Fedora Badges Ticket #464, our corresponding ticket for Ticket #57 should be able to be closed. For now, we can adjust focus to another subproject / team that was on our list, like Infrastructure or Modularity.
** #info === Ticket #71 ===
*** #info "Centralizing Ambassadors / Events resources and utilities"
*** #link https://fedorahosted.org/fedora-commops/ticket/71
*** '''SKIP''': This ticket will be skipped in the meeting for now until jflory7 has a chance to complete his previous action for creating the wiki page breaking down the process in the short-term between Ambassadors and the Design Team.




Line 75: Line 90:
** #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
** #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
** #info === This Week in CommBlog ===
** #info === This Week in CommBlog ===
*** #info (1) ""
*** #info No new posts published this week!
**** #link
**** #info Total Views (date - date):
**** #link
*** #info (2) ""
**** #link
**** #info Total Views (date - date):
**** #link
*** #info (3) ""
**** #link
**** #info Total Views (date - date):
**** #link
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Southeast Linux Fest 2016"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=e048ea9a97
*** #info (2) ""
*** #info (2) "Hosting your own Fedora Test Day"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=c49265f3f2
*** #info (3) ""
*** #info (3) "Fedora 22: End Of Life, 2016 July 19"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5cd19f98b
*** #info (4) "Getting started with 'update-testing' Fedora QA part 2"
**** #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=b50b2a4e03
*** #info (5) "Getting started with Fedora QA part 3"
**** #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=f84ad57ee4




Line 101: Line 109:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-06-28-15.55.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-06-28-15.55.log.html
|next-meeting=2016-07-05
|next-meeting=2016-07-05
}}
}}

Latest revision as of 17:21, 28 June 2016

Fedora CommOps Team Meeting Minutes 2016-06-28

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

CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-06-28)
  • #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 Announcements
    • #info === "Friends. Features. Freedom. First. Forever." ===
    • #info === "Behind the new Fedora Developer Portal" ===
      • #link https://fedoramagazine.org/behind-new-fedora-developer-portal/
      • #info The Developer Portal for developers using Fedora or wanting to contribute to Fedora has had some new changes. Read up on what's new in the Developer Portal and a little bit of background behind its inception in the Fedora Magazine article.
    • #info === Google Summer of Code midterm evaluations ended ===
      • #link https://summerofcode.withgoogle.com/how-it-works/
      • #info Google Summer of Code 2016 midterm evaluations ended yesterday. Students received a pass/fail rating from their mentor(s) on their project status so far and are moving on the final period of their project proposals. Students, make sure to reach out on the mailing lists, communicate with blog posts, and participate in IRC discussions for the final phase of your projects!


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-06-21-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 === [CHANGED] decause review the vFAD goals / objectives / etc. ===
      • #action jflory7 Move forward with making final plans for vFAD or reconsider plans for Flock workshop (???)
    • #info === [CHANGED] decause nail down Flock arrangements and add to fedocal ===
      • #info Further Flock arrangements will be handled by the Flock staff for now, as far as I can tell? --Jflory7 (talk) 03:29, 28 June 2016 (UTC)
    • #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
      • #action jflory7 jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
    • #info === [INCOMPLETE] decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
      • #info Red Hat Summit happening now.
    • #info === [INCOMPLETE] 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 ===
      • #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
    • #info === [IN PROGRESS] jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response ===
      • #action jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response
    • #info === [COMPLETE] jflory7 Create a placeholder article for F22 EoL article in CommBlog so we keep on the agenda ===
    • #info === [COMPLETE] jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article ===


  • #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
      • We agreed for the vFAD to be July 3 - 4, but organizing this now may have some unexpected challenges with the decause's departure. I was trying to think about the vFAD in relation to the CommOps workshop at Flock, but I'm wondering now if it might be better to change focus on the CommOps workshop since it no longer has a lead (and I don't know if I want to see it slip off the schedule). :) Maybe it would be better to refocus efforts for planning for our Flock workshop? Thoughts?
    • #info === Tickets #34, 57 ===
    • #info === Ticket #71 ===
      • #info "Centralizing Ambassadors / Events resources and utilities"
      • #link https://fedorahosted.org/fedora-commops/ticket/71
      • SKIP: This ticket will be skipped in the meeting for now until jflory7 has a chance to complete his previous action for creating the wiki page breaking down the process in the short-term between Ambassadors and the Design Team.





  • #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-28&oldid=459105"