docs January 2010

docs@lists.stg.fedoraproject.org

16 participants
41 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

Docs Meeting 2010-01-28 Summary
by Eric Christensen 28 Jan '10

28 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by Sparks at 00:02:39 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-01-28/fedora-meeting.2… . Meeting summary - --------------- * Roll Call (Sparks, 00:02:45) * Meeting time (Sparks, 00:13:14) * LINK: http://whenisgood.net/docsmeeting1 (radsy, 00:17:16) * LINK: http://whenisgood.net/docsmeeting1/results/htkzrt (Sparks, 00:18:46) * F13 Release Schedule (Sparks, 00:25:02) * LINK: http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-and-trans-tasks.h… (Sparks, 00:25:06) * ACTION: jjmcd to complete the list of descrepancies for the F13 Release schedule and post the link to the list (Sparks, 00:27:30) * Desktop Help Summit (Sparks, 00:28:33) * LINK: http://live.gnome.org/DesktopHelpSummit2010 (Sparks, 00:28:40) * Release Notes (Sparks, 00:39:18) * Status on CMS (Zikula) (Sparks, 00:40:02) * LINK: https://fedoraproject.org/wiki/Zikula#Module_status (Sparks, 00:40:11) * Guide Status (Sparks, 00:42:24) * LINK: https://fedoraproject.org/wiki/Docs_F13_schedule (jjmcd, 00:43:39) * LINK: https://fedoraproject.org/wiki/Docs_F13_schedule (jjmcd, 00:44:26) * New Guides (Sparks, 00:45:56) * Outstanding BZ Tickets (Sparks, 00:47:01) * LINK: #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… (Sparks, 00:48:45) * Open floor (Sparks, 00:48:59) Meeting ended at 00:51:13 UTC. Action Items - ------------ * jjmcd to complete the list of descrepancies for the F13 Release schedule and post the link to the list Action Items, by person - ----------------------- * jjmcd * jjmcd to complete the list of descrepancies for the F13 Release schedule and post the link to the list * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * Sparks (76) * jjmcd (28) * shaunm (8) * radsy (5) * zodbot (3) * rudi (3) * nirik (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLYN/9AAoJEDbiLlqcYamxdxgQAKk9E7sbxLVZgSBj/pzosS3r gE5rRcSNrWnHzRM8BANXbCp8R2LyPJdAeV3L2/y8MkGo/ZVnBR1nE8ogjp7hgTbV fl02m5vPgpEjf2cCaVMDbrMr7vjIpN9QBqxhEt2lHuWbpCVabIi/vtHvP5R1SlWW L1O2+I1zb+cz4kri+M4im7VM0NkGJOR23w25Z9iel4bbmXop2Gz+7rHIXxQCAcnV Z2FYaFSCPCcofJz1tohI8frfcdjLfK4YmqXfQlRtlvnYBZZpgfg8iSLaJFlwadeW +r29cZWyn53kuWEBdJkMJuM1VuSKzC0/r5mTRU6VvWTeCKlQbkq0lnjbDV+xP+Oz VJrLP3FPmaem/bbaPRaZqqKgqBtaFz5fdA4M1TVS7nAbvmU/2tbbCWWM39Pjavrq oU2OOCu84hr9WBaDqvjK60aoLcmuUuLTwkMuFc9SrM8t2LnhmA7PybucMNdxHRv5 JyRQH5KVZN8ZxD6QnStP7yvYThUyyQxRP65zUIg4RLqiug2R4WstCXCQ/DwaoPk/ dF+H3QOzCbY3x9fkEHFfvj8KGyS994k6TJDz3AJ2os32nTtUGw6enyBGlnzSpGb5 F8SoMbpuj7FyGOXI444RLPzDgxaDS6Cr5zeEsUd8GDvBCoyv+w+6sVB6pbjlKDB8 0G1Wk+CF7wov6Jti8VVW =eynI -----END PGP SIGNATURE-----

2 1

Docs Meeting 2010-01-28 IRC log
by Eric Christensen 27 Jan '10

