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
New Guy Introduction
by Drew Meigs
Hi, everyone. I am new to this community and wanted to take a minute to
introduce myself. My name is Drew and I have used Linux off and on for
about eight years or so. My background is in Debian-based systems, but I
think I am quickly getting the hang of Fedora. I am looking forward to
working with this community, as I feel like this is really what I was
missing when I was trying to get involved with Debian.
Though I am not as technically-minded as the developers, my background
is in IT and I (at one point) taught people to use their software. So
while I may never be skilled enough to volunteer with the packagers and
other developers, I feel I can still bring something to this community.
I have the ability to take complicated tasks and break them down into
either more manageable tasks or instructions for those who don't
understand the initial information.
With that being said, I feel like I could be an asset on this team. I am
willing to give pretty much every aspect a try, but what I really like
at face value is the idea of the hubs, the wiki and anything that has to
do with the "internal communications" section of the wiki page. I would
like to help bring the community together in any way that I can.
I look forward to working with you all,
Drew
IRC: rmeigs
FAS: rmeigs
7 years, 11 months
Would like to join the team
by Tim Apple
Hello,
I have been around Linux for many years, mainly as an enthusiest. I
come from the .deb side of the world and I'm new to Fedora.
I am very interested in becoming an active member of the community and
I think Ambassadorship and CommOps may be a good place to start since I
don't code and am unfamiliar with packaging for now.
I spend a lot of time on social media and tracking news. I am also very
interested to gaining in depth knowledge of how to navigate through all
things Fedora. So helping others and sharing seems like a good start.
Basically, learn and then pass it on.
Either way, I am eager to get involved. I may not be the speediest on
replies for now.. I have 4 kids with one being 2 weeks old. But I will
be in IRC, tracking the forums and listening for anything else when I
have the time.
Again, looking foreward to being useful.
Cheers,
Tim Apple
On IRC: LinuxHippie
On FAS: linuxhippie
7 years, 11 months
Self Introduction: Dhanesh Sabane [dhanesh95, UTC +5:30]
by Dhanesh B. Sabane
Hello CommOps!
I am Dhanesh Sabane from Maharashtra, India. I am a Computer Science student and next year will be my last year of the degree course. I was exposed to the world of Fedora last year around September. I was greatly influenced by the notion of Open Source when I first started using Fedora on my college PCs a couple of years ago. The journey has now brought me to the contribution pathways and CommOps seems like the way to begin with some *real* contributions. I'm also trying my hands at RPM Packaging and soon you may well soon see me as an established RPM packager. :P
I observed CommOps for a couple of weeks and then just happened to drop by for the team meeting of this week(Yesterday, as per my time zone). The meeting was quite an experience for me and I was assigned a job too. I'll be working on [1] with Harshal Bhatia (justharshal). Now I know you must be thinking that I've got the whole joining process backwards. And yes, you're right. Guilty as charged. :P
Anyway, that is all about me. I haven't yet decided which sub-project to work on. But I will, soon.
TL;DR
Name: Dhanesh Sabane
State, Country: Maharashtra, India
Timezone: UTC +5:30
Occupation: Student
Nick: dhanesh95
Contribution areas: CommOps, Devel (RPM Packaging)
[1] https://fedorahosted.org/fedora-commops/ticket/68
7 years, 12 months
Re: Test Day report: 2016-04-12 i18n Test Day
by Remy DeCausemaker
On Wed, Apr 20, 2016 at 6:33 PM, Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
> Hey folks! Just some quick news on the i18n Test Day from last week. We
> had a great response - big thanks to everyone who came out and helped
> test! The IRC channel was busy, and the i18n team did a great job of
> helping people out. Here are the statistics:
>
> Testers: 12, Tests: 66, Bugs: 3, Ratio: 0.25
> Open: 2, Dupe: 1, Fixed: 0, Unfixed: 0, Fixed %: 0.0
>
> It's not unusual for the bugs not to be fixed yet, of course, but 12
> testers running 66 tests is great! Thanks everyone :)
Adam,
Excellent news!
CommOps just helped the g11n team promote their testing week on the
CommBlog (post forthcoming tomorrow morning) and I wonder if we can
help i18n similarly next time? We should def talk more about how
CommOps can help get more folks involved next time via Blog post as
least, if not a vFAD with badges, or some other way we haven't thought
of yet.
Looking Forward,
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
7 years, 12 months
GSoC 2016 article scheduled
by Justin W. Flory
Hello all,
On Tuesday's meeting, we discussed publishing the GSoC "Class of 2016"
article. Remy mentioned that we should add URLs to info pages for each
applicant. I added the links to the article, and I've scheduled the
article for 8:45 UTC on 2016-04-27 while this content is still fresh. I
scheduled it a little bit after the Magazine article coming out near the
same time.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 12 months
F24 Beta Release Notes (coming next week)
by Justin W. Flory
Hello all,
Before going further, please note this is a cross-posted thread! There
is a low-traffic mailing list, logistics(a)lists.fedoraproject.org, which
was created for multi-list collaboration on things like this topic. To
centralize discussion, please consider using that list for replies (even
if you unsubscribe after the discussion finishes).
Anyways, assuming all goes according to plan, the F24 Beta is due to
land on May 3rd, or in seven days from today. Therefore, it's time to
review and look over the release notes for the F24 Beta. The current
draft can be found on the wiki.
https://fedoraproject.org/wiki/F24_Beta_release_announcement
As of now, it is a forked version of the Alpha release announcement with
a few changes based on information I gathered from #fedora-qa. If you
could take some time to review the release notes and ensure everything
is *current* and correct since the Alpha release for areas you are
familiar and knowledgeable with, that would be appreciated so we can aim
to ship this next week.
Thanks all!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 12 months
CommOps Weekly Meeting Recap 2016-04-26
by Justin W. Flory
Sorry for the delay in getting these out – I wasn't around for the end
of the meeting!
===
Meeting ended Tue Apr 26 17:56:28 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-04-26)
============================================
Meeting started by jflory7 at 15:57:09 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:57:23)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-04-26
(jflory7, 15:57:28)
* (1) Roll Call / Q&A (jflory7, 15:57:34)
* (2) Announcements (jflory7, 15:57:39)
* (3) Action items from last meeting (jflory7, 15:57:43)
* (4) Tickets (jflory7, 15:57:49)
* (5) Wiki Gardening (jflory7, 15:57:55)
* (6) Community Blog (jflory7, 15:58:01)
* (7) Release Schedule (jflory7, 15:58:07)
* (8) Open Floor (jflory7, 15:58:12)
* Roll Call / Q&A (jflory7, 15:58:22)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:58:24)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Join, and more (jflory7, 15:58:50)
* Dan Mossor, GMT-6, CommOps/Ambassadors/CampusAmbassadors/Server/KDE
(danofsatx, 15:59:15)
* Sachin S. Kamath; UTC+5.30; CommOps, Ambassadors, Security
(skamath, 16:00:23)
* Brian Proffitt, GMT-4, social media (bkp, 16:01:05)
* Tummala Dhanvi ; UTC+5:30 : CommOps , Security , Docs , * (c0mrad3,
16:01:50)
* Wesley Otugo, GMT +1, Goto Guy (wesleyotugo, 16:02:06)
* Corey Sheldon UTC-5(Us/EDT) Commops ,
Securityteam,Docs,Join,mktg,Social * (linuxmodder, 16:03:13)
* rilly good things are happening in Hubs land (decause, 16:03:33)
* decause; UTC-4; CommOps, Council, Hubs, Badges, * (decause,
16:04:05)
* Announcements (jflory7, 16:07:51)
* === "Introducing the extra wallpapers for Fedora 24" === (jflory7,
16:07:52)
* LINK:
https://fedoramagazine.org/introducing-extra-wallpapers-fedora-24/
(jflory7, 16:07:58)
* Sayan Chowdhury; UTC+5:30; CommOps, Magazine, Ambassadors, Marketing
(sayan, 16:07:58)
* The people have spoken! The supplementary wallpapers for Fedora 24
are now official. You can see what beautiful scenery is coming soon
to desktops near you in the next release of Fedora. (jflory7,
16:08:03)
* === "Fedora translation sprint – 5 days, 50 members and 20+ thousand
words" === (jflory7, 16:08:10)
* LINK:
https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-...
(jflory7, 16:08:16)
* The Fedora Globalization group ran a 5-day virtual translation
sprint to focus on the translation of important GUI packages. During
the 5 day sprint, 53 contributors translated 22,723 words to over 18
different languages. Learn more about the awesome work done by the
G11n team in the Community Blog article! (jflory7, 16:08:26)
* === Ticket #29 closed === (jflory7, 16:08:32)
* LINK: https://fedorahosted.org/fedora-commops/ticket/29 (jflory7,
16:08:39)
* Ticket #29, "G11n - proposal for the group revitalization", is now
marked as closed. With the publication of the above event report,
this was the last action item identified to close out this ticket.
Awesome work to everyone involved! (jflory7, 16:08:52)
* === Fedora 24 Beta Release Readiness Meeting, Thursday, April 28
19:00 UTC === (jflory7, 16:09:00)
* Mark Terranova Northern California, Ambadassadors, Community,
Videos, mktg, penguins (MarkDude, 16:09:05)
* LINK:
https://lists.fedoraproject.org/archives/list/logistics@lists.fedoraproje...
(jflory7, 16:09:11)
* Before each public release all of the groups participating in the
development of Fedora's next release meet to make sure the release
is well coordinated. This meeting is called the: Release Readiness
Meeting. The Release Readiness Meeting is held after after the
Go/No-Go Meeting that is held for each public release. CommOpsers
are welcome to attend! (jflory7, 16:09:14)
* if you want to be involved in the Community Bonding for the incoming
interns, or are an incoming intern, please join us in #fedora-hubs
at 14:00UTC tomorrow. (decause, 16:11:10)
* GSoC final selections have been made public (decause, 16:14:36)
* Action items from last meeting (jflory7, 16:15:11)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-19/commops.2016-...
(jflory7, 16:15:17)
* How This Works: We look at past #action items from the last meeting
for quick follow-up. If a task is completed, we move on to the next
one. If it isn't, we get an update and re-action it if needed. If no
status, we'll try to get a quick update and move forward. (jflory7,
16:15:23)
* === decause complete limesurvey account creation process ===
(jflory7, 16:15:30)
* ACTION: decause fill up the LimeSurvey account with $$$ (decause,
16:16:52)
* === [IN PROGRESS] decause Work on migrating the raw University
Involvement Initiative notes from the Etherpad into a more
parseable, digestible format (whether wiki or other format) ===
(jflory7, 16:17:04)
* AGREED: This action item is now Ticket #68. We will revisit this
item later on in the meeting during ticket discussion. (jflory7,
16:17:10)
* === [IN PROGRESS] jflory7 Continue writing and compiling project
profiles of BrickHack 2016 participants (three replies so far, need
to keep communication channels open) === (jflory7, 16:17:15)
* ACTION: jflory7 Continue writing and compiling project profiles of
BrickHack 2016 participants (jflory7, 16:17:21)
* === [INCOMPLETE] decause / jflory7 Ping Marketing mailing list about
Alpha to Beta release announcement research for May 3rd ===
(jflory7, 16:17:27)
* ACTION: decause / jflory7 Ping Marketing mailing list about Alpha to
Beta release announcement research for May 3rd (jflory7, 16:17:39)
* === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack
session to share with CommOps and Design team === (jflory7,
16:18:06)
* ACTION: jflory7 Create a WhenIsGood poll for a badges hack session
to share with CommOps and Design team (jflory7, 16:18:16)
* === [IN PROGRESS] decause / jflory7 Explore how to subscribe the
social-media mailing list to the RSS feed of Community Blog ===
(jflory7, 16:18:25)
* ACTION: decause / jflory7 Explore how to subscribe the social-media
mailing list to the RSS feed of Community Blog (jflory7, 16:18:32)
* === [COMPLETE] jflory7 Upload the local Albanian F24 translation
sprint group photo to the G11n vFAD article on the Community Blog
=== (jflory7, 16:18:39)
* LINK:
https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-...
(jflory7, 16:18:45)
* === [IN PROGRESS] justharshal / dhanesh95 Work on moving the
Etherpad notes into a more readable format on the University
Involvement Initiative wiki page; after converting it, send to
CommOps mailing list for feedback and review === (jflory7,
16:18:52)
* AGREED: This action item is now Ticket #68. We will revisit this
item later on in the meeting during ticket discussion. (jflory7,
16:18:59)
* === [INCOMPLETE] commops / jflory7 Create tickets for the above
items 1-3 so they can be assigned and broken up among CommOps
members === (jflory7, 16:19:07)
* ACTION: commops / jflory7 Create tickets for items 1-3 from Ticket
#69 so they can be assigned and broken up among CommOps members
(jflory7, 16:19:29)
* === [COMPLETE] jflory7 Review and edit "Fedora translation sprint"
article for publication on Thursday, if possible === (jflory7,
16:19:36)
* LINK:
https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-...
(jflory7, 16:19:42)
* === [INCOMPLETE] jflory7 Ship the "Fedora Media Writer" article
ASAP, contact author about dropping a link on the CommOps mailing
list next time so we don't wind up last minute === (jflory7,
16:19:47)
* This deadline was missed, was not published the day of the event :(
(jflory7, 16:19:52)
* Tickets (jflory7, 16:20:06)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7,
16:20:11)
* === Ticket #34, 49 === (jflory7, 16:20:20)
* #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 16:20:27)
* #49: "[Onboarding Series] Infrastructure" (jflory7, 16:20:33)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:20:37)
* LINK: https://fedorahosted.org/fedora-commops/ticket/49 (jflory7,
16:20:42)
* CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs
Team Badges Tracks and Widgets (decause, 16:21:45)
* ACTION: CommOps solidify onboarding steps before 5/23 internships
begin (decause, 16:22:37)
* folks who want to be involved with this workflow please join us tomo
at 14:00UTC in #fedora-hubs (decause, 16:23:37)
* === Ticket #68 === (jflory7, 16:24:23)
* "Reconstructing the Campus Ambassadors program and campus outreach"
(jflory7, 16:24:24)
* LINK: https://fedorahosted.org/fedora-commops/ticket/68 (jflory7,
16:24:30)
* LINK: http://etherpad.osuosl.org/fedora-EDU-refresh (jflory7,
16:24:36)
* LINK:
https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
(jflory7, 16:24:43)
* LINK:
https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiati...
(jflory7, 16:24:49)
* ACTION: decause talk to spot about scheduling an EDU fad after
budget gets settled (decause, 16:26:54)
* AGREED: justharshal and dhanesh95 are still working on this ticket
but neither of them are present in today's meeting. We will check in
on the status of this with them over the next week either in channel
or on the mailing list. (jflory7, 16:27:56)
* === Ticket #69 === (jflory7, 16:28:09)
* "Fedora Modularity onboarding" (jflory7, 16:28:14)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69 (jflory7,
16:28:21)
* (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 (jflory7, 16:28:30)
* (2) Putting together a badge proposal for membership in the
Modularity WG (in the form of a ticket on the fedora-badges Trac)
(jflory7, 16:28:37)
* (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) (jflory7, 16:28:45)
* AGREED: jflory7 will file the smaller tickets for this one this
week. We will work on the specific targets in the next hack session
we plan. (jflory7, 16:34:05)
* === Ticket #70 === (jflory7, 16:34:26)
* "FOSS Student Pack" (jflory7, 16:34:31)
* LINK: https://fedorahosted.org/fedora-commops/ticket/70 (jflory7,
16:34:37)
* 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 (jflory7, 16:37:41)
* === Ticket #71 === (jflory7, 16:41:14)
* "Centralizing Ambassadors / Events resources and utilities"
(jflory7, 16:41:15)
* LINK: https://fedorahosted.org/fedora-commops/ticket/71 (jflory7,
16:41:18)
* ACTION: jflory7 Open discussion on the mailing list about Ticket #71
and centralizing Ambassador resources (to get brainstorming going)
(jflory7, 16:46:57)
* LINK: https://fedorahosted.org/fedora-commops/ticket/72 besides,
LATAM and EMEA, Im sure there might be other meeting logs/times not
current on the wiki. The "fixing process" could help other parts of
Communities in Fedora. Automation via Fed-msg (MarkDude, 16:47:24)
* Community Blog (jflory7, 16:47:40)
* How This Works: There is a quick blast of information about what was
published in the past week with some metrics, followed by posts that
are being drafted. After the information blast, the floor is opened
for any Community Blog-related discussion. Here we go! (jflory7,
16:47:46)
* === This week in CommBlog === (jflory7, 16:47:51)
* (1) "Fedora translation sprint – 5 days, 50 members and 20+ thousand
words" (jflory7, 16:47:56)
* LINK:
https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-...
(jflory7, 16:48:00)
* Total Views (Apr. 21 - Apr. 25): 406 (jflory7, 16:48:05)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 16:48:10)
* === Coming up in CommBlog === (jflory7, 16:48:14)
* (1) "DevConfCZ 2016: Event Report" (jflory7, 16:48:19)
* LINK:
https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=6b95d2c034
(jflory7, 16:48:24)
* (2) "Announcing Fedora Google Summer of Code (GSoC) Class of 2016"
(jflory7, 16:48:31)
* LINK:
https://communityblog.fedoraproject.org/?p=1477&preview=1&_ppp=1693dddaff
(jflory7, 16:48:37)
* (3) "Fedora's Love For Python Continues" (jflory7, 16:48:43)
* LINK:
https://communityblog.fedoraproject.org/?p=1470&preview=1&_ppp=8324c1b68a
(jflory7, 16:48:48)
* (4) "Fedora at Bitcamp 2016" (jflory7, 16:48:53)
* ACTION: jflory7 Write Bitcamp 2016 article on CommBlog and point to
individual event reports by other Ambassadors (jflory7, 16:49:03)
* IDEA: Maybe the CommBlog would be better suited to have its own
separate meeting time slot, even if just a 30 minute meeting
(jflory7, 16:49:23)
* Release Schedule (jflory7, 16:50:59)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(jflory7, 16:51:00)
* Open Floor (jflory7, 16:51:07)
* LINK: https://fedorahosted.org/fedora-commops/ticket/72 besides,
LATAM and EMEA, Im sure there might be other meeting logs/times not
current on the wiki. The "fixing process" could help other parts of
Communities in Fedora. Automation via Fed-msg (MarkDude, 16:51:18)
* LINK: https://fedoraproject.org/wiki/Ambassadors_meetings
(MarkDude, 16:54:12)
* LINK: https://fedoraproject.org/wiki/Ambassadors_meetings
(MarkDude, 16:55:14)
* ACTION: decause let skamath know they can use #action to self-assign
tasks (decause, 16:58:17)
* ACTION: skamath help with gardening of Summer Coding wiki (skamath,
16:59:12)
* jflory7 is going to be getting into the final parts of his semester
soon and will not be as active as normal in coming weeks (jflory7,
17:03:00)
* LINK:
https://blog.slock.it/a-primer-to-the-decentralized-autonomous-organizati...
Decentralized Orgs :) (MarkDude, 17:51:39)
Meeting ended at 17:56:28 UTC.
Action Items
------------
* decause fill up the LimeSurvey account with $$$
* jflory7 Continue writing and compiling project profiles of BrickHack
2016 participants
* decause / jflory7 Ping Marketing mailing list about Alpha to Beta
release announcement research for May 3rd
* jflory7 Create a WhenIsGood poll for a badges hack session to share
with CommOps and Design team
* decause / jflory7 Explore how to subscribe the social-media mailing
list to the RSS feed of Community Blog
* commops / jflory7 Create tickets for items 1-3 from Ticket #69 so they
can be assigned and broken up among CommOps members
* CommOps solidify onboarding steps before 5/23 internships begin
* decause talk to spot about scheduling an EDU fad after budget gets
settled
* 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
* decause let skamath know they can use #action to self-assign tasks
* skamath help with gardening of Summer Coding wiki
Action Items, by person
-----------------------
* commops
* commops / jflory7 Create tickets for items 1-3 from Ticket #69 so
they can be assigned and broken up among CommOps members
* decause
* decause fill up the LimeSurvey account with $$$
* decause / jflory7 Ping Marketing mailing list about Alpha to Beta
release announcement research for May 3rd
* decause / jflory7 Explore how to subscribe the social-media mailing
list to the RSS feed of Community Blog
* decause talk to spot about scheduling an EDU fad after budget gets
settled
* decause let skamath know they can use #action to self-assign tasks
* jflory7
* jflory7 Continue writing and compiling project profiles of BrickHack
2016 participants
* decause / jflory7 Ping Marketing mailing list about Alpha to Beta
release announcement research for May 3rd
* jflory7 Create a WhenIsGood poll for a badges hack session to share
with CommOps and Design team
* decause / jflory7 Explore how to subscribe the social-media mailing
list to the RSS feed of Community Blog
* commops / jflory7 Create tickets for items 1-3 from Ticket #69 so
they can be assigned and broken up among CommOps members
* 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
* skamath
* decause let skamath know they can use #action to self-assign tasks
* skamath help with gardening of Summer Coding wiki
* **UNASSIGNED**
* CommOps solidify onboarding steps before 5/23 internships begin
People Present (lines said)
---------------------------
* decause (238)
* jflory7 (227)
* MarkDude (71)
* linuxmodder (66)
* skamath (40)
* zodbot (32)
* mailga (20)
* danofsatx (9)
* wesleyotugo (7)
* meskarune (7)
* misc (6)
* mizmo (4)
* trishnag (4)
* sayan (4)
* c0mrad3 (3)
* sgallagh (3)
* bkp (2)
* langdon (2)
* Southern_Gentlem (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, 12 months
