From Fedora Project Wiki

(Daylight savings is a thing, this always happens, but I always forget)
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 30: Line 30:
  
 
* '''#topic Announcements'''
 
* '''#topic Announcements'''
** #info === "" ===
+
** #info === NoMoreAlpha: Fedora 27 and beyond may not include Alpha release ===
*** #link  
+
*** #link https://fedoraproject.org/wiki/Changes/NoMoreAlpha
*** #info  
+
*** #info Starting in Fedora 27, there may not be any more Alpha releases as part of Fedora. Instead, people who want to try the latest and greatest are encouraged to install Rawhide and use that to help test and be a part of the release testing process.
** #info === "" ===
+
** #info === Fedora is participating in GSoC 2017! ===
*** #link  
+
*** #link https://summerofcode.withgoogle.com/organizations/5622162267308032/
*** #info
+
*** #link https://communityblog.fedoraproject.org/gsoc-2017-mentors-ideas-needed/
** #info === "" ===
+
*** #info On Monday, Fedora was officially announced as a participating organization of Google Summer of Code 2017. You can see more information about our program this year on the Google page, and you can also see a call for mentors and ideas on the Community Blog.
*** #link  
 
*** #info  
 
  
  
 
* '''#topic Action items from last meeting'''
 
* '''#topic Action items from last meeting'''
** #link  
+
** #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/commops.2017-02-21-17.30.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] jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts ===
** #info === ===
+
*** #action jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
** #info === ===
+
** #info === [INCOMPLETE] jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed ===
 +
*** #action jwf Reach out to schyken with suggestions about integrating with the Fedora community based on original article draft
 +
** #info === x3mboy Follow up with LATAM Ambassadors about if a CommBlog article suffices for reimbursement, update ticket #21 with feedback ===
 +
** #info === [INCOMPLETE] jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports ===
 +
*** #action jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports
 +
** #info === [IN PROGRESS] jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion ===
 +
*** #action jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion
  
  
 
* '''#topic Tickets'''
 
* '''#topic Tickets'''
 
** #link https://pagure.io/fedora-commops/issues?tags=meeting
 
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #info === Ticket #xx: "" ===
+
** #info === Ticket #70: " FOSS Student Pack" ===
*** #link https://pagure.io/fedora-commops/issue/xx
+
*** #link https://pagure.io/fedora-commops/issue/70
** #info === Ticket #xx: "" ===
+
*** What we should discuss first is what the goal or objective of this ticket is. While tangible, sponsored items would be nice to include, we should likely look inward a little more first and consider building the "Fedora Student Pack" with resources within our own community that would be helpful to provide for students to get involved with Fedora and the community (calling this "layer 1"). Once layer 1 is established, we can build and support on top of this with "layer 2", which could include financial support from outside organizations. But before doing that, we should look at (1) who it's designed for, (2) what the impact of doing it would be, and lastly (3) what the first layer looks like.  
*** #link https://pagure.io/fedora-commops/issue/xx
 
** #info === Ticket #xx: "" ===
 
*** #link https://pagure.io/fedora-commops/issue/xx
 
  
  
Line 62: Line 63:
 
** #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) "Google Summer of Code (GSoC) 2017: Mentors and ideas needed!" - rhea++
**** #link
+
**** #link https://communityblog.fedoraproject.org/gsoc-2017-mentors-ideas-needed/
**** #info Total Views ( - ):  
+
**** #info Total Views (Feb. 28): 48
**** #link
+
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3458
*** #info (2) "" -  
 
**** #link  
 
**** #info Total Views ( - ):  
 
**** #link  
 
 
** #info === Coming Up in CommBlog ===
 
** #info === Coming Up in CommBlog ===
*** #info (1) ""
+
*** #info (1) "University Connect – PCCOE , Pune" - amsharma
**** #link  
+
**** #link https://communityblog.fedoraproject.org/?p=3448&preview=1&_ppp=6b492d8d04
*** #info (2) ""
+
*** #info (2) "University Connect - D. Y. Patil College, Pune" - amsharma
**** #link  
+
**** #link https://communityblog.fedoraproject.org/?p=3439&preview=1&_ppp=b329602fdc
 +
*** #info (3) "We're looking for instructors to take up IRC classroom sessions" - ankursinha
 +
**** #link https://communityblog.fedoraproject.org/?p=3483&preview=1&_ppp=f761eb1102
  
  
 
* '''#topic Open Floor'''
 
* '''#topic Open Floor'''
|summary=
+
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/commops.2017-02-28-17.29.html
|log=
+
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/commops.2017-02-28-17.29.log.html
 
|next-meeting=2017-03-07
 
|next-meeting=2017-03-07
 
}}
 
}}

Latest revision as of 17:50, 28 February 2017

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2017-02-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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2017-02-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
    • #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
    • 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/2017-02-21/commops.2017-02-21-17.30.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] jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts ===
      • #action jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
    • #info === [INCOMPLETE] jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed ===
      • #action jwf Reach out to schyken with suggestions about integrating with the Fedora community based on original article draft
    • #info === x3mboy Follow up with LATAM Ambassadors about if a CommBlog article suffices for reimbursement, update ticket #21 with feedback ===
    • #info === [INCOMPLETE] jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports ===
      • #action jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports
    • #info === [IN PROGRESS] jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion ===
      • #action jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion


  • #topic Tickets
    • #link https://pagure.io/fedora-commops/issues?tags=meeting
    • #info === Ticket #70: " FOSS Student Pack" ===
      • #link https://pagure.io/fedora-commops/issue/70
      • What we should discuss first is what the goal or objective of this ticket is. While tangible, sponsored items would be nice to include, we should likely look inward a little more first and consider building the "Fedora Student Pack" with resources within our own community that would be helpful to provide for students to get involved with Fedora and the community (calling this "layer 1"). Once layer 1 is established, we can build and support on top of this with "layer 2", which could include financial support from outside organizations. But before doing that, we should look at (1) who it's designed for, (2) what the impact of doing it would be, and lastly (3) what the first layer looks like.



  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting