commops June 2016

commops@lists.fedoraproject.org

30 participants
39 discussions

Putting together our vFAD
by Justin W. Flory 07 Jun '16

07 Jun '16

Hi CommOps! If you haven't seen already, we're in the process of revisiting the ticket we filed six months ago or so about organizing our own virtual Fedora Activity Day (vFAD). A vFAD is a fancy way of saying a Fedora-related sprint, extended work session, or your own favorite word for targeted and focused group collaboration. The first step of organizing any FAD is explaining the purpose and impact of the event. After our meeting today, I have laid out a basic proposal for what we would want to accomplish at our own vFAD. You can read those comments in the ticket or directly on the wiki page (both are the same at the moment). https://fedorahosted.org/fedora-commops/ticket/10#comment:5 https://fedoraproject.org/wiki/FAD_CommOps_2016 If you could, I'd like to gather the regular +1/0/-1s on the ticket to make sure everyone interested in this vFAD. As per our voting policy, after 48 hours, I'd like to move forward on this ticket and begin considering factors like choosing dates for hosting our vFAD and creating promotional pieces to let others know about our event. Thanks all! -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

CommOps Weekly Meeting Recap 2016-06-07
by Justin W. Flory 07 Jun '16

07 Jun '16

Meeting ended Tue Jun 7 17:30:50 2016 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06… Log: https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06… * * * * * ============================================ #fedora-meeting: Fedora CommOps (2016-06-07) ============================================ Meeting started by jflory7 at 15:58:04 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06… . Meeting summary --------------- * Agenda (jflory7, 15:58:32) * LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-07 (jflory7, 15:58:38) * (1) Roll Call / Q&A (jflory7, 15:58:42) * (2) Announcements (jflory7, 15:58:46) * (3) Action items from last meeting (jflory7, 15:58:52) * (4) Tickets (jflory7, 15:58:56) * (5) Wiki Gardening (jflory7, 15:59:02) * (6) Community Blog (jflory7, 15:59:06) * (7) Release Schedule (jflory7, 15:59:12) * (8) Open Floor (jflory7, 15:59:16) * Roll Call / Q&A (jflory7, 15:59:22) * Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:59:26) * Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Infrastructure, Diversity, Join, and more (jflory7, 15:59:52) * Sachin S. Kamath; UTC +5.30; GSoC, Metrics, Security (skamath, 15:59:54) * Dhanesh B. Sabane. UTC+5:30, CommOps, ML (dhanesh95, 15:59:54) * Florian, EST, fedora and especially ask.fedora enthusiast (not an it professional), just regular end user (augenauf, 16:01:37) * Bee UTC+5.30 CommOps, GSoC, Metrics (bee2502, 16:01:47) * Sayan Chowdhury;UTC+5:30; Infrastructure, Cloud, CommOps, Marketing, Ambassadors etc. (sayan, 16:04:29) * Devyani Kota; UTC +5.30; GSoC, Hubs, Infrastructure etc (devyani7, 16:04:38) * Announcements (jflory7_, 16:07:13) * === "Fedora Cloud FAD 2016" === (jflory7_, 16:07:22) * LINK: https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/ (jflory7_, 16:07:30) * The Cloud FAD is happening now, from June 7 - 8. The Cloud Working Group will be making decisions, tackling tickets, and writing code to help with topics like automated testing, documentation, and increasing the public cloud provider footprint. (jflory7_, 16:07:38) * === "Fedora Design Team lead Máirín Duffy wins O’Reilly Open Source Award" === (jflory7_, 16:07:46) * LINK: https://communityblog.fedoraproject.org/fedora-design-team-lead-mairin-duff… (jflory7_, 16:07:54) * Big congrats to mizmo for winning big at the O'Reilly Open Source Conference (OSCON) this year! Check out the article to learn more about the award. (jflory7_, 16:08:02) * === Fedora 24 releases June 14 === (jflory7_, 16:08:09) * Just in case you forgot, Fedora 24 drops in another seven days! (jflory7_, 16:08:18) * Action items from last meeting (jflory7_, 16:10:41) * LINK: https://meetbot.fedoraproject.org/fedora-meeting/2016-05-31/commops.2016-05… (jflory7_, 16:10:52) * 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. (jflory7_, 16:11:00) * === decause Follow up with tatica and diversity team about LimeSurvey availability === (jflory7_, 16:11:08) * ACTION: decause Follow up with tatica and diversity team about LimeSurvey availability (jflory7_, 16:11:52) * === [COMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) === (jflory7_, 16:12:02) * LINK: https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproje… (jflory7_, 16:12:10) * === [COMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks === (jflory7_, 16:12:18) * LINK: https://fedoraproject.org/wiki/FAD_CommOps_2016 (jflory7_, 16:12:25) * === decause Work with jzb to organize the release party in Raleigh, NC area === (jflory7_, 16:12:34) * ACTION: decause Work with jzb to organize the release party in Raleigh, NC area (jflory7_, 16:12:42) * === decause nail down Flock arrangements, add them to Fedocal === (jflory7_, 16:12:50) * ACTION: decause nail down Flock arrangements, add them to Fedocal (jflory7_, 16:12:56) * === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) === (jflory7_, 16:13:06) * ACTION: decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) (jflory7_, 16:13:14) * === [COMPLETE] decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push === (jflory7, 16:13:56) * LINK: https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/ (jflory7, 16:14:03) * === skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. === (jflory7, 16:14:15) * ACTION: skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed (jflory7, 16:14:40) * === [COMPLETE] jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71 === (jflory7, 16:14:45) * LINK: https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproje… (jflory7, 16:14:50) * === [COMPLETE] jflory7 Update Ticket #71 with the ideas and discussion from this meeting === (jflory7, 16:14:57) * LINK: https://fedorahosted.org/fedora-commops/ticket/71#comment:6 (jflory7, 16:15:01) * === [COMPLETE] jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source === (jflory7, 16:15:07) * LINK: https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/ (jflory7, 16:15:16) * === [COMPLETE] jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session === (jflory7, 16:15:22) * LINK: https://apps.fedoraproject.org/calendar/meeting/3918/ (jflory7, 16:15:29) * Tickets (jflory7, 16:16:03) * LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7, 16:16:07) * === Ticket #10 === (jflory7, 16:16:11) * "CommOps vFAD 2016" (jflory7, 16:16:16) * LINK: https://fedorahosted.org/fedora-commops/ticket/10 (jflory7, 16:16:21) * LINK: https://fedoraproject.org/wiki/FAD_CommOps_2016 (jflory7, 16:16:25) * IDEA: CommOps-related git repos and Etherpads could be organized more effectively for keeping tabs on information from IRC discussions, hack sessions, and meeting discussions (jflory7, 16:20:59) * IDEA: Wiki could take better advantage of categorization of pages (jflory7, 16:21:19) * IDEA: Similar to the Infra team, have a monthly check-in for existing members of CommOps to see if they are still interested in contributing (see: CommOps wiki page members) (jflory7, 16:22:13) * IDEA: Talk pages on wiki can be useful asynchronous discussion and having a record of logged actions for important pages (jflory7, 16:22:32) * LINK: https://fedoraproject.org/wiki/CommOps#Interest_Areas (skamath, 16:22:56) * ACTION: jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) (jflory7, 16:24:58) * === Tickets #34, 49, 69 === (jflory7, 16:25:47) * #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series" (jflory7, 16:25:52) * #49: "[Onboarding Series] Infrastructure" (jflory7, 16:25:57) * #69: "Fedora Modularity onboarding" (jflory7, 16:26:03) * LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7, 16:26:09) * LINK: https://fedorahosted.org/fedora-commops/ticket/49 (jflory7, 16:26:11) * LINK: https://fedorahosted.org/fedora-commops/ticket/69 (jflory7, 16:26:12) * CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets (jflory7, 16:26:18) * AGREED: skamath will file a ticket for the CommOps on-boarding badge in the Badges Trac, will drop a line in IRC / mailing list about ticket, we will revisit then to work on how we can help the Design Team move forward on this (Badge YAML, sysadmin side, maybe artwork too depending) (jflory7, 16:32:10) * === Ticket #71 === (jflory7, 16:33:30) * "Centralizing Ambassadors / Events resources and utilities" (jflory7, 16:33:36) * LINK: https://fedorahosted.org/fedora-commops/ticket/71 (jflory7, 16:33:40) * LINK: https://pagure.io/designassets/tree/master (jflory7, 16:33:48) * IDEA: Design Team strongly prefers being contacted ahead of time by Ambassadors or others for artwork assets - maybe better aim is to help define the process better for Ambassadors for how to get artwork and printed / final products for events (jflory7, 16:37:36) * LINK: https://fedorahosted.org/design-team/wiki/GeneralGuidelines (jflory7, 16:39:19) * IDEA: Part of workflow involves vendor interaction (not really a Design Team responsibility), but Design Team should be in the loop. (jflory7, 16:43:30) * IDEA: Different Ambassadors / regions approach this differently - more organization around that would be useful and helpful (jflory7, 16:43:49) * IDEA: Centralizing the vendors that Ambassadors use would also be extremely helpful for the Design Team and help make their life easier (jflory7, 16:44:17) * IDEA: Design Team Trac tickets have templates for filling out, but not all fields are always filled - this slows down the process and makes it harder for the Design Team to do their work (jflory7, 16:46:19) * IDEA: Sometimes an Ambassador will file a ticket for a random swag idea (without funding or prior discussion by others in region), so it is a difficult situation to resolve for the Design Team (jflory7, 16:47:03) * ACTION: jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on m izmo's feedback (jflory7, 16:51:59) * LINK: https://pagure.io/group/CommOps (skamath, 16:54:49) * Wiki Gardening (jflory7, 16:55:42) * ACTION: commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ] (jflory7, 16:55:47) * Community Blog (jflory7, 16:58:34) * 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! (jflory7, 16:58:41) * === This Week in CommBlog === (jflory7, 16:58:51) * (1) "Fedora CommBlog Keeps it 100" (jflory7, 16:58:56) * LINK: https://communityblog.fedoraproject.org/commblog-keeps-100/ (jflory7, 16:59:00) * Total Views (June 2 - June 7): 53 (jflory7, 16:59:05) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 16:59:09) * (2) "Fedora Cloud FAD 2016" (jflory7, 16:59:14) * LINK: https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/ (jflory7, 16:59:19) * Total Views (June 4 - June 7): 39 (jflory7, 16:59:23) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 16:59:28) * (3) "OSCON 2016 Expo Hall Booth Report" (jflory7, 16:59:33) * LINK: https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/ (jflory7, 16:59:38) * Total Views (June 6 - June 7): 40 (jflory7, 16:59:42) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 16:59:47) * (4) "Fedora Design Team lead Máirín Duffy wins O’Reilly Open Source Award" (jflory7, 16:59:53) * LINK: https://communityblog.fedoraproject.org/fedora-design-team-lead-mairin-duff… (jflory7, 16:59:58) * Total Views (June 6 - June 7): 71 (jflory7, 17:00:03) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 17:00:07) * === Coming Up in CommBlog === (jflory7, 17:00:37) * (1) "Getting started with Fedora QA (Part 1)" (jflory7, 17:00:42) * LINK: https://communityblog.fedoraproject.org/?p=1608&preview=1&_ppp=cc40c9d0e6 (jflory7, 17:00:47) * Scheduled for Thursday, June 9, 8:00 UTC (jflory7, 17:00:52) * (2) "Getting started with 'update-testing' Fedora QA part 2" (jflory7, 17:00:57) * LINK: https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8c73937530 (jflory7, 17:01:01) * (3) "Getting started with Fedora QA part 3" (jflory7, 17:01:06) * LINK: https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=17e4652e53 (jflory7, 17:01:11) * (4) "Event Report: PyCon 2016" (jflory7, 17:01:15) * LINK: https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=cffc2b4a56 (jflory7, 17:01:20) * Tickets - Ticket #71 (revisiting temporarily) (jflory7, 17:06:47) * Printing is a non-trivial thing, it's easy to mess up colors or sizes (jflory7, 17:07:08) * IDEA: Digital resources (icons, banners, fedoramagazine-images, etc.) would be easier to share across channels (jflory7, 17:07:48) * LINK: https://pagure.io/designassets/tree/master (jflory7, 17:08:00) * Release Schedule (jflory7, 17:08:26) * LINK: https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html (jflory7, 17:08:30) * ACTION: decause ship "final" version for review by EoB thursday of F24 GA Release Announcement (decause_otg, 17:11:38) * LINK: https://pagure.io/fedora-mktg (decause_otg, 17:11:56) * Open Floor (jflory7, 17:17:22) * === skamath: summer-coding stats tool === (jflory7, 17:22:02) * LINK: https://sachinwrites.xyz/2016/06/06/digging-deep-into-datagrepper-more-stat… (skamath, 17:23:06) * LINK: https://docs.google.com/spreadsheets/d/1KzVhspdYYclWcpEmqyyup9PKGW7FWRJn2Ma… (skamath, 17:23:31) * LINK: https://pagure.io/gsoc-stats/blob/master/f/README.md (skamath, 17:23:57) * ACTION: jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC (jflory7, 17:30:19) Meeting ended at 17:30:50 UTC. Action Items ------------ * decause Follow up with tatica and diversity team about LimeSurvey availability * decause Work with jzb to organize the release party in Raleigh, NC area * decause nail down Flock arrangements, add them to Fedocal * decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) * skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed * jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) * jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on m izmo's feedback * commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ] * decause ship "final" version for review by EoB thursday of F24 GA Release Announcement * jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC Action Items, by person ----------------------- * commops * skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed * jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) * commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ] * decause * decause Follow up with tatica and diversity team about LimeSurvey availability * decause Work with jzb to organize the release party in Raleigh, NC area * decause nail down Flock arrangements, add them to Fedocal * decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) * jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) * decause ship "final" version for review by EoB thursday of F24 GA Release Announcement * jflory7 * jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) * jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on m izmo's feedback * jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC * skamath * skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jflory7 (280) * skamath (98) * decause_otg (71) * jflory7_ (40) * meskarune (27) * dhanesh95 (22) * zodbot (19) * mizmo (18) * gnokii (10) * augenauf (6) * bee2502 (5) * danofsatx (3) * devyani7 (3) * sayan (3) * puiterwijk (1) * commops (0) * decause (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 IRC Meeting
by Justin W. Flory 06 Jun '16