27 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 00:02:39 <Sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:02:39 <zodbot> Meeting started Thu Jan 28 00:02:39 2010 UTC. The chair is Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:02:39 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:02:45 <Sparks> #topic Roll Call 00:02:47 * Sparks 00:04:10 * radsy . 00:05:22 <Sparks> Where is everyone today? 00:05:37 <shaunm> I'm here, for once 00:05:49 <Sparks> shaunm: welcome! 00:07:17 <Sparks> Well, I'd hate to start the meeting with only three people, including myself, in attendance. 00:07:35 * radsy nudges rudi 00:07:53 <jjmcd> Yeah, rudi sleeping? 00:08:04 <Sparks> #chair jjmcd 00:08:04 <zodbot> Current chairs: Sparks jjmcd 00:08:28 <Sparks> well, rudi joined up just after radsy so he must be around 00:09:28 <Sparks> Apparently rudi can't talk in here 00:09:48 * nirik can change the channel to allow that for the meeting... 00:10:09 <jjmcd> Well, can't he identify? 00:10:21 <nirik> that should be an option too. ;) 00:10:22 <Sparks> nirik: Thank you. 00:10:32 <Sparks> Apparently it was telling him to identify himself 00:11:00 <jjmcd> Yeah, sometimes when there's been a bunch splits you seem to loose that identification 00:11:05 * rudi is here 00:11:09 <jjmcd> hey 00:11:12 <Sparks> rudi: Welcome! 00:11:13 <rudi> Hi :) 00:13:09 <Sparks> Okay, let's get started 00:13:14 <Sparks> #topic Meeting time 00:14:37 <Sparks> Since we haven't been getting the turnout to the meetings here I asked for everyone to go to whenisgood and tell us when is good. 00:14:43 <Sparks> Did everyone get a chance to do that? 00:15:00 <jjmcd> affirmative here 00:16:25 <Sparks> rudi, radsy, shaunm ? 00:16:35 <radsy> Sparks, just did it then 00:16:42 <rudi> Sparks -- no, I've been on vacation for a week; I'll take a look now 00:16:56 <Sparks> a week!?! Weren't you just off for three weeks? 00:17:16 <radsy> http://whenisgood.net/docsmeeting1 00:17:57 <shaunm> I did the whenisgood thing 00:18:16 <Sparks> Okay... Something is wrong... 00:18:39 <Sparks> For the sake of being open here are the results: 00:18:46 <Sparks> #link http://whenisgood.net/docsmeeting1/results/htkzrt 00:19:12 <Sparks> So when you see the results you will see that now is the best time for everyone but hardly anyone shows up. 00:19:20 <Sparks> So what's the problem? 00:19:46 <jjmcd> not enough powerpoints? 00:20:24 <shaunm> hooray, I'm at the top of the list! 00:20:52 <Sparks> heh 00:21:10 <Sparks> Seriously, though. This is a little crazy... 00:21:27 <Sparks> People say they can meet now but they don't. 00:22:15 <Sparks> I guess it's hard to ask you guys what's wrong because you guys keep coming back. 00:22:58 * jjmcd notes that a number of the missing seem to have had school pressures recently 00:23:32 <Sparks> maybe 00:23:57 <jjmcd> I doubt it constitutes a quorum tho 00:24:02 <Sparks> Okay, well I guess this is the best meeting time for everyone so we won't change it. Just wish I knew how to pack the seats more. 00:24:34 <Sparks> Okay, lets move on 00:24:38 <radsy> we're a little limited in Oz (+10) 00:24:55 <Sparks> radsy: Understood... But you guys are always on the ball... 00:24:56 <Sparks> :) 00:25:02 <Sparks> #topic F13 Release Schedule 00:25:06 <Sparks> #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-and-trans-tasks.h… 00:25:19 <Sparks> jjmcd: Were you able to review and make suggestions? 00:25:23 <Sparks> Is this now complete? 00:25:40 * jjmcd put together a page for all the guide owners to agree to their schedule 00:25:47 <jjmcd> haven't actually launched it tho 00:26:00 <jjmcd> seems like I've spent the last week driving through the snow 00:26:03 <Sparks> link? 00:26:08 <jjmcd> at least it feels that way 00:26:21 <jjmcd> It's in a draft now under User:jjmcd ... need to move it 00:26:49 <Sparks> Okay, when you get it squared away can you send the link to the list? 00:27:01 <jjmcd> Yeah, that was the plan 00:27:30 <Sparks> #action jjmcd to complete the list of descrepancies for the F13 Release schedule and post the link to the list 00:27:37 <Sparks> Okay, anything else on this topic? 00:28:33 <Sparks> #topic Desktop Help Summit 00:28:40 <Sparks> #link http://live.gnome.org/DesktopHelpSummit2010 00:28:47 <jjmcd> Docs_F13_Schedule 00:28:50 <Sparks> shaunm: Anything else on this topic? 00:29:49 <shaunm> no updates from me 00:30:20 <shaunm> I would appreciate if people would let me know their plans 00:30:24 <Sparks> Okay. 00:30:36 <Sparks> I think jjmcd is planning on going. Anyone else? 00:31:12 <shaunm> in particular, if there's more than one fedora person, whether you'd like to do anything together on monday 00:31:21 <jjmcd> heh - I realized I didn't update the page, now I can't remember my password 00:32:35 <shaunm> I can update it for you 00:33:36 <jjmcd> I plan to arrive fri nite, depart depending on plane connetcions, other fedorans there 00:34:01 <jjmcd> I'm guessing there won't be enough to make Mon worthwhile -- pity, too 00:34:33 <jjmcd> Oh, and Paul won't be there, Susan depending on her teaching sked 00:35:32 <Sparks> Anything else on this topic? 00:35:40 <jjmcd> Sparks, I assumeyou are still no? 00:35:46 <Sparks> jjmcd: At this time. 00:35:51 <jjmcd> R 00:36:23 <jjmcd> didn't jsmith indicate he might? 00:36:30 <Sparks> I don't remember 00:37:09 <shaunm> and quaid? 00:37:21 <Sparks> I don't remember about quaid either. 00:39:13 <Sparks> Okay... moving on 00:39:18 <Sparks> #topic Release Notes 00:39:24 <Sparks> jjmcd: Any update? 00:39:37 <jjmcd> nope 00:40:02 <Sparks> #topic Status on CMS (Zikula) 00:40:11 <Sparks> #link https://fedoraproject.org/wiki/Zikula#Module_status 00:40:43 <Sparks> I think mchua_afk wrote something on the infra list about Zikula being almost ready 00:40:47 <Sparks> But I'm not sure. 00:42:17 <Sparks> I don't have any other information so we'll just move along 00:42:24 <Sparks> #topic Guide Status 00:42:38 <Sparks> Anyone have anything they want to talk about in the topic of guides? 00:43:28 <jjmcd> Guide owners need to check schedule 00:43:37 <Sparks> Yes 00:43:39 <jjmcd> https://fedoraproject.org/wiki/Docs_F13_schedule 00:44:06 <jjmcd> mark your x 00:44:09 <Sparks> Of course the current item is to have POT files generated but without the new Transifex there isn't anywhere for those POTs to go 00:44:26 <jjmcd> #link https://fedoraproject.org/wiki/Docs_F13_schedule 00:44:34 <jjmcd> (keep meetbot happy!) 00:44:43 * Sparks likes the schedule page 00:45:18 <Sparks> Anything else? 00:45:56 <Sparks> #topic New Guides 00:46:01 <Sparks> Anyone have a new guide? 00:47:01 <Sparks> #topic Outstanding BZ Tickets 00:47:27 <Sparks> Looks like we have 109 tickets we are currently working. 26 of those are new and haven't been assigned. 00:48:12 <Sparks> I'm going to go through those tickets that are not assigned and assign them tonight. 00:48:39 <Sparks> Anytime you want to check to see what tickets need work, check out: 00:48:45 <Sparks> #link #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classificatio… 00:48:59 <Sparks> #topic Open floor 00:49:06 <Sparks> Anyone have anything else they want to talk about? 00:50:26 <Sparks> Okay... 00:50:40 <Sparks> Thanks for everyone coming out today! 00:50:52 <Sparks> Have a great week and we'll do it all over again next week. 00:51:13 <Sparks> #endmeeting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLYN/TAAoJEDbiLlqcYamx6g8P/1ALFj4h8Tsyi22U7AxV7Qkz CfLo8Y3IVibAeqO6T552lMWjWUy4sGyc/llWUeOicdEDmMcsDn0keyyRLXAtSsLU XYYTg67ft/Wwh0J29INy29zZlEYZ8BxPX1zHffv0QwDnMiSeMHpnnPGJovA0fZUm i3nCSzt+7v0ztvpY2AuR16a2zokMTPF1wRdyD74ch8xy983/kGq27uGKY7cgWSHE pZfb9JtKY71/jz/oIt4LAgLR/Snpq/HB7NC5nG6k8mv9q5xcNa1wNbCAfwYQU2NO l8rATzr+ChbUkgvRXXTe84j0UY6h1ypgneyFN+OrzQRswVD6OrwOsPqiS8EkBcge 0UdQRSkmC9ZUVQNBMFr+cs3e/tkxFSsN/BtwbRMl6TckY0eWKGrB8Qm++LHt6f2J XeDsnUhaIc5uLNsFzrzHVJiNUvPAaBGJ33CfM+Br9vf3qgDpjnIWr1Ks09qtkNXm hopq0PZ3yZuclLQu48eRgiIA2YV3E6hTCU0fn1pDx+Xzp+yA9gknXDc7hinIHCXV p0VI5Wr9aELqQA1zUJQa6Izs5lqn7TqPt6gH9Vbf1fCfBi5c4MGsalu7PIY8zGR7 jxyrIeewRysXVOSvkm73SrZ8eECR/TdVlmEa3lLntyC1meEmMTQVnZKuDAhSRNT6 7VP3svOb5tTWY5v4cdkW =qjNa -----END PGP SIGNATURE-----

