March 2018 - [MOVED TO DISCOURSE] Mindshare - https://discussion.fedoraproject.org/tag/mind-co

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

Mindshare Meeting on 26 March
by Brian Exelbierd 26 Mar '18

26 Mar '18

<zodbot> Meeting ended Mon Mar 26 13:08:40 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . <zodbot> Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-26/mindshare.2018-… <zodbot> Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2018-03-26/mindshare.2018-… <zodbot> Log: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-26/mindshare.2018-… ========================== #fedora-meeting: Mindshare ========================== Meeting started by bexelbie at 12:31:13 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2018-03-26/mindshare.2018-… . Meeting summary --------------- * roll call (bexelbie, 12:31:25) * Announcement (bexelbie, 12:35:14) * we published our FAD report: https://communityblog.fedoraproject.org/mindshare-monthly-report-fad-first-… (bexelbie, 12:35:21) * LINK: https://communityblog.fedoraproject.org/mindshare-monthly-report-fad-first-… (bexelbie, 12:35:22) * Tickets (bexelbie, 12:36:16) * LINK: https://pagure.io/mindshare/issue/7 (bexelbie, 12:38:18) * LINK: https://pagure.io/mindshare/issue/6 (bexelbie, 12:38:31) * Research other "representation" programs in other open source communities (bexelbie, 12:38:58) * LINK: https://pagure.io/fedora-commops/issue/145#comment-501074 (jwf, 12:39:24) * A list of other programs is compiled, but needs to be summarized further (jwf, 12:41:18) * Write draft "ambassadors plan" email for review (bexelbie, 12:41:24) * LINK: https://pagure.io/mindshare/issue/8 (bexelbie, 12:41:27) * ACTION: everyone to help edit the working draft (bexelbie, 12:46:14) * mindshare design issues (bexelbie, 12:47:30) * LINK: https://pagure.io/mindshare/issue/9 (bexelbie, 12:47:32) * committee badge is complete pending a push (bexelbie, 12:48:02) * ACTION: nb to consider helping push badge #603 (bexelbie, 12:48:16) * the logo is still a work on progress (bexelbie, 12:48:30) * Explain the two mailing lists (mindshare and mindshare-announce) (bexelbie, 12:48:48) * LINK: https://pagure.io/mindshare/issue/12 (bexelbie, 12:48:52) * ACTION: everyone please comment on https://pagure.io/mindshare/issue/12 (bexelbie, 12:50:36) * Standard footer for fedora websites and webapps (bexelbie, 12:51:18) * LINK: https://pagure.io/mindshare/issue/13 (bexelbie, 12:51:21) * Open Floor (bexelbie, 12:54:12) * Next Meeting Chair (bexelbie, 12:54:21) * jsmith to chair the next meeting (bexelbie, 12:55:34) * Telegram Channel (bexelbie, 12:55:49) * Badge (bexelbie, 13:01:36) * everyone loves it (bexelbie, 13:01:39) Meeting ended at 13:08:40 UTC. Action Items ------------ * everyone to help edit the working draft * nb to consider helping push badge #603 * everyone please comment on https://pagure.io/mindshare/issue/12 Action Items, by person ----------------------- * nb * nb to consider helping push badge #603 * **UNASSIGNED** * everyone to help edit the working draft * everyone please comment on https://pagure.io/mindshare/issue/12 People Present (lines said) --------------------------- * bexelbie (127) * jwf (34) * x3mboy (28) * jsmith (24) * robyduck (19) * zodbot (16) * pingou (1) * mleonova (0) * nb (0) * mleonova[m] (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Mindshare Committee Meeting
by jflory7＠fedoraproject.org 25 Mar '18

25 Mar '18

