September 2018 - [MOVED TO DISCOURSE] Community Operations (CommOps) - https://discussion.fedoraproject.org/tag/commops

Self-Introduction
by Yajushi Srivastava 14 Oct '18

14 Oct '18

Hello Team, I'm a final year undergraduate, pursuing Computer Science Engineering from a private college in Jaipur, India. I have been training in Linux System Administration for over a year. Apart from that, I have been working with OpenStack, AWS and DevOps technologies like Docker and Ansible. I have always been a FOSS/OSS enthusiast because I believe in the scenic genius of Sapiens. It’s crucial for us to collaborate, in order to grow, and Open Source does just that. It provides us with a liberal way to share and to know. Despite our possible differences in political ideologies, beliefs, race and administrative boundaries. We are all bound by our love of technology. I have used several Linux distributions, but it’s in Fedora that I found my haven. I love contributing to Open Source, in whichever way I can. I would like to take my skills to reach out to as many people as I can, and share Fedora with them. And, in sharing, I know that I’ll come across essentials that I may have overlooked in the past. I believe I am an empathetic and creative person. I love knowing people and their stories, and I believe that everyone is inspirational and has limitless potential. I would like to put my skills to use by being a part of CommOps. I’m not yet involved with other things in Fedora. But I’d like to be a part of the Fedora Ambassadors Project. There are several people working on Linux in and around my city, in one way or the other, but often in isolation. And, I would like to encourage collaboration and introduce them to our global community. I represent Docker’s Jaipur Chapter as the Community Leader, and PyJaipur (Official Local Python User’s Group) as the Content Management Lead. I see CommOps as crucial for people involved in Fedora to keep track of the several projects, making the contribution and collaboration process feasible. I also appreciate how CommOps connects people with stories beyond work, through acknowledgement programs and interviews. I look forward to understanding Community Health Monitoring in detail. As far as the questions go, a lot IRC lurking may be required. However, it would be great if somebody could help me get started with my first task. Thanks. Yajushi Srivastava

2 2

Introducing myself
by Harshit Modi 09 Oct '18

09 Oct '18

Hi CommOps Team, I am Harshit Modi. I am interested in getting involved in the Fedora community by contributing to the Fedora CommOps. As Fedora CommOps deals with all other fedora projects, it will provide me good opportunity to work closely with all the community. I am current graduate student at UT Arlington with computer science major. I have 2 years of experience in web development. I have proper knowledge in web stack and had used many open source technologies. As I move forward in my career, I want to dig into more in open source projects. And for that I want to join such project and learn from the highly motivated community. Fedora is well known in open source world and has diverse fields to work with. And CommOps has many active contributors and joining them will help me jump on board and become the part of fedora community. So I am confident that this opportunity will benefit us both. Please let me know if you need any additional information. Thanks! Regards, Harshit Modi https://www.linkedin.com/in/harshit-modi/

2 1

Easyfix + WhatCanIDoForFedora
by Brian Exelbierd 04 Oct '18

04 Oct '18

I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else. Warning - rough edges ahead! --- Conversations with several people have resulted in distilling the following idea: = EasyFix == Changing metadata Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix The table would now include two additional columns (optional) Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support Col 2 = existing point of contact Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.) Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.) == Changing fedoraproject.org/easyfix Today we show only two categories: Issues from Pagure/Github and Bugzillas I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists. For BZs we are either going to have to guess based on BZ metadata or leave them lumped together. = WCIDFF WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire. = Marketing/Promotion The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances. What do people think? regards, bex

4 5

Fedocal article ready to review
by Eduard Lucena 04 Oct '18

04 Oct '18

Hi team, I've written an article about the use of fedocal to promote events. The link to the preview is: https://communityblog.fedoraproject.org/?p=6639&preview=1&_ppp=32c3eaf7c5 I hope you can review it and publish it, to promote this article in Ambassadors and related ML. Br, Eduard Lucena x3mboy

2 3

[Fedocal] Reminder meeting : CommOps Hack Session
by jflory7＠fedoraproject.org 29 Sep '18

29 Sep '18

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2018-09-30 from 17:00:00 to 18:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed. All CommOpsers are welcome to attend, even if it's only for part of the time slot. More information available at: [https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki… Source: https://apps.fedoraproject.org/calendar/meeting/8733/

1 0

[Fedocal] Reminder meeting : CommOps weekly meeting
by jflory7＠fedoraproject.org 27 Sep '18

27 Sep '18

Dear all, You are kindly invited to the meeting: CommOps weekly meeting on 2018-09-26 from 16:00:00 to 17:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets marked for "[review at meeting](https://pagure.io/fedora-commops/issues?status=Open&priority=20)" in our [Pagure repository](https://pagure.io/fedora-commops). More information about CommOps is found [here](https://docs.fedoraproject.org/en-US/commops/). Source: https://apps.fedoraproject.org/calendar/meeting/8732/

1 0

Re: [badges] Event Badges - Policy Discussion
by Justin W. Flory 27 Sep '18

27 Sep '18

Hi! I've been thinking about this thread for a while. This is great feedback and I wonder how we could try to improve the contributing experience for Fedora Badges. In 2015, an early idea was to equip CommOps to work with the Design Team on creating and establishing badge policy and strategy. Perhaps we could revisit this again. I'd like to figure out where we can begin tracking this feedback and organize an effort to address some of these. (One example on my mind is hosting a docs.fedoraproject.org page on Fedora Badges to explain policy and badge rules. It could also be a "new home" for the style guide.) On 8/18/18 9:57 AM, Marie Nordin wrote: > Hello All! > > I am opening up this thread to discuss event badges-- I think it would > be helpful to brainstorm and finalize some standards/regulations > regarding event badges with the input from leadership, design, and > development side. I will do my best to list all the different > thoughts/issues that have been raised. Please feel free to jump in with > other points and/or correct if I don't have the latest info. > > _*Current policy:*_ > - 1 event badge per event (non Fedora, or Fedora) > - 3 event badges per Flock > - attendee > - contributor > - party attendee > - 1 event badge per Fudcon > - attendee > - in the past we have also had speaker/organizer badges > > _*Common issues we encounter:*_ > - People pointing to older badges and asking why we don't make them any more > - I actually haven't seen this as much lately, but have in the past > - People not knowing what or where to find a policy regarding event > badges. People pose potential badges, and we have to turn them down. > - From creation/pushing to site aspect, not getting enough notice that > an event badge is needed, or it gets lost in a sea of update emails > (best to request an event badge at least 1-1.5 months in advance, so we > can see & address at a badges meeting (held bi-weekly unless something > comes up)). Then there is time for gathering of resources (logos), > creation of artwork, and pushing to site. > > _*Outdated badges:*_ > - We have old speaker/organizer badges. Do we want to remove those and > replace them with the new contributor badges? Would this be too big an > effort for the outcome? > > _*New ideas:*_ > - Fedora meet up badge - IMHO, if we created this it should just be one > badge overall that is used for multiple events? Or yearly, so "you > attended a fedora meet up in 2018" I think this is a great idea for > people who are unable to make it to some of the larger conferences, > giving them a chance to earn event badges. On the other side, those > privileged to go to the larger badges will most likely earn these as > well. https://pagure.io/fedora-badges/issue/641 > - Non-Fedora badges - this idea made by Bex on issue 642. I would be > interested to hear more about what this would entail and how to > implement. https://pagure.io/fedora-badges/issue/642 > > _*More Thoughts:*_ > - Why did we move from speaker/organizer badges to contributor badges? > Who made this decision and why? > - A note here is that I am fine with this policy, I am just curious how > this decision came about, and why it wasn't really finalized > "officially" and discussed with the badges team as a whole. I think it > was announced on a badge issue, and we then had to adapt. > > > That is all I have for now. I think it would be great if we had input on > these thoughts, and any others, from all the people who makes badges > happen :) > > Best, > - riecatnor > > > _______________________________________________ > Fedora Badges mailing list -- badges(a)lists.fedoraproject.org > To unsubscribe send an email to badges-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/badges@lists.fedoraproject.or… > -- Cheers, Justin W. Flory jflory7(a)gmail.com