1 0

Upcoming Fedora 13 Tasks
by John Poelstra 27 Jan '10

27 Jan '10

Start End Name Wed 18-Nov Tue 04-May Create POT files for All Guides

1 0

Docs Meeting Time
by Eric Christensen 26 Jan '10

26 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to "When is Good", the two best times during the week are 4P UTC on Tuesdays and our current meeting time. Of course there are people that said that they could make our current meeting time but seldom show up. My evenings are getting more and more packed with stuff so I'd personally like to move it to an afternoon. Opinions? Thoughts? - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLXwKLAAoJEDbiLlqcYamxaDsP/RDEYeKquAaX7toKw+mEBhOl YSg9ucbijdHVMxFZgKn5BTa5ovnECgpKIBjWPLWjZHYCm46IOIF/nlNtRjzAF6me dNktHZO0IKJQbbp5QtbWTbey9R20KJu8w53aTDMiGQRDwslisCEaRDWo4srpDWyc 4BMg4kyUeclWMyR6Cmyu4v4T8juuEIe+L3uxxoewT/WC32yq7bGhElbo3GXec+a9 eD7uHDzJILjzSbeURQ42lf9UoFbyMRU05T/ve4w1PUQYf9GqgpP0rPe4EQu7wh3D 7MKd5thpYoSRAmETjFO1oZgNBdb8P9SOpum22rNxl/I9dB86ER71sERMEGge5r9Q rn2wND2s99WLtQ4RwT/kGIvdzKEeEOzbNzoPlJJg2xNMO+Eji/vfbVy9Gu6UbOi2 6dvpWisgasNg1pqwxRnsibnBkuMr6NylupVq0b74U3M2kemqqTwHas051SI7I+ol /zO9vRdTwJHYrKiHXEMZH4fDJavNFprp+9L1nEnSdrp+CByDgWDVklC6mpXNx6AQ YgDSHkIayqJ1ABLw3xUwgqph+8o0Qhmyza74kOqWwnbtYadekcl6Rolc9FzzAne+ 3Tp0hpR3+mwtDHZGjriU9RnayFpyWRUmxvp0wzb8r9jrLRfzIwGsMtld5yhS3yZH kYL5owS8l8Bxjp9n7RHV =NHaH -----END PGP SIGNATURE-----

