So - we've had a piece from roshi sitting in "pending" for more than two
weeks. If we're going to institute some kind of system where pieces have
to be approved / scheduled, we should communicate with the authors and
ensure these things are being scheduled / dealt with in a timely manner.
* Nothing that's not embargoed should sit longer than a few days,
especially when we have a dearth of content.
* If a piece needs editing, then we need to communicate that to the author.
* If a piece is somehow unsuitable, we need to let the author know.
While we have some discussions/plans for a "community focused"
blog/publication off in the future, it's not here now. We aren't exactly
flooded with content either - there's no good reason not to publish
these things on Fedora Magazine for now.
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
I noticed that you have a pitch in the queue for a powertop article.
I put one in a while back for the gnome-battery-bench (based off an idea
to the list by mattdm iirc)
and I think it might be good to just mention the battery bench in the
powertop article, rather than have two seperate ones.
I am Josef, a Fedora contributor, who is currently co-maintaining Ruby,
Rails and Vagrant among other packages. I am joining as I would like to
publish an article on upcoming Vagrant as a Fedora 22 feature. In fact,
the article is almost ready, so I just need access to submit it:).
I hope I can contribute with other content in future as well.
I plan to send this out tomorrow morning at the Appointed Time.
Thanks especially to Joe Brockmeier for writing some of the best bits
here. A lot of the rest is cobbled together from the F22 talking points
and beta announcements.
It seems pretty good, but maybe a little bit too... releasenotesy. Any
last minute adjustments or feedback?
Fedora Project Leader
Since there wasn't a mass rebuild for F22, the F22 repos have some F21
packages, which is perfectly fine. However, I've seen a few people
worry about this - the most recent query came up on the devel list.
Should we write a short post on the magazine explaining the situation
and allay users' fears? (and twitter and facebook and G+ and so on)
Ankur Sinha "FranciscoD"
next thursday will be held the readiness meeting and at May 26 (if the
go/no go meeting will give thumbs up) is scheduled the final release.
I think we should meet for discussing about the things to be done by us
and taking our time for checking the tickets and more.
Of course is difficult getting it before the readiness meeting, but
we're just in time for the final relase.
Choosing a day of this week would be good.
The agenda I suggest is:
1) check the mktg schedule
2) check the mktg tickets
3) fedora magazine (news, improvements, suggestions and so on).
Feel free to complete the list.
On 05/25/2015 08:02 PM, R Mercado wrote:
> Hello Ryan,
> I forgot about any pitch for a magazine article.
> Could you remind me? Did I post anything?
> I like Stellarium. I once submitted a bug report that turned out to be
> I did not realise there was a marketing team for the magazine.
> R Mercado
> On Mon, 2015-05-25 at 18:11 +1000, Ryan Lerch wrote:
>> hi R Mercado!
>> Just checking up on your pitch for the magazine Article about Stellarium
>> on Fedora!
>> I think this would be a great article for the app-spotlight style like a
>> few I have done in the past. Are you still keen to work on this one?
Yeah, there is one sentence in the article.
Also, the marketing list here is where we discuss magazine related stuff.
hi R Mercado!
Just checking up on your pitch for the magazine Article about Stellarium
I think this would be a great article for the app-spotlight style like a
few I have done in the past. Are you still keen to work on this one?
So, I'm starting to work on
because Tuesday will be here before we know it. :)
I was reviewing http://fedoramagazine.org/announcing-fedora-21/, and
wow, that came out well. Hopefully we can make it that pretty this time
around as well.
Who is in to help?
Here's the format I'm thinking — first, a first-person announcement
from the FPL (I like the conversational, informal approach — but please
feel free to let me know if that's hubris), followed by a Highlights
section, drawn from the talking points
<https://fedoraproject.org/wiki/Fedora_22_talking_points>, and then
basically cut-and-pasting s/21/22/ the "Downloads, upgrades,
documentation, and common bugs" section from the F21 announcement.
Fedora Project Leader
#192: Firefox bookmarks
Reporter: ankursinha | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: Release deliverables | Severity: urgent
Keywords: | Blocked By:
Bookmarks need to be updated and so does the package
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/192>
Marketing team for the Fedora project.