Hey all! This week's meeting just came to a close, although we are still
continuing in #fedora-mktg. We mostly focused on building / generating
our press kits and what that will like (in terms of what we're including
and how it would fit into our release schedule) along with our talking
points (although we're more or less discussing this part in channel now).

Thanks everyone for participating, see you in channel or at next week's
meeting!

= = = = =

Meeting ended Tue Feb 28 15:02:19 2017 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.log.html

* * * * *

======================================================
#fedora-meeting: Fedora Marketing meeting (2017-02-28)
======================================================


Meeting started by jwf at 14:00:03 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.log.html
.



Meeting summary
---------------
* Agenda  (jwf, 14:00:13)
  * LINK:
    https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-02-28
    (jwf, 14:00:17)
  * (1) Roll call  (jwf, 14:00:22)
  * (2) Announcements  (jwf, 14:00:25)
  * (3) Action items from last meeting  (jwf, 14:00:29)
  * (4) Tickets  (jwf, 14:00:33)
  * (5) Upcoming tasks  (jwf, 14:00:37)
  * (6) Open floor  (jwf, 14:00:41)

* Roll call  (jwf, 14:00:45)
  * Name; Timezone; Other sub-projects / interest areas  (jwf, 14:00:49)
  * Justin W. Flory; UTC+1; CommOps, Marketing, Magazine, Ambassadors,
    Diversity Team, sysadmin-badges, and moreā€¦  (jwf, 14:01:08)
  * Eduard Lucena; UTC-4; Magazine, Ambassador, Join, Hubs, Workstation
    (x3mboy, 14:01:13)
  * Ankur Sinha (FranciscoD): UTC; Join, Packaging (and wherever else I
    can help out)  (FranciscoD, 14:01:29)

* Announcements  (jwf, 14:05:16)
  * === In the news: "Fedora Linux Distro to No Longer Offer Alpha
    Builds Starting with Fedora 27" ===  (jwf, 14:05:39)
  * LINK:

http://news.softpedia.com/news/fedora-linux-distro-to-no-longer-offer-alpha-builds-starting-with-fedora-27-513252.shtml
    (jwf, 14:05:44)
  * While it's not true that this is finalized, there is a current
    change proposal to drop Alpha releases from the release cycles of
    Fedora starting in Fedora 27. You can read more information at the
    Change wiki page.  (jwf, 14:05:49)
  * LINK: https://fedoraproject.org/wiki/Changes/NoMoreAlpha   (jwf,
    14:05:54)
  * === In the news: "Fedora 26 Linux Has Been Delayed by a Week, Should
    Now Land on June 13, 2017" ===  (jwf, 14:06:29)
  * LINK:

http://linux.softpedia.com/blog/fedora-26-linux-has-been-delayed-by-a-week-should-now-land-on-june-13-2017-513250.shtml
    (jwf, 14:06:35)
  * Normal coverage about the week delay from no/no-go discussions.
    Article doesn't take strong stance. New release date on 2017-06-13.
    (jwf, 14:06:41)
  * === "Hello, Modern Paste!" ===  (jwf, 14:09:06)
  * LINK: https://fedoramagazine.org/hello-modern-paste/   (jwf,
    14:09:26)
  * Fedora Infrastructure officially migrated our old pastebin service
    to a more modern and clean paste site. You can read more info in the
    article on the Fedora Magazine.  (jwf, 14:10:00)

* Action items from last meetings  (jwf, 14:11:35)
  * LINK:

https://meetbot.fedoraproject.org/teams/marketing/marketing.2017-02-21-13.59.html
    (jwf, 14:11: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.  (jwf,
    14:11:53)
  * === [COMPLETE] jwf Start mailing list thread about using a git forge
    for maintaining and creating a press kit for our release cycle
    activities ===  (jwf, 14:12:02)
  * LINK:

https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/LWFDXEVAM6F4PUJNRIA3263ICAOF35KG/
    (jwf, 14:12:07)

* Tickets  (jwf, 14:12:29)
  * LINK: https://pagure.io/fedora-marketing/issues?tags=meeting   (jwf,
    14:12:35)
  * === Ticket #242: "Update release activity steps / process on the
    wiki" ===  (jwf, 14:12:40)
  * LINK: https://pagure.io/fedora-marketing/issue/242   (jwf, 14:12:44)
  * Left off with discussion about git forge and what should be included
    in the press kit. Can make a quick decision on where we want to host
    this, then focus more on the content that we wanted to put in there
    and how we want to start building it.  (jwf, 14:12:50)
  * LINK:

https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/LWFDXEVAM6F4PUJNRIA3263ICAOF35KG/
    (jwf, 14:12:56)
  * AGREED: Marketing team will host press kit in Pagure (which *does*
    have a web editor!) and use Markdown as default markup language,
    which will also fit into our existing workflow with other repos we
    have on Pagure  (jwf, 14:31:29)
  * What's in a press kit? We suggested: one-page release notes,
    background modules (general Fedora info), feature modules (specific
    to releases), past press coverage, targeted brochures / flyers
    (jwf, 14:32:48)
  * 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:50:03)
  * ACTION: 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:51:31)
  * === Ticket #245: "Create Fedora 26 talking points" ===  (jwf,
    14:51:54)
  * LINK: https://pagure.io/fedora-marketing/issue/245   (jwf, 14:51:58)
  * Talking points officially start today, now that the change window is
    closed for Fedora 26. We're still awaiting feedback from the
    Council, but we try starting with the raw data that is on the
    existing talking points page and try to organize that in a way that
    we can work with? We can also try to task outreach to different WGs
    / SIGs, but this depends on if we want to collect information by
    technical grouping or by audience.  (jwf, 14:52:03)
  * LINK: https://fedoraproject.org/wiki/Fedora_26_talking_points
    (jwf, 14:52:35)

* Upcoming Tasks  (jwf, 15:01:46)
  * LINK:
    https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
    (jwf, 15:01:46)
  * (1) Change Checkpoint: Completion deadline (Tue 2017-02-28)  (jwf,
    15:01:51)
  * (2) Create Talking Points (start: Tue 2017-02-28)  (jwf, 15:01:55)
  * (3) Proposed Changes Profiles (start: Tue 2017-03-07)  (jwf,
    15:01:59)
  * (4) Email WGs to solicit bullet points for Alpha release
    announcement (start: Thu 2017-03-09)  (jwf, 15:02:05)

* Open floor - skipping since we're over time, heading to #fedora-mktg
  (jwf, 15:02:17)

Meeting ended at 15:02:19 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 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




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
* jwf
  * 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
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* jwf (167)
* FranciscoD (66)
* x3mboy (28)
* dhanesh95 (25)
* bkp (20)
* bexelbie (17)
* zodbot (14)
* pingou (2)
* Rhea (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
Cheers,
Justin W. Flory
jflo...@gmail.com

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Fedora Marketing mailing list -- marketing@lists.fedoraproject.org
To unsubscribe send an email to marketing-le...@lists.fedoraproject.org

Reply via email to