docs August 2009

docs@lists.fedoraproject.org

40 participants
83 discussions

Almost-finalized: Marketing F12 schedule
by Mel Chua 03 Aug '09

03 Aug '09

I've updated the F12 schedule according to the meeting (https://www.redhat.com/archives/fedora-marketing-list/2009-July/msg00140.ht…) that Paul, John, and myself had today. https://fedoraproject.org/wiki/Marketing_F12_schedule We've got some dates and such to coordinate with various teams (cc'd here) before Monday in order to make sure our calendars sync up. One of the things we'll be talking about at the Marketing meeting tomorrow (https://fedoraproject.org/wiki/Marketing_meetings) is how to make sure that each Marketing + OtherTeam coordination happens this week - some of these connections already have delegates, others have people who probably should be, others are wide open. The notes below are very, *very* much drafts, and only starting points! It's also entirely possible that I've put *too* much in the notes below (that figuring out something shouldn't be Marketing's job, or its focus). Patches welcome. --Mel ---- Design: We should make sure we get you a release slogan in time, and give fast enough feedback/final-slogan turnaround based on your designs that you can make release buttons/banners with time to spare. Also need to see what sort of work we need to coordinate in order to make spiffy Ambassadors kits. Docs: We should commit to those 1-page shiny release notes you wanted, and find other good points during the cycle to check in with each other. We also need to talk (possibly with News) on who'd like to do what portions of talking points and in-depth feature profiles. (How can we market our documentation as awesome, too?) Ambassadors: We need to schedule a briefing for you folks to happen once the talking points are ready - but most importantly, we need to learn how we can listen to you better so that we can make the things you actually want and *need* to spread the word on the ground. What can we do? Websites: We should talk - potentially with Design - about how we're going to coordinate various webpage redesigns and revisions, and how our respective roles complement each other. News: We also need to talk (possibly with Docs) on who'd like to do what portions of talking points and in-depth feature profiles. We should also figure out what's going on with News and Marketing and Fedora Insight, so we can schedule in coordination times with other teams if needed.

2 3

Release Notes Schedule
by John J. McDonough 03 Aug '09

03 Aug '09

As I dug into John Poelstra's schedule in more detail, I noticed a few issues that I hadn't noticed in earlier reviews. Specifically, very long times on some short tasks with short times on some more difficult tasks, and tasks out of order. Since I don't have a really good feel for the guides, I put together what I thought was a more workable schedule for release notes only. Eric was going to look at guides. My strawman is at: http://jjmcd.fedorapeople.org/F12RN2a.html I fixed major milestones to the same dates that John had so hopefully we don't affect other teams. However, I did put a couple of L10N tasks on the list since they are tied closely to us. I have not, however, had any discussion with L10N as to whether these times make any sense at all to them. John suggested we get together in a Gobby/Talk meeting to get this schedule into sync with his. I think we need to get the guides schedule integrated with this and include a representative from L10N in that meeting. Because of the new definition of alpha and beta, our schedule looks a lot different than earlier releases. Specifically, since alpha should be "feature complete", we should have almost everything we need for release notes by alpha. That means the bulk of our work is between alpha and beta. However, since Beta should include more or less complete release notes, L10N will need time to translate them. That pushes Docs work forward some, meaning we will have a real scramble right around alpha, and L10N will have a pile of work just before beta. The upside is that the work before GA should be a little less onerous, and there should be little left to translate. If we can make our plan of a table for all changes and prose only for significant effort required to convert plus highlighting high-profile features, there should be a lot less prose to write (and translate) than previous releases. We will, however, need some pretty aggressive wiki gardening to allow us to convert to XML quickly. I would like everyone to take a really close look at this, and comment on it on this list. I think I have the major tasks identified, but it is always good to have more input. Thanks --McD

6 19

Is it ok to edit this wiki template?
by Frank Murphy 03 Aug '09

03 Aug '09

https://fedoraproject.org/w/index.php?title=Template:Userpage/Infobox&actio… Can this be updated to include:? skype: msn: -- Regards, Frank jabber | msn | skype: frankly3d http://www.frankly3d.com

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs August 2009