docs December 2009

docs@lists.fedoraproject.org

22 participants
56 discussions

[Bug 514046] New: Oracle-xe page for Spacewalk doesn't work
by Red Hat Bugzilla 16 Feb '10

16 Feb '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Oracle-xe page for Spacewalk doesn't work https://bugzilla.redhat.com/show_bug.cgi?id=514046 Summary: Oracle-xe page for Spacewalk doesn't work Product: Fedora Hosted Projects Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: Deployment_Guide AssignedTo: mhideo(a)redhat.com ReportedBy: mschwage(a)gmail.com QAContact: rlerch(a)redhat.com CC: fedora-docs-list(a)redhat.com Classification: Fedora Description of problem: Sorry about the classification of this. I didn't see Spacewalk anywhere in Bugzilla! Anyway, on the webpage https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#Install, the install instructions don't work as advertised. There, it says "Configure the Oracle XE database by running # /etc/init.d/oracle-xe configure" This did not set the system/sys name correctly. Yes, I know, the oracle-xe command comes from Oracle themselves, but on my RHEL53 machine it just refused to set the password correctly. Did I try to do it 10 times or more? Yes I did, and it did not work at all. Did I fat finger my password every single lousy time I tried it? No I did not, for I was able to create my password as easy as you please using my workaround below. Version-Release number of selected component (if applicable): oracle-xe-univ-10.2.0.1-1.0 oracle-instantclient-basic-10.2.0.4-1 oracle-instantclient-sqlplus-10.2.0.4-1 How reproducible: Every time. Steps to Reproduce: 1. Do this on RHEL53 x86_64. Install the Oracle-XE software as listed. 2. Follow the instructions on https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#Install, up to and including the "Test Your Connection with SQLPlus" part. 3. You fail to login. Actual results: Fail to login. Expected results: Successful login. Additional info: The workaround is to perform the following after running /etc/init.d/oracle-xe configure : su - oracle . /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.sh /usr/lib/oracle/10.2.0.4/client64/bin/sqlplus /NOLOG CONNECT / AS SYSDBA alter user sys identified by password; alter user system identified by password; sqlplus64 'sys@xe as sysdba' -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

Mission statement questions
by Karsten Wade 05 Feb '10

05 Feb '10

We have a mission as a sub-project: https://fedoraproject.org/wiki/Docs_Project_mission_statement The mission of the Fedora Documentation Project is to provide documentation to users and developers to improve the overall usage of Fedora. We do that by explaining the usage of certain pieces of software or systems, provide written accounts of special events (releases, etc), and provide recommendations on setting of software or systems (security, performance, etc). At a few reads, I don't really recognize any of the content. It has a few sentences that introduce newer ideas than I recall being in there. One is welcome in my mind (special events), one is an odd duck (provide recommendations). Also, some content is missing that I recall from before. The gist was, the project has a goal to produce 100% FLOSS content, tools, and processes. This goal fits in to the overall Fedora Project objective of being entirely rebuildable from source. Anyone know the history of the transition of the mission content? Was this discussed and I missed it? Otherwise, I'd like to discuss this mission statement. I posted some questions on these right here: https://fedoraproject.org/wiki/Talk:Docs_Project_mission_statement With a recommendation for an update here: https://fedoraproject.org/wiki/Talk:Docs_Project_mission_statement#Recommen… Your thoughts are appreciated. It's _our_ mission, after all. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://quaid.fedorapeople.org gpg: AD0E0C41

4 5

[Bug 533737] New: Recommend changing the Feedback statement to include the component name.
by Red Hat Bugzilla 21 Jan '10

