CommOps Weekly Meeting Recap 2016-05-24
by Justin W. Flory
Meeting ended Tue May 24 17:28:21 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-05-24)
============================================
Meeting started by jflory7 at 15:58:38 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:58:52)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-24
(jflory7, 15:58:59)
* (1) Roll Call / Q&A (jflory7, 15:59:05)
* (2) Announcements (jflory7, 15:59:11)
* (3) Action items from last meeting (jflory7, 15:59:17)
* (4) Tickets (jflory7, 15:59:22)
* (5) Wiki Gardening (jflory7, 15:59:26)
* (6) Community Blog (jflory7, 15:59:31)
* (7) Release Schedule (jflory7, 15:59:35)
* (8) Open Floor (jflory7, 15:59:43)
* Roll Call / Q&A (jflory7, 15:59:48)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:59:52)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
soon-to-be Infrastructure, Diversity, etc. (jflory7, 16:00:25)
* Sayan Chowdhury;UTC+5:30; Infrastructure, CommOps, Marketing,
Ambassadors etc. (sayan, 16:00:49)
* dhanesh95, UTC+5:30, CommOps, soon-to-be Packager, ML (dhanesh95,
16:00:50)
* skamath; UTC +5.30; CommOps, Metrics, Security (skamath, 16:01:54)
* Trishna Guha; UTC+5:30; Infrastructure, Cloud, CommOps, Magazine
(trishnag, 16:02:27)
* decause; UTC-4; Commops, Council, GSoC, Budget, Flock, * (decause,
16:04:12)
* bee2502; UTC +5.30; CommOps, Metrics, Elections , Fedmsg
(bee2502__, 16:04:22)
* Charles Profitt, UTC-4; Marketing, Cloud, CommOps, Security
(cprofitt, 16:05:24)
* LinuxHippie, UTC-6; commops, ambassadors (LinuxHippie, 16:06:48)
* Announcements (jflory7, 16:06:49)
* === "Flock 2016 schedule is now out" === (jflory7, 16:06:59)
* LINK: https://fedoramagazine.org/flock-2016-schedule-now/
(jflory7, 16:07:04)
* Devyani Kota, UTC+5:30; Infrastructure, CommOps, Hubs. (devyani7,
16:07:14)
* Flock is Fedora's annual contributor conference where Fedorans
across the world get together for talks, sprints, workshops, and
more. The schedule for this year's Flock was recently published and
you can find out what talks and workshops there will be for this
year. Some CommOpsers are giving talks this year! (jflory7,
16:07:14)
* === Google Summer of Code "All-Hands", 2016-05-25, 15:00 UTC ===
(jflory7, 16:07:28)
* The Google Summer of Coding All-Hands meeting will be on Wednesday
at 15:00 UTC in #fedora-meeting. This will be the big kick-off,
officially, for the summer! (jflory7, 16:07:33)
* === Fedora @ PyCon US === (jflory7, 16:07:39)
* There will be Fedora sprints at PyCon this year. They're from
Thursday, 2016-06-02 to Sunday, 2016-06-05. (jflory7, 16:07:45)
* decause will be going to PyCon 2016-05-27 to 2016-06-02 and be
harder to get a hold of than usual (until the sprints). (jflory7,
16:07:52)
* CORRECTION: All-Hands includes GSoC AND Outreachy and Red Hat
interns (jflory7, 16:08:19)
* decause plans to come to SELF (nb, 16:09:56)
* ACTION: cprofitt File a ticket for wiki gardening the Python SIG
page (others who have noticed things can also chime in, cc:
LinuxHippie / dhanesh95) (jflory7, 16:19:39)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-24
(bee2502_, 16:26:42)
* Action items from last meeting (decause, 16:27:29)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-17/commops.2016-...
(decause, 16:27:40)
* 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. (decause,
16:27:48)
* === [COMPLETE] commops add the 'how it works' link above to the
etherpad under resources === (decause, 16:27:55)
* === [COMPLETE] decause send out timeslot requests for GSoC ===
(decause, 16:28:03)
* === decause add money dollars to limesurvey due:Friday ===
(decause, 16:28:08)
* ACTION: decause follow-up with tatica and diversity team about
limesurvey avaiability (decause, 16:29:06)
* AGREED: Complete! decause purchased 5000 responses, so there is
moneydollars in the LimeSurvey account. Next steps is getting it to
tatica and Diversity team. (jflory7, 16:29:47)
* === decause talk to spot about scheduling an EDU FAD after budget
gets settled === (decause, 16:30:21)
* ACTION: commops socialize the wiki page, start drafting a commblog
article to go out before end of June (decause, 16:30:58)
* === [INCOMPLETE] jflory7 Post to the mailing list with ideas about
the FOSS Student Pack, along with links to a planning pad either on
the wiki or in an Etherpad === (decause, 16:31:16)
* ACTION: jflory7 Post to the mailing list with ideas about the FOSS
Student Pack, along with links to a planning pad either on the wiki
or in an Etherpad (decause, 16:31:24)
* === [INCOMPLETE] jflory7 Open discussion on the mailing list about
Ticket #71 and centralizing Ambassador resources (to get
brainstorming going) === (decause, 16:31:34)
* ACTION: jflory7 Open discussion on the mailing list about Ticket #71
and centralizing Ambassador resources (to get brainstorming going)
(decause, 16:31:40)
* === [INCOMPLETE] jflory7 Write Bitcamp 2016 article on CommBlog and
point to individual event reports by other Ambassadors ===
(decause, 16:31:48)
* ACTION: jflory7 Write Bitcamp 2016 article on CommBlog and point to
individual event reports by other Ambassadors (decause, 16:31:55)
* === [INCOMPLETE] jflory7 Bring the CommOps vFAD ticket back up to
the table, make a wiki page, do the metadata planning-esque type of
tasks === (decause, 16:32:05)
* ACTION: jflory7 Bring the CommOps vFAD ticket back up to the table,
make a wiki page, do the metadata planning-esque type of tasks
(decause, 16:32:11)
* === [COMPLETE] jflory7 Ship F24 Party article today === (decause,
16:32:22)
* LINK:
https://communityblog.fedoraproject.org/fedora-24-have-a-party/
(decause, 16:32:33)
* ACTION: decause work with jzb to possibly organize a release party
in RDU (decause, 16:33:01)
* === [IN PROGRESS] jflory7 Remove Ticket #74 from meeting agenda, add
info about where to find the pull request for the ticket ===
(decause, 16:33:32)
* ACTION: jflory7 Add info about where to find the pull request for
Ticket #74 (decause, 16:33:37)
* === decause / commops stop by the docs office hours tomo to discuss
release notes -> release announce flow === (decause, 16:33:50)
* ACTION: decause / commops stop by the docs office hours tomo to
discuss release notes -> release announce flow (decause, 16:34:04)
* ACTION: decause / commops go to docs office hours at 3pm EST (7pm
UTC) to talk release notes -> GA Announcement (decause, 16:36:13)
* === decause add conf schedule to Fedocal === (decause, 16:37:17)
* ACTION: decause nail down Flock arrangements, add them to Fedocal
(decause, 16:37:58)
* === [COMPLETE] dhanesh95 Fork a wiki page for the Education FAD from
the template linked previously and begin templating the details for
the Education FAD to take place over this summer === (decause,
16:38:03)
* LINK: https://fedoraproject.org/wiki/FAD_EDU_2016 (dhanesh95,
16:38:10)
* ACTION: decause / dhanesh95 / spot look into booking conference
rooms in the Tower (Fedora on 9 if it is available) (decause,
16:39:08)
* Tickets (decause, 16:39:58)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (decause,
16:40:09)
* === Tickets #34, 49 === (decause, 16:40:15)
* #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (decause, 16:40:21)
* #49: "[Onboarding Series] Infrastructure" (decause, 16:40:26)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (decause,
16:40:33)
* LINK: https://fedorahosted.org/fedora-commops/ticket/49 (decause,
16:40:38)
* CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs
Team Badges Tracks and Widgets (decause, 16:40:44)
* LINK: http://whenisgood.net/fedora/badges-workshop (decause,
16:41:07)
* LINK:
http://whenisgood.net/fedora/commops/power-sessions/results/xgtq9g2
(jflory7, 16:43:04)
* === Ticket #68 === (decause, 16:46:55)
* "Reconstructing the Campus Ambassadors program and campus outreach"
(decause, 16:47:00)
* LINK: https://fedorahosted.org/fedora-commops/ticket/68 (decause,
16:47:05)
* LINK:
https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
(decause, 16:47:09)
* LINK: https://fedoraproject.org/wiki/FAD_EDU_2016 (decause,
16:47:21)
* AGREED: EDU FAD can be updated in a hack session to include
information about what it is, can be followed by a CommBlog article
and mailing list posts (jflory7, 16:50:03)
* === Ticket #69 === (decause, 16:50:39)
* "Fedora Modularity onboarding" (decause, 16:50:47)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69 (decause,
16:50:53)
* (1) Someone can review the contents of their on-boarding wiki page
and pass feedback about them in the ticket, as compared to other
on-boarding methods in Fedora (decause, 16:51:02)
* (2) Putting together a badge proposal for membership in the
Modularity WG (in the form of a ticket on the fedora-badges Trac)
(decause, 16:51:08)
* (3) A Community Blog article announcing the presence of the
Modularity WG, what they are, what they do, how to get involved
(penned by one of the WG members) (decause, 16:51:13)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69#comment:2
(decause, 16:51:20)
* ACTION: jflory7 add tickets agreed to today for power-session onto
agenda in the power-sessions etherpad (decause, 16:53:04)
* Wiki Gardening (decause, 16:53:12)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps
(decause, 16:53:18)
* LINK: https://fedoraproject.org/wiki/PyCon_2016 (decause,
16:53:50)
* LINK: https://fedoraproject.org/wiki/Red_Hat_Summit_2016 (decause,
16:54:18)
* Community Blog (decause, 16:56:07)
* 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! (decause,
16:56:17)
* === This Week in CommBlog === (decause, 16:56:33)
* (1) "Fedora 24: Let's have a party!" (decause, 16:56:39)
* LINK:
https://communityblog.fedoraproject.org/fedora-24-have-a-party/
(decause, 16:56:44)
* Total Views (May 24): [ no statistics generated yet, just published
] (decause, 16:56:49)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(decause, 16:56:54)
* === Coming Up in CommBlog === (decause, 16:57:01)
* (1) "Fedora at Bitcamp 2016" (decause, 16:57:07)
* (2) "Fedora Loves PyCon 2016" (decause, 16:57:26)
* (3) "Red Hat Summit 2016" (decause, 16:57:46)
* (4) "Flock Schedule Posted (pointer to FM)" (decause, 16:58:07)
* (5) "OSCON Event Report by maxamillion" (decause, 16:58:28)
* Release Schedule (decause, 16:58:47)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(decause, 16:58:58)
* ACTION: maxamillion log into commblog, create a draft for the OSCON
report, and then review decause's edits (decause, 17:01:27)
* ACTION: decause input the report, make edits, clear with
maxamillion, push before Friday Wheels Up for PyCon (decause,
17:02:06)
* Final Release Public Availability (GA) Tue 2016-06-14 (decause,
17:02:34)
* LINK: https://fedoraproject.org/wiki/Red_Hat_Summit_2016 (decause,
17:05:28)
* Open Floor (decause, 17:06:22)
* LINK:
https://fedorahosted.org/design-team/raw-attachment/ticket/431/fedora-pyt...
(decause, 17:11:17)
* LINK: http://imgur.com/6en0x36 (decause, 17:16:02)
* LINK: http://imgur.com/kBK0udF (decause, 17:18:18)
* HELP: Ambassadors Please Submit your Q1 Budget reports by Friday
(decause, 17:19:39)
* LINK: http://pagure.io/fedora-budget (decause, 17:20:07)
* ACTION: commops please vote on the proposal to extend meeting time
and chime in with your comments (decause, 17:21:28)
* Parting Thoughts (decause, 17:23:17)
Meeting ended at 17:28:21 UTC.
Action Items
------------
* cprofitt File a ticket for wiki gardening the Python SIG page (others
who have noticed things can also chime in, cc: LinuxHippie /
dhanesh95)
* decause follow-up with tatica and diversity team about limesurvey
avaiability
* commops socialize the wiki page, start drafting a commblog article to
go out before end of June
* jflory7 Post to the mailing list with ideas about the FOSS Student
Pack, along with links to a planning pad either on the wiki or in an
Etherpad
* jflory7 Open discussion on the mailing list about Ticket #71 and
centralizing Ambassador resources (to get brainstorming going)
* jflory7 Write Bitcamp 2016 article on CommBlog and point to individual
event reports by other Ambassadors
* jflory7 Bring the CommOps vFAD ticket back up to the table, make a
wiki page, do the metadata planning-esque type of tasks
* decause work with jzb to possibly organize a release party in RDU
* jflory7 Add info about where to find the pull request for Ticket #74
* decause / commops stop by the docs office hours tomo to discuss
release notes -> release announce flow
* decause / commops go to docs office hours at 3pm EST (7pm UTC) to talk
release notes -> GA Announcement
* decause nail down Flock arrangements, add them to Fedocal
* decause / dhanesh95 / spot look into booking conference rooms in the
Tower (Fedora on 9 if it is available)
* jflory7 add tickets agreed to today for power-session onto agenda in
the power-sessions etherpad
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps
* maxamillion log into commblog, create a draft for the OSCON report,
and then review decause's edits
* decause input the report, make edits, clear with maxamillion, push
before Friday Wheels Up for PyCon
* commops please vote on the proposal to extend meeting time and chime
in with your comments
Action Items, by person
-----------------------
* commops
* commops socialize the wiki page, start drafting a commblog article
to go out before end of June
* decause / commops stop by the docs office hours tomo to discuss
release notes -> release announce flow
* decause / commops go to docs office hours at 3pm EST (7pm UTC) to
talk release notes -> GA Announcement
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps
* commops please vote on the proposal to extend meeting time and chime
in with your comments
* cprofitt
* cprofitt File a ticket for wiki gardening the Python SIG page
(others who have noticed things can also chime in, cc: LinuxHippie /
dhanesh95)
* decause
* decause follow-up with tatica and diversity team about limesurvey
avaiability
* decause work with jzb to possibly organize a release party in RDU
* decause / commops stop by the docs office hours tomo to discuss
release notes -> release announce flow
* decause / commops go to docs office hours at 3pm EST (7pm UTC) to
talk release notes -> GA Announcement
* decause nail down Flock arrangements, add them to Fedocal
* decause / dhanesh95 / spot look into booking conference rooms in the
Tower (Fedora on 9 if it is available)
* maxamillion log into commblog, create a draft for the OSCON report,
and then review decause's edits
* decause input the report, make edits, clear with maxamillion, push
before Friday Wheels Up for PyCon
* dhanesh95
* cprofitt File a ticket for wiki gardening the Python SIG page
(others who have noticed things can also chime in, cc: LinuxHippie /
dhanesh95)
* decause / dhanesh95 / spot look into booking conference rooms in the
Tower (Fedora on 9 if it is available)
* jflory7
* jflory7 Post to the mailing list with ideas about the FOSS Student
Pack, along with links to a planning pad either on the wiki or in an
Etherpad
* jflory7 Open discussion on the mailing list about Ticket #71 and
centralizing Ambassador resources (to get brainstorming going)
* jflory7 Write Bitcamp 2016 article on CommBlog and point to
individual event reports by other Ambassadors
* jflory7 Bring the CommOps vFAD ticket back up to the table, make a
wiki page, do the metadata planning-esque type of tasks
* jflory7 Add info about where to find the pull request for Ticket #74
* jflory7 add tickets agreed to today for power-session onto agenda in
the power-sessions etherpad
* jzb
* decause work with jzb to possibly organize a release party in RDU
* LinuxHippie
* cprofitt File a ticket for wiki gardening the Python SIG page
(others who have noticed things can also chime in, cc: LinuxHippie /
dhanesh95)
* maxamillion
* maxamillion log into commblog, create a draft for the OSCON report,
and then review decause's edits
* decause input the report, make edits, clear with maxamillion, push
before Friday Wheels Up for PyCon
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* decause (285)
* jflory7 (109)
* dhanesh95 (39)
* zodbot (26)
* skamath (22)
* nb (13)
* cprofitt (12)
* maxamillion (9)
* mizmo (8)
* bee2502_ (8)
* danofsatx (8)
* LinuxHippie (7)
* zoglesby (4)
* bee2502__ (4)
* devyani7 (3)
* sayan (3)
* jzb (2)
* trishnag (2)
* Southern_Gentlem (1)
* jflory7_ (1)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 11 months
Re: [Marketing] community blog article
by Justin W. Flory
On 04/29/2016 05:50 AM, S.Kemter wrote:
> Hi,
>
> I made another article in the community blog:
> https://communityblog.fedoraproject.org/lets-have-a-party/
>
> We have to animate our Ambassadors to start thinking on their release
> parties, that might help.
>
> Maybe its a good idea to make an article in Fedoramagazine when the
> release is there about the parties and where they are.
>
> br gnokii
>
Hey gnokii, thanks for writing! For future reference, for anything
related to the Community Blog, please drop a line on the CommOps mailing
list so some of the folks on this list can review it as well. It will
help make sure it gets a more timely review. :)
Here is a public preview of the article:
https://communityblog.fedoraproject.org/?p=1496&preview=1&_ppp=29ca871c07
At our last CommOps meeting, we put this one on the agenda. We were
curious as to when the ideal time to push this article out would be. Do
you want this to go out as soon as possible or do you want to wait for
closer to Fedora 24 (or maybe right on the tail of the beta announcement
for some extra spotlight)? Let us know what you had in mind and we can
aim to get it out.
Thanks for writing!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 11 months
Event Page for Red Hat Summit 2016 now on the Fedora Wiki
by Remy DeCausemaker
https://fedoraproject.org/wiki/Red_Hat_Summit_2016
As far as I can tell, this list hasn't seen much traffic in _some_
time, but this is the right place to be posting this type of message,
so, welcome back!
If you are attending Red Hat summit this year, and especially if you
are giving a talk, please be sure to add your details. If you know
other Fedora-friends attending Summit, then please point them towards
this wiki page as well.
I'm bcc'ing some folks directly whom I know will be present, or have
included "Fedora" in a talk title or in their profile to get us
started.
Thanks all for helping organize and represent Fedora at Summit!
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
7 years, 11 months
Welcome to Summer Coding 2016: Week 1
by Remy DeCausemaker
Summer Coding Mentors, admins, and Students,
Welcome! I hope that all of you have had a productive community
bonding period, and that you're excited to begin the official coding
period for the summer, which officially starts tomorrow 5/23.
The mentors and admins have put together this handy welcome kit in
etherpad, which goes into deep detail about tasks that you should
complete in your first week, and some general advice moving forward.
Please go through the list and complete the tasks listed under the
"Welcome to Summer Coding 2016" section, starting at line #51
(mentors, you too have some pertinent tasks listed there, so please
give it a good look, particularly the whenisgood.net polls.)
Summer Coding Welcome Kit:
http://etherpad.osuosl.org/fedora-gsoc-welcome-2016
Until we all decide on the best available time, we're going to be
holding the first weekly check-in on Wednesday at 3pm UTC (11am EST)
in #fedora-meeting.
Be sure to join #fedora-summer-coding, #fedora-commops, and any other
fedora-related IRC channels that will be pertinent to your work this
summer (e.g. #fedora-hubs, #fedora-outreachy, #fedora-apps, etc...)
I look forward to getting to know you all more in the next week,
promoting your work, and answering any questions you may have.
Please start tackling any tasks that you've yet to complete in the
welcome kit starting tomorrow when you clock in, and I look forward to
checking in with you all Wednesday!
Your Faithful Org Admin,
--RemyD.
P.S. - Paul, if you could, please forward this message onto the Red
Hat interns, as I do not have contact emails for them yet. Hopefully
they'll be in the system before Wednesday :)
--
Remy DeCausemaker
Hackademic & Community Lead
http://whatcanidoforfedora.org
7 years, 11 months
Reminder: FY17 First Quarter Budget Report due by Friday 5/20
by Remy DeCausemaker
On May 15, 2016 08:00, <viorel(a)fedoraproject.org> wrote:
>
> Dear all,
>
> You are kindly invited to the meeting:
> First Quarter Budget Report on 2016-05-16 from 12:00:00 to 13:00:00 UTC
> At fedora-commops(a)irc.freenode.net
>
> The meeting will be about:
> * Fiscal Year: *FY17*
> * Responsible: *Regional Treasurers → FCL*
>
> **Note:**
> The "→" above indicates that responsibility for that item feeds into a
next step in responsibility; for example, regional treasurers are
responsible for providing the FCL with the relevant information for their
region, and the FCL is responsible for the general report to the community.
Likewise, the Council is responsible for any top-level budget adjustment
when the final budget comes in from our sponsor, and regions responsible to
update accordingly if needed.
>
> More information available at:
> [Budget next](https://fedoraproject.org/wiki/Budget.next)
>
>
> Source: https://apps.fedoraproject.org/calendar/meeting/3315/
Treasurers,
This email is less about an actual "meeting," and more of a general
reminder that this task should be completed by the end of this week. There
are still some finer details to hash out, and we will settle on a common
format and template soon, but so far I like APAC's approach to reporting
with a spreadsheet that includes columns for: a full name for the expense
(not just a conference abbreviation,) email address of whom it was paid to,
link to ticket requesting the funding, link to the *required* event report
after, and any additional links or comments.
***Note: This timing also reflects Red Hat's fiscal quarter timing, and
that expenses reported outside of this time-frame will be recorded in Q2.***
If folks have questions, just drop me an email and I'll begin responding
tomorrow. Pull requests can be sent to: http://pagure.io/fedora-budget.
Happy Hacking,
--RemyD.
P.S. - If you have not already subscribed to the budget fedocal, here is
the link:
https://apps.fedoraproject.org/calendar/Budget/
7 years, 11 months
Marketing-trac: #219: Create Python talking points for Ambassadors
by Marketing Team
#219: Create Python talking points for Ambassadors
---------------------------------+------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: critical | Milestone: Fedora 23
Component: Talking Points | Severity: urgent
Keywords: python, nextmeeting | Blocked By:
Blocking: |
---------------------------------+------------------------
Originally discussed in a
[https://lists.fedoraproject.org/pipermail/marketing/2016-March/019027.html
cross-posted mailing list thread].
= What =
As was identified by mattdm at DevConf CZ (and earlier discussions),
Python, Python developers, and Python communities are a major target
audience for Fedora in 2016. Ambassadors are encouraged to attend and
promote Fedora in these communities and share how Fedora makes working
with Python easier, more effective, etc. However, we are not sending them
out with any documented talking points! Marketing can help with this area.
= How =
We have a limited set of resources from the past we can work with. Ruth
pointed out on the list that there is an existing
[https://fedoraproject.org/wiki/Marketing/Python_brochure Python brochure]
that was created, but the information on it is old, outdated, and it needs
some touching up.
== Brochure update ==
The solution to this I proposed on the list was:
1. Identify "hot topics" of Python and create a list.
* "What makes Python so great on Fedora?"
* "How is working on Python in Fedora easier than other distros?"
* "What tools and resources does Fedora offer for Python developers?"
* "What kind of support is there for Python developers in the project?"
* "I'm a Python developer and want to help contribute. What can I do to
help?"
2. Submitting a ticket on the Design Team Trac with this info and a
request to update the flyer for distribution in 2016.
== Building our resources ==
Like was mentioned on the list, there are not many resources available
showing or teaching how Fedora is Python-friendly. Perhaps working with
our Infrastructure team to get a list of some of the hottest Python
projects they have and using this as a base is in our interest.
= When =
This is an urgent need. Our Ambassadors either are going out or will be
going out to Python events soon across the world and providing them with
the resources to effectively market Python + Fedora is the first step.
* **Tentative Due Date**: End of March, absolute *latest*
= Open Discussion =
Thoughts, ideas, or ways we can tackle this are welcome. I am intending to
add this ticket to the
[https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2016-03-02
2016-03-02 Marketing meeting agenda].
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/219>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
7 years, 11 months
CommOps Hack Session Recap 2016-05-18
by Justin W. Flory
Meeting ended Wed May 18 16:55:49 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-3/2016-05-18/commops.201...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-3/2016-05-18/commops.201...
Log
https://meetbot.fedoraproject.org/fedora-meeting-3/2016-05-18/commops.201...
* * * * *
===========================================================
#fedora-meeting-3: Fedora CommOps Hack Session (2016-05-18)
===========================================================
Meeting started by jflory7 at 13:43:29 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-3/2016-05-18/commops.201...
.
Meeting summary
---------------
* Getting started (jflory7, 13:43:39)
* We are using a Google+ Hangout for today in supplement to the IRC
meeting (jflory7, 13:44:22)
* LINK: https://hangouts.google.com/call/7s5qkbhrxfhudjfate35yfa6iee
(jflory7, 13:44:23)
* Tickets of interest (jflory7, 13:47:37)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
13:47:40)
* LINK: https://fedorahosted.org/fedora-commops/ticket/49 (jflory7,
13:47:44)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69 (jflory7,
13:47:46)
* LINK: https://fedorahosted.org/fedora-commops/ticket/64 (jflory7,
13:48:09)
* Roll call (jflory7, 13:51:29)
* LINK: https://etherpad.gnome.org/p/commops-power-sessions
(jflory7, 13:56:14)
* Explaining Badges (jflory7, 13:59:57)
* LINK: https://badges.fedoraproject.org/builder (jflory7, 14:00:01)
* LINK: https://github.com/fedora-infra/datanommer (jflory7,
14:00:10)
* LINK: https://github.com/fedora-infra/fedmsg (jflory7, 14:00:20)
* Here is an example of a YAML file given to someone when they join a
FAS group: (jflory7, 14:03:25)
* LINK:
https://git.fedorahosted.org/cgit/badges.git/tree/rules/fas-ambassador.yml
(jflory7, 14:03:27)
* The entire repo of all YAML files ever lives here: (jflory7,
14:03:50)
* LINK: https://git.fedorahosted.org/cgit/badges.git/tree/rules
(jflory7, 14:03:51)
* LINK: https://fedorahosted.org/fedora-badges/ (jflory7, 14:08:36)
* Here is a full list of all proposed badges that are not yet
complete: (jflory7, 14:09:40)
* LINK: https://fedorahosted.org/fedora-badges/report/26 (jflory7,
14:09:41)
* LINK: https://fedorahosted.org/fedora-badges/ticket/407 (jflory7,
14:17:53)
* LINK:
http://blog.linuxgrrl.com/2016/04/26/plan-to-level-up-contributors-with-f...
(decause, 14:18:23)
* LINK:
https://fedorahosted.org/fedora-commops/search?q=onboarding+badge
(meskarune, 14:35:49)
* LINK: https://fedorahosted.org/fedora-badges/ticket/303 (jflory7,
14:43:40)
* LINK: https://fedorahosted.org/fedora-badges/ticket/303#comment:6
(jflory7, 14:46:07)
* jflory7's links (jflory7, 15:43:55)
* LINK: https://fedorahosted.org/fedora-infrastructure/ticket/5306
(jflory7, 15:51:24)
* LINK:
https://fedorahosted.org/fedora-badges/attachment/ticket/223/0001-Automat...
(jflory7, 16:00:55)
* LINK:
https://fedorahosted.org/fedora-badges/attachment/ticket/223/fas-summer-c...
(jflory7, 16:01:01)
* LINK: https://fedorahosted.org/fedora-badges/ticket/303#comment:8
(jflory7, 16:28:09)
* LINK: https://fedorahosted.org/fedora-badges/ticket/443#comment:1
(jflory7, 16:30:45)
* LINK: https://fedorahosted.org/fedora-badges/ticket/416#comment:11
(jflory7, 16:44:21)
* LINK: https://fedorahosted.org/fedora-badges/ticket/415#comment:4
(jflory7, 16:46:49)
* LINK: https://fedorahosted.org/fedora-badges/ticket/407#comment:10
(jflory7, 16:54:10)
* ACTION: jflory7 Update Ticket #34 in CommOps Trac with new
information (jflory7, 16:55:42)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:55:45)
Meeting ended at 16:55:49 UTC.
Action Items
------------
* jflory7 Update Ticket #34 in CommOps Trac with new information
Action Items, by person
-----------------------
* jflory7
* jflory7 Update Ticket #34 in CommOps Trac with new information
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (70)
* zodbot (11)
* meskarune (8)
* bee2502 (5)
* devyani7 (4)
* decause (4)
* williamjmorenor (3)
* sayan (2)
* kushal (1)
* linuxmodder (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 11 months