1 0

External review of the doc writing process
by Adam Williamson 25 Jan '10

25 Jan '10

Hey, folks. I thought you may be interested in some comments on the release documentation process and Docs wiki area which Christopher Beland happened to write up - the context was QA group reviewing how we document the process of having issues added to Release Notes / Installation Guide / Common Bugs. It may provide ideas for improvement :) Chris wasn't trying to bash the docs process, he just happened to take a look at it while looking into this issue for QA and make a few comments. ---- The Release Notes are maintained by the Docs Project, which I'm not a primary participant in. Their wikispace is a mess; there are a lot of obsolete pages that need to be cleared out, and current information that needs to be more cleanly organized. The release notes are pretty clearly the place for announcements about changes, and they get written mostly from scratch each cycle. https://fedoraproject.org/wiki/How_To_Contribute_to_the_Release_Notes lists "Six Ways of Submitting Content" which seems a bit crazy. I've not had much success (I think this was between alpha and beta) using the "Beats" process in the wiki, which are supposed to be rolled into release notes. I would really expect to see one page in the wiki somewhere that represents what the Fedora 13 release notes are going to look like, but right now there's just stuff from Fedora 12 marked as "this is final and has been sent for translation". What's actually *in* the Fedora 12 release notes is similar, but clearly a lot of editing has happened between the time it was taken from the wiki and the time it was released. I'm also not confident that methods that involve sending a message to a mailing list are reliable; Bugzilla reports are much better at persisting until someone actually deals with them. There are actually three release note issues in any given release cycle - alpha, beta, and final - each of which to me should build smoothly off the previous issue (adding new notes and deleting obsolete ones). It seems like in an ideal world, these would just live in the wiki, and at the appropriate times in the schedule, get translated and rendered into HTML or XML for publication on the web and in RPMs. Right now, I'm not confident that anything I put in the wiki would get added to the release notes, so I just file reports in Bugzilla and let the Docs team deal. This also seems to be the only way to change release notes after they've been finalized. Which might not be a bad thing, since you think there should be a high bar to changes at that point, but if that's the best route, it's probably best that the documentation reflect that. All of the other guides (Installation, SELinux, Deployment, etc. at http://docs.fedoraproject.org/) also seem to live in a version control system off-wiki, which if you ask me tends to create a bottleneck and discourage random people (like community QA participants) from contributing. A wiki, after all, is just a version control system that manages formatted text in a very user-friendly way. When documents are off-wiki, that also encourages the growth of redundant content in-wiki, which attracts attention and updates, further starving the off-wiki version of contributions. I suppose if the content must remain off-wiki for whatever reason, this could be avoided by squashing these redundant documents and leaving placeholders admonishing potential contributors to file bug reports against the off-wiki documentation instead. It seems right that bugs aren't mentioned in the guides or release notes, as that helps reduce clutter and centralize fast-changing information. Major bugs are fixed before release, and minor bugs are documented online in Common Bugs or Bugzilla, since the status of fixes and workarounds is dynamic. If the slow-changing documents all link to Common Bugs, that should work pretty well, unless you think people without network should have access to "known issues" in their copy of the distribution. That could be fixed by including a snapshot of "Common Bugs" in the fedora-release-notes RPM. There doesn't seem to be much point in updating it after the release except for re-spins (which are unofficial). If you don't have network access, the original version is accurate because you haven't gotten any updates. If you do have network access, you should get the online version, and so the RPM version would need to have a line at the top that says "This page was generated on [date]; for the latest known issues, workarounds, and fixes, please see [url]." ---- Full post: http://lists.fedoraproject.org/pipermail/test/2010-January/088137.html -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