21 Jan '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Recommend changing the Feedback statement to include the component name. https://bugzilla.redhat.com/show_bug.cgi?id=533737 Summary: Recommend changing the Feedback statement to include the component name. Product: Fedora Version: 12 Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: publican-fedora AssignedTo: jfearn(a)redhat.com ReportedBy: eric(a)christensenplace.us QAContact: extras-qa(a)fedoraproject.org CC: jfearn(a)redhat.com, fedora-docs-list(a)redhat.com, nb(a)fedoraproject.org, mmcallis(a)redhat.com, r.landmann(a)redhat.com Classification: Fedora Eric Christensen <eric(a)christensenplace.us> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |review? Created an attachment (id=368073) --> (https://bugzilla.redhat.com/attachment.cgi?id=368073) Proposed patch for Feedback.xml Description of problem: Instead of telling people "When submitting a bug report, be sure to mention the manual's identifier: &BOOKID". It might be better to point them toward the specific component in BZ which just happens to be the same as the &BOOKID (or it should). Version-Release number of selected component (if applicable): 1.0-0.fc12 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

new member introduction
by Vikram Dhillon 06 Jan '10

06 Jan '10

Hi all, How are you guys doing? I have been writing documentation for various project: Firefox, GNOME, KDE, FreeBSD and others, and I would like to get started with writing documentation for fedora. How can I get started here. Thanks for the help in getting me started :D Regards, Vikram Dhillon ~~~ There are lots of Linux users who don't care how the kernel works, but only want to use it. That is a tribute to how good Linux is. -- Linus Torvalds

2 2

Updated Fedora 13 Schedules
by John Poelstra 04 Jan '10

04 Jan '10

I have updated the schedules based on our meeting on 2009-12-22. Let me know if there are any parts of it that still need to be adjusted by telling me the task number and schedule you are referring to. I created the regular version and a slimmed down version that removes some of the sub-headings and phase information. Please tell me if you would prefer this to be the default format going forward. -= Documentation =- http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks.html http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks-flat.html -= Translation =- http://poelstra.fedorapeople.org/schedules/f-13/f-13-trans-tasks.html http://poelstra.fedorapeople.org/schedules/f-13/f-13-trans-tasks-flat.html -= Combined =- http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-and-trans-tasks.h…

2 1

Docs Meeting 2009-12-24 Summary
by John J. McDonough 24 Dec '09

24 Dec '09

