commops November 2016

commops@lists.fedoraproject.org

18 participants
45 discussions

[fedora-commops] Issue #95 `[Onboarding Series] DotNet SIG`
by Pagure 14 Apr '17

14 Apr '17

rhea reported a new issue against the project: `fedora-commops` that you are following: `` This issue is a stub for working out ideas, concepts, and other steps involved for contributors who would like to officially join the DotNet team. ## Problem The goal of the dotnet SIG is to establish dotnet presence in Fedora, from providing information to the user, through taking care of dotnet packages in future Fedora releases, to providing information and help to other packagers. ## Current state Basic [wiki page[1]](https://fedoraproject.org/wiki/DotNet) was drafted, [mailing list[3]](https://lists.fedoraproject.org/admin/lists/dotnet-sig.lists.fedor… and [FAS group[4]](https://admin.fedoraproject.org/accounts/group/view/dotnet-sig) created, and we are currently looking for a good [time](http://whenisgood.net/fedora-dotnet) for IRC [meetings](https://pagure.io/fedora-dotnet/issue/1). During the first IRC meeting we should discuss the future goals and next steps of our progress ([agenda](https://pagure.io/fedora-dotnet/issue/2)) ## Questions & Ideas * **Wiki page** - Everything is currently at [wiki/dotnet[1]](https://fedoraproject.org/wiki/DotNet) while I would like _this_ page to contain general info about dotnet on Fedora, info for the user and packagers how to use dotnet, etc... and to move the organizational part about the team and joining it to [wiki/SIGs/dotnet[2]](https://fedoraproject.org/wiki/SIGs/DotNet) * **FAS Group & Mailing List** - I'm not entirely sure about this, what would it ideally look like in the future, however for now there is no reason to do anything and we can keep it as it is with a single group and list. The idea for the future is, that if dotnet becomes popular and the group would grow, we should split off the core team and create new fas group and mailing list `dotnet-devel` or something along those lines, while the SIG would remain generic and public group of people with common interest. * **What next?** (technical side) - This should be answered during the first (above mentioned) IRC meeting, it should go along the lines of getting all the current problems together (pagure issues) and starting to look into them one by one - we should come up with priorities, etc... Next steps in organization of the group are already outlined and questions are raised in the above points. ### ref 1. wiki/dotnet: https://fedoraproject.org/wiki/DotNet 2. wiki/SIGs/dotnet: https://fedoraproject.org/wiki/SIGs/DotNet 3. mailing list: https://lists.fedoraproject.org/admin/lists/dotnet-sig.lists.fedoraproject.… 4. FAS group: https://admin.fedoraproject.org/accounts/group/view/dotnet-sig `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/95

2 4

[fedora-commops] Issue #94 `Look at how wcidff can be improved`
by Pagure 13 Apr '17

13 Apr '17

ankursinha reported a new issue against the project: `fedora-commops` that you are following: `` We've seen that while wcidff works well, it works well for people looking for tasks to work on, which isn't necessarily the same as people looking to join the project, at least not to begin with. We'd like to see how wcidff can be improved `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/94

3 3

Helping re-energize Marketing
by Justin W. Flory 29 Nov '16

29 Nov '16

======================================================================= | tl;dr | ======================================================================= | WHAT: Bringing more energy into Marketing team | | HOW: Identifying problems, proposing solutions | | WHY: Improve experience in Marketing, helping move towards more | | creative innovation as a team | | WE NEED YOU: Check ticket, read solutions, give feedback | | LINK: https://pagure.io/fedora-commops/issue/48 | ======================================================================= Hey everyone, I wanted to bring a topic up for discussion that started in CommOps a while back and I'm now getting time to revisit. In CommOps, we are working through helping individual sub-projects improve their on-boarding tools and strategies to bring in more contributors and also to help retain them. In the original CommOps meeting to brainstorm, Gabriele and I helped provide context to identifying some of the current struggles and problems of Marketing. After gaining some of the background, we all tried to come up with some ideas on how to fix these problems and improve the experience for newcomers (and maybe even long-time contributors too). :-) All of this discussion is summarized into nice bulletpoints in this ticket: https://pagure.io/fedora-commops/issue/48 It would be great if some other Marketing folks could check out this ticket and leave feedback. Since I'm contributing in both CommOps and Marketing, I'm helping guide this along and hopefully we can begin trying to create a plan or steps to follow to help implement some of the solutions in the ticket at the next Marketing and CommOps meetings. Thanks everyone! -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[fedora-commops] Issue #48 `[Onboarding Series] Marketing`
by Pagure 29 Nov '16

