Hi,
at last year's Flock I announced Fedora Handbook (a "getting started
with Fedora" guide that is printed and can be give away at event etc.).
Because it was created in the Czech community, the original is in
Czech. The handbook was very successful at Czech events, so we
translated it to English, so that it could be used abroad and
translated to other languages.
We have initial English translation, but it's rough and it needs a lot
of proofreading and rewriting which is something that needs to be done
by a native speaker.
It's written in AsciiDoc, easily readable and editable format: https://
github.com/lukaskotek/fedora-handbook-doc
Any volunteer to help? It'd be great to have it finished and printed
for Flock 2016. All I need is final text, we'll take care of
typesetting and printing.
Jiri
#226: Screenshots for Fedora 24
----------------------------------+------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 24
Component: Release deliverables | Severity: urgent
Keywords: meeting | Blocked By:
Blocking: |
----------------------------------+------------------------
= Phenomenon =
'''Discussed in [https://meetbot.fedoraproject.org/fedora-
meeting-1/2016-05-18/marketing.2016-05-18-20.55.html 2016-05-18 meeting].
In the [https://fedorapeople.org/groups/schedule/f-24/f-24-marketing-
tasks.html upcoming marketing tasks] for Fedora 24, it lists taking
screenshots for the next release as an objective.
= Background Analysis =
This was completed for
[https://fedoraproject.org/wiki/Marketing/F23_Screenshots Fedora 23].
Important questions to ask:
* What screenshots are needed?
* Who needs the screenshots?
* Where will they be used?
= Implementation Recommendation =
If needed, we can have someone run the F24 Beta to take screenshots.
cprofitt volunteered to do this earlier if needed.
mailga, since you led this task for Fedora 23, could you explain the
process and what needs to be done for F24 (e.g. do we only need
screenshots of new things or all the DEs)?
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/226>
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.
#222: Publicizing "Fedora affiliates" (or groups using Fedora)
-----------------------------+-------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 23
Component: Feature stories | Severity: not urgent
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+-------------------------
'''Discussed in
[https://meetbot.fedoraproject.org/teams/marketing/marketing.2016-02-24-22.0…
2016-02-24 meeting].'''
= What =
It was mentioned during the meeting that it would be helpful and useful
for Ambassadors to have a place to show people / groups examples of other
groups successfully running Fedora on their own infrastructure.
Ideas for this would be companies powering their infrastructure with
Fedora, schools or universities that have Fedora computer labs, and other
similar types of cases.
= How =
The difficult part in accomplishing this is identifying the list of
entities that are using Fedora in applications like this. Would a call for
action be needed, such as on the Magazine / Community Blog? Do we have a
past list like this somewhere?
Once these questions are answered and we have the list, we can ''then''
move on to how we want to publish and publicize the list.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/222>
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.
#225: Transition to FOSCo - Nomination of the marketing coordinator
---------------------+-------------------------
Reporter: mailga | Owner: mailga
Type: task | Status: new
Priority: normal | Milestone: Open
Component: General | Severity: not urgent
Keywords: | Blocked By:
Blocking: |
---------------------+-------------------------
In order to have a FOSCo proposal for The Council before the deadline
(July 1st), the actual FAMSCo asked for a Marketing coordinator for one of
the seats in the new body.
At the moment FAmSCo is evaluating how FOSCo have to be structured and the
real interest of the groups to be included.
Summarizing the state of the things, cwickert sent a mail in the
Ambassador ML with all the links of interest. You can find it
[https://lists.fedoraproject.org/archives/list/ambassadors@lists.fedoraproje…
here].
Jflory7 is a good choice for coordination, I'm supporting his nomination.
For any other nomination or question, please reply in this ticket. For
proposals about FOSCo transition, reply to the Christoph post in the
ambassadors or in the council-discuss ML.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/225>
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.
#227: Create the release announcement for Fedora 24
----------------------------------+------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: critical | Milestone: Fedora 24
Component: Release deliverables | Severity: urgent
Keywords: meeting | Blocked By:
Blocking: |
----------------------------------+------------------------
= Phenomenon =
It's about that time of year! Fedora 24 is just around the corner. For
Fedora 23, the idea came up of having a different kind of release
announcement, adding more "human" parts of the magic happening for each
release into the announcement. mattdm expressed interest in this then, but
due to the time crunch, we didn't have as much time to work on it as we
liked.
= Background Analysis =
We need to see how many hands we have available for this task, what kind
of angles we want to approach, and whether we want to do one or two
versions of the announcement (and if two, where the two types end up
going).
= Implementation Recommendation =
This will be a good topic for the meeting to decide how we want to shape
this release announcement. We will discuss it in today's meeting and then
also wait for feedback from others who are unable to attend.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/227>
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.
#224: Requesting accoutn permissions change
---------------------------------+--------------------------
Reporter: linuxmodder | Owner: linuxmodder
Type: task | Status: new
Priority: normal | Milestone: Open
Component: Internal operations | Severity: not urgent
Keywords: | Blocked By:
Blocking: |
---------------------------------+--------------------------
= phenomenon =
Changed fas nicks FROM `corey84` TO `linuxmodder`
= background analysis =
Pagure permissions for my account still reside on corey84 (inactive)
thusly preventing me push access to my fork(s).
= implementation recommendation =
change permissions of Corey Sheldon (corey84) TO Corey Sheldon
(linuxmodder)
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/224>
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.
#223: Create Social Media Accounts for Fedora on Diaspora and GNU Social
-------------------------+-------------------------
Reporter: dhanvi | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Open
Component: General | Severity: not urgent
Keywords: | Blocked By:
Blocking: |
-------------------------+-------------------------
We have discussed about it here
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.o…
Joe Brockmeier raised few question such as
1) How are we managing the new accounts?
2) Who has the "keys" to the account?
a) We need more than one person, and ideally folks who are
"accountable" to Fedora. (e.g., Matthew Miller, someone on the council,
etc.)
3) Do we have a plan for managing them? Who's taking responsibility for
that.
If you guys need any help with managing, I can help you with the same
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/223>
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.
Hi guys,
Since jflory liked the look of my blog post for an article in IRC the other
day it's now been polished up as a Fedora Magazine article with that
audience in mind.
It's currently in draft state and can be seen here:
https://fedoramagazine.org/?p=13166&preview_id=13166
I'm trying to think of what imagery I could add to it but struggling a
little in this department. Perhaps pictures of the koji build and bodhi
update? or a snippet of the ansible playbook running?
I'd be happy to link to the playbooks on github if people think that's
sensible (I've removed the links to my blog that discuss how the dynamic
inventory works as I suspect my little blog may not survive the traffic
directed at it) ...
Could you please give it a look over and let me know your thoughts on it.
Cheers,
James