=================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by sparks at 00:00:29 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2009-12-24/fedora-meeting.2… . Meeting summary --------------- * Roll Call (sparks, 00:00:46) * F13 Docs Schedule (sparks, 00:04:46) * Sandbox on Fedora People (sparks, 00:13:25) * Release Notes (sparks, 00:18:07) * Status on CMS (Zikula) (sparks, 00:28:52) * Does yum langpack support help us? (sparks, 00:31:09) * Guide Status (sparks, 00:32:51) * New Guides (sparks, 00:39:29) * Outstanding BZ Tickets (sparks, 00:40:56) * Everything else (sparks, 00:45:05) Meeting ended at 01:01:41 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sparks (88) * jjmcd (82) * ianweller (5) * zodbot (3) * quaid (2) * nb (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Docs Meeting 2009-12-24 IRC log
by John J. McDonough 24 Dec '09

24 Dec '09

00:00:29 <sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:00:29 <zodbot> Meeting started Thu Dec 24 00:00:29 2009 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:29 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:39 <sparks> #chair jjmcd 00:00:39 <zodbot> Current chairs: jjmcd sparks 00:00:46 <sparks> #topic Roll Call 00:00:47 * sparks 00:00:59 * jjmcd . 00:01:23 * nb . 00:01:38 <ianweller> oh look, a meeting 00:03:33 <quaid> oi! 00:03:47 <sparks> wow! quaid is here! 00:03:52 <quaid> :D 00:04:17 <sparks> Okay, let's get started. 00:04:46 <sparks> #topic F13 Docs Schedule 00:05:13 <sparks> So we had a two and a half hour phone conference/Gobby meeting last night... 00:05:37 <sparks> where we got the F13 release schedule hammered out. 00:05:37 <jjmcd> Great fun it was 00:06:00 <sparks> So we made a few changes from previous releases that we need to talk about tonight. 00:06:58 <sparks> The first items is that we aren't going to freeze development of the Release Notes or Guides until the very end 00:07:22 <sparks> So everyone should keep working through the Alpha and Beta freezes 00:07:50 <sparks> Any questions about this or any comments? 00:08:08 <jjmcd> We will be producing pots for L10N on a regular schedule 00:08:08 <ianweller> what reason was there for that? 00:08:20 <sparks> jjmcd: Yeah, that's the next thing. 00:08:30 <sparks> ianweller: for which that? 00:08:33 <jjmcd> All the branches we had to keep track of what L10N had was confusing 00:08:37 <ianweller> 18:06:52 < sparks> The first items is that we aren't going to freeze development of the Release Notes or Guides until the very end 00:08:40 <ianweller> ^ that that 00:08:44 <sparks> :) 00:08:50 <jjmcd> ANd really, we were giving them the MINIMUM amount of time to translate 00:08:50 <sparks> Yeah, it just doesn't make sense. 00:09:02 <ianweller> oic 00:09:04 <jjmcd> This way they get the maximum amount of time 00:09:10 <sparks> yeah 00:09:20 <jjmcd> We had changes we were holding for them that they could have been workin gon 00:10:15 <sparks> The second thing we decided was that we were going to push POT files constantly. 00:10:33 <jjmcd> This way, As soon as we have text it will be available for L10N 00:10:35 <sparks> so nightly we should be pushing updated POT files so the translators aren't just sitting around waiting 00:11:37 <sparks> that means that the guides should be pushing POTs now! (Except we are still waiting for Transifex 0.7) 00:12:24 <sparks> Anything else on this topic? 00:13:25 <sparks> #topic Sandbox on Fedora People 00:13:33 <sparks> jjmcd: Want to talk about this? 00:13:38 <jjmcd> For Fedora 12, we built release notes each night for L10N. It turns out I didn't have the quota on fedorapeople.org for 42 languages, so I ended up putting them on is-sixsigma.com where I had some space. 00:13:54 <jjmcd> Having the RNs on an external host doesn't have the caché of having them on fedoraproject, and it doesn't do anything for guides. 00:14:07 <jjmcd> Ricky agreed to make us a group place where we can put draft documents. 00:14:24 <jjmcd> People in docs will have write access to /srv/groups/docs and that will be accessible via http://fedorapeople.org/groups/docs/ 00:14:36 <jjmcd> Just remember that files owned by you in that directory still count against your quota, so let infra know if you need more. 00:15:13 <jjmcd> I think that sums it up 00:15:17 <jjmcd> Any questions? 00:15:41 <jjmcd> This is for drafts. Finished docs still on docs.fp.o 00:15:57 <sparks> ya 00:17:06 <sparks> Okay, works for me... We'll publish the path when it is all setup. 00:18:01 <sparks> Okay, moving on 00:18:07 <sparks> #topic Release Notes 00:18:18 <sparks> jjmcd: Anything you want to talk about on this? 00:18:23 <jjmcd> I think we covered the exciting stuff 00:18:32 <sparks> Works for me 00:18:36 <jjmcd> We have a handful of bugs before we push an update 00:18:58 <jjmcd> One thing I should mention 00:19:35 <jjmcd> I am giving serious consideration to doing the F13 notes in html rather than Yelp. Plenty of time to change so if you want to dissuade me .... 00:20:31 <sparks> Well... As long as it is easy for the users to find the documents from the GUI... 00:20:45 <jjmcd> html addresses other desktops and I now know how to get the same functionality as yelp 00:20:50 <sparks> I don't have a problem with it. I'm hoping Yelp 3.x will fix a lot of problems for us. 00:21:06 <jjmcd> IF it addresses KDE, XFCE 00:21:18 <sparks> ya 00:22:16 <jjmcd> On the menu they will be hidden under "Release Notes" instead of "Help" 00:22:44 <sparks> And you can have it automagically select the proper language? 00:22:54 <jjmcd> of Vrigave Informatie nar Hulp 00:23:35 <sparks> I'm going to assume that means yes 00:23:39 <jjmcd> yes 00:23:44 <sparks> :) 00:23:47 <sparks> Make it so 00:23:53 <jjmcd> Not just the doc, but also the menu 00:23:59 <sparks> perfect 00:24:04 <sparks> and it's all in the same SRPM? 00:24:07 <jjmcd> yes 00:24:22 <jjmcd> You didn't read the C, did you? 00:24:43 <jjmcd> I know, C is a write-only language 00:25:09 <sparks> I looked at it briefly but I haven't had a chance to study it 00:25:47 <jjmcd> It really is pretty simple 00:26:12 <jjmcd> The only gotcha is that part of the javascript has to be in <head> rather than <body> 00:26:57 <jjmcd> Strangely, in <body> it works sometimes for some languages 00:27:05 <sparks> Hmmm 00:27:23 <jjmcd> but in <head> it always works 00:27:30 <sparks> well, there you go 00:27:41 <jjmcd> ja 00:28:21 <sparks> Okay... anything else? 00:28:26 <jjmcd> not here 00:28:39 <sparks> Okay.. moving on 00:28:52 <sparks> #topic Status on CMS (Zikula) 00:29:00 <sparks> Anyone have any updates on this? 00:29:39 <sparks> ke4qqq: You around tonight? 00:30:48 <sparks> Okay, maybe he'll be around in a few minutes. 00:31:09 <sparks> #topic Does yum langpack support help us? 00:31:17 <sparks> Do we have anything else on this? 00:32:42 <sparks> I guess not 00:32:51 <sparks> #topic Guide Status 00:33:07 <sparks> Okay, anyone have anything they want to talk about on their Guide projects? 00:34:06 <sparks> I'd like some help writing up a section of the Security Guide describing PolicyKit 00:34:35 <jjmcd> Is that even understandable by mortals? 00:35:22 <sparks> PolicyKit? I want to make it understandable... 00:35:24 <sparks> if I can understand it 00:35:49 <jjmcd> I just assumed it was as impenetrable as SELinux policies 00:36:16 <sparks> SELinux isn't impenetrable 00:36:21 <sparks> that's a guide for that 00:36:41 <jjmcd> Yeah, and books. And it makes good sense until you try to understand a policy 00:36:56 <sparks> heh 00:37:23 <jjmcd> I figured "policy" was a code word for too complicated 00:37:49 <sparks> nah 00:38:31 <sparks> anything else? 00:39:29 <sparks> #topic New Guides 00:39:40 <sparks> Anyone have any new guides? 00:40:56 <sparks> #topic Outstanding BZ Tickets 00:41:58 <sparks> There are quite a few open tickets for Fedora Documentation 00:42:15 <jjmcd> most look to be chapter reviews 00:42:24 <sparks> Yes 00:42:56 <jjmcd> I screwed up by not tracking down notting this week I hope I don't have to wait for Jan 4 00:42:58 <sparks> There are quite a few customer requests in there too 00:43:10 <sparks> Might have to 00:43:29 <jjmcd> yeah. Just dunno 00:44:13 <sparks> Okay, anything else on this>? 00:45:05 <sparks> #topic Everything else 00:45:14 <sparks> Anyone have anything they want to discuss? 00:45:33 <jjmcd> Do you want a 10 minute tutorial on multilanguage rpm? 00:45:48 <sparks> Now? If you want to. 00:46:02 <jjmcd> Pretty straightforward if you have the stomach for it 00:46:57 <jjmcd> I don't hear anyone running away screaming 00:47:17 <jjmcd> OK, first, you need a tar. The tar has your doc in a directory per language 00:47:43 <jjmcd> A lot like you have in Publican, except the "format" directory pulled out 00:47:51 <jjmcd> You need 3 additional files 00:48:11 <jjmcd> At the top level, you have an index.html with some magical javascript 00:48:30 <jjmcd> The javascript includes a list of languages that will be in the rpm 00:48:42 <jjmcd> In head, it grabs the browser's language 00:49:07 <jjmcd> In body, it compares the browser language to the list and launches the doc based on the list 00:49:42 <jjmcd> The one tricky part is the language from the browser might be, for example, bn, bn-IN, or bn_IN 00:49:52 <jjmcd> THe list contains bn-IN 00:50:19 <jjmcd> If there is a hit against bn-IN, use it. If not, look for bn* and use the value from the list 00:50:31 <jjmcd> The two other files are desktop files, almost the same 00:51:00 <jjmcd> The menu language in the desktop file can be stolen from Article_Info.xml in the appropriate language 00:51:10 <jjmcd> The two desktop files are almost identical 00:51:42 <jjmcd> Now, the rpm install puts the index file in /usr/share/doc/HTML/<document-name> 00:51:50 <sparks> Anyway we can script this? 00:51:58 <jjmcd> And the publican in /usr/share/doc/HTML/<document-name>/<language> 00:52:06 <jjmcd> Yes, that is what the C program does 00:52:24 <jjmcd> You simply give it a publican directory and get an RPM 00:52:42 <sparks> cool 00:52:48 <sparks> You going to package it? 00:52:52 <jjmcd> The desktop files go in /usr/share/applications and /usr/share/applications/kde4 00:53:03 <jjmcd> I wasn't planning on it, but I suppose I could 00:53:20 <jjmcd> There is a pdf in there that has a gory description of the program 00:54:05 <jjmcd> I have 2 tars on my fedorapeople, one for the app and doc and another for the source 00:54:15 <sparks> cool 00:54:42 <jjmcd> I called it buildrpm. If I was going to package it I would rename it to something less generic 00:54:59 <sparks> ya 00:54:59 <jjmcd> like package-fedora-doc or something 00:55:32 <jjmcd> But if you build a guide in a few languages, you should be able to run it 00:55:39 <jjmcd> then install the rpm and try it out 00:55:52 <jjmcd> It packages what html 00:55:54 <jjmcd> s 00:55:58 <jjmcd> you have built 00:56:11 <jjmcd> so you can package any arbitrary collection of languages 00:56:38 <sparks> Cool 00:56:45 <jjmcd> It looks to find tmp/<lang>/html/index.html 00:57:13 <jjmcd> We should get David to review the spec it makes 00:57:33 <sparks> Yeah... That would be good 00:57:45 <jjmcd> In = publican directory plus a short config file, out=SRPM, RPM, spec 00:58:33 <sparks> Sounds good to me! 00:58:51 <jjmcd> read the pdf, altho it is kinda boring 00:59:39 <sparks> Okay... anything else? 00:59:39 <jjmcd> It does have pictures, tho 00:59:43 <jjmcd> nope 00:59:44 <sparks> Pictures? 00:59:46 <sparks> Cool 01:00:08 <sparks> Okay, anyone else? 01:00:10 <jjmcd> dot pictures, but pictures 01:00:53 <sparks> Does anyone have anything else they want to talk about? 01:01:19 <jjmcd> we put them to sleep 01:01:27 <sparks> I think so 01:01:38 <sparks> Okay, thanks for everyone coming! 01:01:41 <sparks> #endmeeting

1 0

Fedora Docs Meeting Reminder
by Eric Christensen 23 Dec '09

23 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The agenda can be found at: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLMhybAAoJEDbiLlqcYamxvZUQAIkyppKHM0GTv//G8H9MJrwi PnP7V1QyJ/o47A/n4KW540Zjy8RjlXCjdTUX6TeUd50wInzY6D+vg8VpTIET938+ veEiL6iWgPki0mDu20v/DnWxMacDLi83B86ykIgOU6jgox/D21iZx2qE07AWQaO/ 1NKl94qEK3R+bqid40CMF4+z3j6vgaiNx6SlFI8FHcU3sVXtex1JI6D4f1OVi0a7 db4gLCRtdGvCELHhHh3ouHsLwZuY01mgroitXsLhlfrNEkzpFXXxFHOcf4fdbqaZ 2Nq73hjsVBY6RM2QIpMgIAVXs+m9CRFiKsNLfhWfKvx+9QqFblrkf/+Hiwgy/qWf OLemBR0e0kiI9RV3j9YvKJe5cdC8++pEhkFD1PFljTBCGEebDZW8pSpAZoGetaZ5 PgtDYJa4IXVtYZWnngIFRkAhSGFuNdqYoZS6DzDR6XrQZp0CcfwVpyEFcJaVjkj/ 5RFJv68+ytzKj6qPAnOZGl1EcyCa+A6O8IxH4EaQAXPz7QqSUQrLdZl+HUTO67Lb ejKClfiLlCA9xF75V4segOLmx3VzlFi9bcSbLkybWshmxItt86GhoEHfedleYh1Z uSKERc0s9MKZIRkPj1eeW8elmLK9LT0ksRcG1a4NjNPHqNVllKbxF9uGBx4VM+Zq b8kJMRze2Rn3QBzRZQH0 =h80U -----END PGP SIGNATURE-----

1 0

Documentation schedule for F13
by Eric Christensen 23 Dec '09

23 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just got off of a phone conference with other Fedorians where we discussed the Documentation schedule for F13. Wish I could say it's ready for public consumption right now but it is still pretty ugly. I'm sure that John (poelcat) will have it out in a few days. We worked with Noriko on the translator schedule as well. One of the bigger changes that will be happening is that we have eliminated the freezes associated with Alpha and Beta. It will be a continuous work in progress. This has the benefit of allowing the translators to have time to translate the Release Notes as they are being developed and not having hundreds (thousands?) of lines of text made available to them with a short period of time to work. The same will be done for the Guides as well. F13 guide development started the day F12 was released so the new POT files should be made available to the translators now (pending the Transifex 0.7 upgrade). I hope this makes for a smoother process for this release. We will continue to tweak the process along the way as well. - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLMZOLAAoJEDbiLlqcYamxF+4P/2C4LPE9bUGurzDKPUbEnmRb +ARwIB4rpCt7N00PdQkiP4h2xYLAoBXfD7t3CjinmzllVdHga5cdkGMjcZLpmv/v UOBZs1vjwb3mZBb9oUFXwEAZW2rbPomW8rBNkthBS8TXxgvuphjZM4ysnE/uHtDy q6Wp/hzNYj1pyj2+edIZ5UO8KsYx9K8IvEEoheyj6m7Amm2PLj4YOw5+EPAYOo+/ IL7kBTDkBheXHv+T5BgR9bVlmUeq74V8QxUy543/olQsLSGm7Oc6TfUYYhRPOfQL QDtcR9E+pTG2RSKi99VHQZ5dmKfJLrhz0GDwbpnmyGCXCG4yOSFlj6ULOvnT8+P8 Uxe2Rh/b1ZDdVQkIiyL6WoCmYqQAKBEw/Mwr7RLAqhsBBS66o0jcS2CpWHkSlu3o 32D6CG7a3HLQR2SfXWIbg+Tu/5B585f8wH8M49zSFwkUgcH9XWCbowk4WYuFpEf9 W+YJ3mXEiSoGyGTicsS9bPhGvoLXCjvsxxja7i21QhV9cVjgQJLdbNHHXhcr5ujp aIt0gRiiNDLxrnfY9WgyAMwBUQ+7TUoGLCgOPtfaXtsau1vFwBjJ3lresrrHNMBV YDdmVlmDc+9IQXnfYF40VSLg4Q6oOYdoRjxA2qmR2heVPMSOUqrsJz3fOQmW6S8G rK8VYa3//cpG6OUcvp30 =0Z7p -----END PGP SIGNATURE-----

1 0

Documentation & Translation schedule review
by John Poelstra 22 Dec '09

22 Dec '09

In anticipation of the meeting suggested by Sparks on logistics list, I've created a text version of the schedule that should work well for customizing or using in gobby. http://poelstra.fedorapeople.org/schedules/f-13-draft/f-13-docs-trans-sched… This version is a combination of: 1) key milestones for the release as a whole (to provide context) 2) Documentation tasks 3) Translation tasks The most helpful feedback you can give me (at the meeting or elsewhere) is to provide corrections, additions, or deletions based on the version I've created. It does not help me if you create your own version from scratch and refer to it because then I have to start all over which is a big investment of time. A patch or diff against the original file works too. Thanks, John

4 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs December 2009