29 Nov '16

jflory7 added a new comment to an issue you are following: `` **Originally discussed in [2016-10-18 meeting](https://meetbot.fedoraproject.org/teams/commops/commops.2016-10-18… **Briefly mentioned in [2016-11-29 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commop… Apologies for how long it has taken me so long to get back to this ticket, but here's a breakdown of all of the ideas we had during our original meeting when we discussed this topic (to much high interest too). # Existing resources Before diving in too deep, this section can serve as an index for useful pages to make note of with regards to the Marketing team. * [Marketing team: Tasks and roles](https://fedoraproject.org/wiki/Marketing/Tasks_and_roles) # Identifying problems In order for us to find solutions to improving on-boarding to Marketing and retaining those contributors, we first have to identify the specific problems and issues that Marketing faces. The following list is a summary. * **Unclear tasks** * Isn't clear what kind of tasks Marketing is working on during a release cycle and how to participate * **Visible tasks are overwhelming** * Most visible tasks in Marketing are highly intimidating to a newcomer, like release announcements or talking points for new Fedora releases * **Temporary contributor lifespan** * Many Marketing contributors come in cycles. Some people contribute for one, maybe two releases, then they might drop off. Retainment is an issue both with members and Marketing team leaders * **Oversimplified on-boarding** * Current on-boarding steps are simple and don't provide a chance to engage: introduce self on mailing list, say hello in a meeting,and then…? * Strong need for more "easyfix" / low-hanging fruit type of tasks * **Creativity is stifled** * Because of difficulty engaging new members, is challenging to focus on non-essential but important tasks, things other than release announcements and talking points * With increased communication about how to contribute ideas, Marketing could push to be more innovative with how we engage users / Linux community # Creating solutions In the same meeting, we discussed for a long time about some of the potential solutions we could pursue in trying to solve some of the above problems (think _cause and effect_). Some of the ideas we had are in bulletpoints below. Note that the list has not yet been refined. * **Working closely with others** * Presented itself in many ways * Collaborating with Join SIG to engage Marketing newcomers with other areas in Fedora they might be interested in * Inviting other sub-projects to request help with writing or summarizing something, and have Marketing team members help write a report or short article on something happening elsewhere in project * Highlighting a subproject every month to showcase the things they do in Fedora – newcomers could reach out to some members of those teams to gather info and write an article * **Improving current on-boarding pipeline** * Going beyond the mailing list introduction and meeting attendance * Break down the _[Tasks and roles](https://fedoraproject.org/wiki/Marketing/Tasks_and_roles)_ wiki page into better communicated roles and smaller tasks (low-hanging fruit) to engage new contributors * **Better communicating with press** * Establishing relationships with contacts in media and how we can convey Fedora news to them (and how someone could contribute towards this) * **Social media engagement** * Creative strategies to promote stronger engagement on social platforms like Facebook/Twitter/Google+/etc. * Better ways to introduce newcomers to social media presence and encourage engaging with us there * **How I use Fedora!** * Similar to talking points, but more general * Things that contributors are currently doing with Fedora, and convert them into a format that can be spread widely or shared about doing that activity * Later can be used for videos, interviews, streaming, or example work to share on personal channels or platforms * **Creating a badge** * This should be considered a low priority task until we figure out a strategy for the bigger issues like retention – a badge will attract but won't retain * **Podcasting** * Low barrier way to encourage contributors of doing things like feature profiles or interviews, like Chris Ward's Flock Stories podcast on Community Blog # CC There is a lot that is covered here, and it would be extremely helpful if some of the folks from the meeting checked out this ticket and offered some ideas or feedback to the above. @meskarune @rhea @ankursinha @mailga @bex I will also be publicizing this discussion on the Marketing mailing list to help gain the attention and feedback from other Marketing team members. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/48

1 0

PyCon CZ 2016 report for the community blog
by Miro Hrončok 29 Nov '16

29 Nov '16

Hi, Yrina (CC'ed) created a report form PyCon CZ 2016 for the community blog. Here is plaintext with the content: https://paste.fedoraproject.org/470561/35660414/ Could someone please approve it for publishing? Feel free to do some changes if needed. Thanks, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 5

[fedora-commops] Issue #93 `Elections: Better explain roles of Council and FESCo`
by Pagure 29 Nov '16

29 Nov '16

jflory7 added a new comment to an issue you are following: `` **Discussed in [2016-11-29 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commop… We're picking back up on some older tickets again. We wanted to help get this one rolling ASAP since December election cycles are right around the corner! # Summary * @meskarune ~~File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position~~ * **[Done!](https://pagure.io/Fedora-Council/tickets/issue/79)** * @dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the [wiki page](https://fedoraproject.org/wiki/Council#Responsibilities) to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016 * @jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 # Analysis We had a fair amount of discussion about this topic in the meeting. In a nutshell, we broke up the immediate tasks into three things, as described above. @meskarune already filed the [ticket](https://pagure.io/Fedora-Council/tickets/issue/79) in the Fedora Council Pagure about a mentorship or training program for first-time Council members during the meeting, which is awesome! For more info on that, you should [follow the ticket](https://pagure.io/Fedora-Council/tickets/issue/79). @dhanesh95 and I are going to work on starting to improve the profiles / explanation of the roles of the Fedora Council (@dhanesh95) and FESCo (me). **Why do this?** The purpose of us making more clear and concrete examples of what it means to serve in one of these electable bodies should help improve participation and interest in the Elections. The Council has some description and when I last looked for FESCo, I couldn't find anything specific. For both bodies, it would be helpful to draw out clear descriptions of their roles and responsibilities, examples of some of the skills that are helpful to serve in this seats, and the kinds of benefits it offers (e.g. growing your own experience, having an impact on the Fedora community, etc.). Our goal is to get discussion rolling on these things by the end of the week, and hopefully we will have some more to discuss at next week's meeting. # CC @bee2502 @jkurik `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/93

1 0

[fedora-commops] Issue #92 `Start a yearly Fedora Appreciation Day`
by Pagure 29 Nov '16

29 Nov '16

jflory7 added a new comment to an issue you are following: `` **Discussed in [2016-11-29 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commop… We're picking back up on some older tickets again. We wanted to help get this one on the map again for 2017. # Summary 1. Would like to plan for a few weeks after F26 release in June * Feedback from @bex on the proposed timing / date would be helpful 2. If general time frame works, settle on locking down a date or dates for Appreciation Day 3. After determining date… 1. Create public wiki page to hold info 2. Write CommBlog post announcing it as something coming this summer # Analysis In the meeting, we agreed that a little bit after a Fedora release would be a good time to try to plan it. We agreed and disagreed with @bex's point about lining it up with a Fedora release. We disagreed that we should put extra emphasis on local events / release parties since it might exclude a notable number of contributors who don't have access to these events, but we agreed that it would be a great opportunity to help promote Fedora and its awesome community to an audience outside of just our contributors (especially if announcements line up with a Fedora Magazine release week, where views are at the highest). @bex, we were hoping to get your thoughts on holding this somewhere in July (to give some wiggle room if F26 delays). If the timeframe sounds good, we can work on selecting a definite date or range of days to hold the Appreciation Day event. The idea was that once we lock down on a date, we can begin doing some preliminary messaging like creating a wiki page to host information about the event, and a CommBlog post to help raise awareness that this is something happening this summer (we'll likely write more later on, but this is just a first step). Thanks! `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/92

1 0

[Minutes] [2016-11-29] Timeline for Appreciation Day, what *do* the Council and FESCo do?
by Justin W. Flory 29 Nov '16

29 Nov '16

Hey folks! Thanks to everyone who came out to today's meeting. Apologies for my unplanned absences the couple of weeks, and again big shoutout to Rhea for helping take lead. In today's meeting, we spent most of our time discussing two things: Fedora Appreciation Day and improving communication about the responsibilities and roles of the upcoming electable positions. The minutes did a fairly good job of marking up a quick summary of what happened, so I recommend checking them out for a quick read about what's going on in CommOps. Also, I'm hoping to unbury our discussion on Fedora Marketing in October and bring it into the ticket for discussion and collaboration with the Marketing team tonight. We should have more to discuss on that next week. Thanks again all! See you next week. = = = = = Meeting ended Tue Nov 29 18:38:17 2016 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commops.2016-11… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commops.2016-11… Log: https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commops.2016-11… * * * * * ============================================ #fedora-meeting: Fedora CommOps (2016-11-29) ============================================ Meeting started by jflory7 at 17:28:48 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/commops.2016-11… . Meeting summary --------------- * Agenda (jflory7, 17:29:06) * LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-11-29 (jflory7, 17:29:13) * (1) Roll Call / Q&A (jflory7, 17:29:19) * (2) Announcements (jflory7, 17:29:24) * (3) Action items from last meeting (jflory7, 17:29:30) * (4) Tickets (jflory7, 17:29:35) * (5) Community Blog (jflory7, 17:29:40) * (6) Release Schedule (jflory7, 17:29:45) * (7) Open Floor (jflory7, 17:29:51) * Roll Call / Q&A (jflory7, 17:29:55) * Name; Timezone; Sub-projects/Interest Areas (jflory7, 17:30:02) * ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jflory7, 17:30:09) * Radka Janek; UTC+1; CommOps, Diversity, DotNet,... (Rhea, 17:30:20) * Justin W. Flory; UTC-5; CommOps, Magazine, Marketing, Ambassadors, Diversity, Join SIG, sysadmin-badges, and more (jflory7, 17:30:32) * Alberto Rodriguez S;UTC-6;Commops, Metrics, Packaging and more (bt0, 17:31:20) * Dhanesh B. Sabane, UTC+5:30, CommOps, Marketing, ML, Packaging, Python (dhanesh95, 17:31:56) * Announcements (jflory7, 17:36:21) * === "Flock Stories 2016, Episode 5: Haïkel Guémar" === (jflory7, 17:36:28) * LINK: https://communityblog.fedoraproject.org/flock-stories-2016-haikel-guemar/ (jflory7, 17:36:32) * Haïkel Guémar (hguemar / number80) is a long-time Fedora contributor passionate about on-boarding new users into Fedora. Learn more in his interview with Chris Ward as the last episode of the Flock Stories 2016 series! (jflory7, 17:36:39) * === "Fedora at PyCon CZ 2016" === (jflory7, 17:36:45) * LINK: https://communityblog.fedoraproject.org/fedora-at-pycon-cz-2016/ (jflory7, 17:36:50) * Fedora Ambassadors in the Czech Republic and around Europe attended PyCon CZ in Brno, Czech Republic. Learn more about what happened at PyCon (including the Pythonic staff of enlightenment) in ishcherb's event report! (jflory7, 17:36:56) * === Opinions needed: Fedora + freenode partnership article === (jflory7, 17:37:27) * LINK: https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.o… (jflory7, 17:37:32) * We're working on doing a partnership with freenode to publicize the open source projects living on freenode. A first draft of an initial article to publish was shared on the mailing list. Please take a moment to review and offer any feedback. (jflory7, 17:37:38) * Action items from last meeting (jflory7, 17:39:18) * LINK: https://meetbot.fedoraproject.org/teams/commops/commops.2016-11-01-16.29.ht… (jflory7, 17:39:24) * 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, 17:39:30) * === jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list === (jflory7, 17:39:39) * - Better done as a ticketed discussion - we can talk in a meeting, update the ticket, and go from there. We have extra time to plan this now until we determine a date to shoot for. (jflory7, 17:40:19) * === jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket === (jflory7, 17:40:44) * ACTION: jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket (jflory7, 17:40:52) * jflory7 will do this today, guaranteed, no exceptions, no ifs, ands, or buts (jflory7, 17:41:12) * === jflory7 Post to the mailing list breaking down how to help with Ticket #93 === (jflory7, 17:41:27) * - This ticket is added to the meeting agenda for today, and we should discuss together how to break it down and move forward with this into smaller tasks for CommOpsers to take on (jflory7, 17:41:53) * === [COMPLETE] Rhea Update the #95 ticket after the first dotnet meeting === (jflory7, 17:42:47) * LINK: https://pagure.io/fedora-commops/issue/95#comment-39699 (jflory7, 17:42:56) * === FranciscoD work on "Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.)." === (jflory7, 17:43:06) * ACTION: FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.) === (jflory7, 17:44:09) * Tickets (jflory7, 17:44:37) * LINK: https://pagure.io/fedora-commops/issues?tags=meeting (jflory7, 17:44:45) * === Ticket #92 === (jflory7, 17:44:52) * "Start a yearly Fedora Appreciation Day" (jflory7, 17:44:56) * LINK: https://pagure.io/fedora-commops/issue/92 (jflory7, 17:45:01) * IDEA: Current objective for Fedora Appreciation Day: Establish a timeline for planning by choosing a month or date to aim for, break up smaller tasks for how we can prepare for it (messaging, communication, options for contributors to thank each other) (jflory7, 17:51:49) * AGREED: Next steps will be to update ticket with proposed timeline for events, pending bexelbie's thoughts. After, we will try setting a date in the calendar. Then, we will (1) create a public wiki page to hold info, and (2) write a CommBlog post announcing it to come in the summer (jflory7, 18:00:46) * ACTION: jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting (jflory7, 18:02:24) * === Ticket #93 === (jflory7, 18:03:03) * "Elections: Better explain roles of Council and FESCo" (jflory7, 18:03:07) * LINK: https://pagure.io/fedora-commops/issue/93 (jflory7, 18:03:12) * IDEA: Better explaining roles and responsibilities of Council and FESCo so people know what they are expected to do if they choose to run (jflory7, 18:09:08) * IDEA: Go over benefits for running, e.g. the sorts of skills you would use and also improve on (jflory7, 18:09:26) * IDEA: Having a mentorship period or "training" for first-time candidates elected into the Council or FESCo (jflory7, 18:12:01) * LINK: https://pagure.io/Fedora-Council/tickets/issues (jflory7, 18:16:05) * ACTION: meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position (jflory7, 18:16:42) * ACTION: dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016 (jflory7, 18:18:44) * ACTION: jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 (jflory7, 18:19:05) * AGREED: Action items delegated, will check in on progress next meeting! (jflory7, 18:20:12) * === Ticket #48 === (jflory7, 18:20:22) * "[Onboarding Series] Marketing" (jflory7, 18:20:27) * LINK: https://pagure.io/fedora-commops/issue/48 (jflory7, 18:20:32) * LINK: https://meetbot.fedoraproject.org/teams/commops/commops.2016-10-18-16.30.lo… (jflory7, 18:20:37) * ACTION: jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week (jflory7, 18:22:31) * Community Blog (jflory7, 18:25:25) * 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, 18:25:57) * === The past couple of weeks in CommBlog === (jflory7, 18:26:15) * (1) "Where to point newcomers to Fedora" - FranciscoD++ (jflory7, 18:26:23) * LINK: https://communityblog.fedoraproject.org/where-point-newcomers-fedora/ (jflory7, 18:26:28) * Total Views (Nov. 10 - Nov. 29): 675 (jflory7, 18:26:34) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:26:39) * (2) "Migration from Trac / FedoraHosted" - Amita++ (jflory7, 18:26:46) * LINK: https://communityblog.fedoraproject.org/migration-from-trac-fedorahosted/ (jflory7, 18:26:50) * Total Views (Nov. 10 - Nov. 29): 273 (jflory7, 18:26:56) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:27:02) * (3) "Flock Stories 2016, Episode 3: Brian Exelbierd" - cward++ (jflory7, 18:27:08) * LINK: https://communityblog.fedoraproject.org/flock-stories-2016-brian-exelbierd/ (jflory7, 18:27:15) * Total Views (Nov. 11 - Nov. 29): 32 (jflory7, 18:27:22) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:27:27) * (4) "Base Runtime and the Generational Core" - sgallagh++ (jflory7, 18:27:35) * LINK: https://communityblog.fedoraproject.org/base-runtime-generational-core/ (jflory7, 18:27:40) * Total Views (Nov. 15 - Nov. 29): 97 (jflory7, 18:27:45) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:27:50) * (5) "Flock Stories 2016, Episode 4: Matthew Miller" - cward++ (jflory7, 18:27:57) * LINK: https://communityblog.fedoraproject.org/flock-stories-2016-matthew-miller/ (jflory7, 18:28:02) * Total Views (Nov. 18 - Nov. 29): 75 (jflory7, 18:28:07) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:28:13) * (6) "Flock Stories 2016, Episode 5: Haïkel Guémar" - cward++ (jflory7, 18:28:19) * LINK: https://communityblog.fedoraproject.org/flock-stories-2016-haikel-guemar/ (jflory7, 18:28:24) * Total Views (Nov. 25 - Nov. 29): 24 (jflory7, 18:28:29) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:28:35) * (7) "Fedora at PyCon CZ 2016" - ishcherb++ (jflory7, 18:28:43) * LINK: https://communityblog.fedoraproject.org/fedora-at-pycon-cz-2016/ (jflory7, 18:28:49) * Total Views (Nov. 29): 171 (jflory7, 18:28:58) * LINK: https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=… (jflory7, 18:29:05) * === Coming Up in CommBlog === (jflory7, 18:29:12) * (1) "Heroes of Fedora (HoF) – F25 Final" - 2016 Dec. 1 - coremodule++ (jflory7, 18:29:19) * LINK: https://communityblog.fedoraproject.org/?p=3050&preview=1&_ppp=3575de209b (jflory7, 18:29:25) * (2) "Celebrating Fedora 25 with freenode" - jflory7 (jflory7, 18:29:36) * LINK: https://communityblog.fedoraproject.org/?p=3065&preview=1&_ppp=ed70b52525 (jflory7, 18:29:37) * (3) "Freenode cloaks for Fedora Contributors" - dhanvi (jflory7, 18:29:43) * LINK: https://communityblog.fedoraproject.org/?p=2999&preview=1&_ppp=1787e4c1e9 (jflory7, 18:29:48) * ACTION: jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok (jflory7, 18:30:30) * Release Schedule (jflory7, 18:31:35) * LINK: https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html (jflory7, 18:31:41) * LINK: https://fedorapeople.org/groups/schedule/f-26/f-26-key-tasks.html (jflory7, 18:31:46) * (1) Fedora 23 EOL auto closure (Tue 2016-12-20) (jflory7, 18:31:52) * (2) Change Checkpoint: Proposals requiring mass rebuild submission deadline (Tue 2017-01-10) (jflory7, 18:31:59) * Open Floor (jflory7, 18:32:35) Meeting ended at 18:38:17 UTC. Action Items ------------ * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket * FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.) === * jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting * meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position * dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016 * jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 * jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week * jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok Action Items, by person ----------------------- * commops * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * dhanesh95 * dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016 * jflory * jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket * jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting * jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 * jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week * jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok * jflory7 * jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket * jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting * jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 * jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week * jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok * meskarune * meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position * **UNASSIGNED** * FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.) === People Present (lines said) --------------------------- * jflory7 (241) * dhanesh95 (58) * zodbot (31) * meskarune (19) * Rhea (15) * bt0 (9) * mailga (7) * jflory (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

[fedora-commops] Issue #44 `Talking Points: EDU`
by Pagure 29 Nov '16

29 Nov '16

jflory7 added a new comment to an issue you are following: `` Putting this onto a backburner for a bit… I think we bit off a little more than we can chew at the moment. We will definitely pick this one up later in 2017… `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-commops/issue/44

1 0

Re: [marketing] Re: Partnership opportunity with freenode!
by Justin W. Flory 29 Nov '16

29 Nov '16

On 11/02/2016 08:40 PM, Matthew Miller wrote: > On Wed, Nov 02, 2016 at 01:17:53AM -0400, Justin W. Flory wrote: >> showcase the awesome work happening throughout freenode. I reached >> out via email to their community team to see if Fedora could try to >> help pilot something with regards to these new outreach efforts. > > Awesome -- thanks for doing this, Justin! > >> 1) Articles about the Fedora Project, the Fedora community, or other >> exciting news about Fedora for the freenode blog and other platforms > > I can see an article with some statistics for how much we use and > depend on Freenode every day. > It took me a little longer than I wanted to circle back around to this, but I have a first draft of something we could share with the freenode team to publish on their community blog. Since this would likely be shared across a wide audience, I wanted to make sure that we get our messaging right in this article (CCing Magazine and CommOps mailing lists too). It might also be because I'm tired, but I was trying to brainstorm ideas for how to use IRC effectively a la Fedora's recommendations, but was coming up short. Any additions or ideas would be appreciated! You can find a public preview of the article here: https://communityblog.fedoraproject.org/?p=3065&preview=1&_ppp=ed70b52525 And it can be edited here: https://communityblog.fedoraproject.org/wp-admin/post.php?post=3065&action=… Feel free to critique any other parts of the article as well – I am very open to feedback! Thanks everyone. -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

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