-----BEGIN PGP SIGNED MESSAGE-----
00:01:38 #startmeeting Docs Project Meeting - Agenda:
00:01:38 Meeting started Thu Sep 24 00:01:38 2009 UTC. The chair is
Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:01:38 Useful Commands: #action #agreed #halp #info #idea #link #topic.
00:01:47 #topic Roll Call
00:01:48 * Sparks
00:02:07 * jjmcd .
00:02:56 * danielsmw
00:03:31 * ianweller kinda sorta not really
00:05:47 * Sparks gives everyone just a few more minutes
00:08:34 Okay, let's get started.
00:08:48 #topic Last week's action items
00:09:00 quaid to follow up with Richard about the use of the CC logo
on the wiki.
00:09:01 none of the action item guys are here
00:09:09 Yeah, I just realized that.
00:09:24 We'll just pass these by...
00:09:42 #topic Release notes format changes
00:09:50 jjmcd: Is there any further discussion on this?
00:09:56 what were we changing?
00:10:26 A little late, they are being built each night
00:10:34 I don't know.
00:10:42 We'll just call this topic done.
00:10:54 #topic Status on CMS (Zikula)
00:11:02 Is there any update on Zikula?
00:11:25 Um, I guess I have a small one
00:11:31 danielsmw: go ahead
00:11:45 I hope I'm not being a blocker, but I'm not done with my package yet.
00:11:48 I am very close though
00:11:51 and most of the work is done
00:11:59 danielsmw: Which package?
00:12:01 what I need is a legit packager to help me out with my
00:12:04 Xinha, for Scribite!
00:12:17 #link https://fedoraproject.org/wiki/Zikula#Module_status
00:12:26 ^^^ I don't see it on the list. Could you add it, please?
00:12:53 danielsmw: I'm a packager but certainly not legit.
ianweller is one, though.
00:13:01 Sparks: alright
00:13:05 If he can't help you then maybe he can point you to someone who can
00:13:07 wait, should this be on this list?
00:13:23 even though it's a general package
00:13:26 and not a zikula module?
00:13:54 Well... it's needed for Zikula, right?
00:13:56 It's just that it's _for_ zikula, which is why I brought it up now.
00:13:58 Yeah, it is
00:14:02 So I guess it goes there then.
00:14:05 I'll update the list. :)
00:14:40 danielsmw: Do you know how much more time it will take to
get it straight?
00:14:57 if I may... I had started to package Xinha for a project of
mine (but they I abandoned as I didn't use it in the end)
00:15:18 Sparks: i really do have most of it done now, I believe.
It's just silly rpmbuild errors
00:15:27 all I remember is that it wasn't a hard package, I had it built
00:15:40 bochecha: it doesn't look that hard, I'm just no good at packaging. :)
00:15:41 danielsmw: What are the errors?
00:15:54 danielsmw, if I can help, drop me an email, I had already done it :P
00:16:09 Sparks: things like... using sources that aren't archives, and such.
00:16:12 bochecha: will do, thanks!
00:16:25 Sparks: but the main outline of what I"m doing is there.
00:17:20 danielsmw: Okay. If I can get my head above water (maybe
this weekend) I'll be happy to look at it. ianweller fixed so many
errors for me that I might know how to fix yours
00:17:41 Sparks: might. thanks, it looks like I'll be getting plenty of help.
00:17:47 danielsmw, if you have time tomorrow I might help, too tired tonite
00:18:14 thanks everyone.
00:18:17 i appreciate it.
00:18:20 Anything else for zikula?
00:19:23 I have a question
00:19:27 danielsmw: Go ahead
00:19:35 * quaid arrives back
00:19:38 On that page you told me to edit, FCKeditor is listed as
something that needs to be packaged
00:19:46 * quaid can address his item when it comes back around
00:19:47 which is basically the same thing as Xinha.
00:19:53 is there a reason they should both be done?
00:20:25 or is that just left over?
00:20:26 Not really
00:20:30 okay, i'll remove it then.
00:21:11 Okay, anything else for Zikula?
00:22:03 #topic Status on CC license rollout.
00:22:14 quaid: Were you able to follow up with Legal?
00:22:16 danielsmw: did you get hooked up with the Beacon maintainer?
00:22:19 Sparks: yes!
00:22:25 quaid: no, I forgot!
00:22:28 ironically, Richard just pointed back to spot
00:22:41 and spot knows of the problem; and there doesn't seem to be a solution
00:22:51 i.e., the CC logo(s) are not coverable by the CC-BY-SA
00:23:04 but maybe spot can explain better ...
00:23:08 * quaid forgot to ask if he'd be around
00:23:16 neither is our logo...
00:23:24 BUT, I'm good either way
00:23:44 heh, nor are other logos we might carry
00:24:22 spot: You around?
00:25:14 I guess not.
00:25:24 So I don't see the problem with using it.
00:25:47 And I do see a problem with using it.
00:26:00 So are we going to go with "don't use it"?
00:26:07 well, we have a clear legal guidance for don't use
00:26:13 so, for now, we don't use it.
00:26:24 I'll ask spot to explain on list, k?
00:27:08 #link https://fedoraproject.org/wiki/License_changeover_schedule
00:27:29 So I guess we need to make internal notifications and then
get ianweller on changing the wiki over
00:28:08 rudi's not here tonight but he was still trying to get
access to those packages so he could change the Publican brand files
00:28:30 * danielsmw is sneaking out early. peace.
00:28:37 danielsmw: Have a good one
00:28:46 Anything else on the license changeover?
00:29:02 * quaid is happy :)
00:29:30 #topic #
00:29:32 #topic Shared open-source style guide
00:29:47 I think this is a rudi thing, too. Anyone have anything to
report on this?
00:30:09 well, yes
00:30:14 this was just part of something, righ?
00:30:14 quaid: Go ahead
00:30:20 do we have someone who is focusing on what is going on
00:30:25 with the upstream initiative?
00:30:29 writingopensource.org, right?
00:30:39 I don't remember now
00:30:49 I think rudi was working on getting RH to release their docs
00:31:04 I think ke4qqq was going to work on it as well
00:31:17 that is something we can contribute to the upstream effort,
or so I thought we discussed :)
00:31:27 I forget who was on-list with this item ...
00:31:36 he's a gnome.org person, iirc.
00:31:38 yeah, I think someone else had point but I don't remember who
00:31:48 * quaid looks
00:34:38 It's been so long ago I don't even remember
00:34:49 shaun mcchance?
00:34:57 * quaid having slow browser ...
00:35:50 * quaid joins http://identi.ca/group/wosdocs
00:36:19 So we need to figure out who from FP is going to work on this.
00:36:56 I think ke4qqq was interested but I don't know how much time
he has now
00:38:53 Let's take this to the list and see if we can stir up any interest
00:38:57 anything else on this?
00:39:28 #topic Guide needs?
00:39:38 Are their any guides (or RN) that need help?
00:40:13 I see some weird stuff
00:40:19 need to get w/rudi
00:40:56 okay... anything else?
00:41:36 #topic New Guides
00:41:40 Any new guides?
00:42:33 #topic All other business
00:42:46 Anyone have anything else?
00:44:32 * Sparks thinks we're going to get done early
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.8)
-----END PGP SIGNATURE-----
Hello Transifex System User,
This message serves as notification that you will not receive any more courtesy notices
from our members for two days. Messages you have sent will remain in a lower
priority queue for our member to review at their leisure.
Future messages will be more likely to be viewed if you are on our member's priority
This courtesy notice is part of a free service to make email
more reliable and useful. Boxbe (http://www.boxbe.com) uses
your existing social network and that of your friends to keep
your inbox clean and make sure you receive email from people
who matter to you.
Boxbe: Say Goodbye to Email Overload
Hi Fedora Docs team,
I was contacted by an editor for a well-known series of UNIX volumes
who asked me to check with the Docs team to see if there was anyone
interested in serving as a technical assistant for their upcoming book
that in part covers Fedora 12. It's a for-fee job.
I don't want to clog the list with "me too" messages, so please
respond to me off-list. I'll forward all names I receive by COB
Friday, September 25th to the editor for action, and note them here to
the list as well for transparency.
Here are the skills, abilities, and knowledge you'll need to do the
* Access to a pre-Fedora 12 (Rawhide) system, staying current with
* RHCE certification, or an equivalent level of skill -- that is,
skill in most pieces of the Fedora platform -- is helpful
* A significant amount of spare time to fact-check all the relevant
chapters, usually a few at a time
* The ability to relay and revise information if something changes
over the period of work
* Ability to work well and be accurate and thorough under pressure and
strict time deadlines
* The ability to communicate clearly in English to other people on the
team such as authors and editors
I've done technical editing on a book in the past, and it is a fairly
demanding part-time job that requires several weeks of detail-oriented
reading, testing, note-taking, and communication with the writers. I
don't think I could have done it alongside my tasks in a release cycle
at the time, but I happened to come into a project during downtime
after a release so everything worked out OK. Fortunately, it can be
very rewarding if you enjoy the subject matter.
I look forward to hearing from any interested folks off-list.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
----- Original Message -----
From: "Göran Uddeborg" <goeran(a)uddeborg.se>
To: "John J. McDonough" <wb8rcr(a)arrl.net>; "Fedora Translation Project List"
Cc: "For participants of the Documentation Project"
Sent: Friday, September 25, 2009 4:14 PM
Subject: Fedora 12 Release Notes
> There are certain parts of the release notes missing from the pot
> files. For example section "1.5.1. We Need Feedback!". Is this
> something that is planned to be fixed later on, or should I write a
> bugzilla about it?
Interesting. That section is part of "Common Content", and as such, isn't
really a part of the Release Notes but a part of the Fedora branding for
Publican. So no its not a bug, and no it shouldn't be in the pot.
I have just installed updated branding so if all goes well, a copy with the
branding bits in the correct language for nl and se should be up in an hour
or less. All the languages will be done overnight.
----- "Christopher Curran" <ccurran(a)redhat.com> wrote:
> > a) add @books to the Development category,
> > (fits the 3 current opensource devel books there)
> There is no point breaking string
> freeze if the books are already deprecated.
I don't think any are deprecated.
For reference the current books are:
- ldd-pdf (linux device drivers)
so yeah developer-oriented.
I went ahead and put @books into the Development category for F12.
I am still wondering about a "Content" category for F13.
Should we go with that even it only were to contain @books
for now? Anyway probably more important would be getting
gnome-packagekit to list books when we have more.
I am currently uploading a build of the release notes to
for all the languages. All the languages should be there in a few hours.
Most only have a little translation done, but I appreciate folks getting
right on this. I will update this copy frequently over the next couple of
weeks so that translators have a chance to review their work without having
to personally go through all the gyrations of building the notes.
Thanks for your hard work
I have just joined the group, I'm want to help translation of documents.I'm
from turkey.I only know turkish and english so I'm planning to translate
some english docs to my native language
Where can I start?
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Need to move the Documentation Guide to the wiki
Summary: Need to move the Documentation Guide to the wiki
Product: Fedora Documentation
Need to move the Documentation Guide to the wiki for further clean up and
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.