Docs meeting time
by Eric Christensen 21 Jan '10

21 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In the last few months we've had very few people attending the Docs meetings. I'm guessing it might be because of the time. So if you want to be active in Docs please go to http://whenisgood.net/docsmeeting1 and click on the times that you are able to meet on a weekly basis. Thanks! - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJLWJm1AAoJEDbiLlqcYamxd2cP/R/qlcyO6Qs4P+bjIIMiX14V r2WShFnstU4MZJmS324cTTyuR7DY7Cdtpjjj2w86gXOgS8It3igDOi/P6/9JJV7G Xho7DEsscOr2NtPbqwP2LGjekM/zMXIkcRRSPTzoaVlUIb2utc/zLg0EBk/qqdzh nu0hRZKx6DXMbYjYUVGm9nIvRAO3yR81AGwTvYUoAeQ3aVfpJ1DdbIBqPlUcOCsk Ao98JqtqwL8bdN2IQBNRJbQuWPuLfaK4mTfkhK++xUtqUEWF7aNFGLll1mUVu28e 5R9Eidi4xJGJD/MyrL3VXwtq4i5+YSnDw2XzPEESD6apFg1PWMDJhQL6wzynN55f dybLCK0QIYNF1eh+gfx8mXL2FqjDdybfneAhbPItO3mGdZ8gN6ORMUbg3AoE5g8Z bUjAoVQQhhZ3ChbhuiLksGPRkVVmdZW1OPmQaBiOZ50dMubiO5B5tCm9yDwlYmDJ 3XCUBuLT3SHacmqyb5kQ9lUdoD8opNHuEKHMGEJv28kLCvnu1X+chMqPDxnOC3OA 2zKp6le376p7AyhScEJihJxFkb6h4NuQ7JAzqSKSQ075aOlRmQjdN3klah5Vnww1 r/E9elKj+F2MZXF8J94rhmYyfeCsieM4IP5WAOIZvV52Cz8ZnEnoly8hTyrMqHOj OCitbNFmagrIaX7KyMcv =YFgp -----END PGP SIGNATURE-----