2 3

[Meeting] [2018-09-26] Discourse migration
by Justin W. Flory 26 Sep '18

26 Sep '18

The weekly CommOps meeting came to an end a bit ago. We were low bandwidth so it was a quick meeting. We covered the following: * Currently on target for Appreciation Week in November * Discourse migration beginning next Monday Thanks everyone for participating – see you around IRC or elsewhere. = = = = = Meeting ended Wed Sep 26 16:40:37 2018 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-09… Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-09… Log: https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-09… * * * * * ============================================ #fedora-commops: Fedora CommOps (2018-09-26) ============================================ Meeting started by jwf at 16:08:35 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-09-26/commops.2018-09… . Meeting summary --------------- * Agenda (jwf, 16:08:43) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fed… (jwf, 16:08:47) * (1) Roll call / Q&A (jwf, 16:08:50) * (2) Announcements (jwf, 16:08:52) * (3) Action items from last meeting (jwf, 16:08:54) * (4) Tickets (jwf, 16:08:56) * (5) Open floor (jwf, 16:08:58) * Roll call / Q&A (jwf, 16:09:02) * Name; Timezone; Sub-projects/Interest Areas (jwf, 16:09:04) * ACTION: commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] (jwf, 16:09:08) * Justin W. Flory; UTC-5; CommOps, D&I Team, Mindshare (for a month more), Fedora Badges sysadmin (jwf, 16:09:34) * Ben Cotton; UTC-4; FPgM (bcotton, 16:09:45) * Announcements (jwf, 16:11:57) * === "FPgM report: 2018-38" === (jwf, 16:12:04) * LINK: https://communityblog.fedoraproject.org/fpgm-report-2018-38/ (jwf, 16:12:04) * This week in Fedora is brought to you in part by bcotton. (jwf, 16:12:04) * === "Submit a Fedora talk to DevConf.cz 2019" === (jwf, 16:12:46) * LINK: https://communityblog.fedoraproject.org/submit-fedora-talk-devconf-cz-2019/ (jwf, 16:12:46) * The CfP for the DevConf devops conference in Brno, Czech Republic is now open. Fedora topics welcome! (jwf, 16:12:46) * === "Announcing the release of Fedora 29 Beta" === (jwf, 16:14:06) * LINK: https://fedoramagazine.org/announcing-fedora-29-beta/ (jwf, 16:14:11) * Fedora 29 Beta launched this week! Get a sneak peek into what's ahead for Fedora and what's planned for the final release next month. (jwf, 16:14:36) * Action items from last meeting (jwf, 16:15:35) * LINK: https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09… (jwf, 16:15:38) * 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 if needed. If no status, we'll try to get a quick update and move forward. (jwf, 16:15:42) * === [COMPLETE] "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" === (jwf, 16:15:54) * === [DELAYED] "jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Sept. 26" === (jwf, 16:16:31) * ACTION: jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3 (jwf, 16:16:31) * === [COMPLETE] "jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week" === (jwf, 16:17:13) * We reached out to pingou via email to see if Nuancier can be used for FAW. Might be a slow response since a major Pagure update released this week too. (jwf, 16:17:13) * === [IN PROGRESS] "bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3)" === (jwf, 16:17:52) * ACTION: bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) (jwf, 16:17:53) * === [COMPLETE] "bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings)" === (jwf, 16:18:25) * === [COMPLETE] "bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings)" === (jwf, 16:18:53) * LINK: https://pagure.io/fedora-commops/issue/184 (jwf, 16:18:53) * Tickets (jwf, 16:19:47) * LINK: https://pagure.io/fedora-commops/issues?status=Open&priority=20 (jwf, 16:19:50) * Ticket #110: "Fedora Appreciation Week 2018" (jwf, 16:20:34) * LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 16:20:34) * LINK: https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org (jwf, 16:20:34) * No updates as of now; bt0 and jwf working with pingou for using Nuancier. dhanesh95 filed tickets for Design and Badges. Still need a common header for CommBlog posts published during FAW, but may slip to next month. (jwf, 16:23:38) * Ticket #178: "Pilot run a CommOps section on discussion.fedoraproject.org" (jwf, 16:24:34) * LINK: https://pagure.io/fedora-commops/issue/178 (jwf, 16:24:34) * LINK: https://discussion.fedoraproject.org/ (jwf, 16:24:34) * Work to do before Monday, Oct. 1 launch: (1) explicitly announce transition on list, (2) set up an auto-mailer message for the mailing list about Discourse, (3) set up / configure the CommOps subforum with help from sanja (jwf, 16:27:34) * Fedocal automated email messages need consideration (jwf, 16:31:12) * ACTION: jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26 (jwf, 16:32:29) * ACTION: jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30 (jwf, 16:33:01) * Ticket #168: "Propose a set of Pagure tags than help the onboarding process" (jwf, 16:34:35) * LINK: https://pagure.io/fedora-commops/issue/168 (jwf, 16:34:36) * Next Steps: find the correct place for this docs (CommOps docs?? another repo, a brand new docs page?) (jwf, 16:34:36) * ACTION: bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3 (jwf, 16:36:20) * Open floor (jwf, 16:36:47) * LINK: https://pagure.io/wordcloudbot (jwf, 16:38:40) Meeting ended at 16:40:37 UTC. Action Items ------------ * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3 * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26 * jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30 * bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3 Action Items, by person ----------------------- * bt0 * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * bt0 Update Ticket #168 (Pagure tags ticket) by next meeting on Wednesday, Oct. 3 * commops * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * jwf * jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Oct. 3 * jwf Send an email announcement to CommOps list to boost awareness of upcoming Mailman => Discourse migration experiment by end of day Wednesday, Sept. 26 * jwf Set up auto-email response for new threads on CommOps list to explain Discourse migration by Sunday, Sept. 30 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (127) * zodbot (11) * fcommops-tg1 (7) * bcotton (6) * nb (2) * labbott (1) * bt0 (0) * commops (0) * bee2502 (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Fedocal] Reminder meeting : CommOps Hack Session
by jflory7＠fedoraproject.org 22 Sep '18