06 Jun '16

Dear all, You are kindly invited to the meeting: CommOps IRC Meeting on 2016-06-07 from 12:00:00 to 13:30:00 US/Eastern At fedora-meeting(a)irc.freenode.net The meeting will be about: This meeting is for team members of the Community Operations (CommOps) team. The weekly agenda is mostly comprised of the different tasks detailed on the CommOps wiki page, although it is subject to change depending on time and context of what is going around the Fedora Project. More information can be found on the [wiki page](https://fedoraproject.org/wiki/CommOps). Source: https://apps.fedoraproject.org/calendar/meeting/3244/

1 0

[Fedocal] Reminder meeting : Fedora Hubs Weekly Check-in
by Remy DeCausemaker 06 Jun '16

06 Jun '16

Dear all, You are kindly invited to the meeting: Fedora Hubs Weekly Check-in on 2016-06-07 from 10:00:00 to 11:00:00 US/Eastern At fedora-hubs(a)irc.freenode.net The meeting will be about: The Fedora Hubs team meets up once a week to check in on development status of Fedora Hubs, work through issues, and make progress on development. Current developers and anyone interested in developing for Hubs are encouraged to attend. You can find the source code on http://pagure.io/fedora-hubs More information available at: [https://fedoraproject.org/wiki/Fedora_Hubs](https://fedoraproject.org/wiki/… Source: https://apps.fedoraproject.org/calendar/meeting/3863/

1 0

CommOps Hack Session Recap 2016-06-03
by Justin W. Flory 03 Jun '16

03 Jun '16

Meeting ended Fri Jun 3 22:54:08 2016 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-meeting-3/2016-06-03/commops.2016-… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-3/2016-06-03/commops.2016-… Log: https://meetbot.fedoraproject.org/fedora-meeting-3/2016-06-03/commops.2016-… * * * * * =========================================================== #fedora-meeting-3: Fedora CommOps Hack Session (2016-06-03) =========================================================== Meeting started by jflory7 at 20:56:52 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-3/2016-06-03/commops.2016-… . Meeting summary --------------- * Roll Call (jflory7, 20:57:01) * We're using Google Hangouts for tonight's hack session: please try connecting at the following link! (jflory7, 20:57:44) * LINK: https://hangouts.google.com/call/en5lzau3tffx3goxsaccqsq5tye (jflory7, 20:57:45) * LINK: https://etherpad.gnome.org/p/commops-power-sessions (jflory7, 21:01:08) * How To Push a Badge 101 (jflory7, 21:24:31) * Ralph (threebean) explained how to push a badge in Fedora Infrastructure with a screenshare walkthrough (jflory7, 21:24:55) * === Prerequisites === (jflory7, 21:25:13) * 1) Cloned `badges` repository where all badges live: https://git.fedorahosted.org/cgit/badges.git (jflory7, 21:25:35) * 2) Sysadmin privileges on Batcave and badges-web (jflory7, 21:26:06) * === Taking care of art assets === (jflory7, 21:26:21) * 1) Go to the ticket for a badge and pull the artwork assets (both png and svg) into the `badges` repository (jflory7, 21:26:47) * 2) Place art assets into their appropriate folder, preferred to name image files the name of the badge for easy indexing later on (jflory7, 21:27:12) * 3) Double-check to make sure the image assets you pulled down are "good" - sometimes the images can be corrupted and this can cause problems later (jflory7, 21:27:43) * 4) Add the files in git, commit, push (or if you don't have push privileges, make a patch and add it to the ticket to save time...??) (jflory7, 21:28:17) * === Pushing out the badge === (jflory7, 21:28:32) * Important to note that just because you push to fedorahosted does not mean the badge is "out there" yet - introducing the powers of Ansible yet again (jflory7, 21:28:58) * 1) Log into the `batcave` machine in Fedora Infrastructure and locate the `push-badges` playbook (jflory7, 21:29:25) * 2) Sysadmins with privileges will be able to run the playbook to pull the changes from fedorahosted to batcave - the changes then get synced to the badges-web server (jflory7, 21:29:56) * LINK: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/ma… (jflory7, 21:30:38) * 3) Wait for playbook to finish, check if the png is publicly viewable on badges.fp.o (jflory7, 21:31:01) * === Adding a badge from badges.fp.o === (jflory7, 21:31:10) * Once the art assets are on badges-web, you will be ready to make the badge. BEWARE: Creating a badge is easy, but editing it is not! Make sure the information you are entering is right on the first go. (jflory7, 21:31:49) * 1) Log into admin interface on badges.fp.o (jflory7, 21:31:59) * 2) Go to add badge section (jflory7, 21:32:09) * 3) Enter in the information (e.g. pull the badge name / description from the ticket, enter the correct image location for the badge), hit "Create badge" button (jflory7, 21:33:15) * 4) In admin interface, grant privileges to appropriate person (IF NOT AN AUTOMATIC BADGE) at bottom of the interface. Use badge name and @fedoraproject.org email for the person who needs privileges (jflory7, 21:34:03) * === Success! === (jflory7, 21:34:09) * Congratulations! You pushed a badge. (jflory7, 21:34:22) * ACTION: jflory7 Write up a SOP on pushing a badge for Fedora Infra if there is not one already (make any improvements if there is one?) (jflory7, 21:37:45) * LINK: https://www.youtube.com/watch?v=QV5R-2wlzUY (decause, 21:44:09) * mizmo OSCON Open Source Award Video (decause, 21:44:24) * On to hacking! (jflory7, 21:44:32) * jflory7 will try to draft up a post about mizmo's award at OSCON to go out near maxamillion's OSCON post on Monday (jflory7, 21:44:52) * LINK: https://www.oreilly.com/ideas/oreilly-open-source-awards-oscon-austin-2016 (decause, 21:49:19) * LINK: https://twitter.com/Remy_D/status/737697932657332224 (decause, 21:52:05) * LINK: http://imgur.com/a/PvJGZ (decause, 21:59:32) * "CommBlog Keeps it 100" wallpapers and backgrounds (decause, 22:00:02) * LINK: https://infrastructure.fedoraproject.org/infra/docs/badges.rst (decause, 22:05:38) * LINK: https://github.com/sindresorhus/awesome (decause, 22:09:23) * LINK: https://github.com/vinta/awesome-python (decause, 22:09:51) * LINK: https://fedorahosted.org/marketing-team/ticket/227 (jflory7, 22:14:11) * LINK: https://fedoraproject.org/wiki/F24_release_announcement (jflory7, 22:14:57) * LINK: https://fedoraproject.org/wiki/FAD_Cloud_WG_2016 (decause, 22:24:21) * LINK: http://imgur.com/s1XtwQC (decause, 22:48:29) Meeting ended at 22:54:08 UTC. Action Items ------------ * jflory7 Write up a SOP on pushing a badge for Fedora Infra if there is not one already (make any improvements if there is one?) Action Items, by person ----------------------- * jflory7 * jflory7 Write up a SOP on pushing a badge for Fedora Infra if there is not one already (make any improvements if there is one?) * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jflory7 (83) * skamath (19) * decause (18) * zodbot (15) * skrzepto (6) * maxamillion (4) * zoltanh7211 (3) * kushal (1) * lmacken (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

Thank you, CommBlog contributors!
by Justin W. Flory 03 Jun '16

03 Jun '16

Hey all, decause noticed a pretty big milestone for the Community Blog today. https://communityblog.fedoraproject.org/commblog-keeps-100/ We just recently hit the 100+ published posts milestone on the Community Blog! Woohoo! Thanks to all who have contributed so far, and I'm looking forward to seeing the next 100 posts and beyond. Nice work, CommOps! -- Cheers, Justin W. Flory jflory7(a)gmail.com

2 2

[Fedocal] Reminder meeting : CommOps Hack Session
by Justin W. Flory 02 Jun '16

02 Jun '16

Dear all, You are kindly invited to the meeting: CommOps Hack Session on 2016-06-03 from 17:00:00 to 19:00:00 US/Eastern At fedora-meeting-3(a)irc.freenode.net The meeting will be about: This meeting is a power session to work on some ongoing tasks and tickets related to Fedora Badges and CommOps tickets. The meeting will take place in either a Jitsi meeting or a Google+ Hangout, with a text meeting in #fedora-meeting-3 for those with video problems. All CommOpsers are welcome to attend, even if it's only for part of the time slot. This hack session is also the "special edition" PyCon US 2016 hack session. decause will be attending remotely from the US West Coast from PyCon. A few others there may join us too. More information available at: [https://etherpad.gnome.org/p/commops-power-sessions](https://etherpad.gnome… Source: https://apps.fedoraproject.org/calendar/meeting/3918/

1 0

Starting a Fedora Badges Workshop
by Justin W. Flory 01 Jun '16

01 Jun '16

Hello all, In the CommOps meetings for the past couple weeks, we've been throwing around the idea of having a Badges workshop where CommOps and the Design team can meet together. This also fits into some of the discussion about Fedora Hubs as of recently too. In the workshop, we would try to work through any important badges that need to be created or defined, talk about strategy for creating badges, and maybe triage existing badge tickets. It could also specialize in specific topics for Badges based on other needs too. I put together a WhenIsGood poll to help find times that work for anyone that is interested in contributing or attending such a workshop. If you're interested, please fill out the times that work best for you below! http://whenisgood.net/fedora/badges-workshop Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

4 4

Re: Hello from Tokyo:
by Justin W. Flory 01 Jun '16

01 Jun '16

On 05/19/2016 09:41 PM, Scott Day wrote: > Hello All, > > I wanted to pitch in and help the project in whatever way I could and > wherever you all need me. I am an almost twenty year veteran of Linux, > sysadmin, network "administration" (when we called it that) and now > naturally DevOps. I have been working with RH based distros since YDL > (YelloDog Linux) in 1998, having spent my share of time trying to 'make' > my workflow fit a distro I have settled on Fedora. OpenSuSE Leap is > great, KDE and Gnome are not on the distro, Ubuntu, well, unity - come > on now. Ah, I should metnion that yes when OpenSolaris was a thing I ran > it as my primary OS with VirtualBox for a required windows image. > > In any case, I have been around the block from dot com 1.0, to startups, > to 2.0, to serious enterprise level at Apple, Samsung, GAP e-comm, HPE, > among others. My specific focus these days is in data center automation > (Ansible, Puppet, when I have to Chef). Also, I have been tasked with > developing and doing POCs with Docker. I can be used wherever you need > me, hopefully that gives you enough background. Linux, DBs > (RDBMS/NoSQL), web infra (LBs, Caching servers, proxies, etc.), anything > OpenStack. > > Thanks - hope the bio was not too much or too little. As a good Linux > guy I'm not exactly fond about wearing my war paint in the open. Much of > that experience came at great personal cost (at times). > > Warmest Regards, > -Scott D. > Meguro-ku, Tokyo, Japan Hi Scott! I was closing loops on emails today and noticed it seems like your email was caught up in the spam filter. It seems like you subscribed to the list with your fedoraproject.org email alias - if you use your @gmx.com email, you should be able to send and receive mail to the list. Sounds like you have a lot of background and experience working with Linux. There's plenty of ways for you to get involved and contribute in the Fedora community, and we'd be happy to help you find a place to get involved in. There is a great site called whatcanidoforfedora.org that is an interactive way for you to find a place that you may be able to contribute to based on your interests. http://whatcanidoforfedora.org/en Alternatively, if you prefer text, you can also find this wiki page too as a good reference. https://fedoraproject.org/wiki/Join Hopefully this is enough info for you to see what all is out there in the Fedora community. There are plenty of different sub-projects, from CommOps to Infrastructure to Packaging to Marketing and beyond to get involved with. If you'd like some more specific pointers, let us know what your interests are and we'd be happy to help guide you to the right place. Sorry again for the late reply. :) -- Cheers, Justin W. Flory jflory7(a)gmail.com

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

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