1 0

[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

Docs Meeting 2010-01-21 IRC log
by John J. McDonough 20 Jan '10

20 Jan '10

00:01:45 <jjmcd> #startmeeting Docs Project Meeting 2010-01-21 00:01:45 <zodbot> Meeting started Thu Jan 21 00:01:45 2010 UTC. The chair is jjmcd. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:01:58 <jjmcd> #topic roll call 00:02:04 * jjmcd . 00:02:09 * quaid 00:02:21 * rudi is here but not with 100% attention... 00:03:19 <jjmcd> Sorry if a little disorganized. I only found out sparks was AWOL a couple minutes ago 00:03:39 <jjmcd> #topic F13 Release Schedule 00:03:46 * laubersm stands in the back 00:03:52 <jjmcd> #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-and-trans-tasks.h… 00:04:05 <jjmcd> Don't be hiding laubersm 00:04:23 <jjmcd> ANyone have any comments, difficulties etc with the F13 schedule? 00:05:03 <jjmcd> I was unable to find my notes for John and haven't had time to recreate them, but they weren't biggies anyway 00:05:38 <quaid> for the last release, were there any miscommunications 00:05:42 <quaid> or disconnects? 00:05:45 <jjmcd> Yes 00:05:48 <jjmcd> quite a few 00:05:58 <jjmcd> I think most got addressed in the new schedule 00:05:59 <quaid> do we need to get an actual affirmative from people about the schedule? 00:06:09 <quaid> "Put your name on this wiki page" or mark a checkbox or something? 00:06:38 <jjmcd> That might be worthwhile, although I suspect ianweller, danielsmw, ke4qqq and othere may or may not be here 00:06:58 <jjmcd> But there is a good idea quaid 00:07:22 <jjmcd> #action jjmcd will put up a wiki page for each of the content owners to agree to the schedule 00:07:44 <jjmcd> Everyone OK with that? 00:07:57 <laubersm> I think the larger communication issues were with other groups though... like releng needing the rpm before we were scheduled to build it.. 00:08:20 <laubersm> I'm good with the sched (as much as I have looked) and good with a wiki to get the people really involved to sign off 00:08:21 <jjmcd> Well, yeah. That was a biggie, and you better believe this time i triple checked 00:08:56 <jjmcd> And we will have some surprises this time since we are handling the L10N interface differently 00:09:33 <jjmcd> OK, anything else on the schedule? 00:10:18 <jjmcd> Moving on 00:10:24 <jjmcd> #topic Desktop Help Summit 00:10:40 <jjmcd> #link http://live.gnome.org/DesktopHelpSummit2010 00:10:52 <jjmcd> OK, it looks as if sparks might not be able to go 00:11:02 <laubersm> too far out on the schedule for me to say if I can be there. But it is not out of the question. 00:11:04 <jjmcd> laubersm, any news on whether you will make it? 00:11:10 <jjmcd> OK 00:11:24 <jjmcd> Is anyone else thinking about it? 00:11:34 <laubersm> Still even a possibilty I can get RH schedule me to teach up there before or after (thus covering plane at the same time) 00:11:59 <jjmcd> That would be a perfect scenario 00:12:08 <laubersm> They won't have the schedule together for a while (working on the first 2 weeks of Feb today) 00:12:22 <jjmcd> Right now I think I am the only for sure going, and we really should have two or three of us 00:12:45 <jjmcd> I told Max in a perfect world, rudi would be there but he didn't bite 00:12:55 <laubersm> :) 00:13:08 <rudi> lolz thanks anyway :) 00:13:33 <jjmcd> Well, especially without sparks it would be really good, but it is kind of a hike 00:14:04 <jjmcd> Anything else on the summit? 00:14:27 <jjmcd> Oh, I started to mention, Max did indicate he can make some funding available 00:14:58 <jjmcd> And we really should have more representation than me if Susan can't make it 00:15:51 <jjmcd> OK, moving on 00:16:08 <jjmcd> #topic Release Notes 00:16:30 <jjmcd> This one is quick. I did post a new updated test RPM if anyone wants to test 00:16:44 <jjmcd> I don't have the link right here but I did send it to the list 00:17:06 * quaid has to move networks (head home), bbi7m 00:17:13 <jjmcd> Paul made a good catch on the first one, but other than that 00:17:16 <jjmcd> Thanks quaid 00:17:37 <jjmcd> Any questions, updates, comments, concerns about release notes? 00:18:27 <jjmcd> #topic Status on CMS (Zikula) 00:18:35 <jjmcd> #link https://fedoraproject.org/wiki/Zikula#Module_status 00:18:57 <jjmcd> I'm not so sure we have any of the usual suspects here 00:19:05 <jjmcd> Any reports on Zikula? 00:20:02 <jjmcd> I guess not 00:20:13 <jjmcd> so 00:20:23 <jjmcd> #topic Guide Status 00:20:42 <jjmcd> rudi, any comments/updates on the guides? 00:21:01 <rudi> jjmcd -- nothing this week 00:21:11 <jjmcd> OK, anyone else on guides? 00:21:47 <jjmcd> #topic New Guides 00:22:04 <jjmcd> Anyone starting new guides? 00:23:21 <jjmcd> #topic All other business 00:23:22 <radsy> http://docs.fedoraproject.org/selinux-faq/ i'm updating that 00:23:30 <jjmcd> OK, here I do have something 00:24:23 <jjmcd> It looks as if sparks may be scarce for a little while here, I don't have any data on how long at this point, so if you see a leadership vacuum please don't be shy about stepping up 00:25:32 <jjmcd> Of course, under normal circumstances there is no need to be timid, but for now try to get over your timidity please 00:25:57 <jjmcd> Ahh, rasdy, sorry I middes that 00:26:16 <jjmcd> How are you coming? Need anything? 00:26:35 <radsy> nope, going fine - waiting for the next sync on that page, and adding a lot from dwalsh@ 00:26:57 <jjmcd> good deal 00:27:12 <jjmcd> I still need to do some recruiting for the ARG 00:27:15 <radsy> was considerably out-dated 00:27:40 <jjmcd> hehe - that is something that needs not only documentation, but also marketing 00:28:52 <radsy> i also had a couple of EOI for adding to the wireless-guide, but no email responses or IRC arrivals :( 00:29:10 <jjmcd> ahh 00:29:30 <jjmcd> I think a lot of people imagine that they aren't 31337 enough or something 00:30:14 <radsy> nothing else from me at this point 00:30:27 <jjmcd> Is there anything else for the good of the order? 00:30:51 <jjmcd> If you're thinking about going to Chicago, think harder! 00:31:29 <jjmcd> last call 00:31:43 <jjmcd> 9 00:31:46 <jjmcd> 8 00:31:52 <jjmcd> 7 00:31:56 <jjmcd> 6 00:32:01 <jjmcd> 5 00:32:01 <laubersm> 12 00:32:03 <laubersm> 42 00:32:04 <laubersm> hut 00:32:10 <jjmcd> 432 00:32:19 <jjmcd> #endmeeting

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs January 2010