22 Sep '18

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2018-09-23 from 17:00:00 to 18:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed. All CommOpsers are welcome to attend, even if it's only for part of the time slot. More information available at: [https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki… Source: https://apps.fedoraproject.org/calendar/meeting/8733/

1 0

Friday reading list: "How to feel connected on a distributed team"
by Justin W. Flory 21 Sep '18

21 Sep '18

Hi all, This came up on my Twitter feed and I thought it was a good article on the experience of working remote and building a sense of community in a team: https://opensource.com/article/18/9/connected-on-distributed-team In the context of Fedora Appreciation Week, I thought it made a lot of sense. :-) -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Minutes] [2018-09-19] Community picture voting, Discourse pilot, Pagure labels
by Justin W. Flory 19 Sep '18

19 Sep '18

Hi all! This week's meeting (at our new day and time) just came to a close. This week's topics included: * Appreciation Week follow-up: using Nuancier for community to submit their own pictures * Discourse pilot: Trialing discussions.fedoraproject.org for two months starting on Oct. 1 2018 * Pagure labels: Putting together the first pieces of the on-boarding guide Lots of cool stuff is going on. More details are below in the minutes. Thanks everyone for participating today. See you next week! = = = = = Meeting ended Wed Sep 19 17:09:06 2018 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09… Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09… Log: https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09… * * * * * ============================================ #fedora-commops: Fedora CommOps (2018-09-19) ============================================ Meeting started by jwf at 16:01:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-09-19/commops.2018-09… . Meeting summary --------------- * Agenda (jwf, 16:01:48) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fed… (jwf, 16:01:52) * (1) Roll call / Q&A (jwf, 16:02:03) * (2) Announcements (jwf, 16:02:05) * (3) Action items from last meeting (jwf, 16:02:07) * (4) Tickets (jwf, 16:02:09) * (5) Open floor (jwf, 16:02:11) * Roll call / Q&A (jwf, 16:02:13) * Name; Timezone; Sub-projects/Interest Areas (jwf, 16:02:15) * ACTION: commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] (jwf, 16:02:19) * Justin W. Flory; UTC-5; CommOps, D&I, others (jwf, 16:03:11) * Ben Cotton; UTC-4; FPgM (bcotton, 16:03:15) * Alberto Rodríguez; UTC-5; today mainly science; looking from telegram (jwf, 16:04:03) * Announcements (jwf, 16:05:55) * === "FPgM report: 2018-37" === (jwf, 16:06:03) * LINK: https://communityblog.fedoraproject.org/fpgm-report-2018-37/ (jwf, 16:06:07) * This week in Fedora is brought to you in part by bcotton, as we slowly move closer to the Sept. 25 Fedora 29 Beta launch. (jwf, 16:06:10) * === "Say thank you this November during Fedora Appreciation Week 2018" === (jwf, 16:06:14) * LINK: https://communityblog.fedoraproject.org/fedora-appreciation-week-2018/ (jwf, 16:06:17) * Extra, extra! Read more about Fedora Appreciation Week, coming this November to the Fedora Project community. (Did I mention Contributor Stories?) (jwf, 16:06:22) * === Fedora Women's Day resource pack === (jwf, 16:06:26) * LINK: https://docs.fedoraproject.org/en-US/diversity-inclusion/fedora-womens-day/… (jwf, 16:06:29) * A neat collection of resources. It aims to promote key, critical parts of Fedora and share them with representatives of Fedora at events. A lot of it is based off of the Marketing team's work! (jwf, 16:06:33) * Action items from last meeting (jwf, 16:08:11) * LINK: https://meetbot.fedoraproject.org/teams/commops/commops.2018-09-10-14.30.ht… (jwf, 16:08:16) * 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 if needed. If no status, we'll try to get a quick update and move forward. (jwf, 16:08:22) * === [In Progress] "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" === (jwf, 16:08:28) * ACTION: bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) (jwf, 16:08:33) * === [DELAYED] "jwf Write a CommBlog article summarizing CommOps @ Flock by Monday, Sept. 17" === (jwf, 16:08:38) * ACTION: jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Sept. 26 (jwf, 16:08:41) * === [COMPLETE] "bt0 will send a mail asking for help to write the docs about mentors best practices" === (jwf, 16:10:52) * LINK: https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.o… (jwf, 16:10:57) * Tickets (jwf, 16:12:23) * LINK: https://pagure.io/fedora-commops/issues?status=Open&priority=20 (jwf, 16:12:26) * Ticket #110: "Fedora Appreciation Week 2018" (jwf, 16:12:59) * LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 16:12:59) * LINK: https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org (jwf, 16:12:59) * Next steps: (1) Confirming final status of Fedora Happiness Packets with @algogator, @bee2502, @jonatoni, and (2) gathering pictures of community members to show on Community Blog / YouTube slideshow (jwf, 16:13:14) * IDEA: jwf had a crazy idea of using Nuancier, the tool used for supplementary wallpapers, for people to submit their favorite pictures and have people vote on them. Too crazy? (jwf, 16:15:00) * ACTION: jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week (jwf, 16:23:22) * AGREED: Will follow-up with Nuancier discussion with pingou and follow-up on design tickets for FAW (jwf, 16:28:34) * Ticket #178: "Pilot run a CommOps section on discussion.fedoraproject.org" (jwf, 16:28:39) * LINK: https://pagure.io/fedora-commops/issue/178 (jwf, 16:28:43) * HELP: Do we want to trial replacing our mailing list with a new category on Fedora's Discourse site? (jwf, 16:28:48) * LINK: https://discussion.fedoraproject.org/ (jwf, 16:28:52) * AGREED: We will run a trial of using discourse instead of the commops mailing list from 1 Oct 2018 through 30 Nov 2018 (jwf, 16:38:44) * Ticket #168: "Propose a set of Pagure tags than help the onboarding process" (jwf, 16:39:45) * LINK: https://pagure.io/fedora-commops/issue/168 (jwf, 16:39:46) * Next Steps: find the correct place for this docs (CommOps docs?? another repo, a brand new docs page?) (jwf, 16:39:52) * LINK: https://pagure.io/fedora-commops/onboarding-guide (jwf, 16:41:41) * IDEA: Centralizing the on-boarding guide underneath CommOps' existing documentation (jwf, 16:45:21) * bcotton also trying to create similar resources for project management resources across Fedora (jwf, 16:45:46) * IDEA: CommOps can take a strong opinion on the content and guide other teams (e.g. Join SIG) to it (jwf, 16:46:08) * ACTION: bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) (jwf, 16:52:51) * Open floor (jwf, 16:54:55) * ACTION: bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings) (jwf, 17:01:41) Meeting ended at 17:09:06 UTC. Action Items ------------ * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) * jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Sept. 26 * jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings) Action Items, by person ----------------------- * bcotton * bcotton File a new CommOps ticket about an editorial calendar for the CommBlog to prevent editors stepping on toes for scheduling articles (and other ways to improve awareness of CommBlog happenings) * bt0 * bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) * jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * commops * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * bt0 Collect info on current Pagure issue tags used in fedora-commops / fedora-marketing and add proposal as comment to ticket #168 (by Wednesday, Oct. 3) * jwf * jwf Write a CommBlog article summarizing CommOps @ Flock by Wednesday, Sept. 26 * jwf Work with bt0 and pingou to configure a new event to collect and vote on community photos in Nuancier for Fedora Appreciation Week * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (206) * fcommops-tg1 (61) * bcotton (23) * zodbot (15) * nb (2) * commopsbot (1) * bt0 (0) * commops (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Fedocal] Reminder meeting : CommOps weekly meeting
by jflory7＠fedoraproject.org 18 Sep '18

