Fedora 26 Alpha Release Readiness Meeting on Thursday, March 16 @ 19:00 UTC
by Jan Kurik
Join us on irc.freenode.net in #fedora-meeting-2 for the Fedora 26
Alpha Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, March 16, 2017 at 19:00
UTC. Please check the [1] link for your time zone.
We will meet to make sure we are coordinated and ready for the Alpha
release of Fedora 26. Please note that this meeting is going to be
held even if the release is delayed at the Go/No-Go meeting on the
same day two hours earlier.
You may received this message several times, but it is by purpose to
open this meeting to the teams and to raise awareness, so hopefully
more team representatives will come to this meeting. This meeting
works best when we have representatives from all of the teams.
For more information please check the [2] link.
[1] https://apps.fedoraproject.org/calendar/meeting/5306/
[2] https://fedoraproject.org/wiki/Release_Readiness_Meetings
Thank you for your support,
Regards, Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
7 years, 1 month
#help: Need a chair for 2017-03-14
by Justin W. Flory
Hi all,
I will not be available to chair next week's meeting (2017-03-14) due to
personal travel. Is there anyone who would be able to help and chair
next week's meeting?
Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
[fedora-marketing] Issue #248 `Create a education-focused marketing campaign`
by Justin W. Flory
jflory7 reported a new issue against the project: `fedora-marketing` that you are following:
``
**Originally discussed in [2017-02-14 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/mark...
# Summary
Similar to the [Fedora <3 Python](https://fedoralovespython.org/) campaign, the Marketing Team should organize a campaign targeted towards an education type of audience (students, professors, faculty, teachers, etc.).
# Analysis
This was a long discussion in our meeting, and before summarizing it, it's important to have some context of other similar things where this has been discussed or has been focused on already.
* [Fedora Objective: University Involvement Initiative](https://fedoraproject.org/wiki/Objectives/University_Involvem...
* [Original EDU FAD 2016 plans](https://fedoraproject.org/wiki/FAD_EDU_2016)
* [EDU refresh - raw notes](http://etherpad.osuosl.org/fedora-EDU-refresh)
* [CommOps ticket 43: EDU Roster](https://pagure.io/fedora-commops/issue/43)
There's no easy way to summarize this one. But in short, we identified the unique success of the [Fedora <3 Python](https://fedoralovespython.org/) campaign in appealing to a unique niche of our broader audience of users. Ideally, we would like to craft a similar campaign that focuses more closely at a university / education type of audience.
### How to move forward
We established a strong interest and some general directions for how to proceed for this, but we will want to establish some sort of planning milestones and also circulate this idea with other groups. This would make a good candidate for something to share our more complete thoughts with the Fedora Council with, as per ticket #246, to get their input and feedback.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/248
7 years, 1 month
[Minutes] [2017-03-07] Talking points for F26, EDU campaign milestones
by Justin W. Flory
Hey all,
The weekly Marketing meeting just wrapped up. It was only me and Eduard
today, but we mostly focused on getting ready for the talking points in
two weeks and to begin expanding on milestones for the EDU campaign
ticket (that we hope to present to the Council in the State of Marketing
session).
Full minutes and logs are available below! See you all in channel or on
the list.
= = = = =
Meeting ended Tue Mar 7 14:59:27 2017 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-03-07/marketing.201...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-03-07/marketing.201...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-03-07/marketing.201...
* * * * *
======================================================
#fedora-meeting: Fedora Marketing meeting (2017-03-07)
======================================================
Meeting started by jwf at 14:00:00 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-03-07/marketing.201...
.
Meeting summary
---------------
* Agenda (jwf, 14:00:11)
* LINK:
https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-03-07
(jwf, 14:00:15)
* (1) Roll call (jwf, 14:00:20)
* (2) Announcements (jwf, 14:00:24)
* (3) Action items from last meeting (jwf, 14:00:29)
* (4) Tickets (jwf, 14:00:32)
* (5) Upcoming tasks (jwf, 14:00:37)
* (6) Open floor (jwf, 14:00:41)
* Roll call (jwf, 14:00:50)
* Name; Timezone; Other sub-projects / interest areas (jwf, 14:00:51)
* Justin W. Flory; UTC+1; CommOps, Marketing, Magazine, Ambassadors,
Diversity Team, sysadmin-badges, and more… (jwf, 14:01:14)
* Eduard Lucena; UTC-4; Magazine,Marketing,Ambassadors,Join and
starting with infra (x3mboy, 14:01:51)
* Announcements (jwf, 14:04:47)
* No new weekly news coverage on jflory7's radar… (jwf, 14:04:55)
* === "fedorahosted.org retired today (2017-03-01)" === (jwf,
14:05:01)
* LINK:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
(jwf, 14:05:06)
* FedoraHosted.org was officially retired last week. All projects are
either defunct or have migrated to Pagure (or elsewhere). (jwf,
14:05:12)
* Action items from last meetings (jwf, 14:06:58)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.201...
(jwf, 14:07:03)
* 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. (jwf,
14:07:10)
* === FranciscoD / bkp Discuss and draft a short proposal of what
one-page release announcements looks like for the press kit, with
(1) timeline for when they should be created during the release, (2)
type of content to include in the announcement, and (3) how it
should be delivered === (jwf, 14:07:15)
* ACTION: FranciscoD / bkp Discuss and draft a short proposal of what
one-page release announcements looks like for the press kit, with
(1) timeline for when they should be created during the release, (2)
type of content to include in the announcement, and (3) how it
should be delivered (jwf, 14:08:37)
* === [COMPLETE] jwf Draft a simple proposal for what background
modules / past press coverage should be in the press kit, add
comment to ticket #242 for discussion at next meeting === (jwf,
14:08:50)
* LINK: https://pagure.io/fedora-marketing/issue/242#comment-428896
(jwf, 14:08:56)
* Tickets (jwf, 14:09:19)
* LINK: https://pagure.io/fedora-marketing/issues?tags=meeting (jwf,
14:09:23)
* === Ticket #242: "Update release activity steps / process on the
wiki" === (jwf, 14:09:28)
* LINK: https://pagure.io/fedora-marketing/issue/242 (jwf, 14:09:32)
* AGREED: This ticket still needs input from FranciscoD and bkp. Along
with impending deadlines for talking points and State of Fedora
Marketing presentation, we will revisit this ticket after the Alpha
release on March 21st. (jwf, 14:11:16)
* === Ticket #245: "Create Fedora 26 talking points" === (jwf,
14:11:24)
* LINK: https://pagure.io/fedora-marketing/issue/245 (jwf, 14:11:28)
* AGREED: Will separate this ticket into two pieces – a new ticket for
the "vision" or long-term task of creating our talking points
(described in past meetings as release notes) into audiences, and
then focus our efforts over the next two weeks on F26 Talking Points
in the same way as usual (jwf, 14:14:36)
* ACTION: jwf Separate #245 into a new ticket for the long-term vision
of audience-based TPs (jwf, 14:15:00)
* LINK: https://fedoraproject.org/wiki/Fedora_26_talking_points
(jwf, 14:15:41)
* LINK: https://fedoraproject.org/wiki/Fedora_25_talking_points
(jwf, 14:16:30)
* === Ticket #248: "Create an education-focused marketing campaign"
=== (jwf, 14:25:46)
* LINK: https://pagure.io/fedora-marketing/issue/248 (jwf, 14:25:52)
* AGREED: To better focus our resources towards developing and
building this campaign, we want to start with a smaller, similar
audience that could be expanded later. We first narrowed the scope
to "university" and then to "students". (jwf, 14:39:28)
* ** Three first milestones to building this campaign ** (jwf,
14:39:31)
* IDEA: (1) Build a "roster" of Fedora contributors involved at
universities across the world (updating the list we have already)
(jwf, 14:40:11)
* LINK:
https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiati...
(jwf, 14:40:12)
* IDEA: (2) Build university-focused "talking points" useful for
Fedora contributors to introduce Fedora (and possibly wider concepts
like Linux and open source) to students (jwf, 14:41:15)
* IDEA: (3) From the points, begin creating resources (e.g. logos,
brochures / flyers, etc.) based on the talking points to highlight
strong parts and make it easier to get a message across (jwf,
14:42:12)
* Upcoming Tasks (jwf, 14:46:20)
* LINK:
https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
(jwf, 14:46:24)
* (1) Change Checkpoint: Completion deadline (Tue 2017-02-28) (jwf,
14:46:28)
* (2) Create Talking Points (start: Tue 2017-02-28) (jwf, 14:46:34)
* (3) Proposed Changes Profiles (start: Tue 2017-03-07) (jwf,
14:46:38)
* (4) Email WGs to solicit bullet points for Alpha release
announcement (start: Thu 2017-03-09) (jwf, 14:46:43)
* Open Floor (jwf, 14:46:47)
* ACTION: jsandys For Design Team ticket #502, add a screenshot of the
placeholder for the website and clarify what the deliverable should
be (is it HTML/CSS files sent to the organizers? is it a graphic?
etc.) (jwf, 14:56:59)
Meeting ended at 14:59:27 UTC.
Action Items
------------
* FranciscoD / bkp Discuss and draft a short proposal of what one-page
release announcements looks like for the press kit, with (1) timeline
for when they should be created during the release, (2) type of
content to include in the announcement, and (3) how it should be
delivered
* jwf Separate #245 into a new ticket for the long-term vision of
audience-based TPs
* jsandys For Design Team ticket #502, add a screenshot of the
placeholder for the website and clarify what the deliverable should be
(is it HTML/CSS files sent to the organizers? is it a graphic? etc.)
Action Items, by person
-----------------------
* bkp
* FranciscoD / bkp Discuss and draft a short proposal of what one-page
release announcements looks like for the press kit, with (1)
timeline for when they should be created during the release, (2)
type of content to include in the announcement, and (3) how it
should be delivered
* FranciscoD
* FranciscoD / bkp Discuss and draft a short proposal of what one-page
release announcements looks like for the press kit, with (1)
timeline for when they should be created during the release, (2)
type of content to include in the announcement, and (3) how it
should be delivered
* jsandys
* jsandys For Design Team ticket #502, add a screenshot of the
placeholder for the website and clarify what the deliverable should
be (is it HTML/CSS files sent to the organizers? is it a graphic?
etc.)
* jwf
* jwf Separate #245 into a new ticket for the long-term vision of
audience-based TPs
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (148)
* x3mboy (46)
* jsandys (11)
* zodbot (8)
* Rhea (4)
* mizmo (3)
* FranciscoD (0)
* bkp (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
[fedora-marketing] Issue #242 `Update release activity steps / process on the wiki`
by Justin W. Flory
jflory7 added a new comment to an issue you are following:
``
**Discussed in [2017-02-28 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/mark...
To break up what this press kit looks like, we tasked a few people to write a simple description or idea of what these things look like into this ticket. Then, we can port this over to a wiki page later and also try working on the first version to include in our press kit for this release. @ankursinha and @bproffit were going to discuss one-page release announcement, and @ankursinha was going to leave a comment answering questions about:
1. Timeline for when to be created during the release (being mindful of Fedora Docs team timeline)
2. General content to include or focus on in the announcement
3. How and where it should be delivered
My action was for background modules and past press coverage, which I have below. Note that these are suggestions that we will discuss and vote on at our next meeting.
## Background modules
* **What?**: General info about Fedora / Fedora community such as project metrics about technical and community components (similar to [State of Fedora talk](https://mattdm.org/fedora/2016flock/StateofFedoraAugust2016-v160731...)
* **Time to complete**: Created once, updated every key event
I see this information being most helpful for outward sources reporting on the Fedora Project. This would consist of news sites, media outlets, other Linux newsy sites, etc. Ideally, this information would be compiled once, and then along with each annual update, the numbers would be adjusted and updated as needed. This would likely be around Flock, when the FPL gives the State of Fedora talk.
Therefore, I see this best being a Markdown file in the press kit that we could convert to a PDF for delivery or sharing with media sites. We could communicate this somewhere between Beta and GA.
## Past press coverage
* **What?**: Short document with list of all news outlets / sites reporting on Fedora sorted by release
* **Time to complete**: Updated every meeting / reviewed at every release milestone
To me, it's unclear whether this is best used internally or externally. Clarifying this would be helpful to understand what we want to do for generating this document and how we deliver it. However, since we're already doing this roughly every meeting with the "_In the news_" announcements, it would be easy enough to sort this data from the meeting logs into a Markdown file inside of the press kit repository. We could do whatever we want with it after.
I definitely want to understand better why this document is important or what its role in a press kit would be. Is it helpful for other news outlets to see what other sites are writing about Fedora? Could this potentially bias them (positively or negatively)? An experienced marketeer's opinion would be helpful here. :grinning:
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/242
7 years, 1 month