Dear all, You are kindly invited to the meeting: Mindshare Committee Meeting on 2018-03-26 from 12:30:00 to 13:30:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: More information available at: [https://fedoraproject.org/wiki/Mindshare](https://fedoraproject.org/wiki/Mi… Source: https://apps.fedoraproject.org/calendar/meeting/8744/

1 0

Mindshare Meeting Minutes - 19 March
by Brian Exelbierd 19 Mar '18

19 Mar '18

<zodbot> Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-19/mindshare.2018-… <zodbot> Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2018-03-19/mindshare.2018-… <zodbot> Log: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-19/mindshare.2018-… ========================== #fedora-meeting: Mindshare ========================== Meeting started by bexelbie at 12:30:15 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2018-03-19/mindshare.2018-… . Meeting summary --------------- * Roll Call (bexelbie, 12:31:32) * README (bexelbie, 12:34:52) * LINK: https://pagure.io/mindshare/issue/1 (bexelbie, 12:34:54) * AGREED: Set ticket #1 to easy fix knowing x3mboy may still do it. jwf is the point of contact until may (bexelbie, 12:39:59) * ACTION: bex to set up the easy fix tag and website (bexelbie, 12:40:13) * Ticket 3 is blocked - https://pagure.io/mindshare/issue/3 (bexelbie, 12:40:33) * ticket 5 is the same https://pagure.io/mindshare/issue/5 (bexelbie, 12:40:53) * Research by CommOps (bexelbie, 12:41:07) * LINK: https://pagure.io/mindshare/issue/6 (bexelbie, 12:41:10) * FAD Outbound report (bexelbie, 12:43:26) * LINK: https://pagure.io/mindshare/issue/7 (bexelbie, 12:43:29) * LINK: https://etherpad.gnome.org/p/Mindshare_Report (x3mlinux, 12:43:55) * ambassador conversation kickstart (bexelbie, 12:48:11) * LINK: https://pagure.io/mindshare/issue/8 (bexelbie, 12:48:13) * open design tickets (bexelbie, 12:49:34) * LINK: https://pagure.io/mindshare/issue/9 (bexelbie, 12:49:35) * LINK: https://pagure.io/fedora-badges/issue/603 - here I would make them different (mleonova, 12:50:42) * LINK: https://pagure.io/design/issue/580 this I just started, suggestions welcome (mleonova, 12:51:02) * Feedback on the design tickets is encouraged in the tickets (bexelbie, 12:53:23) * Open Floor (bexelbie, 12:54:30) * LINK: https://communityblog.fedoraproject.org/?p=5425&preview=1&_ppp=aa1df99942 (jwf, 12:59:55) * robyduck checked on beta/pre-release tasks/blockers (bexelbie, 13:04:09) * LINK: https://pagure.io/fedora-commops/pull-request/146 (jwf, 13:04:10) * LINK: https://bryn.justinwflory.com/commops.html (jwf, 13:04:15) * jwf requested reviews of https://pagure.io/fedora-commops/pull-request/146 (bexelbie, 13:05:31) * x3mboy asked about whether we had guidance for FLISOL international airfare tickets in LATAM (bexelbie, 13:14:42) Meeting ended at 13:16:29 UTC. Action Items ------------ * bex to set up the easy fix tag and website Action Items, by person ----------------------- * bex * bex to set up the easy fix tag and website * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bexelbie (110) * jwf (45) * x3mboy (20) * mleonova (18) * robyduck (18) * zodbot (15) * x3mlinux (13) * jsmith (12) * jflory7 (0) * nb (0) * bex (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Mindshare Committee Meeting
by jflory7＠fedoraproject.org 18 Mar '18

18 Mar '18

Dear all, You are kindly invited to the meeting: Mindshare Committee Meeting on 2018-03-19 from 12:30:00 to 13:30:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: More information available at: [https://fedoraproject.org/wiki/Mindshare](https://fedoraproject.org/wiki/Mi… Source: https://apps.fedoraproject.org/calendar/meeting/8744/

1 0

Mindshare Meeting Minutes - Monday 12 March 2018
by Brian Exelbierd 12 Mar '18

12 Mar '18

<zodbot> Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-12/mindshare.2018-… <zodbot> Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2018-03-12/mindshare.2018-… <zodbot> Log: https://meetbot.fedoraproject.org/fedora-meeting/2018-03-12/mindshare.2018-… You are encouraged to subscribed to the low-volume Mindshare Mailing list to ensure you stay informed about what is going on. Mindshare uses it's pagure (pagure.io/mindshare) to track open issues so that information is easy to find and subscribe too. ======================================================== #fedora-meeting: Fedora Mindshare Committee - 2018-03-12 ======================================================== Meeting started by jwf at 12:30:54 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2018-03-12/mindshare.2018-… . Meeting summary --------------- * Roll call (jwf, 12:30:59) * Tickets (bexelbie, 12:37:19) * LINK: https://pagure.io/mindshare/issues (bexelbie, 12:37:23) * LINK: https://pagure.io/mindshare/issue/7 (bexelbie, 12:37:44) * represenation research (bexelbie, 12:39:45) * LINK: https://pagure.io/mindshare/issue/6 (bexelbie, 12:39:47) * ambassadors code of conduct page (bexelbie, 12:45:08) * LINK: https://pagure.io/mindshare/issue/5 (bexelbie, 12:45:09) * Ambassadors REps (bexelbie, 12:49:10) * LINK: https://pagure.io/mindshare/issue/4 (bexelbie, 12:49:13) * feature profiles (bexelbie, 12:53:13) * LINK: https://pagure.io/mindshare/issue/3 (bexelbie, 12:53:15) * swag vendor list (bexelbie, 13:01:54) * LINK: https://pagure.io/mindshare/issue/2 (bexelbie, 13:01:56) * readme (bexelbie, 13:04:59) * LINK: https://pagure.io/mindshare/issue/1 (bexelbie, 13:05:00) * LINK: https://pagure.io/Fedora-Council/tickets/blob/master/f/README.md (jwf, 13:06:19) * Draft of Ambassadors Ideas (bexelbie, 13:11:09) * LINK: https://pagure.io/mindshare/issue/8 (jsmith, 13:12:25) * LINK: https://pagure.io/mindshare/issue/8 (bexelbie, 13:12:47) * Open Floor (bexelbie, 13:16:16) * ACTION: everyone to send receipts from the FAD to bexelbie(a)redhat.com with paypal address and currency preference where possible (not promised) (bexelbie, 13:19:24) * LINK: https://pagure.io/design/issue/580 (mleonova, 13:19:32) * ACTION: robyduck to open ML tickets for us and a tracker in our pagure (bexelbie, 13:19:34) * ACTION: mleonova to open a tracker ticket for our design tickets in our pagure (bexelbie, 13:19:44) Meeting ended at 13:25:11 UTC. Action Items ------------ * everyone to send receipts from the FAD to bexelbie(a)redhat.com with paypal address and currency preference where possible (not promised) * robyduck to open ML tickets for us and a tracker in our pagure * mleonova to open a tracker ticket for our design tickets in our pagure Action Items, by person ----------------------- * bexelbie * everyone to send receipts from the FAD to bexelbie(a)redhat.com with paypal address and currency preference where possible (not promised) * mleonova * mleonova to open a tracker ticket for our design tickets in our pagure * robyduck * robyduck to open ML tickets for us and a tracker in our pagure * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bexelbie (146) * jwf (55) * x3mboy (31) * jsmith (31) * mleonova (25) * zodbot (17) * nb (16) * robyduck (13) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : Mindshare Committee Meeting
by jflory7＠fedoraproject.org 12 Mar '18

12 Mar '18

Dear all, You are kindly invited to the meeting: Mindshare Committee Meeting on 2018-03-12 from 12:30:00 to 13:30:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: More information available at: [https://fedoraproject.org/wiki/Mindshare](https://fedoraproject.org/wiki/Mi… Source: https://apps.fedoraproject.org/calendar/meeting/8744/

4 3

Mindshare FAD - Day 3 notes
by Justin W. Flory 06 Mar '18

06 Mar '18

The third and final day of the Mindshare FAD came to a close. We discussed the following topics: * Budget allocation and procedure for Mindshare * Finding a common meeting time (actually hard…) * Reporting and devising action plan for messaging * Generating post-FAD action items Details are all below. Thanks everyone for your time, energy, and motivation this week. For many of us, this was back-to-back with other travel and strategic planning, but I think we all are happy with what we came up with at the end. See you in channel, mailing list, or elsewhere soon. :-) = = = = = Meeting ended Tue Mar 6 10:06:31 2018 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-06/mindshare.201… Minutes (text): https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-06/mindshare.201… Log: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-06/mindshare.201… * * * * * ==================================================== #fedora-mindshare: Fedora Mindshare FAD 2018 - Day 3 ==================================================== Meeting started by x3mboy at 08:56:01 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-06/mindshare.201… . Meeting summary --------------- * Budget (x3mboy, 08:57:01) * bexelbie is presenting several alternatives to request budget and how to handle it (x3mboy, 08:59:34) * AGREED: Mindshare will request to allocate regional budgets directly to Mindshare for FY19 (robyduck, 09:22:53) * Mindshare will communicate how this will be handled and allocated regional wise for the transitional period (robyduck, 09:23:37) * Mindshare Meeting Time (robyduck, 09:24:08) * LINK: https://ethercalc.org/ubtgupvviq6y (bexelbie, 09:25:11) * AGREED: New Meeting time is Monday from 12:30 -13:30 UTC (robyduck, 09:37:23) * Mindshare Reporting (x3mboy, 09:42:05) * Six areas of focus: Modularity, CI, Internet of Things, Workstation Edition, Server Edition, Atomic Edition (jwf, 09:49:17) * === Three strategies for focusing on our topics === (jwf, 09:49:27) * (1) Use resources wisely as we have limited volunteer attention, time, and money (jwf, 09:49:41) * (2) Increase adoption of Fedora in areas related to messaging (jwf, 09:49:50) * (3) Improve communication to facilitate these messages (jwf, 09:50:03) * Representatives to take the messaging back to the other teams (design, docs, marketing, CommOps) (jwf, 09:56:03) * === Mindshare is successor to FAmSCo and FOSCo === (jwf, 09:56:22) * starting conversations about how to improve ambassadors as part of this charter in two weeks (jwf, 09:56:37) * AGREED: Announce Meeting Time: 12:30 - 13:30 UTC on Mondays (jwf, 09:56:53) * Action items for post-FAD (jwf, 09:57:05) * ACTION: x3mboy Write first monthly report - Friday March 16 to be drafted and in the committee email for review - ideal publish the following week (jwf, 09:57:20) * ACTION: mleonova[m] Take our messaging and issues to Design (jwf, 09:57:36) * ACTION: robyduck Take our messaging and issues to Web (jwf, 09:57:49) * ACTION: x3mboy Take our messaging and issues to Marketing (jwf, 09:58:07) * ACTION: jwf nee jflory7 nee Mr. Roboty Take our messaging and issues to CommOps (jwf, 09:58:40) * === Recurring Mindshare tasks === (jwf, 09:59:53) * Every meeting, check outreach/mindshare calendars for meeting goals/deadlines (jwf, 10:00:12) * Every month, publish an outbound report (rotating by person by month) built from bullet points generated in the meetings (jwf, 10:00:30) * Ticket triage (jwf, 10:00:39) * Closing up (jwf, 10:04:46) * AGREED: We will never have a FAD in this room again (because lighting) (jwf, 10:04:56) * AGREED: But the hotel rooms and the views are great :D (jwf, 10:05:32) Meeting ended at 10:06:31 UTC. Action Items ------------ * x3mboy Write first monthly report - Friday March 16 to be drafted and in the committee email for review - ideal publish the following week * mleonova[m] Take our messaging and issues to Design * robyduck Take our messaging and issues to Web * x3mboy Take our messaging and issues to Marketing * jwf nee jflory7 nee Mr. Roboty Take our messaging and issues to CommOps Action Items, by person ----------------------- * jwf * jwf nee jflory7 nee Mr. Roboty Take our messaging and issues to CommOps * mleonova[m] * mleonova[m] Take our messaging and issues to Design * robyduck * robyduck Take our messaging and issues to Web * x3mboy * x3mboy Write first monthly report - Friday March 16 to be drafted and in the committee email for review - ideal publish the following week * x3mboy Take our messaging and issues to Marketing * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (30) * x3mboy (9) * zodbot (6) * robyduck (4) * bexelbie (1) * langdon (0) * nb (0) * mleonova[m] (0) * mattdm (0) * jsmith (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 : Mindshare Committee Meeting
by jflory7＠fedoraproject.org 05 Mar '18

05 Mar '18

Dear all, You are kindly invited to the meeting: Mindshare Committee Meeting on 2018-03-06 from 20:00:00 to 21:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: More information available at: [https://fedoraproject.org/wiki/Mindshare](https://fedoraproject.org/wiki/Mi… Source: https://apps.fedoraproject.org/calendar/meeting/8744/

1 0

Mindshare FAD - Day 2 notes
by Justin W. Flory 05 Mar '18

05 Mar '18

The second day of the Mindshare FAD came to an end a little bit ago. Today was intense but we covered a lot of ground! The full details are in the minutes so I won't summarize, but here's an outline of what we covered: * Council FAD recap: Understanding Fedora's mission * Why we want mindshare (not committee, the idea) and how to measure it * Messaging we want to deliver to outreach teams * Communicating messaging with Ambassadors * What do we say in our messaging? * Swag logistics / delivery * Role of Design in Mindshare * Role of CommOps in Mindshare * Role of Marketing in Mindshare * Role of Docs in Mindshare * Role of Ambassadors in Mindshare * Structure of Ambassadors It was a really intense day. But in the best kind of way. :-) We'll be back for Round 2 in the morning. Ciao! = = = = = Meeting ended Mon Mar 5 16:40:34 2018 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-05/mindshare.201… Minutes (text): https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-05/mindshare.201… Log: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-05/mindshare.201… * * * * * ==================================================== #fedora-mindshare: Fedora Mindshare FAD 2018 - Day 2 ==================================================== Meeting started by jwf at 08:09:36 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-05/mindshare.201… . Meeting summary --------------- * Getting started (jwf, 08:09:45) * LINK: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-04/mindshare.201… (jwf, 08:12:09) * Welcome nb! Quick recap this morning to get him up to speed (jwf, 08:14:33) * Council FAD recap (jwf, 08:23:59) * LINK: http://etherpad.osuosl.org/fedoramktreqs (mattdm, 08:24:01) * langdon asked me to start that etherpad but I don't know why yet (mattdm, 08:24:15) * Goal to walk out with refined set of requirements, know if we're meeting those requirements, and then how to deliver on those requirements (jwf, 08:25:37) * mattdm presenting overview of output of council fad that resulted in a new mission (bexelbie, 08:27:33) * original mission: We are making a general purpose linux distro ... (bexelbie, 08:27:46) * that was general and put us in a "box" (bexelbie, 08:28:19) * next mission lead advancement of free and open source software and content as a collaborative community (bexelbie, 08:28:21) * this wasn't actionable, is hard and isn't really answered by a distro. So it was disconnected and asprirational and the world changed without us necessarily being the leaders of it (bexelbie, 08:28:55) * said, lets get back to basics of what is unique, what are we doing, who for, etc. (mission statements) (bexelbie, 08:29:47) * LINK: https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html#… (jwf, 08:30:43) * current mission: in the context of the foundations, fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and comunity members to build tailored solutions for their users (bexelbie, 08:30:50) * Fedora has editions recognizing that we are more than just a desktop and has multiple audiences (bexelbie, 08:32:13) * IDEA: Enabling platforms for people to do things (jwf, 08:34:52) * In addition to making this platform, also build reference platforms to work and serve particular needs we think need to be filled in a circular way (jwf, 08:36:01) * IDEA: Fedora is not just a desktop operating system but a platform to do a number of things (jwf, 08:37:47) * Why we want mindshare and how we measure it - langdon (jwf, 08:41:43) * Why is Fedora different and what makes it different from everything else in this space? (jwf, 08:41:58) * === What makes Fedora unique? === (jwf, 08:42:36) * LINK: http://etherpad.osuosl.org/fedoramktreqs (jwf, 08:43:50) * Interactive discussion! Typing into the Etherpad to answer the questions of what makes Fedora unique to understand our audience and what we're trying to target (jwf, 08:44:25) * IDEA: jsmith: "People stick around in Fedora because of the community – all carrot, no stick" (jwf, 08:47:30) * IDEA: People get personal satisfaction for contributing to this community (jwf, 08:47:54) * LINK: http://etherpad.osuosl.org/x3mboyNotes (x3mboy, 10:55:31) * Lunch break! (jwf, 10:58:12) * LINK: https://communityblog.fedoraproject.org/ambassadors-fedora-strategy/ (mattdm, 11:04:04) * Recap from our discussion this morning (jwf, 11:59:52) * === Messaging we want to see === (jwf, 12:00:02) * Modularity (jwf, 12:00:06) * Fedora CI (jwf, 12:00:10) * Internet of Things (jwf, 12:00:12) * Desktop Edition (jwf, 12:00:16) * Server Edition (jwf, 12:00:18) * Atomic Edition (jwf, 12:00:22) * These are things currently in progress; specifics will change over time (jwf, 12:00:48) * AGREED: These are the areas of focus we want to emphasize in our outreach teams (jwf, 12:01:21) * === Focus of thought === (jwf, 12:01:35) * Use resources wisely as we have limited volunteer attention, time, money (jwf, 12:01:46) * Increase adoption of Fedora in areas related to messaging (jwf, 12:02:12) * Improve communication to facilitate these messages (jwf, 12:02:31) * Messaging we want to deliver (jwf, 12:03:14) * Messaging we want to take to the groups and identify challenges we want to address or help them address (jwf, 12:03:16) * Ambassador focus: How do we communicate? (jwf, 12:03:59) * IDEA: nb: Document to explain what something is in layman's terms (e.g. "What is Fedora CI??") (jwf, 12:05:35) * ambassadors seem to just kind of do what they have always done and maybe don't always keep themselves up to date on the current objectives (nb, 12:12:05) * do we do events because we have always done that event, or do we have a goal for that event (nb, 12:12:19) * Where is this information located? Do we have a place to go to get links? Is this info translated? (jwf, 12:14:45) * How do we communicate our focus on these objectives? (jwf, 12:16:42) * IDEA: Ask for more thought on evaluating requests and alignment with our overall goals? (jwf, 12:16:54) * IDEA: at some point those of us here at the mindshare FAD should sign each other's GPG keys (nb, 12:18:36) * IDEA: Doing the outreach via the CommBlog, possibly mailing lists (jwf, 12:22:51) * What do we say in our messaging? (jwf, 12:23:15) * Tactically: Messaging means CommBlog and email (jwf, 12:23:25) * Ask for more thought on evaluating requests and alignment with our overall goals? (jwf, 12:23:38) * Explain the message and where to find details (jwf, 12:23:56) * Explain the constraints and goals and ask for more consideration (jwf, 12:24:07) * Explain that this is the Fedora Focus (jwf, 12:24:17) * Keep doing events we want you to be more focused, but keep doing events (jwf, 12:24:37) * === Needs from Ambassadors === (jwf, 12:47:12) * Documented process for becoming an Ambassador (jwf, 12:47:35) * People who are actively doing work today (to identify contributors) (jwf, 12:47:56) * Recognition for having an Ambassador at one time (jwf, 12:48:03) * IDEA: Messaging: As our charter, we are carrying out the work we were created to do (jwf, 12:48:21) * Design: Where does design fit? (jwf, 12:50:35) * How can we better equip our Ambassadors? Materials? Demos? Equipment? (jwf, 12:50:55) * Where do they find up-to-date, "approved" materials? Tickets? (jwf, 12:51:10) * LINK: https://communityblog.fedoraproject.org/new-guidelines-fedora-ambassadors-d… (jwf, 12:53:52) * LINK: https://fedoraproject.org/wiki/Ambassadors/Design (jwf, 12:54:21) * LINK: https://fedoraproject.org/wiki/Marketing_collateral (x3mboy, 12:55:28) * IDEA: Clear, easy-to-find way to show this is how you interact with us, and if doesn't have proper level of specificity, what is needed up front to be successful (jwf, 12:57:54) * LINK: https://pagure.io/designassets (jwf, 12:58:44) * IDEA: Every time has a different workflow process and this needs to be documented (sharing best practices?) (jwf, 12:59:58) * What do we say in our messaging? (continued) (jwf, 13:01:01) * IDEA: Messaging: As our charter, we are carrying forward with the work we were created to do (jwf, 13:04:44) * Offering: New low-friction processes for release parties and "small" events (jwf, 13:04:58) * Pushing: As the successors to FAmSCo and FOSCo (and perhaps FAmA?), we will be changing some things (jwf, 13:05:29) * Design: Where does design fit? (continued) (jwf, 13:06:51) * Figuring out why Ambassadors don't produce on their own and why guidelines are in place with Design; but how to make design team more accessible? (jwf, 13:07:25) * HELP: Marketing collateral wiki page is still used as a current resource by Ambassadors (jwf, 13:07:58) * Standardizing small parties helps standardize workflow for design team (jwf, 13:10:18) * Delivery of swag and logistics (jwf, 13:18:39) * Contributor attention and time > money (jwf, 13:18:52) * Mindshare is capable of dealing with logistics (jwf, 13:19:27) * 1. Offer as a service that we will handle logistics of shipping (jwf, 13:39:13) * 2. Offer that we will just send standard swag under the right conditions (jwf, 13:39:31) * 3. Support better country specific things like a release box for France (jwf, 13:39:40) * Role of CommOps within Mindshare (jwf, 13:41:58) * AGREED: leave ambassadors seats unfilled until pending discussion about what defines an ambassador is complete, the representatives will be FAmA and the other representatives who are also ambassadors (nb, 13:59:52) * we have at least 1 representative from all of NA, EMEA, and LATAM (nb, 14:00:11) * LINK: http://etherpad.osuosl.org/fedoramktreqs (nb, 14:01:50) * CommOps is a purely tactical body that focuses on internal "marketing" (storytelling), measure of engagement (metrics), and supporting sub-project best practices; CommOps works with Mindshare to understand strategic aim of our work (jwf, 14:03:32) * AGREED: CommOps will mostly continue forward with the work we are already doing now but will not take on the responsibility of driving strategic planning (jwf, 14:03:41) * ACTION: jwf Move recent copytext from CommOps wiki page rewrite to describe strategic goals of Mindshare (jwf, 14:04:02) * Role of Marketing in Mindshare (jwf, 14:04:12) * Specifically define Marketing as *Marketing Execution* (jwf, 14:06:28) * What is Marketing capable of doing today? (jwf, 14:08:54) * 1. Release announcements (jwf, 14:17:26) * 2. Talking points (jwf, 14:17:31) * === Simple additional things Marketing can do === (jwf, 14:17:49) * IDEA: Marketing helping Design Team with text (jwf, 14:17:57) * IDEA: Three Things in Fedora This Week (jwf, 14:18:05) * IDEA: What happened in Objectives this quarter? (jwf, 14:18:14) * IDEA: Better connection with social media (jwf, 14:18:20) * IDEA: Pre-release kickoff "event" marketing kit (e.g. what we ship to release parties) (jwf, 14:18:44) * === What Marketing needs from Mindshare === (jwf, 14:19:17) * Answers to strategic questions from Mindshare and Council (Marketing brings us a list) (jwf, 14:19:35) * Role of Docs in Mindshare (jwf, 14:25:03) * Docs has no resources presently but we are on track to solve this problem from last week's Docs FAD (jwf, 14:25:08) * Trying to get publishing toolchain problem solved (jwf, 14:25:16) * Mindshare is not asking them for anything else right now (jwf, 14:25:27) * Role of elected members in Mindshare (jwf, 14:27:10) * Moving away from yesterday's idea of elected members selecting smaller groups to represent in interest of bandwidth concerns (jwf, 14:27:50) * Elected members to support work of Mindshare Committee so we don't suddenly find ourselves under-resourced (jwf, 14:28:19) * Role of Ambassadors in Mindshare (jwf, 14:28:24) * What is the role of an ambassador? (see http://etherpad.osuosl.org/fedoramktreqs ) (nb, 15:48:58) Meeting ended at 16:40:34 UTC. Action Items ------------ * jwf Move recent copytext from CommOps wiki page rewrite to describe strategic goals of Mindshare Action Items, by person ----------------------- * jwf * jwf Move recent copytext from CommOps wiki page rewrite to describe strategic goals of Mindshare * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (129) * zodbot (16) * nb (16) * x3mboy (11) * mattdm (9) * bexelbie (8) * langdon (3) * mleonova[m] (3) * Amita (3) * Southern_Gentlem (2) * robyduck (2) * alciregi (2) * Rhea (1) * jsmith (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

[mindshare] Issue #7: Write event report from FAD
by Justin W. Flory 05 Mar '18

05 Mar '18

jflory7 reported a new issue against the project: `mindshare` that you are following: `` From the combined Meetbot minutes, Etherpad, and/or handwritten notes, form an event report to publish on the Community Blog. `` To reply, visit the link below or just reply to this email https://pagure.io/mindshare/issue/7

1 0

[mindshare] Issue #6: Research other "representation" programs in other open source communities
by Justin W. Flory 05 Mar '18

05 Mar '18

jflory7 reported a new issue against the project: `mindshare` that you are following: `` In the context of our [Ambassadors discussion], add research about external communities and how they manage / run their representation programs `` To reply, visit the link below or just reply to this email https://pagure.io/mindshare/issue/6

1 0

[mindshare] Issue #5: update ambassadors conduct document, put in new docs site
by Matthew Miller 05 Mar '18

05 Mar '18

mattdm reported a new issue against the project: `mindshare` that you are following: `` https://fedoraproject.org/wiki/Ambassadors/Conduct is an interested document -- looks like a never-approved doc. This should be updated and put on the new docs site `` To reply, visit the link below or just reply to this email https://pagure.io/mindshare/issue/5

1 0

Mindshare FAD - Day 1 notes
by Justin W. Flory 04 Mar '18

04 Mar '18

The first day of the Mindshare FAD wrapped up today. I did my best to take notes and capture the discussion, ideas, and implementation items we discussed. A lot of our discussion topics for today will be extended into tomorrow when Nick joins us (currently onward-bound via train)! Feel free to follow along in #fedora-mindshare for the next two days. I'll try and take notes again for tomorrow and Tuesday. = = = = = Meeting ended Sun Mar 4 16:36:44 2018 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-04/mindshare.201… Minutes (text): https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-04/mindshare.201… Log: https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-04/mindshare.201… * * * * * ==================================================== #fedora-mindshare: Fedora Mindshare FAD 2018 - Day 1 ==================================================== Meeting started by jwf at 08:49:34 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-mindshare/2018-03-04/mindshare.201… . Meeting summary --------------- * Getting started (jwf, 08:49:56) * === Agenda for FAD === (jwf, 08:58:08) * Presented by robyduck (jwf, 08:58:18) * Sunday: Establishing workflow, organization, what Mindshare owns and how we work on tasks (jwf, 08:58:34) * Monday: Ambassador-focused day; two Ambassador seats for Committee, criteria to communicate to regions about swag organization, how regional budgets are managed, reporting and sharing best practices (jwf, 09:00:21) * Tuesday: Communication (how do we communicate between outreach teams on Committee?); shared release schedule (sharing information to the right people, emphasizing connection between Marketing and FESCo decisions when relevant to Ambassadors); standardization across events and measuring event / activity success (jwf, 09:01:57) * May be modified as we go (jwf, 09:02:41) * Quick recap: Looking at Mindshare (jwf, 09:03:08) * === What are we doing well as outreach? === (jwf, 09:03:16) * Events: Ambassadors organizing minor events and presenting at main events (jwf, 09:03:25) * Budget process: Mostly working in part to dedicated role in Fedora (jwf, 09:03:35) * Design & Web: Two teams collaborating together and offer good user experience (jwf, 09:03:48) * Marketing: Fedora Magazine and generating talking points (jwf, 09:04:05) * Docs: We have Docs, but at Flock when this was originally presented, the team was small; Docs FAD was last week and may impact this (jwf, 09:04:45) * === What is going wrong? === (jwf, 09:04:55) * Communication: Missing effective communication between single teams (jwf, 09:05:09) * Best practices: Not shared between teams, some teams have efficient processes (jwf, 09:05:20) * Reporting: From Council POV, info we need is not well-informed from events we attend (jwf, 09:05:38) * Marketing: Disconnected from other teams and its messages need to drive outreach teams again (jwf, 09:05:53) * Local communities: Strong interest from local communities but support not in place to help engage and include them in project (jwf, 09:06:49) * info-graphic.png (bubble graphic from robyduck's slides that demonstrates connections between technical teams, outreach teams, and end users) (jwf, 09:08:19) * === Mindshare's targets === (jwf, 09:08:28) * Improving communication between teams (jwf, 09:08:33) * Better collaboration and sharing of best practices between teams (jwf, 09:08:43) * Supporting management of budget for impact (jwf, 09:08:54) * More informed event planning with inputs from several groups (jwf, 09:09:15) * Ambassadors (jwf, 09:09:35) * Largest group within outreach teams (jwf, 09:09:47) * 500-700 Ambassadors, but much smaller number in practice (jwf, 09:10:01) * Find way to effectively measure who is an active contributor and Ambassador and better connect those people to the outreach goals and objectives for Fedora (jwf, 09:10:26) * IDEA: Moving away from regions: Serves as a divisive way of separating contributors from each other and working in silos; we recognize important of cultural differences but we need to have the Ambassadors functioning as a singular group with consistent messaging across all regions (jwf, 09:11:12) * Cross-region mentoring is also happening too, which may also make regional organization ineffective (jwf, 09:11:43) * IDEA: bexelbie: We would be lucky to have problem of active, local-language Ambassadors to figure out how to get them involved versus fractioned, divided way of communication and lack of working together across regions (jwf, 09:13:59) * mattdm has infographic to share to visualize teams in Fedora (jwf, 09:17:02) * Budget (jwf, 09:17:05) * Some blockers to overcome; bexelbie to drive this discussion on Monday (jwf, 09:17:36) * Storytellers: Recognizing the importance of these roles but there is no definition; nobody knows what they are (jwf, 09:17:52) * Budget is partially a challenge because of problems related to card-holding around regions (jwf, 09:19:00) * IDEA: But budget should be easy; transferring mechanical work (not decision-making work) where budget is easy will be important (jwf, 09:19:19) * IDEA: Anyone should be able to help maintain the budget (jwf, 09:19:26) * Design & Web; CommOps; Marketing (jwf, 09:19:43) * Design & Web need more input from outreach teams (jwf, 09:19:50) * CommOps: Not just CommBlog; could be more improved if responsible for "operations"; driving the communication process as a helpful activity (jwf, 09:20:24) * Marketing: Drive outreach activities (again); produce messages and strategies to reach targets (jwf, 09:20:49) * LINK: https://pagure.io/Fedora-Council/council-docs/raw/c29e147bed49e67ae787bb4ed… (mattdm, 09:23:21) * Looking at what our community is (jwf, 09:25:25) * LINK: https://pagure.io/Fedora-Council/council-docs/raw/master/f/project/images/o… (jwf, 09:25:29) * Four major directions splitting from the Fedora Council: FESCo, Mindshare, Diversity & Inclusion, Objectives (jwf, 09:25:57) * Beyond those four groups, details get fuzzy (jwf, 09:26:05) * bexelbie: On the right, problems we face in Mindshare are needing people to be aware of everything on the right side of the infographic (jwf, 09:26:51) * Recognizing needs for Globalization: Globalization is critical but outside of scope of Mindshare **Committee**; needs of that group supported by FPL/FCAIC but not Mindshare (jwf, 09:30:11) * IDEA: Ambassadors: Participating as Ambassador doesn't require activity in other part of project (jwf, 09:32:03) * IDEA: x3mboy: People don't understand what it means to be an Ambassador (jwf, 09:32:23) * LINK: https://communityblog.fedoraproject.org/x-international-it-report/ (jwf, 09:32:44) * "Show up and do something" (jwf, 09:33:56) * IDEA: Requiring people to join a group to do something, but we want people to do something (jwf, 09:34:17) * Recognizing the stop energy behind debating titles of Ambassadors (looking at regional issues of what the Ambassador title "means") (jwf, 09:36:33) * IDEA: Translations does not equal Ambassadorship: In LATAM / APAC, local contributors are tired of being directed to translations when that's not their interests or something they enjoy (jwf, 09:39:51) * AGREED: Recognizing importance of Globalization and communication, but something this Committee addresses (jwf, 09:40:15) * AGREED: Need to address messaging and social media within outreach bubble (jwf, 09:44:08) * AGREED: Major plumbing to do in Ambassadors (jwf, 09:44:15) * LINK: https://fedoraproject.org/wiki/Marketing_social_networks?rd=Social_media (x3mboy, 09:44:58) * AGREED: Not spending the three days discussing what we are / what the committee is; setting an opinion and moving forward to drive discussion (jwf, 09:50:47) * Marketing messaging (jwf, 09:52:07) * Moving away from: "Why are we building Fedora 28?" => "Because it's that time of the year" (jwf, 09:52:50) * mattdm: "Because of how Fedora works with rapid releases and changes (we don't ask what our goals are for this release), driving message about why we build Fedora and what we're doing" (jwf, 09:54:01) * IDEA: Release messaging separated from "what we're doing" messaging (jwf, 09:54:50) * Recognizing that engineering groups have pre-existing sentiment towards marketing and we've struggled engaging with those technical people to participate in Marketing (jwf, 09:57:29) * IDEA: jwf: "Felt like Marketing was checking boxes and following a process when I was driving it, possibly need to start fresh and re-evaluate what we're doing today" (jwf, 09:58:01) * IDEA: bexelbie: "What Fedora is and how we message our operating system; not focus exclusively on releases; release press is modeled off what we're doing today and is continual off what we do year-round" (jwf, 09:58:52) * IDEA: Changes process: Thinking through what a (FESCo) change plans to accomplish and tying that in early to a marketing message (jwf, 10:00:16) * IDEA: x3mboy: "Splitting marketing into multiple roles"; jwf: "Drive-by contribution model was common in the past before in Marketing" (jwf, 10:03:01) * IDEA: Redirecting feedback or energy on things like marketing to teams and groups like the Marketing / outreach teams (jwf, 10:06:51) * IDEA: Tying Objectives into outreach: Communicating high-level goals inward and outward (jwf, 10:25:52) * IDEA: Question queue: What do people want to know about Fedora? What do they not understand? What do we want to emphasize about why we're doing something? (jwf, 10:26:23) * Using interviews as a concrete activity to connect dots between technical teams to non-technical outreach teams without putting work on outreach teams to create message (jwf, 10:27:03) * LINK: https://www.pragmaticmarketing.com/framework (bexelbie, 10:27:30) * IDEA: Pragmatic marketing: Marketing has two pieces, strategic and execution; creating a new group (e.g. "marketing execution") to work on execution and strategic direction into Mindshare (jwf, 10:30:13) * AGREED: Marketing strategy and direction focused within Mindshare; execution as a task within the outreach teams (jwf, 10:37:08) * LINK: https://etherpad.gnome.org/p/fedora-personas a sampling of personas from fedora land.. in various states of "currentness" (langdon, 10:54:24) * Framework: How to drive discussion / learning for creating messaging (jwf, 10:59:37) * People care about Fedora enables them to do (jwf, 11:01:21) * IDEA: Focus on stories we want people to be interested in (then technical / non-technical details fall underneath) (jwf, 11:01:49) * LINK: https://pagure.io/fedora-marketing/issue/262 (x3mboy, 11:04:20) * Lunch break! (jwf, 11:13:09) * How this team communicates and takes the message "home" (jwf, 13:55:31) * Design Team: Email is most effective way to communicate and get things noticed (jwf, 13:55:47) * LINK: https://pagure.io/Fedora-Council/council-docs/raw/master/f/project/images/o… (jwf, 14:10:55) * IDEA: Elected representatives serving as community liaisons to the different smaller communities without representation (jwf, 14:11:20) * IDEA: Mailing list(s) to balance administration work / internal Committee work and other smaller teams on a larger list (jwf, 14:16:25) * IDEA: Have an ongoing place where we track messaging we want to send each month; we rotate through committee members to write the article we publish month (not a writing exercise, a "do it and done" task) (jwf, 14:24:07) * Small event standardization (jwf, 14:39:19) * LINK: https://fedoraproject.org/wiki/Ambassadors/Latam/EventOrganizationGuideLine (jwf, 14:39:24) * === Release parties === (jwf, 14:40:30) * IDEA: Lowering barrier of entry for community members to organize local events, starting with release parties (with the goal to expand to more types of small events later) (jwf, 14:41:09) * Focused on release parties to talk about release and related topics (jwf, 14:41:41) * We'll send stickers and $100 USD to organize event (jwf, 14:41:50) * Requires a blog post on Community Blog to answer who, what, when, where (and some evaluation questions to be written) (jwf, 14:42:12) * Mindshare Committee receives, approves, handles these requests (jwf, 14:43:46) * IDEA: Building a model to be replicated across for other activities (jwf, 14:45:19) * === LATAM event guidelines === (jwf, 14:47:50) * Structured in pre- and post-event tasks (jwf, 14:47:57) * Focusing on ticket-based workflow from the existing pre-event tasks (jwf, 14:49:13) * Post-event tasks: Write post in the CommBlog to talk about event and impact (jwf, 14:50:20) * Reporting as a requirement for reimbursement (jwf, 14:50:45) * IDEA: Wrapping social media coverage into event guidelines as an ask to organizer (jwf, 14:52:11) * IDEA: Sample micro-messages (e.g. tweets) (jwf, 14:52:49) * IDEA: Anyone on Committee goes into release event party request reads ticket, sees required info for threshold, event approved, then with guidelines passed to event organizers for organizing their event (jwf, 14:55:50) * IDEA: Design team tie-in: Standard media creation with things like banners / images / content (when ready) (jwf, 14:56:36) * IDEA: Tagging Fedora account for specific social media platform; hashtag of #FedoraReleaseParty (jwf, 14:58:46) * IDEA: Creating release posters side-by-side with wallpaper creation along with FXX badge (jwf, 15:04:42) * Fedora Meet-ups (jwf, 15:10:09) * Assuming release party model works, what changes? (jwf, 15:10:18) * IDEA: Initially this is for Ambassadors and intended to be low-friction (like release parties); a lesser amount as default value and required justification for me (jwf, 15:13:45) * === What do you have to do? === (jwf, 15:14:30) * (1) Be an Ambassador (jwf, 15:14:35) * (2) Open a ticket (when, where, why, how) (jwf, 15:14:49) * (3) Report follow-up (event report, photo, suggestions on how to improve) (jwf, 15:15:03) * Travel budget <$25 USD for transportation. This is for local, one-off meet-ups. (jwf, 15:17:39) * Budget discussions (jwf, 15:48:13) * Is this group allocated budget and managed within the committee? What are logistics of budget? (jwf, 15:48:30) * AGREED: Keeping the Mindshare line budget item for next fiscal year (jwf, 15:50:07) * CommOps coverage and tasks (x3mboy, 16:12:36) * ACTION: jwf Review CommOps ticket queue to evaluate what CommOps is doing that is strategy work or tactical work (jwf, 16:14:31) * Figuring out where CommOps fits into the bigger picture of Mindshare with strategy and tactics (jwf, 16:23:42) * Mindshare sees CommOps as a tactical body to execute the strategy determined via Mindshare and to inform Mindshare of the success / failure of strategical implementation (jwf, 16:24:30) * In English: Mindshare brainstorms, CommOps does the things; CommOps tells Mindshare if what we're doing is working or we need to back up (jwf, 16:25:04) * IDEA: CommOps needs to specify the difference more between Marketing and CommOps (jwf, 16:27:08) * Summary (jwf, 16:29:02) * AGREED: Ticket-based workflow for how we work on tasks (jwf, 16:29:17) * AGREED: Strategy and plan to execute event management for small events (e.g. release parties and meetups) (jwf, 16:29:39) * Conversation set up for tomorrow about strategy to gain actual mindshare within the Fedora community (jwf, 16:29:55) * Queuing conversation to make Ambassador group more effective on what we think they need to be doing and how we communicate that down to them (jwf, 16:30:17) * AGREED: Communication plan for how we communicate to the rest of the community: Using certain, using our members to represent the other sub-projects in this committee (e.g. our ticket getting feedback from the Design Team via the Design rep) (jwf, 16:33:07) * IDEA: Need to ensure we document what we discussed, and then deliver an updated wiki / doc page-site-thing (jwf, 16:33:56) Meeting ended at 16:36:44 UTC. Action Items ------------ * jwf Review CommOps ticket queue to evaluate what CommOps is doing that is strategy work or tactical work Action Items, by person ----------------------- * jwf * jwf Review CommOps ticket queue to evaluate what CommOps is doing that is strategy work or tactical work * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (223) * zodbot (17) * nb (15) * x3mboy (6) * langdon (5) * bexelbie (2) * mattdm (1) * robyduck (0) * mleonova[m] (0) * mindshare (0) * jsmith (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

[MOVED TO DISCOURSE] Mindshare - https://discussion.fedoraproject.org/tag/mind-co March 2018