docs March 2012

docs@lists.stg.fedoraproject.org

17 participants
27 discussions

Fedora Docs Meeting Reminder
by Ben Cotton 11 Mar '12

11 Mar '12

This is an automated message to remind you that we will be meeting at 9 AM EST (1400 UTC) in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.

1 0

Help for chronic beat writers
by John J. McDonough 07 Mar '12

07 Mar '12

If you write a beat regularly, or if you have chosen a beat with a lot of packages, the checkBeat app might help. I've been doing this for a while, and recently made a simple change that might make it helpful for others. (Previously you had to edit the C for each release). First time you do this there are a bunch of steps, but then it gets easier. 1) $ yum install sqlite-devel 2) Make a directory to work in. If you're a regular beat writer, you may want to keep this around. 3) go to http://git.fedorahosted.org/git/?p=docs/tools.git;a=tree;f=tools/checkBeat and download checkBeatMW.c and Makefile into your directory. If your beat has a bazillion packages, you might also want to look at makeBeats.sh. You could clone the docs/tools repo, but all you really need from there are these two files. 4) $ make checkBeatMW 5) Create 2 subdirectories, new and old 6) go to http://git.fedorahosted.org/git/?p=docs/technical-notes.git;a=tree;f=build and grab the primary.sqlite corresponding to the previous and next release. That location has a directory for each release, and a subdirectory for alpha, beta, release. Alternatively, the README has instructions for getting the latest in case I haven't pushed it yet. Place these in the new and old subdirectories. 7) Make a file containing the list of packages in your beat. The makeBeats.sh script will make such a file, but it is based on the RPM groups, which are wrong more often than not, and needs to be edited for each release. Figuring out how to edit it requires poking around in the SQLite database. yum groupinfo <groupname> could give you a reasonable start if your beat maps to a group. 8) $ ./checkBeatMW my.beat >myBeat.mw 9) myBeat.mw will now contain a list of any packages in your beat which have changed, with the previous and next versions and a link to the upstream site. The list is marked up for MediaWiki. You can paste this into your beat and use it as a placeholder for apps you need to research. The Development Tools beat has an example, which, of course, will disappear as I research those packages. Circuit Design, Embedded and Amateur Radio also contain examples but I should complete those in the next day or two. On subsequent releases you just need to grab the new primary.sqlite and run checkBeat again. Keep in mind that in many cases the changes will be minor tweaks or bugfixes which don't really need to be captured in the release notes. --McD

1 0

Fedora Technical Notes
by John J. McDonough 05 Mar '12

05 Mar '12

The Fedora 17 Alpha Technical Notes are now available at http://fedorapeople.org/groups/docs/technical-notes/en-US/ --McD

1 0

Fedora Docs Meeting Reminder
by Ben Cotton 04 Mar '12

04 Mar '12

This is an automated message to remind you that we will be meeting at 9 AM EST (1400 UTC) in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.

1 0

Volunteer needed to lead docs meeting
by Ben Cotton 04 Mar '12

04 Mar '12

I'm going to be traveling on Monday and won't be around for the meeting. Anyone want to volunteer to keep MeetBot in line? https://fedoraproject.org/wiki/Docs_Project_admin_notes#Starting_a_meeting -- Ben Cotton Fedora Docs Leader

3 2

Fedora 17 beats open
by Ben Cotton 04 Mar '12

04 Mar '12

Docs team, It's time to start thinking about writing beats for the Release Notes. The beats are now open. You can take a beat, or re-take your previous beat by removing * from your name at: https://fedoraproject.org/wiki/Documentation_Beats Thanks, BC -- Ben Cotton

5 7

quick guide translation status
by Kévin Raymond 03 Mar '12

03 Mar '12

Hi there, I am actually cleaning things under transifex.net. We have some projects outsourcing the Fedora Hub, like docs, but not in any Fedora releases (fedora-web, fedora-docs, fedora-main, fedora-uptream-projects). The difference is how we found projects to translate. 1. from the main hub: https://fedora.transifex.net/projects/p/fedora/access/outsource/ 2. from the release, like: https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/ (click on resources) Should we add all guides to the fedora-docs? (Some are out to date, so I don't really know). Actually we have some docs not there, please see[1] and tell me, I'll add them if asked to do so. I am already adding those that I think should be there (will strike them). I've also reported the projects that have not been updated in a while[2], that would be great to let translators know if the guide if out to date (a maintainer could use the announce tab or disable translation) [1] https://fedoraproject.org/wiki/User:Shaiton/trans#Projects_under_the_Fedora… [2] https://fedoraproject.org/wiki/User:Shaiton/trans#Default_of_maintainers_or… Cheers, -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs March 2012