18 Sep '18

Dear all, You are kindly invited to the meeting: CommOps weekly meeting on 2018-09-19 from 16:00:00 to 17:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets marked for "[review at meeting](https://pagure.io/fedora-commops/issues?status=Open&priority=20)" in our [Pagure repository](https://pagure.io/fedora-commops). More information about CommOps is found [here](https://docs.fedoraproject.org/en-US/commops/). Source: https://apps.fedoraproject.org/calendar/meeting/8732/

1 0

New meeting time: Wednesdays, 16:00-17:00 UTC
by Justin W. Flory 16 Sep '18

16 Sep '18

Hi all, The new meeting time for CommOps is on Wednesdays, 16:00 – 17:00 UTC. https://apps.fedoraproject.org/calendar/meeting/8732/ The new time was selected from the WhenIsGood poll sent last week. Some common time zone conversions: * 09:00 US/Pacific * 12:00 US/Eastern * 16:00 UTC * 18:00 CEST * 21:30 IST Our next meeting will be this Wednesday, Sept. 19th. Hope to see you then! -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Fedocal] Reminder meeting : CommOps weekly meeting
by jflory7＠fedoraproject.org 16 Sep '18

16 Sep '18

Dear all, You are kindly invited to the meeting: CommOps weekly meeting on 2018-09-17 from 14:30:00 to 15:30:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets tagged as "[meeting](https://pagure.io/fedora-commops/issues?status=Open&tags=meeting)" in our [Pagure repository](https://pagure.io/fedora-commops). More information about CommOps is found [here](https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/d…. Source: https://apps.fedoraproject.org/calendar/meeting/8732/

1 0

Ticket #133 Creating summer coding "best practices" docs for mentors
by Alberto Rodriguez Sanchez 15 Sep '18

15 Sep '18

Hi team, I need to ask if somebody is interested in contributing with the (g)soc best practices for mentors, if you are, please check the ticket[1] for more information. Regards. [1] https://pagure.io/fedora-commops/issue/133

1 0

[Fedocal] Reminder meeting : CommOps Hack Session
by jflory7＠fedoraproject.org 15 Sep '18

15 Sep '18

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2018-09-16 from 17:00:00 to 18:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed. All CommOpsers are welcome to attend, even if it's only for part of the time slot. More information available at: [https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki… Source: https://apps.fedoraproject.org/calendar/meeting/8733/

1 0

[draft ready for review] Say thank you this November during Fedora Appreciation Week
by Justin W. Flory 10 Sep '18

10 Sep '18

Hi all, As discussed at the last meeting, the final draft of the Appreciation Week announcement article is ready for review; please review the draft and leave any feedback before Thursday, Sept. 13. https://docs.google.com/document/d/1CZbKirCS7OWY2pxjoI0-twA59n__gWqjjNaa3Jy… This gives a short introduction to FAW and also gives a boost to the Contributor Stories. I hope to schedule this article for Tuesday, Sept. 18. Please take a look and leave any comments in the document before Thursday, Sept. 13. I'll move it to the CommBlog and schedule it shortly after. Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

4 4

Meeting Minutes 09-10-2018
by Alberto Rodriguez Sanchez 10 Sep '18

10 Sep '18

Hello CommOps Team, Here the minutes of our weekly meeting: Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-09-10/commops.2018-09… Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-09-10/commops.2018-09… Log: https://meetbot.fedoraproject.org/fedora-commops/2018-09-10/commops.2018-09… ============================================ #fedora-commops: Fedora CommOps (2018-09-10) ============================================ Meeting started by bt0 at 14:30:31 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-09-10/commops.2018-09… . Meeting summary --------------- * Agenda (bt0, 14:31:18) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fed… (bt0, 14:31:45) * (1) Roll call / Q&A (bt0, 14:31:46) * (2) Announcements (bt0, 14:31:46) * (3) Action items from last meeting (bt0, 14:31:46) * (4) Tickets (bt0, 14:31:46) * (5) Open floor (bt0, 14:31:48) * Roll call / Q&A (bt0, 14:33:01) * Name; Timezone; Sub-projects/Interest Areas (bt0, 14:33:44) * ACTION: commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] (bt0, 14:33:53) * Alberto Rodriguez S; UTC-6;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Marketing (Member), Ambassadors (Member), Fedora-Join(Member) ,Cats (lover) (bt0, 14:35:14) * Ben Cotton; UTC-4; FPgM (bcotton, 14:35:23) * Dhanesh B. Sabane, UTC+5:30, CommOps, Join, Python, Packaging, loves cats (dhanesh95, 14:38:49) * Announcements (bt0, 14:44:55) * === "FPgM report: 2018–36" === (bt0, 14:45:18) * LINK: https://communityblog.fedoraproject.org/fpgm-report-2018-36/ (bt0, 14:45:22) * Another weekly report by FPgM bcotton. See what changes were accepted in the upcoming Fedora 30 release. (bt0, 14:45:22) * === "fedora-infra/datagrepper - Python 3 support" === (bt0, 14:49:02) * LINK: https://github.com/fedora-infra/datagrepper/pull/2144 (bt0, 14:49:03) * Datagrepper now supports Python 3! (bt0, 14:49:03) * === "Test Day: Virtualization 2018-09-11" === (bt0, 14:50:35) * LINK: https://communityblog.fedoraproject.org/test-day-virtualization-2018-09-11/ (bt0, 14:50:36) * Action items from last meeting (bt0, 14:53:46) * LINK: https://meetbot.fedoraproject.org/fedora-commops/2018-09-03/commops.2018-09… (bt0, 14:54:01) * 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 if needed. If no status, we'll try to get a quick update and move forward. (bt0, 14:54:01) * === [COMPLETE] "jwf Finish CommBlog article for Appreciation Week announcement by Monday, Sept. 10" === (bt0, 14:54:20) * LINK: https://docs.google.com/document/d/1CZbKirCS7OWY2pxjoI0-twA59n__gWqjjNaa3Jy… (bt0, 14:54:20) * See the mailing list for more info. Please leave feedback by Thursday, Sept. 13. (bt0, 14:54:21) * === [COMPLETE] "jwf Update Pagure tickets with new comments from Flock discussion / session by Monday, October 10" === (bt0, 14:55:19) * All existing tickets covered at Flock now have updated comments to summarize in-person discussion. (bt0, 14:55:19) * === [In Progress] "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" === (bt0, 14:55:47) * ACTION: "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" (bt0, 14:56:02) * === [COMPLETE] "jwf Update Pagure tickets with new comments from Flock discussion / session by Monday, October 10" === (bt0, 14:56:22) * All existing tickets covered at Flock now have updated comments to summarize in-person discussion. (bt0, 14:56:22) * === [NOT YET STARTED] "jwf If possible, a CommBlog article summarizing CommOps @ Flock by Monday, October 17" === (bt0, 14:56:38) * ACTION: jwf Write a CommBlog article summarizing CommOps @ Flock by Monday, October 17 (bt0, 14:56:39) * === [COMPLETE] "jwf Set up and send a WhenIsGood poll to the mailing list for finding a new meeting time from Sept. to Dec. 2018" === (bt0, 14:56:56) * LINK: http://whenisgood.net/fedora/commops/fall-2018-meetingg (bt 0, 14:56:56) * Please add your availability to select a new meeting before Friday, Sept. 14. A new time will be chosen over the following weekend. (bt0, 14:56:56) * Tickets (bt0, 14:58:16) * LINK: https://pagure.io/fedora-commops/issues?status=Open&priority=20 (bt0, 14:58:26) * Ticket #133: "Creating summer coding "best practices" docs for mentors" (bt0, 14:58:54) * LINK: https://pagure.io/fedora-commops/issue/1333 (bt0, 14:58:54) * ACTION: bt0 will send a mail asking for help to write the docs about mentors best practices (bt0, 15:08:45) * Ticket #163: "Community Blog post highlighting Google Summer of Code 2018 interns" (bt0, 15:09:51) * LINK: https://pagure.io/fedora-commops/issue/1633 (bt0, 15:10:15) * Ticket #110: "Fedora Appreciation Week 2017" (bt0, 15:17:24) * LINK: https://pagure.io/fedora-commops/issue/1100 (bt0, 15:17:46) * LINK: https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org (bt0, 15:17:46) * HELP: Review needed on FAW announcement draft - https://docs.google.com/document/d/1CZbKirCS7OWY2pxjoI0-twA59n__gWqjjNaa3Jy… (bt0, 15:17:46) * HELP: Need volunteer to create Design Team ticket for design assets for Appreciation Week (logos, social media banners, and badge for submitting a Contributor Story for FAW 2018) (bt0, 15:17:46) * HELP: Need to figure out where to store photographs among CommOps members to build a slideshow / video compilation closer to FAW (Google Drive? Dropbox? Other shared file hosting solutions?) (bt0, 15:17:46) * ACTION: dhanesh95 will ask for a file sharing option with the fedora infra people (bt0, 15:44:14) * Open floor (bt0, 15:47:08) Meeting ended at 15:51:36 UTC. Action Items ------------ * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" * jwf Write a CommBlog article summarizing CommOps @ Flock by Monday, October 17 * bt0 will send a mail asking for help to write the docs about mentors best practices * dhanesh95 will ask for a file sharing option with the fedora infra people Action Items, by person ----------------------- * bt0 * "bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24)" * bt0 will send a mail asking for help to write the docs about mentors best practices * commops * commops New members, please introduce yourself on the CommOps mailing list [ https://docs.fedoraproject.org/en-US/commops/contribute/join/ ] * dhanesh95 * dhanesh95 will ask for a file sharing option with the fedora infra people * **UNASSIGNED** * jwf Write a CommBlog article summarizing CommOps @ Flock by Monday, October 17 People Present (lines said) --------------------------- * bt0 (118) * dhanesh95 (29) * zodbot (13) * fcommops-tg1 (8) * skamath (7) * bcotton (5) * JohnMH (4) * commopsbot (3) * commopswatch (2) * commops (0)

1 0

[Fedocal] Reminder meeting : CommOps weekly meeting
by jflory7＠fedoraproject.org 09 Sep '18

09 Sep '18

Dear all, You are kindly invited to the meeting: CommOps weekly meeting on 2018-09-10 from 14:30:00 to 15:30:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets tagged as "[meeting](https://pagure.io/fedora-commops/issues?status=Open&tags=meeting)" in our [Pagure repository](https://pagure.io/fedora-commops). More information about CommOps is found [here](https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/d…. Source: https://apps.fedoraproject.org/calendar/meeting/8732/

1 0

Choose new meeting time for Sept. to Dec. 2018
by Justin W. Flory 08 Sep '18

08 Sep '18

Hi all, As discussed at the last meeting, please add your availability to meet to the WhenIsGood poll by Friday, September 14: http://whenisgood.net/fedora/commops/fall-2018-meeting This will be used to select a new meeting time, beginning in the week of Monday, Sept. 17. When filling out the poll, remember to change the time zone. If you would like your meeting time to be considered but not blocking, please distinguish in the comment field. Please be sure to fill out the meeting time poll by Friday, Sept. 14 for full consideration of your schedule. Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Fedocal] Reminder meeting : CommOps Hack Session
by jflory7＠fedoraproject.org 08 Sep '18

08 Sep '18

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2018-09-09 from 17:00:00 to 18:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed. All CommOpsers are welcome to attend, even if it's only for part of the time slot. More information available at: [https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki… Source: https://apps.fedoraproject.org/calendar/meeting/8733/

1 0

Re: Fedora Pune Meetup – June 2018
by Justin W. Flory 07 Sep '18

07 Sep '18

Hi Suprith, thank you for your patience. Could another Community Blog editor/admin help review this article and schedule it for Thursday, Sept. 6 at 08:30 UTC? On 08/17/2018 04:25 AM, Suprith Gangawar wrote: > Hello, > > Any update on this? > > > On Tuesday, July 17, 2018, 12:32:08 PM GMT, Suprith Gangawar > <suprith_4989(a)yahoo.com> wrote: > > > Made necessary changes. > Please check and comment if anything to be changed/added. > > Thank you for the go through. > On Saturday, July 14, 2018, 12:37:35 AM GMT, Justin W. Flory > <jflory7(a)gmail.com> wrote: > > > On 07/13/2018 05:33 AM, Pravin Satpute wrote: >> *Different thing we tried for this FAD.* >> >> * More time for hands-on session. >> * Since more experienced Fedora users were there from different >> groups, We divided meetup into different groups as per interest. >> o Trying Fedora new features and upgrading Fedora. [Parag, >> Praveen Kumar] >> o Editing Fedora Wiki page and create own Fedora user page. > [Pravin] >> o Creating FAS and earning easy badges. [Suprith and Ompragash] >> o QE session. [Amita and Pooja] >> * Celebration of Fedora 28. It was good. >> > > It would be great to get this into the article draft. Especially for > what activities are more engaging or informative – these are questions > many other people are trying to figure out too. :-) > >> *Next time:* >> >> 1. We asked participants itself what they would like to do in next >> meetup. They suggested few topics (Packaging, kernel, IRC > communication) >> 2. Test days >> > > I'd definitely like to know more about what feedback people had and were > interested in doing! Would you be able to add a couple of lines into the > event report about this too? > > Also, it looks there were images added, but they are all broken for me: > > > https://screenshots.firefox.com/jhZGBrBN3pJEZv9c/communityblog.fedoraprojec… > > Could you make sure these images are uploaded directly to the Community > Blog so they will appear in the post? You can do this with the "Add > Media" button inside of the article editor – you can upload any images > > there. > > > Thanks! > > -- > Cheers, > Justin W. Flory > jflory7(a)gmail.com <mailto:jflory7@gmail.com> > -- Cheers, Justin W. Flory jflory7(a)gmail.com

3 5

Ticket 110: Fedora Appreciation Week (Flock advances)
by Alberto Rodriguez Sanchez 03 Sep '18

03 Sep '18

Hello CommOps team, I'm writing this mail for ask about the advances or agreements generated in the FLOCK about the FWD, Actually this is our most urgent ticket (i think) and i want to know how to help :) Regards -- Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>

2 1

Call for users of statscache
by Clement Verna 03 Sep '18

03 Sep '18

Dear all, During our last meeting [0], we have talked about retiring the statscache service [1]. This is in line with an on going effort to reduce the number of application the infrastructure team has to maintain. The motivation behind this service was to generate statistics using the data of the fedmsg bus. We believe that this service has very little users if not none. Also the commops groups is currently working on another solution to generated statistics using fedmsg [2], this solution is based on GrimoireLab [3]. If there is little interest for this project, we will likely to retire it after the F29 beta freeze [4] Regards, Clément [0] - https://meetbot.fedoraproject.org/teams/infrastructure/infrastructure.2018-… [1] - https://apps.fedoraproject.org/statscache/web/getting-started [2] - https://pagure.io/fedora-commops/issue/114 [3] - https://chaoss.github.io/grimoirelab/ [4] - https://fedoraproject.org/wiki/Releases/29/Schedule?rd=Schedule

2 1

Re-introduction: John M. Harris, Jr.
by John Harris 03 Sep '18

03 Sep '18

My name is John Harris, and I'm a systems engineer for Splentity Software. I have been a member of CommOps in the past, though I've had about two years of inactivity. I now have more stable employment, and I can attend commops meetings more regularly. I also plan to become more active in other areas of Fedora, as a packager. Additionally, I am a current member of both the Games SIG and 3D Printing SIG. It's good to be back. -- John M. Harris, Jr. <johnmh(a)splentity.com> Splentity

2 1

Fedora Science SIGs: bringing them together
by Ankur Sinha 03 Sep '18

03 Sep '18

Hello everyone, I hope everyone had an amazing Flock this year! I was hoping to discuss this there in-person but I couldn't make it this year :( I've recently resurrected the NeuroFedora SIG (it's my area of research so I'm quite happy to maintain it), but while I was looking around I saw that we already have a few science related SIGs in Fedora---I was aware of maybe one or two, but not all of them, in spite of one or two being featured on labs.fp.o! - https://fedoraproject.org/wiki/SIGs/bigdata - https://fedoraproject.org/wiki/Category:Astronomy_SIG - https://fedoraproject.org/wiki/SIGs/ML - https://fedoraproject.org/wiki/SIGs/FedoraMedical - https://fedoraproject.org/wiki/SIGs/NeuroFedora - https://fedoraproject.org/wiki/SIGs/Robotics - https://fedoraproject.org/wiki/SIGs/SciTech Now, mostly, these are groups of people who come together and package up software that is relevant to the particular field, and the SIGs work independently of each other. However when one looks at them, one realises that lots of work that each SIG does overlaps with other SIGs. I think it's quite within our community goals to further Open Science. So, I was wondering if we could organise the SIGs better under a common umbrella: "Fedora <3 science" or something of the sort. It'll give all SIGs a common theme, it'll also enable us to market science in Fedora better (or so I think), and it'll enable other community members interested in other sciences to start their own SIGs in the future. What do folks think? Would this come under CommOps? I'm happy to help with this, of course---I'd really like to make Fedora a "go-to" distribution for whatever sciences the community can support, not just Neuroscience. -- Thanks, Regards, Ankur Sinha "FranciscoD" https://fedoraproject.org/wiki/User:Ankursinha Timezone: Europe/London

3 3

Notification on commblog comments
by Brian (bex) Exelbierd 03 Sep '18

03 Sep '18

Is the commblog set up to notify authors when people comment on their articles? I didn't get one recently for a comment. Thanks, bex -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org

2 1

Question about weekly FPgM update posts
by Ben Cotton 03 Sep '18

03 Sep '18

Hi all, I've started publishing weekly FPgM updates. Right now, I publish on my blog and put it in my 'fedoraplanet' tag so it shows up on Fedora Planet. But I thought it might be suitable as a regular part of the community blog...or it might not. So I put it to you. I'll publish it wherever you think is best. Thanks, BC -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

3 6

Question about the workshop FLOCK 2018
by Alberto Rodriguez Sanchez 03 Sep '18

03 Sep '18

Hello CommOps team, I'm writing for ask about clarification of the content/syllabus of our workshop in FLOCK, do we have to update the etherpad? [0] Just to write it down in the ticket #160 [1] and check if we need ask for help about generate more content or examples. Regards [0] https://etherpad.gnome.org/p/CommOps_Flock2018 [1] https://pagure.io/fedora-commops/issue/160

2 1

Looking for review on PR#175, PR#176
by Justin W. Flory 03 Sep '18

03 Sep '18

Hi all, I made two pull requests to fedora-commops with updated documentation – could someone please review one or both of these pull requests? https://pagure.io/fedora-commops/pull-request/175 https://pagure.io/fedora-commops/pull-request/176 These are smaller changes, so they should be easier to review. :-) -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Meeting] [2018-09-03] Flock 2018 status update, updated roadmap for FAW, and find new meeting time
by Justin W. Flory 03 Sep '18

03 Sep '18

Hi all! Our meeting ended a few short moments ago. The high-level recap: * Update on discussions at CommOps session at Flock 2018 * Reviewing GSoC mentor / student best practice ticket: finish or close * Reviewing timeline to Appreciation Week and setting goals for months ahead Additionally, I will send out a WhenIsGood poll to suggest a new meeting time for our weekly IRC meetings. Keep an eye out for this soon. Thanks everyone for participating, and see you next week! = = = = = Meeting ended Mon Sep 3 15:48:30 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . [11:47:08] <zodbot> Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-09-03/commops.2018-09… [11:47:08] <zodbot> Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-09-03/commops.2018-09… [11:47:08] <zodbot> Log: https://meetbot.fedoraproject.org/fedora-commops/2018-09-03/commops.2018-09… * * * * * ============================================ #fedora-commops: Fedora CommOps (2018-09-03) ============================================ Meeting started by jwf at 14:31:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-09-03/commops.2018-09… . Meeting summary --------------- * Agenda (jwf, 14:31:27) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fed… (jwf, 14:31:27) * (1) Roll call / Q&A (jwf, 14:31:27) * (2) Announcements (jwf, 14:31:27) * (3) Action items from last meeting (jwf, 14:31:27) * (4) Tickets (jwf, 14:31:29) * (5) Open floor (jwf, 14:31:33) * Roll call / Q&A (jwf, 14:31:45) * Name; Timezone; Sub-projects/Interest Areas (jwf, 14:31:46) * ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 14:31:47) * Justin W. Flory; UTC-4; CommOps, D&I, Mindshare, Fedora Badges (jwf, 14:32:12) * algogator, bt0, and meskarune also here! (jwf, 14:37:43) * Announcements (jwf, 14:37:48) * === "Flock : Best 4 Days of 2018" === (jwf, 14:38:15) * LINK: https://communityblog.fedoraproject.org/flock-best-4-days-of-2018/ (jwf, 14:38:15) * Short event report of Flock 2018 by thelittlewonder. Shows some aspects of the conference and what happened at Flock this year. (jwf, 14:38:15) * === "FPgM report: 2018-35" === (jwf, 14:38:31) * LINK: https://communityblog.fedoraproject.org/fpgm-report-2018-35/ (jwf, 14:38:31) * Take your morning coffee with a sitrep of what's happening in Fedora this week, from Fedora Program Manager bcotton. (jwf, 14:38:31) * ==== "Test Days: Internationalization (i18n) features for Fedora 29" === (jwf, 14:38:44) * LINK: https://communityblog.fedoraproject.org/test-days-internationalization-i18n… (jwf, 14:38:44) * The Fedora Internationalization (i18n) Team is testing internationalization features every day this week. See the post for how you can get involved and help. (jwf, 14:38:44) * === "Event Badges - Policy Discussion" === (jwf, 14:39:49) * LINK: https://lists.fedoraproject.org/archives/list/badges@lists.fedoraproject.or… (jwf, 14:39:56) * New thread by riecatnor about deciding new policy for Fedora Badges used at events, to help better support people using badges at events with their requests and the Design Team taking on new work (jwf, 14:40:43) * Action items from last meeting (jwf, 14:42:16) * LINK: https://meetbot.fedoraproject.org/teams/commops/commops.2018-08-27-14.46.ht… (jwf, 14:42:22) * 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 if needed. If no status, we'll try to get a quick update and move forward. (jwf, 14:42:22) * === [INCOMPLETE] jwf Finish CommBlog article: Appreciation Week announcement" === (jwf, 14:42:30) * LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 14:42:30) * ACTION: jwf Finish CommBlog article for Appreciation Week announcement by Monday, Sept. 10 (jwf, 14:42:43) * === "bt0 will write a contributor story before the next meeting (2018-09-03)" === (jwf, 14:43:20) * ACTION: bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) (jwf, 14:47:20) * Tickets (jwf, 14:47:34) * LINK: https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting (jwf, 14:47:40) * Ticket #160: "Plan a CommOps session for Flock 2018" (jwf, 14:48:42) * LINK: https://pagure.io/fedora-commops/issue/160 (jwf, 14:48:49) * Hands-on session in the room split between Fedora Appreciation Week and picking the metrics discussion back up (jwf, 14:52:22) * FAW discussion mostly about revisiting our timeline and developing a roadmap. First draft of new roadmap in Etherpad. (jwf, 14:54:00) * LINK: https://etherpad.gnome.org/p/fedora-commops-flock-2018-session (jwf, 14:54:01) * LINK: https://fedoraproject.org/easyfix/ (jwf, 15:06:14) * Metrics discussion was quick check-in on status of GrimoireLabs + fedmsg integration. Since Grimoire is still blocked, we drove the discussion about answering data questions now with the tools we have available today. (jwf, 15:08:38) * Through an interactive activity, we came to two final questions we wanted to begin exploring and felt like we could answer with current fedmsg tools (with the help of a fedmsg developer who happened to be in the room!). (jwf, 15:09:24) * Q1. Do we have many contributors in specific, narrow places versus contributors working in many different areas? If so, could we better connect the narrow places to other parts of the community that find their input valuable? Example of connecting a group to something like the Fedora Magazine or CommBlog. (jwf, 15:10:55) * Q2. Do we have many activities that are small in time needed to contribute but generate high levels of activity by drive-by contributors? Can we get more visibility of some of these high-interest places across the wider community? (jwf, 15:12:12) * LINK: https://pagure.io/fedora-commops/onboarding-guide (jwf, 15:14:32) * IDEA: Two main efforts in 2019 could be to (1) answer some of the metrics questions above, and (2) begin writing this guide for publication (jwf, 15:17:29) * ACTION: jwf Update Pagure tickets with new comments from Flock discussion / session by Monday, October 10 (jwf, 15:18:33) * ACTION: jwf If possible, a CommBlog article summarizing CommOps @ Flock by Monday, October 17 (jwf, 15:19:20) * Ticket #133: "Creating summer coding "best practices" docs for mentors" (jwf, 15:20:32) * LINK: https://pagure.io/fedora-commops/issue/133 (jwf, 15:20:32) * HELP: Looking for help of someone to write new documentation on Google Summer of Code mentor / student best practices from past mentor feedback: https://pagure.io/fedora-commops/issue/133#comment-529325 (jwf, 15:24:50) * AGREED: Will keep ticket open for one more week to look for someone interested in leading work. Otherwise, we will close it and point to the upstream ticket in mentored-projects (jwf, 15:25:32) * Ticket #110: "Fedora Appreciation Week 2017" (jwf, 15:26:30) * LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 15:26:31) * LINK: https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephone.cloud (jwf, 15:26:31) * LINK: https://screenshots.firefox.com/xu7fdJ4v3sVLlQYh/etherpad.gnome.org (jwf, 15:27:54) * IDEA: Possible inclusion of standardized / suggested hashtags for consistency and visibility into contributor guide (jwf, 15:34:41) * Open floor (jwf, 15:39:57) * ACTION: jwf Set up and send a WhenIsGood poll to the mailing list for finding a new meeting time from Sept. to Dec. 2018 (jwf, 15:43:22) Meeting ended at 15:48:30 UTC. Action Items ------------ * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * jwf Finish CommBlog article for Appreciation Week announcement by Monday, Sept. 10 * bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) * jwf Update Pagure tickets with new comments from Flock discussion / session by Monday, October 10 * jwf If possible, a CommBlog article summarizing CommOps @ Flock by Monday, October 17 * jwf Set up and send a WhenIsGood poll to the mailing list for finding a new meeting time from Sept. to Dec. 2018 Action Items, by person ----------------------- * bt0 * bt0 Write a second contributor story for FAW (due no later than Monday, 2018-09-24) * commops * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * jwf * jwf Finish CommBlog article for Appreciation Week announcement by Monday, Sept. 10 * jwf Update Pagure tickets with new comments from Flock discussion / session by Monday, October 10 * jwf If possible, a CommBlog article summarizing CommOps @ Flock by Monday, October 17 * jwf Set up and send a WhenIsGood poll to the mailing list for finding a new meeting time from Sept. to Dec. 2018 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (189) * meskarune (44) * fcommops-tg (23) * zodbot (11) * commopsbot (2) * commopswatch (2) * bt0 (0) * algogator (0) * commops (0) * bt0_ (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[Fedocal] Reminder meeting : CommOps weekly meeting
by jflory7＠fedoraproject.org 02 Sep '18

02 Sep '18

Dear all, You are kindly invited to the meeting: CommOps weekly meeting on 2018-09-03 from 14:30:00 to 15:30:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This meeting is for members of the Community Operations (CommOps) team. We meet once a week on the Freenode IRC channel. Our meeting format is ticket-driven, so we look at tickets tagged as "[meeting](https://pagure.io/fedora-commops/issues?status=Open&tags=meeting)" in our [Pagure repository](https://pagure.io/fedora-commops). More information about CommOps is found [here](https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/d…. Source: https://apps.fedoraproject.org/calendar/meeting/8732/

1 0

[Fedocal] Reminder meeting : CommOps Hack Session
by jflory7＠fedoraproject.org 01 Sep '18

01 Sep '18

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2018-09-02 from 17:00:00 to 18:00:00 UTC At fedora-commops(a)irc.freenode.net The meeting will be about: This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed. All CommOpsers are welcome to attend, even if it's only for part of the time slot. More information available at: [https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki… Source: https://apps.fedoraproject.org/calendar/meeting/8733/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

[MOVED TO DISCOURSE] Community Operations (CommOps) - https://discussion.fedoraproject.org/tag/commops September 2018