From Fedora Project Wiki

(Prepare agenda for a future meeting)
 
(Add announcements, action items, and CommBlog)
Line 21: Line 21:
** #info (5) Wiki Gardening
** #info (5) Wiki Gardening
** #info (6) Community Blog
** #info (6) Community Blog
** #info (7) Release Schedule
** #info (7) Open Floor
** #info (8) Open Floor




Line 31: Line 30:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === Fedora 25 Alpha Release: 2016-08-30 ===
*** #link  
*** #link https://fedoraproject.org/wiki/Releases/25/Schedule
*** #info  
*** #info The current targeted date for the Fedora 25 Alpha is for August 30, 2016.
** #info === "" ===
** #info === "List of Flock blogs and more" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
*** #info  
*** #info Brief overview of Flock 2016 with links to individual contributor blog posts and reports about the event. Good way to reflect / review on discussions and focuses from Flock or to see what happened if you were not able to attend.
** #info === "" ===
** #info === "FOSS wave: Bhopal, Madhya Pradesh, India" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-india/
*** #info  
*** #info Ongoing efforts to introduce FOSS, Fedora Quality Assurance, and testing to students across India. Sumantro Mukherjee (sumantrom) is helping lead these efforts. Watch for more information on the Community Blog in coming weeks!
** #info === REMINDER: Pagure migration, 2016-08-29 ===
*** #info Reminder that the migration from Trac to Pagure is targeted for Monday, August 29th, 2016. We will be abandoning Trac soon. More information to come.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-08-16-15.59.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 === [INCOMPLETE] downey Edit original UnixStickers shirt article to include links / mentions of the women's sizes / editions too ===
** #info === ===
*** #action downey Ping jflory7 for editing article / adding paragraph into article
** #info === ===
** #info === skamath file a ticket on fedmsg repo for the mailman bug ===
** #info === ===
** #info === [INCOMPLETE] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
** #info === ===
** #info === [INCOMPLETE] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
*** #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
** #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
*** #action jflory7 Review emails for pending posts on the CommBlog
*** There's more… ;)
** #info === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop ===
*** #action jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
** #info === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
*** #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
** #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
*** #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
** #info === [COMPLETE] jflory7 Remove Ticket #10 from meeting agenda, collaborate with bee2502 on sorting through feedback / ideas from Flock ===




Line 75: Line 87:
** #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 (1) "FOSS wave: Bhopal, Madhya Pradesh, India"
**** #link  
**** #link https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-india/
**** #info Total Views (date - date):  
**** #info Total Views (Aug. 18 - Aug. 22): 18
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2096
*** #info (2) ""
**** #action jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal
**** #link
*** #info (2) "List of Flock blogs and more"
**** #info Total Views (date - date):
**** #link https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
**** #link
**** #info Total Views (Aug. 18 - Aug. 22): 54
*** #info (3) ""
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2185
**** #link  
**** #info Total Views (date - date):  
**** #link  
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "FOSS Wave: Delhi, India" - scheduled 2016-08-23
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2145&preview=1&_ppp=143a11a08f
*** #info (2) ""
*** #info (2) "Fedora 24 Release Party in Singapore" - scheduled 2016-08-24
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2010&preview=1&_ppp=1df831e1a4
*** #info (3) ""
*** #info (3) "Modularity Infrastructure Design" - scheduled 2016-08-25
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2154&preview=1&_ppp=7146c2ee3c
 
*** #info (4) "Say No to Wiki SPAM!"
 
**** #link https://communityblog.fedoraproject.org/?p=2208&preview=1&_ppp=1cf79eb584
* '''#topic Release Schedule'''
*** #info (5) "Globalization improvements in Fedora 24"
** #link https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
**** #link https://communityblog.fedoraproject.org/?p=2212&preview=1&_ppp=005a502ebc
*** #info (6) "Modularity and Containers"
**** #link https://communityblog.fedoraproject.org/?p=2235&preview=1&_ppp=4da4ccff52
*** #info (7) "What are Personas and Why Should you Care?"
**** #link https://communityblog.fedoraproject.org/?p=2230&preview=1&_ppp=33758937f3
*** #info (8) "Heroes of Fedora (HoF) - F24 Alpha"
**** #link https://communityblog.fedoraproject.org/?p=2091&preview=1&_ppp=98aec2b146
*** #info (9) "Heroes of Fedora (HoF) - F24 Beta"
**** #link https://communityblog.fedoraproject.org/?p=2142&preview=1&_ppp=405ee85506
*** #info (10) "Heroes of Fedora (HoF) - F24 Final"
**** #link https://communityblog.fedoraproject.org/?p=2204&preview=1&_ppp=0c855ab7c8





Revision as of 06:16, 23 August 2016

Fedora CommOps Team Meeting Minutes 2016-08-23

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-08-23)
  • #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 === Fedora 25 Alpha Release: 2016-08-30 ===
    • #info === "List of Flock blogs and more" ===
    • #info === "FOSS wave: Bhopal, Madhya Pradesh, India" ===
    • #info === REMINDER: Pagure migration, 2016-08-29 ===
      • #info Reminder that the migration from Trac to Pagure is targeted for Monday, August 29th, 2016. We will be abandoning Trac soon. More information to come.


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-08-16-15.59.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 === [INCOMPLETE] downey Edit original UnixStickers shirt article to include links / mentions of the women's sizes / editions too ===
      • #action downey Ping jflory7 for editing article / adding paragraph into article
    • #info === skamath file a ticket on fedmsg repo for the mailman bug ===
    • #info === [INCOMPLETE] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
    • #info === [INCOMPLETE] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
      • #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
    • #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
      • There's more… ;)
    • #info === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop ===
      • #action jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
    • #info === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
      • #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
    • #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
      • #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
    • #info === [COMPLETE] jflory7 Remove Ticket #10 from meeting agenda, collaborate with bee2502 on sorting through feedback / ideas from Flock ===





  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting