From bugzilla at redhat.com Sun Nov 1 01:36:12 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 31 Oct 2009 21:36:12 -0400 Subject: [Bug 504067] Student mentoring In-Reply-To: References: Message-ID: <200911010136.nA11aCKw006803@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504067 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo? | --- Comment #3 from Eric Christensen 2009-10-31 21:36:11 EDT --- This is a tracker on the student mentoring project. Not sure it's been visited lately. -- 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. From r.landmann at redhat.com Sun Nov 1 06:30:52 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Sun, 01 Nov 2009 16:30:52 +1000 Subject: Fwd: [publican-list] Publican 1.0 nearly here Message-ID: <4AED2B1C.8030501@redhat.com> Hey all -- Publican 1.0 is very nearly here and addresses a large number of problems that we've all experienced with the 0.x versions of the tool. It's a lot faster too, which is always nice :) In general, members of the docs team should not be shy about upgrading to the new tool as it becomes available in your version of Fedora; Publican 1.0 includes functionality to help you migrate documentss from the old version to the new version. Furthermore, you can include the files necessarily to build in Publican 0 or Publican 1 in the same document -- it's not an either/or scenario. The only people who should *not* upgrade to the new Publican prior to the release of F-12 are those of us using Publican to build documents in languages other than English. Differences exist between the way that Publican 0 handled certain elements in PO files and the way that Publican 1 handles them. These changes have been made to make translators' jobs easier, but mean that some PO files translated for Publican 0 will require fine-tuning to build properly in Publican 1. Obviously, that's not something we should be doing for docs that are already frozen for translation! The User Guide for Publican 1.0 is available here, if you want to read up on what's ahead: http://rlandmann.fedorapeople.org/pug/ If there's any way that I can help you through the transition, please don't hesitate to ask! Cheers Ruediger -------- Original Message -------- Subject: [publican-list] Publican 1.0 nearly here Date: Sun, 01 Nov 2009 16:05:53 +1000 From: Ruediger Landmann Reply-To: Publican discussions To: Publican discussions The long-awaited Publican 1.0 and its brand package for Fedora will appear in Rawhide shortly. The current state for other versions of Fedora is as follows: Fedora 12 Packages built; Fedora 12 is currently in freeze prior to release. Fedora 11 Waiting on owner of docbook-style-xsl to build version>= 1.75.1 for F-11 -- https://bugzilla.redhat.com/show_bug.cgi?id=532258 Fedora 10 Waiting on owner of docbook-style-xsl to build version>= 1.75.1 for F-10 -- https://bugzilla.redhat.com/show_bug.cgi?id=532259 Waiting on owner of perl-Class-Trigger to build version>= 0.13 for F-10 -- https://bugzilla.redhat.com/show_bug.cgi?id=531969 Waiting on owner of perl-Syntax-Highlight-Engine-Kate to branch and build for F-10 -- https://bugzilla.redhat.com/show_bug.cgi?id=532278 Cheers Ruediger _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican From eric at christensenplace.us Sun Nov 1 20:05:59 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 1 Nov 2009 15:05:59 -0500 Subject: Attn Guide Leads: Update meeting agenda with your guide status. Message-ID: <20091101200558.GE2533@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like for all guide leads to update their guide status on the meeting agenda[1] in the appropriate location. I'd also like to ask that you be here for the meeting this week so we can make sure everything is squared away before the F12 release. [1] https://fedoraproject.org/wiki/Docs_Project_meetings Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrt6iYACgkQfQTSQL0MFMGpsQCfah9wehNnn6ah8UE1YEt6Ki93 U6YAoLIYqTCWWHu2vBkj/0Yil1/wznPw =+20+ -----END PGP SIGNATURE----- From noriko at redhat.com Mon Nov 2 06:09:56 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Mon, 02 Nov 2009 16:09:56 +1000 Subject: Guides changed to CC-BY-SA license. In-Reply-To: <4AEC61D9.4010500@gmail.com> References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> Message-ID: <4AEE77B4.9040202@redhat.com> Piotr Dr?g ????????: > W dniu 31.10.2009 17:06, Eric Christensen pisze: >> The Security Guide has been regenerated and posted on docs.fp.o in >> English and Spanish. The Dutch version is having problems being >> built, however, so this version hasn't been pushed. Also, the >> Security Guide package has been updated as well. >> >> I believe Rudi said that all other guides have been rebuilt and >> pushed to docs.fp.o. Can everyone verify that their package has been >> updated, please? Please post to the list what you find. >> > > Translation Quick Start Guide has not been regenerated for a long time. > Noriko, could you do that? All languages are correctly split into > smaller Publican files, they just need to be build with the newest > publican-fedora and push on web. > Done. Piort, thanks for your reminder! I have build errors to solve with es, pt_BR and uk, as well need some work to add uk and zh_TW as newly translated. To be continued... noriko From noriko at redhat.com Mon Nov 2 08:18:13 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Mon, 02 Nov 2009 18:18:13 +1000 Subject: Marketing stuff (e.g. flyers) translation In-Reply-To: <2f3d0f330911010710r20601376qdce917067c369d2e@mail.gmail.com> References: <2f3d0f330911010710r20601376qdce917067c369d2e@mail.gmail.com> Message-ID: <4AEE95C5.8080307@redhat.com> Zoltan Hoppar ????????: > Hi, > > I am one of the translators, but I am working also as Ambassador - and > I have run into an small problem. For Ambassadors, we have some texts, > flyers, and other materials (e.g. educational presentations) what > needs to be translated. Currently we have an wiki, where most of these > files are uploaded, but for us - these materials mostly available in > one language: English. > I would like to change this, and I need help to make it to reality - > also I know this possible project needs some cooperation between > several teams....Maybe this is not the correct channel to begin this. > > I have thought through several times, and I say it can be a huge step > ahead for ambassadors to win new contributors, when I could give the > interested people some printed advertising in their language. > Therefore I have thought on some empty prepared document templates at > in the ambassadors wiki for each actual release, and an Transifex > project category for these texts - available for all translating > teams. If it is possible, then I would to like have these in such a > format, that could be merged, edited to have at the end an perfect > multipliable DTP stuff easily. > Furthermore, I just hope, when this come truth - the ambassadors could > have these printings for shows sometime.... and we could win a lot of > contributors to every channel. > > I would like to hear your thoughts too, This is absolutely relevant channel to discuss :-) And I give +100 to make this happen, great idea. If this follows each release, you should contact John to include it into his release task schedule. So that translators will know when Ambassador's material is ready to translate and the deadline. It would also nice if advertising can include corresponding team information as well. #I actually asked the question to John if any translation request from Ambassador team at the beginning of F12. I am very happy to hear this movement. Thanks, Zoltan! noriko From stickster at gmail.com Mon Nov 2 14:03:57 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 2 Nov 2009 09:03:57 -0500 Subject: Strange piece in the release notes In-Reply-To: <19182.54385.623829.305308@freddi.uddeborg> References: <19182.54385.623829.305308@freddi.uddeborg> Message-ID: <20091102140357.GB28061@victoria.internal.frields.org> On Mon, Nov 02, 2009 at 01:45:37PM +0100, G?ran Uddeborg wrote: > In this message in the release notes, is really the parentheses meant > to be kept? It feels like an internal message within the doc team. > > #. Tag: para > #: FileSystems.xml:15 > #, no-c-format > msgid "" > "Fusecompress is a compressing filesystem mountable by " > "unprivileged users. (Note: this may mean we don't want this note in the " > "system admin section). Fedora-11 had fusecompress-1.99.19. Fedora-12 updates " > "to fusecompress-2.6. This fixes many very nasty bugs but changes the on-disk " > "format. Users with fusecompress filesystems will need to migrate their data " > "to the new format. Unless they decompress before upgrading, they will need " > "the fusecompress_offline1 package to do so." I think you're right and that text shouldn't be in the translatables that were sent out. I would caution the Docs team to only use admonitions for these sorts of comments (which will stick out like a sore thumb and beg for removal at the right time), or actual HTML comments that won't show up in the translatables (but which might be missed in review). -- 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 From piotrdrag at gmail.com Mon Nov 2 16:15:24 2009 From: piotrdrag at gmail.com (=?UTF-8?B?UGlvdHIgRHLEhWc=?=) Date: Mon, 02 Nov 2009 17:15:24 +0100 Subject: Guides changed to CC-BY-SA license. In-Reply-To: <4AEE77B4.9040202@redhat.com> References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> <4AEE77B4.9040202@redhat.com> Message-ID: <4AEF059C.6060605@gmail.com> W dniu 02.11.2009 07:09, Noriko Mizumoto pisze: > I have build errors to solve with es, pt_BR and uk, as well need some > work to add uk and zh_TW as newly translated. To be continued... > I have just fixed these errors. But it appears that license is still OPL on regenerated documents. Publican guys, could you please tell us how it can be fixed? -- Piotr Dr?g http://raven.pmail.pl From mel at redhat.com Mon Nov 2 16:28:14 2009 From: mel at redhat.com (Mel Chua) Date: Mon, 02 Nov 2009 11:28:14 -0500 Subject: Accessibility Guide In-Reply-To: <20091031155224.GA7049@desk.christensenplace.us> References: <20091031155224.GA7049@desk.christensenplace.us> Message-ID: <4AEF089E.4010503@redhat.com> On 10/31/2009 11:52 AM, Eric Christensen wrote: > I've contacted GNOME for information on their accessibility tools > that they ship with GNOME. I'll be doing the same with KDE. I'm > hoping I can get the necessary information on their tools, and maybe > some ready-made documentation, that would be beneficial. > > If anyone would like to help with this project or have some input > ready to go please let me know. There was a large gathering of open source accessibility folks at Toronto this past week - details at http://wiki.fluidproject.org/display/fluid/Open+Source+Accessibility. Hopefully there'll be some contact information in there, and details on their projects; I know there were some GNOME folks there and I would be surprised if someone from KDE wasn't also around. That's all I know about the event/group - only got to meet them briefly at dinner one night since I was at the Teaching Open Source section of things - but just in case it helps. --Mel From eric at christensenplace.us Mon Nov 2 16:45:00 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 2 Nov 2009 11:45:00 -0500 Subject: Accessibility Guide In-Reply-To: <4AEF089E.4010503@redhat.com> References: <20091031155224.GA7049@desk.christensenplace.us> <4AEF089E.4010503@redhat.com> Message-ID: On Mon, Nov 2, 2009 at 11:28, Mel Chua wrote: > On 10/31/2009 11:52 AM, Eric Christensen wrote: >> >> I've contacted GNOME for information on their accessibility tools >> that they ship with GNOME. ?I'll be doing the same with KDE. ?I'm >> hoping I can get the necessary information on their tools, and maybe >> some ready-made documentation, that would be beneficial. >> >> If anyone would like to help with this project or have some input >> ready to go please let me know. > > There was a large gathering of open source accessibility folks at Toronto > this past week - details at > http://wiki.fluidproject.org/display/fluid/Open+Source+Accessibility. > Hopefully there'll be some contact information in there, and details on > their projects; I know there were some GNOME folks there and I would be > surprised if someone from KDE wasn't also around. > > That's all I know about the event/group - only got to meet them briefly at > dinner one night since I was at the Teaching Open Source section of things - > but just in case it helps. > > --Mel Thanks Mel. I've been in communications with the GNOME Documentation Lead and he has been helping me out quite a bit. It looks like we might be working together on this project. This will allow some of our documentation to go back upstream to GNOME. The biggest problem, right now, is that their documents are being transitioned from GFDL to CC and the accessibility documents are still GFDL which means they can't use our information and we can't use theirs, yet. I still need to connect with the KDE folks, too. Thanks for the link. I'll take a look at the information you provided. --Eric From eric at christensenplace.us Mon Nov 2 16:45:45 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 2 Nov 2009 11:45:45 -0500 Subject: Guides changed to CC-BY-SA license. In-Reply-To: <4AEF059C.6060605@gmail.com> References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> <4AEE77B4.9040202@redhat.com> <4AEF059C.6060605@gmail.com> Message-ID: On Mon, Nov 2, 2009 at 11:15, Piotr Dr?g wrote: > W dniu 02.11.2009 07:09, Noriko Mizumoto pisze: >> >> I have build errors to solve with es, pt_BR and uk, as well need some >> work to add uk and zh_TW as newly translated. To be continued... >> > > I have just fixed these errors. But it appears that license is still OPL > on regenerated documents. Publican guys, could you please tell us how it > can be fixed? > > -- > Piotr Dr?g > http://raven.pmail.pl > Update to the latest publican-fedora brand package. That should fix the licensing issues. --Eric From atmb4u at gmail.com Tue Nov 3 18:18:48 2009 From: atmb4u at gmail.com (Anoop Thomas Mathew) Date: Tue, 3 Nov 2009 23:48:48 +0530 Subject: Self-Introduction Message-ID: *Hi all,* I am Anoop Thomas Mathew, interested to be a part of fedora pride. You may check out my profile description at https://fedoraproject.org/wiki/User:Atmb4u . I have previous experience in VIM and Scribus projects. Though I don't have a direct documentation experience. I have been using fedora and other open source since 2004, and started open source development early 2006. I am pretty well in documentation and technical writing. I am a good graphic designer, also a user interface designer. Also, I have the skill to make the other person understand through words. Last but not least, Experience is the best teacher. I would like to work with fedora documentations, and become keen in documenting softwares. I would like to be a part of fedora documentation,user interface and front end designer groups. _________________________________________________________________ [atm at localhost ~]$ gpg --fingerprint 8A1D9C6B pub 1024R/8A1D9C6B 2009-11-02 Key fingerprint = B1DE 5EB1 BF1E EA3C FCCF 5FCD FE32 E0E4 8A1D 9C6B uid Anoop Thomas Mathew _________________________________________________________________ looking forward to hear from you all soon, Anoop Thomas Mathew atm ___ College of Engineering Chengannur Samuel Goldwyn - "I'm willing to admit that I may not always be right, but I am never wrong." -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at christensenplace.us Wed Nov 4 12:10:50 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 4 Nov 2009 07:10:50 -0500 Subject: Meeting Reminder - 05 Nov 2009 Message-ID: <20091104121048.GA2266@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 MEETING REMINDER: Tonight the Docs Project will hold its regular meeting at 0001UTC in #fedora-meeting. The agenda[1] is already on the wiki. If you have any changes to make to the agenda please do so no later than 23:30UTC. Please remember that this might be a time change for some people that just came off of Daylight Savings Time. [1] https://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_November_05.2C_2009_.28Wed_US_Time.29 Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrxb0gACgkQfQTSQL0MFMGgbwCgxml+83IsFwUI2BswMkJkaOo8 Nx0AmgNS4n5CBfI7lZd4C7t39M6c3JPw =/eS5 -----END PGP SIGNATURE----- From noriko at redhat.com Wed Nov 4 13:07:36 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Wed, 04 Nov 2009 23:07:36 +1000 Subject: Guides changed to CC-BY-SA license. In-Reply-To: References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> <4AEE77B4.9040202@redhat.com> <4AEF059C.6060605@gmail.com> Message-ID: <4AF17C98.9060105@redhat.com> Eric Christensen ????????: > On Mon, Nov 2, 2009 at 11:15, Piotr Dr?g wrote: > >> W dniu 02.11.2009 07:09, Noriko Mizumoto pisze: >> >>> I have build errors to solve with es, pt_BR and uk, as well need some >>> work to add uk and zh_TW as newly translated. To be continued... >>> >>> >> I have just fixed these errors. But it appears that license is still OPL >> on regenerated documents. Publican guys, could you please tell us how it >> can be fixed? >> >> -- >> Piotr Dr?g >> http://raven.pmail.pl >> >> > > Update to the latest publican-fedora brand package. That should fix > the licensing issues. > After update to 1.0-0 (from 0.18-0), I am unable to build at all.... need some time to find the cause. Pls allow me some time. noriko From piotrdrag at gmail.com Wed Nov 4 17:33:32 2009 From: piotrdrag at gmail.com (=?UTF-8?B?UGlvdHIgRHLEhWc=?=) Date: Wed, 04 Nov 2009 18:33:32 +0100 Subject: Guides changed to CC-BY-SA license. In-Reply-To: <4AF17C98.9060105@redhat.com> References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> <4AEE77B4.9040202@redhat.com> <4AEF059C.6060605@gmail.com> <4AF17C98.9060105@redhat.com> Message-ID: <4AF1BAEC.9080603@gmail.com> W dniu 04.11.2009 14:07, Noriko Mizumoto pisze: > Eric Christensen ????????: >> Update to the latest publican-fedora brand package. That should fix >> the licensing issues. > After update to 1.0-0 (from 0.18-0), I am unable to build at all.... > need some time to find the cause. Pls allow me some time. > Sure. :) The cause is simple. Documents written with Publican 0.x in mind (like TQSG) are not buildable with Publican 1.0. Eric was probably thinking about the latest publican-fedora brand package from F11 updates (which is 0.19-3 in this moment and is proven to work with TQSG), not 1.0. I hope this would help you! -- Piotr Dr?g http://raven.pmail.pl From eric at christensenplace.us Wed Nov 4 17:42:36 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 4 Nov 2009 12:42:36 -0500 Subject: Guides changed to CC-BY-SA license. In-Reply-To: <4AF1BAEC.9080603@gmail.com> References: <20091031160613.GA7651@desk.christensenplace.us> <4AEC61D9.4010500@gmail.com> <4AEE77B4.9040202@redhat.com> <4AEF059C.6060605@gmail.com> <4AF17C98.9060105@redhat.com> <4AF1BAEC.9080603@gmail.com> Message-ID: On Wed, Nov 4, 2009 at 12:33, Piotr Dr?g wrote: > W dniu 04.11.2009 14:07, Noriko Mizumoto pisze: >> >> Eric Christensen ????????: >>> >>> Update to the latest publican-fedora brand package. That should fix >>> the licensing issues. >> >> After update to 1.0-0 (from 0.18-0), I am unable to build at all.... >> need some time to find the cause. Pls allow me some time. >> > > Sure. :) > > The cause is simple. Documents written with Publican 0.x in mind (like > TQSG) are not buildable with Publican 1.0. Eric was probably thinking > about the latest publican-fedora brand package from F11 updates (which > is 0.19-3 in this moment and is proven to work with TQSG), not 1.0. I > hope this would help you! > > -- > Piotr Dr?g > http://raven.pmail.pl I was not thinking about 1.0. Yeah, Publican 1.0 docs are... different. I think the official release is coming to a Fedora near you but right now it isn't ready for production. --Eric From poelstra at redhat.com Thu Nov 5 00:49:18 2009 From: poelstra at redhat.com (John Poelstra) Date: Wed, 04 Nov 2009 16:49:18 -0800 Subject: Upcoming schedule tasks Message-ID: <4AF2210E.6000102@redhat.com> Start End Name Tue 03-Nov Mon 09-Nov Build GA release note htmls for Translation Tue 03-Nov Mon 09-Nov Review and correct GA Release Notes (daily builds html) Thu 05-Nov Thu 12-Nov Daily builds of guides for Translation Mon 09-Nov Mon 09-Nov F12 Blocker Review (go/no go) 3 PM EDT Mon 09-Nov Tue 10-Nov Build fedora-release-notes.rpm Wed 11-Nov Wed 11-Nov F12 Project Wide Release Readiness Meeting Wed 11-Nov Fri 13-Nov Create GA Announcement Fri 13-Nov Fri 13-Nov Final Build All Guides: All Languages Mon 16-Nov Tue 17-Nov Port publican to fh.o/rel-notes Tue 17-Nov Tue 17-Nov GA Release Tue 17-Nov Wed 18-Nov 0-Day rel-notes generate POT Tue 17-Nov Wed 18-Nov 0-Day rel-notes build updated rpm Tue 17-Nov Wed 18-Nov 0-Day rel-notes update docs.fp.org From eric at christensenplace.us Thu Nov 5 01:09:26 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 4 Nov 2009 20:09:26 -0500 Subject: Docs Meeting 2009-11-05 IRC Log Message-ID: <20091105010855.GA11748@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 00:00:44 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:00:44 Meeting started Thu Nov 5 00:00:44 2009 UTC. The chair is Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:01:18 #topic Roll Call 00:01:20 * Sparks 00:01:26 * jjmcd . 00:01:26 * rudi is here 00:03:02 Wow ... where are all the troublemakers and ne'er do wells? 00:03:44 jjmcd: That's just what I was thinking 00:04:04 prolly missed the time change 00:04:26 jjmcd: Yeah, it's going to be a little annoying for a couple of weeks 00:04:41 Okay, let's get started as we have a lot to cover... 00:04:50 #topic Old Business 00:04:51 Well, MITN moved to 6 on account of conditions so no conflict there 00:05:02 Sparks to follow up with quaid to check on courtesy note to previous contributors 00:05:17 ^^^ done and I'll follow up on this during the CC discussion 00:05:29 #topic Release Announcement 00:05:39 To be ready no later than November 10. 00:06:05 We need to get with Marketting on this and make sure that everyone is on the same page. 00:06:26 who is mktg contact? 00:06:32 Can I get a volunteer to work with Marketting to make sure everything good? 00:06:43 jjmcd: I think mchua_afk 00:06:50 But I don't know 00:07:23 Anyone? 00:07:52 * jjmcd is concerned about zero day RN issues overlapping with reporting time of month which is normally bad 00:08:07 Ya 00:08:17 Okay, I'll put the word out on the list. 00:08:32 #action Follow up with mktg on the Release Announcement. 00:08:49 #topic Guide Status - Release Notes 00:08:56 jjmcd: What's the latest? 00:09:05 Let me relate what went on 00:09:09 it was a disaster 00:09:24 Asyou know our schedule had us building the rpm a week after it was needed 00:09:45 When I first tried to build it, I had a terrible time with the omfs, not sure why 00:10:04 even now, there is a lot of weirdness about bits of the omfs being translated and others not 00:10:25 haven't yet sorted out what is causing that -- right now there appears to be no pattern 00:10:58 Once I got the omfs to work, yelp would crash 2-5 minutes after opening the rn's whether you were looking around or not 00:11:30 Eventually concluded yelp has some sort of size limitation, so I replaced the tables with a link to docs.fp.o 00:11:51 Also, stupid publican doesn't make the index for xml, just says "index belongs here" essentially 00:12:18 and at one point, all the xml's had a note saying they were empty. Don't know where that came from or why it went away 00:12:54 Anyway, eventually got the help to work, but when you go to about-fedora directly from the menu, as opposed to from help, it isn't formatted properly 00:13:30 Interestingly, the publican produced xml is kind of screwed up, but help seems to deal with it. Fixing the screw ups, tho, doesn't change anything 00:14:01 Anyway, as you know, we encountered pub 1.0 on koji, so we worked around it by runing publican outside of rpmbuild 00:14:26 We will need to do that for zero day, too. Really not much of a problem except when you discover it an hour before you need the rpm! 00:14:36 So, that;s where we are. Any questions? 00:14:59 So many with so little time. 00:15:15 that was last night! 00:15:30 But the package got built in koji and we lived happily ever after... until zero day... right? 00:15:36 right 00:15:48 Not everything we wanted 00:16:14 tables are linked to instead of there, a-f from menu screwy, and help titles partly translated 00:16:22 Okay, but everything is on target for the release day, correct? 00:16:28 correct 00:16:34 Okay... moving on! :) 00:16:36 We will fiz what we can on zero day 00:16:51 But we won't try the make inside rombuild until next rel 00:17:02 #topic Guide Status - Installation Guide 00:17:29 rudi: I guess you are up. Is the Installation Guide ready for prime time? 00:17:51 Good to go 00:18:13 Excellent. 00:18:25 #topic Guide Status - Installation Quick Start Guide 00:18:33 jjmcd: And I'm guessing this is ready as well? 00:18:38 rudi: And I'm guessing this is ready as well? 00:18:55 * jjmcd has no idea about iqsg 00:18:55 Yep :) 00:19:15 #topic Guide Status - Deployment Guide 00:19:38 I don't think the lead is on tonight for the Deployment Guide. 00:19:49 Is that up on docs.fp.o? 00:19:59 Yeah -- it's up there 00:20:27 Yeah, just checked. In English... 00:20:34 rudi, were you going to have the redirect pages ready for release? 00:20:51 jjmcd -- yeah, I will 00:21:06 #topic Guide Status - User Guide 00:21:07 I started that last week and ended up toasting my entire local copy of the site ;) 00:21:15 rudi: Yikes! 00:21:23 don't you just love that 00:21:26 danielsmw: You here tonight? 00:22:08 Hmmm... Well I see it on the docs.fp.o for F12... 00:22:12 Yeah -- I got bit because I forgot that different docs have entirely different directory structures :) 00:22:12 I'll take that as a good sign. 00:22:26 rudi: We need to remedy that. 00:22:43 We need to be sure we don't do that on zikula 00:22:47 yes 00:22:54 #topic Guide Status - 00:22:57 Fixing it in cvs will be a major pita 00:23:00 #topic Guide Status - SELinux User Guide 00:23:15 radsy: What say you on your SELinux guide(s)? 00:23:16 jjmcd -- yeah; I am *not* going to volunteer for that job :) 00:23:44 Sparks, services guide didn't get an update for f12 00:23:54 radsy: Did it need an update? 00:24:05 no, it's all still accurate/recent 00:24:11 I'm good with that. 00:24:29 rudi: Can you make sure that the F12 docs include radsy's guides on SELinux? 00:24:36 i've been doing the wireless guide, and might be branching into desktop documentation, so i'm likely to be in and out a bit. 00:24:57 radsy: No problem. Just let us know where we can help! 00:25:10 #topic Guide Status - Security Guide 00:25:31 Sparks -- will do 00:25:33 Very little changed from F11 to F12 in this guide. I have started working on improvements for F13, though. 00:25:37 rudi: Thank you 00:25:50 #topic Guide Status - Virtualization Guide 00:26:00 Tsagadai: You here tonight? 00:26:20 sure am 00:26:34 Tsagadai: Got an update on your Virtualization Guide? 00:26:42 I've been preoccupied with the RHEV release :) 00:27:02 but, there are a lot of updates coming very shortly (hopefully this week) 00:27:22 Tsagadai: But it's ready for F12, correct? 00:27:34 ready in a sense 00:27:50 Well okay then! :) 00:28:24 Tsagadai: Thanks for the update. Let us know if any assistance is needed. 00:28:42 #topic Guide Status - Fedora Live Images 00:28:51 I see this is on the website... 00:28:55 rudi: Is this yours? 00:29:09 Not officially, no 00:29:21 But since no-one else was tending it, I've been looking after it :) 00:29:21 rudi: Are any of them officially yours? :) 00:29:32 lolz IG and IQSG :) 00:29:48 rudi: Ya... Another one of those that is on my rescue list. Thanks for picking it up. 00:30:01 rudi: So it's out there for F12 so that's good 00:30:06 And yes, it's ready to go :) 00:30:15 Excellent! 00:30:23 #topic Guide Status - Making Fedora Discs 00:30:31 rudi: And this one is also ready to go! 00:30:36 Yeah 00:30:44 Excellent. 00:30:57 #topic Guide Status - Accessibility Guide 00:31:03 And this is one that I picked up... 00:31:26 It needs work. It was very well written years ago but some of the information is dated and there are new solutions available now. 00:31:54 So I've been working on a reorganization with the help of rudi fact checking the existing information. 00:32:16 I don't think it will be ready before F12 but it will be available somewhere between F12 and F13 for sure. 00:32:31 #topic Guide Status - Overall Picture 00:33:03 I just want to take a second and say thank you to everyone that contributed to the many guides we have. 00:33:25 Without the Accessibility Guide, we will have nine guides going to "press" for F12! 00:33:30 That is outstanding! 00:33:49 We should have a Docs press release alongside the F12 press release 00:34:00 We should! 00:34:04 +1 00:34:18 I'll have to go back in my notes but I think we shipped maybe five guides last release. 00:34:19 hey! there is life in kalifornia 00:34:27 * quaid blames tardiness on daylight savings 00:34:29 * ianweller is here 00:34:52 #topic New Guides 00:35:01 radsy: You want to talk about your new projects? 00:36:38 radsy is AFK 00:36:42 Okay 00:36:58 Well, I'll let him tell the tale. 00:37:46 Anything else guide-related? 00:38:20 #topic Status on CMS (Zikula) 00:38:29 #link https://fedoraproject.org/wiki/Zikula#Module_status 00:39:20 I think danielsmw finished packaging one of the editors. 00:39:42 Does anyone else have any other items on this? 00:40:20 Okay, moving on! 00:40:27 #topic Status on CC license rollout. 00:40:41 #link https://fedoraproject.org/wiki/License_changeover_schedule 00:41:02 So I think we are ready to officially announce the change to CC-BY-SA! 00:42:16 ianweller: You gonna do the announcement? 00:42:51 suuuuuuure 00:43:13 Sparks: everything's done? 00:43:28 ianweller: AFAIK 00:43:34 back 00:43:42 quaid: Any other obsticles that you know of? 00:43:42 front 00:43:50 nope 00:43:52 right 00:43:55 all clear! 00:44:00 Guides have been regenerated... wiki has been changed 00:44:14 Guides now all in rpm as well? 00:44:29 I think spot has given us the go ahead. 00:44:41 * quaid . o O { The final pieces of The Master Plan are coming together! } 00:44:41 i'll make the announcement after the meeting then 00:44:47 lemee go double check where it is 00:44:48 oops, did I think that outloud? 00:44:50 jjmcd: The only guides in RPM are f-r-n and the Security Guide and I did the Security Guide the other day 00:44:54 https://fedoraproject.org/wiki/User:Ianweller/Creative_Commons_press_release ? 00:45:17 anybody have any qualms about what we're sending out 00:45:50 #link https://fedoraproject.org/wiki/User:Ianweller/Creative_Commons_press_release 00:45:55 oh my gosh! You're going to send out THAT? 00:46:16 jjmcd: Yeah, except we are going to put your name on it. 00:46:24 oh, ok 00:46:40 ianweller: Do we (you) need to talk with the CC folks directly about this so they can do something if they wish? 00:46:57 lovin the we (you) 00:47:04 Sparks: i'll ping mlinksvayer 00:47:08 ianweller: You are my resident CC guy 00:47:13 ianweller: Cool 00:47:17 * Sparks is excited! 00:47:24 and he *just* quit IRC 00:47:26 lulz 00:47:26 did that go through 00:47:42 the *new" press release mojo of f-marketing-l? 00:47:54 * quaid mixes his ASCII markup 00:48:05 quaid: yeah mchua_afk looked at it 00:48:17 So I'll mark 8 complete 00:48:19 snazzed it up 00:49:52 oh 00:49:53 So is everyone a go for the license change? Any issues we haven't thought of? 00:50:13 also note that mlinksva offered to provide a quote for the press release (i just reread the email he sent me a few months back) 00:50:21 if we wanna do that? 00:50:24 I only changed the omf's for those languages we are shipping 00:50:27 +1 00:50:27 ianweller: Sure if you want. 00:50:42 we'll do that, and then push the PR through all the relevant tubez 00:50:51 There may be other omf footprints hidden in f-r-n, about-fedora and others 00:51:00 errr OPL footprints 00:51:28 jjmcd: Okay. I'm sure we'll need to shake out a few here and there. 00:51:33 yeah 00:51:40 I was surprised to find that there last night 00:52:03 yeah, it's not going to kill us 00:52:15 if we have to take some bug reports and fix some packages after release 00:52:21 the intention is clear and our there, that counts a lot 00:52:25 You only find it if you go rummaging around in /usr/share/gnome as far as I can tell 00:53:27 Okay, anything else on this topic? 00:53:53 #action ianweller to get a quote from mlinksva (CC) to include in the press release 00:54:10 #action ianweller to ship the press release to all the necessary tubez 00:54:22 ianweller: When do you think this will occur? 00:54:27 "soon" 00:54:36 announcement tonight, maybe a quote back from mlinksva by tomorrow 00:54:37 Before the end of the year? 00:54:37 who knows 00:54:44 then i'll ask mel about pushing through tubez 00:54:45 Okay. :) 00:54:56 Does RH handle that? 00:54:56 hehe hopefully before january ;) 00:54:59 i dunno. 00:55:05 yeah, we can ask for an RHT hand-off 00:55:10 i really have no clue, and i'm hoping mchua_afk does ;) 00:55:11 there is the business wire stuff 00:55:15 and the press.redhat.com 00:55:18 and/or coordinate it 00:55:23 cool. 00:55:26 yeah, she does; there is likely an SOP on it somewhere 00:55:52 #action ianweller to coordinate with mchua_afk on the press release 00:55:57 Okay, anything else? 00:56:40 #topic New Guides 00:56:55 Going back to this topic because I'm excited by some of radsy's work 00:57:02 radsy: Tell us about your new projects 00:57:04 please 00:57:21 ok 00:57:33 I've been silently working on a wireless guide: http://sradvan.fedorapeople.org/Wireless_Guide/en-US/html-single/ 00:57:52 mainly a high-level overview of 802.11 stuff, but other mobile tech (ev-do, hsdpa etc.) will end up in there 00:58:29 started as a side project really but has gained a bit of attention here, which could lead me to doing desktop/network docs, especially emerging desktop tech 00:58:45 but we're still in talks to find out priorities/agendas, etc. 00:58:46 that's all 00:59:07 I've read the WG and it's cool. 00:59:20 radsy: Is the guide hosted on fhosted.o? 00:59:26 Sparks, not as yet 00:59:42 radsy: Okay. Do you need a BZ component for handling tickets? 01:00:04 once i'm a bit happier with it, yes I will 01:00:23 radsy: Okay, just let me know and we'll get you setup. 01:00:23 no rush straight away however 01:00:26 ok 01:00:35 Anyone have any questions? 01:01:08 Okay, thanks radsy! 01:01:29 #topic Outstanding BZ Tickets 01:01:42 #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW 01:01:56 There are currently 9 new bugs that have not been assigned. 01:02:17 Please visit the link above and see if you can handle one (or more) of these tickets, please. 01:02:59 #topic All other business 01:03:06 Okay, does anyone have anything else? 01:03:43 Anyone? 01:03:45 Anything? 01:04:47 Okay, then we'll go ahead and close down tonight. 01:04:51 Thanks everyone for coming! 01:04:57 Keep up the excellent work! 01:05:01 #endmeeting - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkryJacACgkQfQTSQL0MFMGCigCgpa+MEXOfAnii3cpKtV0jePHX rlQAn0t33eyEirhc+MygbUJ3iD5uHF/U =1F+I - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkryJcUACgkQfQTSQL0MFMGIyQCfaiAhepLD27i4yzgY8kAnBbXf t4MAn1aJlb04a9S0S15OIsg6IKqF00oV =aaXe -----END PGP SIGNATURE----- From eric at christensenplace.us Thu Nov 5 01:10:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 4 Nov 2009 20:10:52 -0500 Subject: Docs Meeting 2009-11-05 Summary Message-ID: <20091105011051.GB11748@desk.christensenplace.us> -----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:00:44 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2009-11-05/fedora-meeting.2009-11-05-00.00.log.html . Meeting summary - --------------- * Roll Call (Sparks, 00:01:18) * Old Business (Sparks, 00:04:50) * Release Announcement (Sparks, 00:05:29) * ACTION: Follow up with mktg on the Release Announcement. (Sparks, 00:08:32) * Guide Status - Release Notes (Sparks, 00:08:49) * Guide Status - Installation Guide (Sparks, 00:17:02) * Guide Status - Installation Quick Start Guide (Sparks, 00:18:25) * Guide Status - Deployment Guide (Sparks, 00:19:15) * Guide Status - User Guide (Sparks, 00:21:06) * Guide Status - (Sparks, 00:22:54) * Guide Status - SELinux User Guide (Sparks, 00:23:00) * Guide Status - Security Guide (Sparks, 00:25:10) * Guide Status - Virtualization Guide (Sparks, 00:25:50) * Guide Status - Fedora Live Images (Sparks, 00:28:42) * Guide Status - Making Fedora Discs (Sparks, 00:30:23) * Guide Status - Accessibility Guide (Sparks, 00:30:57) * Guide Status - Overall Picture (Sparks, 00:32:31) * New Guides (Sparks, 00:34:52) * Status on CMS (Zikula) (Sparks, 00:38:20) * LINK: https://fedoraproject.org/wiki/Zikula#Module_status (Sparks, 00:38:29) * Status on CC license rollout. (Sparks, 00:40:27) * LINK: https://fedoraproject.org/wiki/License_changeover_schedule (Sparks, 00:40:41) * LINK: https://fedoraproject.org/wiki/User:Ianweller/Creative_Commons_press_release ? (ianweller, 00:44:54) * LINK: https://fedoraproject.org/wiki/User:Ianweller/Creative_Commons_press_release (Sparks, 00:45:50) * ACTION: ianweller to get a quote from mlinksva (CC) to include in the press release (Sparks, 00:53:53) * ACTION: ianweller to ship the press release to all the necessary tubez (Sparks, 00:54:10) * ACTION: ianweller to coordinate with mchua_afk on the press release (Sparks, 00:55:52) * New Guides (Sparks, 00:56:40) * Outstanding BZ Tickets (Sparks, 01:01:29) * LINK: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW (Sparks, 01:01:42) * All other business (Sparks, 01:02:59) Meeting ended at 01:05:01 UTC. Action Items - ------------ * Follow up with mktg on the Release Announcement. * ianweller to get a quote from mlinksva (CC) to include in the press release * ianweller to ship the press release to all the necessary tubez * ianweller to coordinate with mchua_afk on the press release Action Items, by person - ----------------------- * ianweller * ianweller to get a quote from mlinksva (CC) to include in the press release * ianweller to ship the press release to all the necessary tubez * ianweller to coordinate with mchua_afk on the press release * **UNASSIGNED** * Follow up with mktg on the Release Announcement. People Present (lines said) - --------------------------- * Sparks (140) * jjmcd (45) * ianweller (26) * quaid (17) * rudi (15) * radsy (14) * Tsagadai (4) * zodbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkryJhsACgkQfQTSQL0MFMEAbgCgtpKIxxssCM/bHfA0RCqeNzUE bloAn1UOpFZOZU9xdEXCSkXEb0NxZwPm =xU34 -----END PGP SIGNATURE----- From laubersm at fedoraproject.org Thu Nov 5 02:00:14 2009 From: laubersm at fedoraproject.org (Susan Lauber) Date: Wed, 4 Nov 2009 21:00:14 -0500 Subject: User Guide update / Re: Docs Meeting 2009-11-05 Message-ID: Rudi, RE: User's Guide update for F12 I've got some time early next week - maybe over the weekend - not before. Make it idiot proof and I'll help - ie assign me a unit or three and I'll see if I can't get them updated. oh - and make sure I know what branch I am supposed to be working on in git. I already have (or had last release) commit to the git and I've got a F12 test box handy. -Susan 00:21:06 #topic Guide Status - User Guide 00:21:07 I started that last week and ended up toasting my entire local copy of the site ;) 00:21:15 rudi: Yikes! 00:21:23 don't you just love that 00:21:26 danielsmw: You here tonight? 00:22:08 Hmmm... Well I see it on the docs.fp.o for F12... 00:22:12 Yeah -- I got bit because I forgot that different docs have entirely different directory structures :) 00:22:12 I'll take that as a good sign. 00:22:26 rudi: We need to remedy that. 00:22:43 We need to be sure we don't do that on zikula 00:22:47 yes > > * Guide Status - User Guide ?(Sparks, 00:21:06) > -- Susan Lauber, (RHCX, RHCA, RHCSS) Lauber System Solutions, Inc. http://www.laubersolutions.com gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 From eric at christensenplace.us Fri Nov 6 00:35:38 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 5 Nov 2009 19:35:38 -0500 Subject: Self-Introduction - atmb4u In-Reply-To: References: Message-ID: <20091106003537.GB3057@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Nov 03, 2009 at 11:48:48PM +0530, Anoop Thomas Mathew wrote: > *Hi all,* > > I am Anoop Thomas Mathew, interested to be a part of fedora pride. You may > check out my profile description at > https://fedoraproject.org/wiki/User:Atmb4u . > > I have previous experience in VIM and Scribus projects. Though I don't have > a direct documentation experience. > > I have been using fedora and other open source since 2004, and started open > source development early 2006. I am pretty well in documentation and > technical writing. > > I am a good graphic designer, also a user interface designer. Also, I have > the skill to make the other person understand through words. > > Last but not least, Experience is the best teacher. I would like to work > with fedora documentations, and become keen in documenting softwares. > > I would like to be a part of fedora documentation,user interface and front > end designer groups. > > _________________________________________________________________ > [atm at localhost ~]$ gpg --fingerprint 8A1D9C6B > pub 1024R/8A1D9C6B 2009-11-02 > Key fingerprint = B1DE 5EB1 BF1E EA3C FCCF 5FCD FE32 E0E4 8A1D 9C6B > uid Anoop Thomas Mathew > > _________________________________________________________________ > > looking forward to hear from you all soon, > Anoop Thomas Mathew > > atm > ___ > College of Engineering Chengannur > Welcom Anoop. You caught us at one of two busy times of the year. Being less than two weeks from general release of a new version has us on our toes and working to get new documentation ready for production. Please join us on IRC[1] on Thursdays at 0001 UTC in #fedora-meeting for our weekly Docs Project meeting. We also hang out in #fedora-docs to work on projects. Please take a look at our finished guides[2] and our in-development guides[3] as they are our primary workload right now. Glad to have you aboard! [1] https://fedoraproject.org/wiki/How_to_communicate_using_IRC [2] http://docs.fedoraproject.org [3] https://fedoraproject.org/wiki/Docs_Project_meetings#Guides - --Eric Fedora Docs Project Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrzb1kACgkQfQTSQL0MFMHc3gCfaRzDV+SFDBtm8RIfUml78Ahb 5iwAn1l2//p9Jee/XPzp8VIcqyruxMdB =ATH8 -----END PGP SIGNATURE----- From bugzilla at redhat.com Fri Nov 6 13:19:24 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 6 Nov 2009 08:19:24 -0500 Subject: [Bug 533327] "Fedora_11" should be "Fedora_12" in urls for Fedora 12 beta In-Reply-To: References: Message-ID: <200911061319.nA6DJOVR005440@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533327 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwade at redhat.com, | |stickster at gmail.com Component|homepage |project-tracking AssignedTo|stickster at gmail.com |fedora-docs-list at redhat.com QAContact|kwade at redhat.com |eric at christensenplace.us -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From amarnathjmsc at gmail.com Fri Nov 6 16:44:57 2009 From: amarnathjmsc at gmail.com (Amarnath Jayaraman) Date: Fri, 06 Nov 2009 22:14:57 +0530 Subject: Self Introduction Message-ID: <4AF45289.8020009@gmail.com> Dear All, This is Amarnath Jayaraman. I am really looking forward to contribute and take some responsibility in Fedora Projects. I have registered for Fedora Install and SELinux Guide Git Commit Group. At present i am working as a Linux System administrator. I have worked on Linux Distros like Red Hat , Fedora , CentOS , Debian as well as Ubuntu. 1) In the past i have participated and conducted lot of IT related technology topics. As well as i have done many paper presentation . 2) I have an Master Level Computer Skills ( I Have Completed RHCE 4 , RHCE 5 and CCNA) 3) System Administration Tasks, Soft Skills and Seminar Presentation 4) As i have presented more seminars and papers as well as i am doing by Master of Philosophy and i can help the newbies and other linux user by my small contribution as documents and guides., this makes me to work under the Leading Open Source fedora projects Thanks & Regards, https://fedoraproject.org/wiki/User:Amarnathj GPG fingerprint = 730A B221 8B92 3E8E 1A33 A5B4 D3EC 82E0 DB38 C748 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 552 bytes Desc: OpenPGP digital signature URL: From bugzilla at redhat.com Fri Nov 6 20:17:05 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 6 Nov 2009 15:17:05 -0500 Subject: [Bug 533327] "Fedora_11" should be "Fedora_12" in urls for Fedora 12 beta In-Reply-To: References: Message-ID: <200911062017.nA6KH5R5021329@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533327 Ruediger Landmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED --- Comment #2 from Ruediger Landmann 2009-11-06 15:17:04 EDT --- Thanks for the catch -- that's fixed now and should show up the next time that the server syncs up. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From eric at christensenplace.us Fri Nov 6 22:00:09 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 6 Nov 2009 17:00:09 -0500 Subject: Self Introduction In-Reply-To: <4AF45289.8020009@gmail.com> References: <4AF45289.8020009@gmail.com> Message-ID: <20091106220007.GA2507@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Nov 06, 2009 at 10:14:57PM +0530, Amarnath Jayaraman wrote: > Dear All, > > This is Amarnath Jayaraman. I am really looking forward to > contribute and take some responsibility in Fedora Projects. I have > registered for Fedora Install and SELinux Guide Git Commit Group. At > present i am working as a Linux System administrator. I have worked on > Linux Distros like Red Hat , Fedora , CentOS , Debian as well as Ubuntu. > > 1) In the past i have participated and conducted lot of IT related > technology topics. As well as i have done many paper presentation . > > 2) I have an Master Level Computer Skills ( I Have Completed RHCE 4 , > RHCE 5 and CCNA) > 3) System Administration Tasks, Soft Skills and Seminar Presentation > 4) As i have presented more seminars and papers as well as i am doing by > Master of Philosophy and i can help the newbies and other linux user by > my small contribution as documents and guides., this makes me to work > under the Leading Open Source fedora projects > > Thanks & Regards, > > https://fedoraproject.org/wiki/User:Amarnathj > GPG fingerprint = 730A B221 8B92 3E8E 1A33 A5B4 D3EC 82E0 DB38 C748 > Welcome aboard, Amarnath. I think I got you straightened out with all the groups. Glad to see you are so excited to help with the install guide. - --Eric Docs Project Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkr0nGYACgkQfQTSQL0MFMHkZwCeJncFqBH+eRRUrovHHzKueyQR fAUAn1BUa9P5ge73hHqN12+ezi8X7s5z =g2QK -----END PGP SIGNATURE----- From r.landmann at redhat.com Sat Nov 7 08:22:21 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Sat, 07 Nov 2009 18:22:21 +1000 Subject: Self Introduction In-Reply-To: <4AF45289.8020009@gmail.com> References: <4AF45289.8020009@gmail.com> Message-ID: <4AF52E3D.6080809@redhat.com> On 11/07/2009 02:44 AM, Amarnath Jayaraman wrote: > This is Amarnath Jayaraman. I am really looking forward to > contribute and take some responsibility in Fedora Projects. I have > registered for Fedora Install and SELinux Guide Git Commit Group. Hi Amarnath and welcome aboard! Is there something in particular that you'd like to help out with on the Installation Guide? (For example, any errors that you're aware of?) The Installation Guide is pretty stable at the moment (and the SELinux Guide too, I think), meaning that there's not much work to do here. Nevertheless, if you'd specifically like to help out with the Installation Guide, probably the best thing you could do would be to take a look at its abbreviated version -- the Installation Quick Start Guide[1] -- and review it to make sure that the instructions work for you. It's always good to have a fresh set of eyes test the instructions to make sure that we've explained things correctly. If you find any problems, the guide also provides instructions for reporting these (so you can test those instructions at the same time!) If you're more interested in writing new material rather than reviewing or maintaining stable documents, please let us know that as well; particularly if you've thought of a useful piece of documentation that we don't provide to our users yet. But don't worry -- if you want to work on new documentation but don't have any plans yet, there are certainly areas where we could use your help. Once again, welcome, and feel free to have a chat in IRC when we're actually in there at the same time :) Cheers Rudi [1] http://docs.fedoraproject.org/installation-quick-start-guide/f12/en-US/html/ From domingobecker at gmail.com Sat Nov 7 13:52:55 2009 From: domingobecker at gmail.com (Domingo Becker) Date: Sat, 7 Nov 2009 10:52:55 -0300 Subject: moreinfo option in xml tags in deployment guide Message-ID: <4818cd80911070552h5f2794b4l2144fcbd3d97ba95@mail.gmail.com> There are thousands of strings marked fuzzy in the deployment guide and the only difference is the following: msgid "the string in English" msgstr "the string in Spanish" Is it safe to remove the fuzzy tag without removing the " moreinfo=\"none\""? I guess the moreinfo option will not be used anyway in the publican tools. The translations are correct. k.r. Domingo Becker (es) From eric at christensenplace.us Sun Nov 8 19:14:07 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 8 Nov 2009 14:14:07 -0500 Subject: Accessibility Guide Update Message-ID: <20091108191406.GB4488@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hard to believe but I've actually had time to work on the Accessibility Guide. Still trying to get all the GNOME stuff into the guide, though. GNOME has lots of information but it is spread out all over the place. I doubt I can get this out before the F12 release BUT I'm going to try to release some version of the guide shortly there after. I need a couple of things to make this happen, however. I need fact checkers, docbook editors, and a grammar editor. I'm going to work on the fact checking but I don't write as much as some do in docbook so I might be missing some tags. Could someone take a look at the current markup and check things out? It shouldn't take long as the guide isn't comprehensive and is only a few pages (eight in PDF). Thanks! - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkr3GH4ACgkQfQTSQL0MFMGFsQCfSL4Cxr4oUyKvmy1nWSOujCFF fSkAniMs3lnuBRW6d38S2oJXd72xbXOE =VcRX -----END PGP SIGNATURE----- From bugzilla at redhat.com Sun Nov 8 20:25:40 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 8 Nov 2009 15:25:40 -0500 Subject: [Bug 533737] New: Recommend changing the Feedback statement to include the component name. Message-ID: 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 at redhat.com ReportedBy: eric at christensenplace.us QAContact: extras-qa at fedoraproject.org CC: jfearn at redhat.com, fedora-docs-list at redhat.com, nb at fedoraproject.org, mmcallis at redhat.com, r.landmann at redhat.com Classification: Fedora Eric Christensen 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. From bugzilla at redhat.com Sun Nov 8 20:55:17 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 8 Nov 2009 15:55:17 -0500 Subject: [Bug 533741] New: License should be CC-BY-SA instead of Open Publication Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: License should be CC-BY-SA instead of Open Publication https://bugzilla.redhat.com/show_bug.cgi?id=533741 Summary: License should be CC-BY-SA instead of Open Publication Product: Fedora Version: 12 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: publican-fedora AssignedTo: jfearn at redhat.com ReportedBy: eric at christensenplace.us QAContact: extras-qa at fedoraproject.org CC: jfearn at redhat.com, fedora-docs-list at redhat.com, nb at fedoraproject.org, mmcallis at redhat.com, r.landmann at redhat.com Classification: Fedora Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |review? Created an attachment (id=368076) --> (https://bugzilla.redhat.com/attachment.cgi?id=368076) Proposed patch for defaults.cfg Description of problem: When building a package in Publican 1.x the spec file shows a license of Open Publication instead of CC-BY-SA. 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. From laubersm at fedoraproject.org Sun Nov 8 21:56:59 2009 From: laubersm at fedoraproject.org (Susan Lauber) Date: Sun, 8 Nov 2009 16:56:59 -0500 Subject: Accessibility Guide Update In-Reply-To: <20091108191406.GB4488@desk.christensenplace.us> References: <20091108191406.GB4488@desk.christensenplace.us> Message-ID: On Sun, Nov 8, 2009 at 2:14 PM, Eric Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hard to believe but I've actually had time to work on the Accessibility Guide. ?Still trying to get all the GNOME stuff into the guide, though. ?GNOME has lots of information but it is spread out all over the place. > > I doubt I can get this out before the F12 release BUT I'm going to try to release some version of the guide shortly there after. ?I need a couple of things to make this happen, however. ?I need fact checkers, docbook editors, and a grammar editor. ?I'm going to work on the fact checking but I don't write as much as some do in docbook so I might be missing some tags. ?Could someone take a look at the current markup and check things out? ?It shouldn't take long as the guide isn't comprehensive and is only a few pages (eight in PDF). I have a little time to look at it... now If I only knew where to find it.... :) -Susan > > Thanks! > > - --Eric > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkr3GH4ACgkQfQTSQL0MFMGFsQCfSL4Cxr4oUyKvmy1nWSOujCFF > fSkAniMs3lnuBRW6d38S2oJXd72xbXOE > =VcRX > -----END PGP SIGNATURE----- > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -- Susan Lauber, (RHCX, RHCA, RHCSS) Lauber System Solutions, Inc. http://www.laubersolutions.com gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 From stickster at gmail.com Mon Nov 9 01:15:29 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 9 Nov 2009 11:15:29 +1000 Subject: Accessibility Guide Update In-Reply-To: References: <20091108191406.GB4488@desk.christensenplace.us> Message-ID: <20091109011529.GG6242@victoria.internal.frields.org> On Sun, Nov 08, 2009 at 04:56:59PM -0500, Susan Lauber wrote: > On Sun, Nov 8, 2009 at 2:14 PM, Eric Christensen > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hard to believe but I've actually had time to work on the Accessibility Guide. ?Still trying to get all the GNOME stuff into the guide, though. ?GNOME has lots of information but it is spread out all over the place. > > > > I doubt I can get this out before the F12 release BUT I'm going to try to release some version of the guide shortly there after. ?I need a couple of things to make this happen, however. ?I need fact checkers, docbook editors, and a grammar editor. ?I'm going to work on the fact checking but I don't write as much as some do in docbook so I might be missing some tags. ?Could someone take a look at the current markup and check things out? ?It shouldn't take long as the guide isn't comprehensive and is only a few pages (eight in PDF). > > I have a little time to look at it... now If I only knew where to find it.... > > :) Hi Susan, I think what you want is here: https://fedorahosted.org/accessibility-guide/ -- 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 From laubersm at fedoraproject.org Mon Nov 9 01:25:12 2009 From: laubersm at fedoraproject.org (Susan Lauber) Date: Sun, 8 Nov 2009 20:25:12 -0500 Subject: Accessibility Guide Update In-Reply-To: <20091109011529.GG6242@victoria.internal.frields.org> References: <20091108191406.GB4488@desk.christensenplace.us> <20091109011529.GG6242@victoria.internal.frields.org> Message-ID: On Sun, Nov 8, 2009 at 8:15 PM, Paul W. Frields wrote: > On Sun, Nov 08, 2009 at 04:56:59PM -0500, Susan Lauber wrote: >> On Sun, Nov 8, 2009 at 2:14 PM, Eric Christensen >> wrote: >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > Hard to believe but I've actually had time to work on the Accessibility Guide. ?Still trying to get all the GNOME stuff into the guide, though. ?GNOME has lots of information but it is spread out all over the place. >> > >> > I doubt I can get this out before the F12 release BUT I'm going to try to release some version of the guide shortly there after. ?I need a couple of things to make this happen, however. ?I need fact checkers, docbook editors, and a grammar editor. ?I'm going to work on the fact checking but I don't write as much as some do in docbook so I might be missing some tags. ?Could someone take a look at the current markup and check things out? ?It shouldn't take long as the guide isn't comprehensive and is only a few pages (eight in PDF). >> >> I have a little time to look at it... ?now If I only knew where to find it.... >> >> :) > > Hi Susan, I think what you want is here: > > ?https://fedorahosted.org/accessibility-guide/ thanks Paul! I did find it - once I found my back to the Docs Project category in the wiki and the Guides table I found the link. Mainly I was poking at Eric for asking us to take a look but not providing a link.. I also found Eric on IRC about the same time... -Susan > > > -- > 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 > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -- Susan Lauber, (RHCX, RHCA, RHCSS) Lauber System Solutions, Inc. http://www.laubersolutions.com gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 From eric at christensenplace.us Mon Nov 9 01:43:54 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 8 Nov 2009 20:43:54 -0500 Subject: Accessibility Guide Update In-Reply-To: References: <20091108191406.GB4488@desk.christensenplace.us> <20091109011529.GG6242@victoria.internal.frields.org> Message-ID: <20091109014353.GC9755@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Nov 08, 2009 at 08:25:12PM -0500, Susan Lauber wrote: > On Sun, Nov 8, 2009 at 8:15 PM, Paul W. Frields wrote: > > On Sun, Nov 08, 2009 at 04:56:59PM -0500, Susan Lauber wrote: > >> On Sun, Nov 8, 2009 at 2:14 PM, Eric Christensen > >> wrote: > >> > -----BEGIN PGP SIGNED MESSAGE----- > >> > Hash: SHA1 > >> > > >> > Hard to believe but I've actually had time to work on the Accessibility Guide. ?Still trying to get all the GNOME stuff into the guide, though. ?GNOME has lots of information but it is spread out all over the place. > >> > > >> > I doubt I can get this out before the F12 release BUT I'm going to try to release some version of the guide shortly there after. ?I need a couple of things to make this happen, however. ?I need fact checkers, docbook editors, and a grammar editor. ?I'm going to work on the fact checking but I don't write as much as some do in docbook so I might be missing some tags. ?Could someone take a look at the current markup and check things out? ?It shouldn't take long as the guide isn't comprehensive and is only a few pages (eight in PDF). > >> > >> I have a little time to look at it... ?now If I only knew where to find it.... > >> > >> :) > > > > Hi Susan, I think what you want is here: > > > > ?https://fedorahosted.org/accessibility-guide/ > > > thanks Paul! > > I did find it - once I found my back to the Docs Project category in > the wiki and the Guides table I found the link. > Mainly I was poking at Eric for asking us to take a look but not > providing a link.. Oh that doesn't sound like anything I'd do... - -Eric > I also found Eric on IRC about the same time... > > -Susan > > > > > > > -- > > 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 > > > > -- > > fedora-docs-list mailing list > > fedora-docs-list at redhat.com > > To unsubscribe: > > https://www.redhat.com/mailman/listinfo/fedora-docs-list > > > > > > -- > Susan Lauber, (RHCX, RHCA, RHCSS) > Lauber System Solutions, Inc. > http://www.laubersolutions.com > gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkr3c9kACgkQfQTSQL0MFMEmqgCgrdz3n9RNO8GBIFsoWg+OlnEk 0QgAniYFlawb6/KTLoIpJpzXQQcXId5e =pK6i -----END PGP SIGNATURE----- From bugzilla at redhat.com Mon Nov 9 02:20:34 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 8 Nov 2009 21:20:34 -0500 Subject: [Bug 533741] License should be CC-BY-SA instead of Open Publication In-Reply-To: References: Message-ID: <200911090220.nA92KYuW019004@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533741 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jfearn at redhat.com |rlandman at redhat.com --- Comment #1 from Jeff Fearn 2009-11-08 21:20:29 EDT --- Rudi, this is the license field in defaults.cfg of the brand. -- 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. From poelstra at redhat.com Tue Nov 10 05:21:29 2009 From: poelstra at redhat.com (John Poelstra) Date: Mon, 09 Nov 2009 21:21:29 -0800 Subject: Final Fedora 12 Schedule Tasks Message-ID: <4AF8F859.30804@redhat.com> Start End Name Tue 03-Nov Mon 09-Nov Build GA release note htmls for Translation Tue 03-Nov Mon 09-Nov Review and correct GA Release Notes (daily builds html) Thu 05-Nov Thu 12-Nov Daily builds of guides for Translation Mon 09-Nov Mon 09-Nov F12 Blocker Review (go/no go) 3 PM EDT Mon 09-Nov Tue 10-Nov Build fedora-release-notes.rpm Wed 11-Nov Wed 11-Nov F12 Project Wide Release Readiness Meeting Wed 11-Nov Fri 13-Nov Create GA Announcement Fri 13-Nov Fri 13-Nov Final Build All Guides: All Languages Mon 16-Nov Tue 17-Nov Port publican to fh.o/rel-notes Tue 17-Nov Tue 17-Nov GA Release Tue 17-Nov Wed 18-Nov 0-Day rel-notes generate POT Tue 17-Nov Wed 18-Nov 0-Day rel-notes build updated rpm Tue 17-Nov Wed 18-Nov 0-Day rel-notes update docs.fp.org From kwade at redhat.com Tue Nov 10 16:41:40 2009 From: kwade at redhat.com (Karsten Wade) Date: Tue, 10 Nov 2009 08:41:40 -0800 Subject: [gdk@redhat.com: [TOS] Textbook sprint today, 1pm - 4pm eastern US time] Message-ID: <20091110164140.GA8457@calliope.phig.org> For those who don't know, we're working via teachingopensource.org on a textbook, "Practical Open Source Software Engineering," for how to teach participating in open source projects. It's a textbook aimed at instructors teaching classes where FLOSS participation might happen -- could be software, but could be other disciplines. Anyway, another writing sprint happening today. http://en.flossmanuals.net/bin/view/PracticalOSSEngineering I'll be working on the documentation chapter again today. Stop by if you are interested and find out what we are doing; you are welcome to leap right in. ----- Forwarded message from Greg DeKoenigsberg ----- Date: Tue, 10 Nov 2009 09:53:15 -0500 (EST) From: Greg DeKoenigsberg To: tos at teachingopensource.org Subject: [TOS] Textbook sprint today, 1pm - 4pm eastern US time X-BeenThere: tos at teachingopensource.org Hello all. For those interested -- in participating, watching, heckling -- we will have a TOS textbook sprint today. Join us on irc.freenode.net, #teachingopensource, at 1pm. --g -- Computer Science professors should be teaching open source. Help make it happen. Visit http://teachingopensource.org. _______________________________________________ tos mailing list tos at teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos ----- End forwarded message ----- -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From poelstra at redhat.com Tue Nov 10 21:57:02 2009 From: poelstra at redhat.com (John Poelstra) Date: Tue, 10 Nov 2009 13:57:02 -0800 Subject: dmraid in install guide Message-ID: <4AF9E1AE.7070402@redhat.com> I came across this and wondering if we have addressed it in the install guide or if it still needs to be chased down. https://fedoraproject.org/wiki/Anaconda/Features/MDRaid#Documentation John From ricky at fedoraproject.org Wed Nov 11 12:40:17 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Wed, 11 Nov 2009 07:40:17 -0500 Subject: [kerry@wsr.com: broken link on home page] Message-ID: <20091111124017.GD16826@alpha.rzhou.org> Hi, somebody reported a blank release notes index page linked from fedoraproject.org. Does anybody know why http://docs.fedoraproject.org/release-notes/f11/ is blank now? I think there used to be a language selection page there back during the F11 release, but it'd be nice to make something available there for now to fix the broken link (we could change the website link, but then all language pages would point to the English document, which isn't that great). Also, will there still be index/language selection pages for specific documents? While http://docs.fedoraproject.org/ has language selection dropdowns for all documents right now, we sometimes want to link specifically to one particular document from he website, like for the release notes, or the install guide on the download page. Thanks, Ricky ----- Forwarded message from richard ----- From: richard To: webmaster at fedoraproject.org Cc: Date: Wed, 11 Nov 2009 03:09:17 -0700 Subject: broken link on home page Hello, On the Fedora Home Page (http://fedoraproject.org/index.html) there is a link to the release notes. What's new in Fedora 11? Read the release notes. >> where is this supposed to take me? I assume it is supposed to go to http://docs.fedoraproject.org/ but it does not, it takes me to a blank page. Richard. -- Fedora-websites-list mailing list Fedora-websites-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-websites-list ----- End forwarded message ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Wed Nov 11 13:30:49 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 11 Nov 2009 08:30:49 -0500 Subject: [kerry@wsr.com: broken link on home page] In-Reply-To: <20091111124017.GD16826@alpha.rzhou.org> References: <20091111124017.GD16826@alpha.rzhou.org> Message-ID: <20091111133047.GC2338@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Nov 11, 2009 at 07:40:17AM -0500, Ricky Zhou wrote: > Hi, somebody reported a blank release notes index page linked from > fedoraproject.org. Does anybody know why > http://docs.fedoraproject.org/release-notes/f11/ is blank now? I think > there used to be a language selection page there back during the F11 > release, but it'd be nice to make something available there for now to > fix the broken link (we could change the website link, but then all > language pages would point to the English document, which isn't that > great). Rudi was working a new solution. That URL should have been redirected to docs.fp.o, I think, where you could make the selection on format and language. It's still a work in progress... We could probably put the Release Notes specific links on that page, though. > > Also, will there still be index/language selection pages for specific > documents? While http://docs.fedoraproject.org/ has language selection > dropdowns for all documents right now, we sometimes want to link > specifically to one particular document from he website, like for the > release notes, or the install guide on the download page. To point to a specific format and language all guides should be in the following format: guide/f##/lang/format. This is not necessarily true for ALL documents so you'll have to check the link to verify. Hopefully F13 will use that format for all docs, though. > > Thanks, > Ricky - --Eric > > > ----- Forwarded message from richard ----- > > From: richard > To: webmaster at fedoraproject.org > Cc: > Date: Wed, 11 Nov 2009 03:09:17 -0700 > Subject: broken link on home page > > Hello, > On the Fedora Home Page (http://fedoraproject.org/index.html) there is a link > to the release notes. > What's new in Fedora 11? Read the release notes. >> > where is this supposed to take me? > I assume it is supposed to go to http://docs.fedoraproject.org/ but it does > not, it takes me to a blank page. > > Richard. > > > -- > Fedora-websites-list mailing list > Fedora-websites-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-websites-list > > > ----- End forwarded message ----- > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkr6vIcACgkQfQTSQL0MFMHrlACgo/vq38N2EhDMQ+VH7G8VBFak mKMAn2FGofRP5KUBpLmjIPkzLH3rbe+o =EwX5 -----END PGP SIGNATURE----- From wb8rcr at arrl.net Wed Nov 11 14:08:20 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 11 Nov 2009 09:08:20 -0500 Subject: [kerry@wsr.com: broken link on home page] References: <20091111124017.GD16826@alpha.rzhou.org> <20091111133047.GC2338@desk.christensenplace.us> Message-ID: ----- Original Message ----- From: "Eric Christensen" Subject: Re: [kerry at wsr.com: broken link on home page] > To point to a specific format and language all guides > should be in the following format: guide/f##/lang/format. > This is not necessarily true for ALL documents so you'll > have to check the link to verify. Hopefully F13 will use > that format for all docs, though. The proliferation of languages, formats and documents has made the old structure of docs.fp.o somewhat untenable. rudi put together the new, much friendlier format. Unfortunately, not all the "functionality" of the old format has been retained, and without a significant development effort, replacing that capability becomes a significant maintenance burden. It would be reasonable to provide some automation for a single document, but since no two documents seem to use the same naming/directory structure, such an effort would have to be on a per document basis. It might seem to make more sense to restructure the site so there was some consistency, but given the number of documents/formats/languages and the slowness of cvs that turns out to be a huge job. The answer has been "wait for zikula", but every day that seems to be a little farther off. I guess I feel some pressure to do "something" at least for release notes. No promises, though. --McD From ricky at fedoraproject.org Wed Nov 11 20:07:42 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Wed, 11 Nov 2009 15:07:42 -0500 Subject: [kerry@wsr.com: broken link on home page] In-Reply-To: References: <20091111124017.GD16826@alpha.rzhou.org> <20091111133047.GC2338@desk.christensenplace.us> Message-ID: <20091111200741.GE16826@alpha.rzhou.org> On 2009-11-11 09:08:20 AM, John J. McDonough wrote: > The proliferation of languages, formats and documents has made the old > structure of docs.fp.o somewhat untenable. rudi put together the new, > much friendlier format. Unfortunately, not all the "functionality" of > the old format has been retained, and without a significant > development effort, replacing that capability becomes a significant > maintenance burden. > > It would be reasonable to provide some automation for a single document, > but since no two documents seem to use the same naming/directory > structure, such an effort would have to be on a per document basis. It > might seem to make more sense to restructure the site so there was some > consistency, but given the number of documents/formats/languages and the > slowness of cvs that turns out to be a huge job. Would it be possible to get even a plain white list of languages links to the HTML documents for just http://docs.fedoraproject.org/install-guide/f12/ and http://docs.fedoraproject.org/release-notes/f12/, or could we get a list of URLs that need to be directed to the main docs.fp.o index? We can't really change the link on the website at this point, being way past the string freeze, and it's pretty important that those links go to something especially for the F12 release (although fp.o is already currently full of these broken links for F11 docs). Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From ricky at fedoraproject.org Wed Nov 11 20:53:25 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Wed, 11 Nov 2009 15:53:25 -0500 Subject: [Change Request] Re: [kerry@wsr.com: broken link on home page] In-Reply-To: <20091111200741.GE16826@alpha.rzhou.org> References: <20091111124017.GD16826@alpha.rzhou.org> <20091111133047.GC2338@desk.christensenplace.us> <20091111200741.GE16826@alpha.rzhou.org> Message-ID: <20091111205325.GF16826@alpha.rzhou.org> On 2009-11-11 03:07:42 PM, Ricky Zhou wrote: > > It would be reasonable to provide some automation for a single > > document, but since no two documents seem to use the same > > naming/directory structure, such an effort would have to be on a per > > document basis. It might seem to make more sense to restructure the > > site so there was some consistency, but given the number of > > documents/formats/languages and the slowness of cvs that turns out > > to be a huge job. > Would it be possible to get even a plain white list of languages links > to the HTML documents for just > http://docs.fedoraproject.org/install-guide/f12/ and > http://docs.fedoraproject.org/release-notes/f12/, or could we get a list > of URLs that need to be directed to the main docs.fp.o index? > > We can't really change the link on the website at this point, being way > past the string freeze, and it's pretty important that those links go to > something especially for the F12 release (although fp.o is already > currently full of these broken links for F11 docs). If this is fine with you guys, here's a change request to add redirects for those two to the docs.fp.o index page where visitors can choose their language and version of the document they want. -- diff --git a/modules/fedora-docs/files/fedora-docs-proxy.conf b/modules/fedora-docs/files/fedora-docs- index 259cfbd..61dfc04 100644 --- a/modules/fedora-docs/files/fedora-docs-proxy.conf +++ b/modules/fedora-docs/files/fedora-docs-proxy.conf @@ -7,6 +7,15 @@ RewriteRule ^(.*)/fc7$ http://docs.fedoraproject.org/$1/f7/ [R,L] RewriteRule ^/release-notes/f10preview(.*) /release-notes/f10$1 [R=301,L] RewriteRule ^/release-notes/f11preview(.*) /release-notes/f11$1 [R=301,L] +# Language selection indexes for these documents are gone now, so redirect +# to the main docs page where users can choose their language. + +RewriteRule ^/release-notes/f11/$ / [R=301,L] +RewriteRule ^/release-notes/f12/$ / [R=301,L] + +RewriteRule ^/install-guide/f11/$ / [R=301,L] +RewriteRule ^/install-guide/f12/$ / [R=301,L] + Options Indexes -- Alternatively, we can update all links to point at eg. http://docs.fedoraproject.org/install-guide/f12/en-US/html/ and mark those as translatable, which would be a late break of the string freeze, but still a pretty small one (the effect would be that all website links would point to the English doc until translators update them to point to their specific language's URL). Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From trac at fedorahosted.org Thu Nov 12 01:11:23 2009 From: trac at fedorahosted.org (Design Team) Date: Thu, 12 Nov 2009 01:11:23 -0000 Subject: [Design Team] #82: Need a logo for the Docs team Message-ID: <057.7d4cf03c5aaf9af8c859f92f4bb4e895@fedorahosted.org> #82: Need a logo for the Docs team -------------------------+-------------------------------------------------- Reporter: rlandmann | Owner: duffy Type: task | Status: new Priority: minor | Component: Artwork Severity: Quick & Easy | Keywords: -------------------------+-------------------------------------------------- Publican (the XML publishing tool used by the docs team) includes a small logo and hyperlink at the top right corner of the pages it builds in HTML. The hyperlink points to the documentation team responsible for the doc (in the case of Fedora docs, the Fedora Documentation Project), plus that team's logo. No logo for the Fedora docs team actually exists, so on all our Publican docs, we just get a "Made with Publican" logo instead. You can see an example here: http://docs.fedoraproject.org/release-notes/f11/en-US/ Something actually relevant to Fedora, documentation, or Fedora documentation would be much better :) -- Ticket URL: Design Team Fedora Design Team From trac at fedorahosted.org Thu Nov 12 01:17:10 2009 From: trac at fedorahosted.org (Design Team) Date: Thu, 12 Nov 2009 01:17:10 -0000 Subject: [Design Team] #82: Need a logo for the Docs team In-Reply-To: <057.7d4cf03c5aaf9af8c859f92f4bb4e895@fedorahosted.org> References: <057.7d4cf03c5aaf9af8c859f92f4bb4e895@fedorahosted.org> Message-ID: <066.a99569b595a8bebd60391ea53f078dfa@fedorahosted.org> #82: Need a logo for the Docs team -------------------------+-------------------------------------------------- Reporter: rlandmann | Owner: ryanlerch Type: task | Status: assigned Priority: minor | Component: Artwork Severity: Quick & Easy | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by ryanlerch): * owner: duffy => ryanlerch * status: new => assigned -- Ticket URL: Design Team Fedora Design Team From ryanlerch at gmail.com Thu Nov 12 11:26:59 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Thu, 12 Nov 2009 21:26:59 +1000 Subject: [Design-team] CD/DVD cover design question In-Reply-To: <4AFBBE5D.40605@nicubunu.ro> References: <4AF38A5C.6030802@fedoraproject.org> <4AF3EA98.2010903@nicubunu.ro> <4AF481B1.5090600@fedoraproject.org> <4AF67F34.3080702@fedoraproject.org> <4AF7E0C8.1090906@nicubunu.ro> <4AF8CBFC.2080602@fedoraproject.org> <20091110150138.GA8292@nostromo.devel.redhat.com> <4AFB23BD.6030106@fedoraproject.org> <20091111205250.GA17534@nostromo.devel.redhat.com> <4AFBBE5D.40605@nicubunu.ro> Message-ID: <671a617b0911120326r407dc5d1vd6d0913c2ee4e163@mail.gmail.com> A change to the relnotes this close to release will hit a _lot_ of translators. Not too sure about this one, so I'm ccing to the docs list. Cheers, ryanlerch On Thursday, November 12, 2009, Nicu Buculei wrote: > On 11/11/2009 10:52 PM, Bill Nottingham wrote: >> Luya Tshimbalanga (luya at fedoraproject.org) said: >>> Could you verify the specification I listed on CD/DVD covers[1]? >>> Suggestion welcome. >>> >>> Ref: [1] http://luya.fedorapeople.org/media/ >> >> 200 Mhz Pentium-class or better is wrong. Pentium will *not* work. >> Needs to be Pentium II (or Pentium Pro, but I doubt anyone still >> has those lying around) > > Do we have anyone from the documentation team listening here? The > release notes must be also updated with this info: > http://docs.fedoraproject.org/release-notes/f12/en-US/html/index.html#sect-Release_Notes-Hardware_Requirements > > -- > nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com/ > _______________________________________________ > design-team mailing list > design-team at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/design-team > From wb8rcr at chartermi.net Thu Nov 12 13:38:26 2009 From: wb8rcr at chartermi.net (wb8rcr at chartermi.net) Date: Thu, 12 Nov 2009 5:38:26 -0800 Subject: [Design-team] CD/DVD cover design question Message-ID: <20091112083826.IMAKR.3323440.root@mp05> ryanlerch said: > A change to the relnotes this close to release will hit a _lot_ of > translators. Not too sure about this one, so I'm ccing to the docs > list. The prose quoted is from an earlier version of the release notes. The version currently on f12-updates says: "Fedora 12 requires an Intel Pentium Pro or better processor, and is optimized for i686 and later processors. " I pushed and tagged this to docs.fp.o on Monday, but it isn't showing up. I am currently trying to track down why not. Unfortunately, I have relatives visiting which limits my time somewhat. --McD From kwade at redhat.com Fri Nov 13 04:15:04 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 12 Nov 2009 20:15:04 -0800 Subject: how to become a docs contributor (video) Message-ID: <20091113041504.GQ8457@calliope.phig.org> "how to become a docs contributor" http://www.youtube.com/watch?v=LJXyeIS-eIU Yesterday I was helping Mel[0] with the POSSE[1] class in Singapore[2]. Basically, I covered what open source content in Fedora does (technical docs, process docs, community self-knowledge docs), the common tools and styles we try to propagate, and then walked the class through how to contribute to the release notes. The exercise was focused on editing to the wiki. I explained the rest of the process in the abstract with lots of links.[3] The class[4] are all instructors in polytechnical or business schools in APAC - Singapore, Shangai, and so forth. Ideally, they take back the "how to be an active contributor in an open source community" training to their classes. Even better, if they do classes where part of the student work is being active in FLOSS communities. You may find the IRC log[3] interesting, but Mel did a good job capturing the basics in that screencast. It is useful for showing to anyone who drops by #fedora-docs. We'll try to get an OGG version to grab from somewhere so we can have it in the /topic on #fedora-docs. :) Cheers - Karsten [0] Mel - http://blog.melchua.com/ - http://blog.melchua.com/2009/11/11/how-to-become-a-release-notes-editor/ [1] http://teachingopensource.org/index.php/POSSE [2] http://teachingopensource.org/index.php/POSSE_APAC [3] I start the session at 01:53:38: http://meetbot.fedoraproject.org/teachingopensource-posse/2009-11-12/teachingopensource-posse.2009-11-12-00.25.log.html#l-337 [4] http://teachingopensource.org/index.php/POSSE_Blogs http://blog.melchua.com/2009/11/10/new-bloggers-adopt-a-lecturer/ http://teachingopensource.org/index.php/Planet -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mel at redhat.com Fri Nov 13 12:37:48 2009 From: mel at redhat.com (Mel Chua) Date: Fri, 13 Nov 2009 20:37:48 +0800 Subject: how to become a docs contributor (video) In-Reply-To: <20091113041504.GQ8457@calliope.phig.org> References: <20091113041504.GQ8457@calliope.phig.org> Message-ID: <4AFD531C.8070208@redhat.com> Thanks to Karsten for a fantastic docs session - the lecturers (POSSE is a weeklong bootcamp immersing professors in open source contribution so they can get their classes involved) were impressed by not just the quality of docs, and the processes and tools we use, but also by the neat spontaneous learning moments that can happen in open source - the notion of a contributor wandering by and going "oh, I can teach that!" is, alas, a strange one in many academic institutions (but we're trying to change that!) > You may find the IRC log[3] interesting, but Mel did a good job > capturing the basics in that screencast. It is useful for showing to > anyone who drops by #fedora-docs. We'll try to get an OGG version to > grab from somewhere so we can have it in the /topic on > #fedora-docs. :) Argh, I didn't copy the original ogg to my laptop (I did it from a computer lab machine). I'll download the mp4 from youtube and put it on my fedorapeople space temporarily - can anyone grab, convert to ogg and host it... somewhere more appropriately permanent? --Mel From mmcgrath at redhat.com Sat Nov 14 01:49:09 2009 From: mmcgrath at redhat.com (Mike McGrath) Date: Fri, 13 Nov 2009 19:49:09 -0600 (CST) Subject: how to become a docs contributor (video) In-Reply-To: <4AFD531C.8070208@redhat.com> References: <20091113041504.GQ8457@calliope.phig.org> <4AFD531C.8070208@redhat.com> Message-ID: On Fri, 13 Nov 2009, Mel Chua wrote: > Thanks to Karsten for a fantastic docs session - the lecturers (POSSE is a > weeklong bootcamp immersing professors in open source contribution so they can > get their classes involved) were impressed by not just the quality of docs, > and the processes and tools we use, but also by the neat spontaneous learning > moments that can happen in open source - the notion of a contributor wandering > by and going "oh, I can teach that!" is, alas, a strange one in many academic > institutions (but we're trying to change that!) > > > You may find the IRC log[3] interesting, but Mel did a good job > > capturing the basics in that screencast. It is useful for showing to > > anyone who drops by #fedora-docs. We'll try to get an OGG version to > > grab from somewhere so we can have it in the /topic on > > #fedora-docs. :) > > Argh, I didn't copy the original ogg to my laptop (I did it from a computer > lab machine). I'll download the mp4 from youtube and put it on my fedorapeople > space temporarily - can anyone grab, convert to ogg and host it... somewhere > more appropriately permanent? > alt.fedoraproject.org would work -Mike From mel at redhat.com Sun Nov 15 02:40:28 2009 From: mel at redhat.com (Mel Chua) Date: Sun, 15 Nov 2009 10:40:28 +0800 Subject: how to become a docs contributor (video) In-Reply-To: References: <20091113041504.GQ8457@calliope.phig.org> <4AFD531C.8070208@redhat.com> Message-ID: <4AFF6A1C.1060202@redhat.com> >> Argh, I didn't copy the original ogg to my laptop (I did it from a computer >> lab machine). I'll download the mp4 from youtube and put it on my fedorapeople >> space temporarily - can anyone grab, convert to ogg and host it... somewhere >> more appropriately permanent? >> > > alt.fedoraproject.org would work > > -Mike mp4 is up at http://mchua.fedorapeople.org/how%2520to%2520become%2520a%2520docs%2520contributor.mp4 - if you grab/convert/move the resulting ogg to somewhere more appropriate, let me know so I can take it down. --Mel From vishuindian at gmail.com Sun Nov 15 07:29:13 2009 From: vishuindian at gmail.com (vishesh kumar) Date: Sun, 15 Nov 2009 12:59:13 +0530 Subject: how to become a docs contributor (video) In-Reply-To: <4AFF6A1C.1060202@redhat.com> References: <20091113041504.GQ8457@calliope.phig.org> <4AFD531C.8070208@redhat.com> <4AFF6A1C.1060202@redhat.com> Message-ID: Thanks karsten , video is great learning experience for newbie in docs community like me. On 11/15/09, Mel Chua wrote: >>> Argh, I didn't copy the original ogg to my laptop (I did it from a >>> computer >>> lab machine). I'll download the mp4 from youtube and put it on my >>> fedorapeople >>> space temporarily - can anyone grab, convert to ogg and host it... >>> somewhere >>> more appropriately permanent? >>> >> >> alt.fedoraproject.org would work >> >> -Mike > > mp4 is up at > http://mchua.fedorapeople.org/how%2520to%2520become%2520a%2520docs%2520contributor.mp4 > - if you grab/convert/move the resulting ogg to somewhere more > appropriate, let me know so I can take it down. > > --Mel > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -- http://linuxinterviews.blogspot.com From bugzilla at redhat.com Sun Nov 15 15:47:03 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Nov 2009 10:47:03 -0500 Subject: [Bug 516793] Need to package FCKeditor In-Reply-To: References: Message-ID: <200911151547.nAFFl3M5029763@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=516793 Leo Way changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loadgold at gmail.com Flag|needinfo? | --- Comment #2 from Leo Way 2009-11-15 10:47:02 EDT --- Your comment seens like dis offical 0f redhat . If not AD. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Sun Nov 15 15:47:32 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Nov 2009 10:47:32 -0500 Subject: [Bug 516794] Need to package OpenWYSIWYG In-Reply-To: References: Message-ID: <200911151547.nAFFlWhM029850@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=516794 Leo Way changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loadgold at gmail.com Flag|needinfo? | --- Comment #2 from Leo Way 2009-11-15 10:47:32 EDT --- Your comment seens like dis offical 0f redhat. If not AD. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Sun Nov 15 16:05:32 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Nov 2009 11:05:32 -0500 Subject: [Bug 516794] Need to package OpenWYSIWYG In-Reply-To: References: Message-ID: <200911151605.nAFG5W8D017048@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=516794 --- Comment #3 from Eric Christensen 2009-11-15 11:05:31 EDT --- (In reply to comment #2) > Your comment seens like dis offical 0f redhat. > If not AD. Huh? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Sun Nov 15 16:06:19 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Nov 2009 11:06:19 -0500 Subject: [Bug 516793] Need to package FCKeditor In-Reply-To: References: Message-ID: <200911151606.nAFG6JxS017206@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=516793 --- Comment #3 from Eric Christensen 2009-11-15 11:06:18 EDT --- (In reply to comment #2) > Your comment seens like dis offical 0f redhat . > If not AD. Huh? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From kwade at redhat.com Sun Nov 15 21:46:54 2009 From: kwade at redhat.com (Karsten Wade) Date: Sun, 15 Nov 2009 13:46:54 -0800 Subject: handling attributions for Docs Message-ID: <20091115214654.GG25638@calliope.phig.org> Now we have a clear need for attributing source information: thanks to being relicensed under CC BY SA 3.0 means we can import lots of good content and so we're likely to do so. Efficient attribution is now important. There are two parts to this discussion: * Technical - how it works in DocBook and Publican * Brand - how does the Fedora Documentation Project want to attribute I was going to look at it from a social angle, but I think the brand angle overrides the social angle. Read on for more. == Technical proposal == To handle copyright attribution, I recommend we adopt this approach: * For single or a few imports of a chunk of attributable content, use a . Attribution happens on the page it occurs. Example: Pulling a description of AES encryption from Wikipedia for the Fedora Security Guide. * For longer imports, blends, or remixing of content, use . Example: All of the people who work on a guide over the years would be lists in a standard format under the primary Fedora/Red Hat legal language. For the usage, we would need: * A standard format for all attributions, to make it fair, clear, equitable. Alphabetical, for example. * A change to Publican(?) to look for and use a file, en-US/Attribution.xml, if it is present. This allows attribution to be kept within the main document source tree. == Brand proposal == This is a proposal only affecting Fedora-branded works. An upstream, such as the "Linux Security Guide" (https://fedorahosted.org/securityguide/), can attribute as it sees fit, just as a downstream "Red Hat Enteprise Linux Security Guide" can attribute as it sees fit. Currently, for some works, we have primary authors in a long list on the front cover of a work. We've long discussed swapping that for "Fedora Documentation Project". Especially as we work with a larger group, the list of authors on the front cover grows. It visually competes with the Fedora branding. In other parts of the Fedora Project, we don't see the authors presented in that fashion. Anaconda is "Anaconda Team ". This is more the norm for FLOSS projects. This is how a "Fedora Docs Team" focus looks in practice: http://docs.fedoraproject.org/release-notes/f12/en-US/html/ A good bonus to that would be having either a link to the project page or text inline that links to the mailing list or project page. Another idea is to have a notice in the authorship/editorship section, "For full attribution of contributions to this work, refer to the [legalnotice]." One reason for picking a standard is to set the expectation for how we attribute under the Fedora brand. When we put up individual names, it creates a competitive space. External content originators that are remixed may demand front-page attribution. This causes the visual appeal to diminish while increasing the attribution maintenance. Having _all_ Fedora-branded guides follow the same standard that puts the Fedora brand first does the best service to the Fedora Project. It gives us the least headaches. I think it is the right thing to do. What do you think? - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ryanlerch at gmail.com Mon Nov 16 00:10:11 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Mon, 16 Nov 2009 10:10:11 +1000 Subject: [Design-team] F12 One-Page Release Notes PDF In-Reply-To: <36a6faa60911151535i768157b5r79dc5234c8c42257@mail.gmail.com> References: <1258155683.2724.6.camel@localhost.localdomain> <1258155872.2724.8.camel@localhost.localdomain> <671a617b0911151228k24384e2cmf21ec72a1a67dc2a@mail.gmail.com> <20091115215632.GA7636@victoria.internal.frields.org> <36a6faa60911151535i768157b5r79dc5234c8c42257@mail.gmail.com> Message-ID: <671a617b0911151610id9e0151y12443980db6ba8f7@mail.gmail.com> CC'ing this thread to the fedora-docs-list. On Mon, Nov 16, 2009 at 9:35 AM, Kris Thomsen wrote: > Looks fantastic, I'm translating those into Danish :) Awesome! AFAIK, these release notes (the awesome PDF version the design-team produced): http://duffy.fedorapeople.org/collateral/release%20notes/f12/F12ReleaseNotes-All.pdf are a subset of the Release Notes that the docs team produced: http://docs.fedoraproject.org/release-notes/f12/en-US/html/ so strings may match between these documents. That said, i think we should also start planning on how to get this awesome (and useful) doc localised for the f13 version. cheers, ryanlerch > > // Kris > > 2009/11/15 Paul W. Frields >> >> On Mon, Nov 16, 2009 at 07:28:03AM +1100, Ryan Lerch wrote: >> > 2009/11/14 M?ir?n Duffy : >> > > On Fri, 2009-11-13 at 18:41 -0500, M?ir?n Duffy wrote: >> > >> http://duffy.fedorapeople.org/collateral/release% >> > >> 20notes/f12/F12ReleaseNotes-All.pdf >> > > >> > > Oh! I forgot to mention it is designed for A4. So if you are using >> > > Letter-sized paper, make sure you tell the printer to center the >> > > document. Otherwise it'll print out all spaced out weird on the page. >> > > >> > > ~m >> > >> > This is _AWESOME_ ! >> > >> > When I first downloaded it, though, i was a bit surprised at the 14MB >> > filesize. I assume this is because of the bitmaps needing to be larger >> > for when it is printed out? >> > >> > awesome work mo! (and all the screenshot capturing people) >> >> Hear, hear -- it's really superb. ?I love the way you made the layout >> hang together so nicely compared to the wiki version. ?(The wiki's a >> great place to draft, but it's really hard to do good layout there!) >> >> This is going to be a nice way for people to present Fedora. ?Sorry it >> ended up being long. ?I hope we can use the learning opportunities to >> make sure the next version will be easier to fit on a single >> double-sided page. ?Nice work to everyone who participated! >> >> -- >> 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 >> _______________________________________________ >> design-team mailing list >> design-team at lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/design-team > > > _______________________________________________ > design-team mailing list > design-team at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/design-team > > From ccurran at redhat.com Mon Nov 16 01:26:09 2009 From: ccurran at redhat.com (Christopher Curran) Date: Mon, 16 Nov 2009 11:26:09 +1000 Subject: handling attributions for Docs In-Reply-To: <20091115214654.GG25638@calliope.phig.org> References: <20091115214654.GG25638@calliope.phig.org> Message-ID: <4B00AA31.8010908@redhat.com> Karsten Wade wrote: > Now we have a clear need for attributing source information: thanks to > being relicensed under CC BY SA 3.0 means we can import lots of good > content and so we're likely to do so. Efficient attribution is now > important. > > There are two parts to this discussion: > > * Technical - how it works in DocBook and Publican > * Brand - how does the Fedora Documentation Project want to attribute > > I was going to look at it from a social angle, but I think the brand > angle overrides the social angle. Read on for more. > > == Technical proposal == > > To handle copyright attribution, I recommend we adopt this approach: > > * For single or a few imports of a chunk of attributable content, use > a . Attribution happens on the page it occurs. > > Example: Pulling a description of AES encryption from Wikipedia for > the Fedora Security Guide. > > Footnotes come from one school of attribution. There is another school of thought that preaches endnotes. I would recommend neither and suggest we go with a page of attribution and thanks were we mention various voluntary and 'acquired' contributions. This gives us a wider scope for referencing conversations, technical input, code, and other miscellaneous contribution. Useful as we will be without a formal and ridged format which would normally exclude those types of contributions. > * For longer imports, blends, or remixing of content, use > . > > Example: All of the people who work on a guide over the years would > be lists in a standard format under the primary Fedora/Red Hat legal > language. > > That isn't relevant, really. If something is exceedingly, heavily rewritten it counts as an original work. Credit where credit is due, of course. However, if the original is unrecognisable all it does is make notices longer and unwieldy. > For the usage, we would need: > > * A standard format for all attributions, to make it fair, clear, > equitable. Alphabetical, for example. > Always by importance. Alphabetical is rubbish for translations and other languages. > * A change to Publican(?) to look for and use a file, > en-US/Attribution.xml, if it is present. This allows attribution to > be kept within the main document source tree. > +1 > == Brand proposal == > > This is a proposal only affecting Fedora-branded works. An upstream, > such as the "Linux Security Guide" > (https://fedorahosted.org/securityguide/), can attribute as it sees > fit, just as a downstream "Red Hat Enteprise Linux Security Guide" can > attribute as it sees fit. > > Currently, for some works, we have primary authors in a long list on > the front cover of a work. We've long discussed swapping that for > "Fedora Documentation Project". > > In all writing projects there is always one to three actual writers. Primary writers should be up the front and secondary, tertiary and other contributors up the back/front in a references/attribution section. > Especially as we work with a larger group, the list of authors on the > front cover grows. It visually competes with the Fedora branding. > > And we should note that an important part of Open Source is personal gain. People's names are their brand. Most people involved in Open Source want their name present in patches and so forth as they are trying to grow their own brands. This should be encouraged, not hidden away. It brings personal pride to the work involved and enforces accountability. > In other parts of the Fedora Project, we don't see the authors > presented in that fashion. Anaconda is "Anaconda Team > ". This is more the norm for FLOSS > projects. > > There is often an AUTHORS page or similar included in the code or the program. Man pages are full of personal attributions. We should no abstract or removed this for previously mentioned reasons. > This is how a "Fedora Docs Team" focus looks in practice: > > http://docs.fedoraproject.org/release-notes/f12/en-US/html/ > > A good bonus to that would be having either a link to the project page > or text inline that links to the mailing list or project page. > > Another idea is to have a notice in the authorship/editorship section, > "For full attribution of contributions to this work, refer to the > [legalnotice]." > I agree, but we should keep a focus on primary contributors. > One reason for picking a standard is to set the expectation for how we > attribute under the Fedora brand. When we put up individual names, it > creates a competitive space. External content originators that are > remixed may demand front-page attribution. This causes the visual > appeal to diminish while increasing the attribution maintenance. > > If the remix is sufficient, we can give them a middle finger and suggest they take a hike. The world of publishing and technical documentation is nothing like the world of academic writing. Attribution is handled differently. If a work is sufficiently distinct it counts as an original work. Only original or patented ideas /must/ be attributed. I'm not saying we act like jerks to the community, I am just saying we don't have to comply when they act like jerks. I think we want to create a competitive space. We want to work as a team but really bring credit to our standout players. We want to put them out there and say, "This person is really great". That may change from version to version and that is a Good Thing. > Having _all_ Fedora-branded guides follow the same standard that puts > the Fedora brand first does the best service to the Fedora Project. > It gives us the least headaches. I think it is the right thing to do. > > What do you think? > > - Karsten > IANAL Chris From ryanlerch at gmail.com Mon Nov 16 01:43:41 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Mon, 16 Nov 2009 11:43:41 +1000 Subject: Documentation Logo Design Message-ID: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> Hi everyone on the Docs and Design Lists! I have whipped up a first attempt at a logo for the Documentation team. (ticket#82 in the design queue) Here is a mockup of how it will look when integrated with publican: http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup.png and here is the SVG and PNG of the logo itself: http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs-logo.png http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs.svg thoughts, ideas or comments welcome! cheers, ryanlerch From r.landmann at redhat.com Mon Nov 16 01:59:29 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 16 Nov 2009 11:59:29 +1000 Subject: Documentation Logo Design In-Reply-To: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> Message-ID: <4B00B201.5040308@redhat.com> On 11/16/2009 11:43 AM, Ryan Lerch wrote: > Hi everyone on the Docs and Design Lists! > > I have whipped up a first attempt at a logo for the Documentation > team. (ticket#82 in the design queue) > > Here is a mockup of how it will look when integrated with publican: > http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup.png > > and here is the SVG and PNG of the logo itself: > http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs-logo.png > http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs.svg > > thoughts, ideas or comments welcome! > Thanks Ryan! Looking good ? I'd be happy to see that replace the "Made with Publican" logo in our docs! Cheers Rudi From eric at christensenplace.us Mon Nov 16 02:47:07 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 15 Nov 2009 21:47:07 -0500 Subject: handling attributions for Docs In-Reply-To: <4B00AA31.8010908@redhat.com> References: <20091115214654.GG25638@calliope.phig.org> <4B00AA31.8010908@redhat.com> Message-ID: <20091116024706.GC2264@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 16, 2009 at 11:26:09AM +1000, Christopher Curran wrote: > Karsten Wade wrote: > >Now we have a clear need for attributing source information: thanks to > >being relicensed under CC BY SA 3.0 means we can import lots of good > >content and so we're likely to do so. Efficient attribution is now > >important. > > > >There are two parts to this discussion: > > > >* Technical - how it works in DocBook and Publican > >* Brand - how does the Fedora Documentation Project want to attribute > > > >I was going to look at it from a social angle, but I think the brand > >angle overrides the social angle. Read on for more. > > > >== Technical proposal == > > > >To handle copyright attribution, I recommend we adopt this approach: > > > >* For single or a few imports of a chunk of attributable content, use > > a . Attribution happens on the page it occurs. > > > > Example: Pulling a description of AES encryption from Wikipedia for > > the Fedora Security Guide. > > > Footnotes come from one school of attribution. There is another > school of thought that preaches endnotes. I would recommend neither > and suggest we go with a page of attribution and thanks were we > mention various voluntary and 'acquired' contributions. This gives > us a wider scope for referencing conversations, technical input, > code, and other miscellaneous contribution. Useful as we will be > without a formal and ridged format which would normally exclude > those types of contributions. While it is great to say "we used all these references and people to make this guide" I don't think that meets the 1) letter of the license or 2) the spirit of sharing. If the text we use comes from someone else who says to use it but attribute it back we should do that. We would need some way to point from the text to the attribution so it is proper. > >* For longer imports, blends, or remixing of content, use > > . > > > > Example: All of the people who work on a guide over the years would > > be lists in a standard format under the primary Fedora/Red Hat legal > > language. > > > That isn't relevant, really. If something is exceedingly, heavily > rewritten it counts as an original work. Credit where credit is > due, of course. However, if the original is unrecognisable all it > does is make notices longer and unwieldy. Again, we have to follow the letter of the license. We would want others to do the same. > >For the usage, we would need: > > > >* A standard format for all attributions, to make it fair, clear, > > equitable. Alphabetical, for example. > Always by importance. Alphabetical is rubbish for translations and > other languages. How do you determine importance? > >* A change to Publican(?) to look for and use a file, > > en-US/Attribution.xml, if it is present. This allows attribution to > > be kept within the main document source tree. > +1 > >== Brand proposal == > > > >This is a proposal only affecting Fedora-branded works. An upstream, > >such as the "Linux Security Guide" > >(https://fedorahosted.org/securityguide/), can attribute as it sees > >fit, just as a downstream "Red Hat Enteprise Linux Security Guide" can > >attribute as it sees fit. > > > >Currently, for some works, we have primary authors in a long list on > >the front cover of a work. We've long discussed swapping that for > >"Fedora Documentation Project". > > > In all writing projects there is always one to three actual > writers. Primary writers should be up the front and secondary, > tertiary and other contributors up the back/front in a > references/attribution section. Maybe but there are times that distinction is always clear. > >Especially as we work with a larger group, the list of authors on the > >front cover grows. It visually competes with the Fedora branding. > > > And we should note that an important part of Open Source is > personal gain. People's names are their brand. Most people involved > in Open Source want their name present in patches and so forth as > they are trying to grow their own brands. This should be > encouraged, not hidden away. It brings personal pride to the work > involved and enforces accountability. I don't think anyone is suggesting that we hide contributor's names in the metadata somewhere. But we aren't building these guides as a billboard, either. > >In other parts of the Fedora Project, we don't see the authors > >presented in that fashion. Anaconda is "Anaconda Team > >". This is more the norm for FLOSS > >projects. > > > There is often an AUTHORS page or similar included in the code or > the program. Man pages are full of personal attributions. We should > no abstract or removed this for previously mentioned reasons. > >This is how a "Fedora Docs Team" focus looks in practice: > > > >http://docs.fedoraproject.org/release-notes/f12/en-US/html/ > > > >A good bonus to that would be having either a link to the project page > >or text inline that links to the mailing list or project page. > > > >Another idea is to have a notice in the authorship/editorship section, > >"For full attribution of contributions to this work, refer to the > >[legalnotice]." > I agree, but we should keep a focus on primary contributors. > >One reason for picking a standard is to set the expectation for how we > >attribute under the Fedora brand. When we put up individual names, it > >creates a competitive space. External content originators that are > >remixed may demand front-page attribution. This causes the visual > >appeal to diminish while increasing the attribution maintenance. > > > If the remix is sufficient, we can give them a middle finger and > suggest they take a hike. The world of publishing and technical > documentation is nothing like the world of academic writing. > Attribution is handled differently. If a work is sufficiently > distinct it counts as an original work. Only original or patented > ideas /must/ be attributed. I'm not saying we act like jerks to the > community, I am just saying we don't have to comply when they act > like jerks. Again we have to follow the license. Personally, I've never run into someone that was demanding, yet, but if I did I'd simply remove their text from the document and move on. But I think we still have to attribute back to the original even if we modified the work afterwards due to the original license. Now a complete rewrite may be different. > > I think we want to create a competitive space. We want to work as a > team but really bring credit to our standout players. We want to > put them out there and say, "This person is really great". That may > change from version to version and that is a Good Thing. I think the end result is having a product that is up to date and helpful. People come to our guides because they have questions. We should want to help answer those questions. If you are in it just to have your name in lights go get yourself a blog. > > >Having _all_ Fedora-branded guides follow the same standard that puts > >the Fedora brand first does the best service to the Fedora Project. > >It gives us the least headaches. I think it is the right thing to do. > > > >What do you think? > > > >- Karsten > IANAL > > Chris > - --Eric - ---end quoted text--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksAvSoACgkQfQTSQL0MFMEeygCgjZANfLx1lyxftEB9/V5PHwga EjAAoMqICEI8Boc+phkXE4JDSHg4Os3D =6Tj2 -----END PGP SIGNATURE----- From eric at christensenplace.us Mon Nov 16 02:52:39 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 15 Nov 2009 21:52:39 -0500 Subject: Documentation Logo Design In-Reply-To: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> Message-ID: <20091116025238.GD2264@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 16, 2009 at 11:43:41AM +1000, Ryan Lerch wrote: > Hi everyone on the Docs and Design Lists! > > I have whipped up a first attempt at a logo for the Documentation > team. (ticket#82 in the design queue) > > Here is a mockup of how it will look when integrated with publican: > http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup.png > > and here is the SVG and PNG of the logo itself: > http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs-logo.png > http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs.svg > > thoughts, ideas or comments welcome! > > cheers, > ryanlerch Very cool. Can we do something to dress up the book? Maybe put the Fedora logo on it or something? - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksAvnYACgkQfQTSQL0MFMGT/ACfbg7ui/DYLBvyKiq5R37axSQp ohcAn1CpWnyeWi4ORe0HtkNEmkY9ip0O =YPt8 -----END PGP SIGNATURE----- From sradvan at redhat.com Mon Nov 16 02:58:48 2009 From: sradvan at redhat.com (Scott Radvan) Date: Mon, 16 Nov 2009 12:58:48 +1000 Subject: Announcing the Fedora Wireless Guide Message-ID: <20091116125848.5d3b1fd2@stratos.eternia.lan> Hi list, Announcing the Fedora Wireless Guide, an overview of wireless technology (primarily 802.11) and their implementation in Fedora. This guide is designed to provide a high-level summary of 802.11 wireless technology, equipment, standards, security concerns and myths, and communication concepts, etc. -- to provide those with little knowledge of wireless a good starting point to the terms and ideas. It is not intended to be an advanced guide, rather to provide a good grounding in wireless. Of course, it allows a lot of room for expansion into more advanced topics. Also covered briefly are other mobile technologies (EV-DO, HSDPA, etc.) Trac details: https://fedorahosted.org/wireless-guide/ Latest build: http://sradvan.fedorapeople.org/Wireless_Guide/en-US/html-single/ A Bugzilla component also exists. This will hit CVS/F12 section of d.fp.o soon, so I would greatly appreciate any proof-reading/review, bugzillas or other comments. Thanks! -- Scott Radvan Content Author, Platform (Installation and Deployment) Red Hat Asia Pacific (Brisbane) http://www.apac.redhat.com From ryanlerch at gmail.com Mon Nov 16 02:59:52 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Mon, 16 Nov 2009 12:59:52 +1000 Subject: Documentation Logo Design In-Reply-To: <20091116025238.GD2264@desk.christensenplace.us> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> <20091116025238.GD2264@desk.christensenplace.us> Message-ID: <671a617b0911151859q7958fb2fy33219a547972ffe2@mail.gmail.com> On Mon, Nov 16, 2009 at 12:52 PM, Eric Christensen wrote: > > > Very cool. ?Can we do something to dress up the book? ?Maybe put the > Fedora logo on it or something? I did play around a bit with getting the logo on there, but could not make it look any good, while still keeping to the logo guidelines... http://fedoraproject.org/wiki/Logo/UsageGuidelines does anyone have any ideas? cheers, ryanlerch > > - --Eric From eric at christensenplace.us Mon Nov 16 03:04:47 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 15 Nov 2009 22:04:47 -0500 Subject: Announcing the Fedora Wireless Guide In-Reply-To: <20091116125848.5d3b1fd2@stratos.eternia.lan> References: <20091116125848.5d3b1fd2@stratos.eternia.lan> Message-ID: <20091116030447.GE2264@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 16, 2009 at 12:58:48PM +1000, Scott Radvan wrote: > Hi list, > > > Announcing the Fedora Wireless Guide, an overview of wireless > technology (primarily 802.11) and their implementation in Fedora. > > This guide is designed to provide a high-level summary of 802.11 > wireless technology, equipment, standards, security concerns and myths, > and communication concepts, etc. -- to provide those with little > knowledge of wireless a good starting point to the terms and ideas. > > It is not intended to be an advanced guide, rather to provide a good > grounding in wireless. Of course, it allows a lot of room for expansion > into more advanced topics. > > Also covered briefly are other mobile technologies (EV-DO, HSDPA, etc.) > > > Trac details: > https://fedorahosted.org/wireless-guide/ > > Latest build: > http://sradvan.fedorapeople.org/Wireless_Guide/en-US/html-single/ > > > A Bugzilla component also exists. This will hit CVS/F12 section of > d.fp.o soon, so I would greatly appreciate any proof-reading/review, > bugzillas or other comments. > > > Thanks! > > -- > Scott Radvan > Content Author, Platform (Installation and Deployment) > Red Hat Asia Pacific (Brisbane) http://www.apac.redhat.com > That's awesome work! - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksAwU8ACgkQfQTSQL0MFMEBQgCeKmmvBfPRwHUf+RsJPvsy+HaE Mx4AnjuFzqbPIrTIrtoLx2VZB28NS8p0 =fuCe -----END PGP SIGNATURE----- From eric at christensenplace.us Mon Nov 16 03:18:10 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 15 Nov 2009 22:18:10 -0500 Subject: Publishing Guides for F12 Release Message-ID: <20091116031810.GG2264@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We are less than 36 hours away from the F12 release. If possible, please have the latest version of your guide uploaded to the CVS where docs.fp.o pulls from no later than 0001 UTC on 17 Nov so we can make sure that all the pages are properly sync'd and the homepage is linked properly. Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksAxHIACgkQfQTSQL0MFMGBKQCgyaeJQcfnC2ryNepMc9Re95XL eEkAn0UJAQHk14hCUNGsWN4rHaPhJ789 =6wHU -----END PGP SIGNATURE----- From r.landmann at redhat.com Mon Nov 16 03:39:21 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 16 Nov 2009 13:39:21 +1000 Subject: [Design-team] Documentation Logo Design In-Reply-To: <4B00B72F.8050609@fedoraproject.org> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> <4B00B72F.8050609@fedoraproject.org> Message-ID: <4B00C969.3010808@redhat.com> On 11/16/2009 12:21 PM, Luya Tshimbalanga wrote: > On 11/15/2009 05:43 PM, Ryan Lerch wrote: > >> Here is a mockup of how it will look when integrated with publican: >> http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup.png >> > Problem with that layout, Fedora brand is redundant (top left and > middle). Reader already know the > document is for Fedora. > FWIW, the big Fedora logo in the middle only appears on the first page (title page) of a doc. Here's a more typical page: http://docs.fedoraproject.org/release-notes/f12/en-US/html/sect-Release_Notes-Web_and_Content_Servers.html the new logo is to take the place of the boilerplate "Made with Publican" logo. Note too that the logos at the "ears" of the page are hyperlinked; the Fedora logo links to www.fedoraproject.org and the "Made with Publican" logo links to docs.fedoraproject.org From ryanlerch at gmail.com Mon Nov 16 04:04:02 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Mon, 16 Nov 2009 14:04:02 +1000 Subject: [Design-team] Documentation Logo Design In-Reply-To: <4B00C969.3010808@redhat.com> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> <4B00B72F.8050609@fedoraproject.org> <4B00C969.3010808@redhat.com> Message-ID: <671a617b0911152004n51387df0w8b5fdc63c7697c32@mail.gmail.com> On Mon, Nov 16, 2009 at 1:39 PM, Ruediger Landmann wrote: > > FWIW, the big Fedora logo in the middle only appears on the first page > (title page) of a doc. Here's a more typical page: > > http://docs.fedoraproject.org/release-notes/f12/en-US/html/sect-Release_Notes-Web_and_Content_Servers.html Thanks rudi! That is a _much_ better sample page than the one i chose for my mockup. So i created another mockup based on the page rudi suggested: http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup2.png > > the new logo is to take the place of the boilerplate "Made with Publican" > logo. > > Note too that the logos at the "ears" of the page are hyperlinked; the > Fedora logo links to www.fedoraproject.org and the "Made with Publican" logo > links to docs.fedoraproject.org > cheers, ryanlerch From r.landmann at redhat.com Mon Nov 16 04:04:33 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 16 Nov 2009 14:04:33 +1000 Subject: Photographs of hardware in Fedora documentation Message-ID: <4B00CF51.7050308@redhat.com> The new Fedora Wireless Guide includes photographs of different types of wireless adapter: http://sradvan.fedorapeople.org/Wireless_Guide/en-US/html-single/#sect-Wireless_Guide-Hardware-Types_Of_Cards In each case, the manufacturer's logos and/or (obviously) the design of the hardware itself is visible in the photograph. Some questions: 1. Are the manufacturer's labels on the hardware and/or the design of the hardware itself (particularly the styling of the USB adapter in the first picture) likely to be protected by copyright? If so: * Is our use of the image to illustrate a generic component of a particular type likely to be covered by "fair use" for publication in the United States? * Is this protection likely to cause problems for people who want to reuse our content? (I'm thinking in particular of places that have no "fair use" or equivalent concept in their copyright law, or for reusers who want to use the image in a completely different context) -- and if so, do we care, or are reusers on their own here? 2. Could using specific pieces of hardware to illustrate a generic type of hardware be construed to be an endorsement of this particular piece of hardware or its manufacturer? If so, do we want to do this in our docs? Cheers Ruediger From ccurran at redhat.com Mon Nov 16 05:30:31 2009 From: ccurran at redhat.com (Christopher Curran) Date: Mon, 16 Nov 2009 15:30:31 +1000 Subject: handling attributions for Docs In-Reply-To: <20091116024706.GC2264@desk.christensenplace.us> References: <20091115214654.GG25638@calliope.phig.org> <4B00AA31.8010908@redhat.com> <20091116024706.GC2264@desk.christensenplace.us> Message-ID: <4B00E377.7010009@redhat.com> Eric Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, Nov 16, 2009 at 11:26:09AM +1000, Christopher Curran wrote: > > Karsten Wade wrote: > > >Now we have a clear need for attributing source information: thanks to > > >being relicensed under CC BY SA 3.0 means we can import lots of good > > >content and so we're likely to do so. Efficient attribution is now > > >important. > > > > > >There are two parts to this discussion: > > > > > >* Technical - how it works in DocBook and Publican > > >* Brand - how does the Fedora Documentation Project want to attribute > > > > > >I was going to look at it from a social angle, but I think the brand > > >angle overrides the social angle. Read on for more. > > > > > >== Technical proposal == > > > > > >To handle copyright attribution, I recommend we adopt this approach: > > > > > >* For single or a few imports of a chunk of attributable content, use > > > a . Attribution happens on the page it occurs. > > > > > > Example: Pulling a description of AES encryption from Wikipedia for > > > the Fedora Security Guide. > > > > > Footnotes come from one school of attribution. There is another > > school of thought that preaches endnotes. I would recommend neither > > and suggest we go with a page of attribution and thanks were we > > mention various voluntary and 'acquired' contributions. This gives > > us a wider scope for referencing conversations, technical input, > > code, and other miscellaneous contribution. Useful as we will be > > without a formal and ridged format which would normally exclude > > those types of contributions. > > While it is great to say "we used all these references and people to > make this guide" I don't think that meets the 1) letter of the license > or 2) the spirit of sharing. If the text we use comes from someone else > who says to use it but attribute it back we should do that. We would > need some way to point from the text to the attribution so it is proper. > > I wasn't referring to just a list of names. I meant name, affiliation (if requested/required), and a short description about the nature of the contribution. Of course, follow the letter of the license. "Attribution ? You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)." That is pretty broad though. I'm not sure how a list of names and descriptions would invalidate that. Again, IANAL. > > >For the usage, we would need: > > > > > >* A standard format for all attributions, to make it fair, clear, > > > equitable. Alphabetical, for example. > > Always by importance. Alphabetical is rubbish for translations and > > other languages. > > How do you determine importance? > With great difficulty. As subjective as that is it is probably more useful than English alphabetical order. Order of appearance would also be a possibility. > > In all writing projects there is always one to three actual > > writers. Primary writers should be up the front and secondary, > > tertiary and other contributors up the back/front in a > > references/attribution section. > > Maybe but there are times that distinction is always clear. > Sure. Isn't that the problem this entire thread is trying to solve? > > > > > I think we want to create a competitive space. We want to work as a > > team but really bring credit to our standout players. We want to > > put them out there and say, "This person is really great". That may > > change from version to version and that is a Good Thing. > > I think the end result is having a product that is up to date and > helpful. People come to our guides because they have questions. We > should want to help answer those questions. If you are in it just to > have your name in lights go get yourself a blog. > > I'm probably not being as clear as I could be. I am arguing to keep attribution prominent. The rest is waffle and small-point discussion. My views are my own and I'm not representing anyone else. I may seem hostile or argumentative, but that is just how I think and I'm not really like that :) Chris From rivanvx at gmail.com Mon Nov 16 11:14:00 2009 From: rivanvx at gmail.com (=?UTF-8?Q?Vedran_Mileti=C4=87?=) Date: Mon, 16 Nov 2009 12:14:00 +0100 Subject: Introduction and Command Line Survival Guide Message-ID: Hi everyone, my name is Vedran Mileti? and I work as a teaching and research assistant at Department of informatics, University in Rijeka, Croatia. I teach lab exercises in Operating systems and auditory exercises in Computer networks, and in Operating systems we learn how to work in Linux environment. A the moment, we use "Mandrake Command Line Reference" dating back in October 2004. Certainly, lots of things remained the same, but some have changed. In order to make a new textbook for our students and new Fedora users interested in command line in general, I applied to this group. I see there is already a draft of Command Line Survival Guide at http://fedoraproject.org/wiki/Docs/Drafts/CommandLineSurvivalGuide and it covers pretty much what I want. I tried contacting James McElhannon who was working on it, but the domain of his mail adress is dead. That being said, I would like to take the work on this and continue where he left it, if someone is willing to point me how to do it. Hope we can create something great and useful (and ready in time for Fedora 13 release!). Regards, -- Vedran Mileti? From r.landmann at redhat.com Mon Nov 16 12:57:14 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 16 Nov 2009 22:57:14 +1000 Subject: Introduction and Command Line Survival Guide In-Reply-To: References: Message-ID: <4B014C2A.6020901@redhat.com> On 11/16/2009 09:14 PM, Vedran Mileti? wrote:That being said, I would like to take the work on this and continue > where he left it, if someone is willing to point me how to do it. Hope > we can create something great and useful (and ready in time for Fedora > 13 release!) Hi Vedran and welcome! This would be a fantastic resource to add to our collection of documents -- thanks for volunteering to develop it further. Generally, we author our docs in DocBook XML, and host the source files on fedorahosted. We then use a DocBook publishing tool called Publican to build HTML and PDF versions of the documents for publication on the docs.fedoraproject.org site. Most of the docs team are busy for the next day or two publishing the Fedora 12 documents, but if you can be patient with us, we'll be happy to help you set up a new project for your book. You'll find us on IRC in #fedora-docs on freenode -- this is probably the easiest way to keep in touch and get help. Don't worry if you haven't worked with XML before -- there are plenty of us who will help ease you into it once the current crisis is over :) Until we get your new project set up, you can make a start by expanding the existing wiki page that you have already found. Please feel free to jump straight in and start editing. This content can then be moved to XML fairly easily later. Welcome once again Cheers Ruediger From eric at christensenplace.us Mon Nov 16 13:32:36 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 16 Nov 2009 08:32:36 -0500 Subject: Introduction and Command Line Survival Guide In-Reply-To: References: Message-ID: <20091116133234.GD2226@desk.christensenplace.us> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 16, 2009 at 12:14:00PM +0100, Vedran Mileti? wrote: > Hi everyone, > > my name is Vedran Mileti? and I work as a teaching and research > assistant at Department of informatics, University in Rijeka, Croatia. > I teach lab exercises in Operating systems and auditory exercises in > Computer networks, and in Operating systems we learn how to work in > Linux environment. Welcome Vedran. I saw your questions on IRC this morning but only hours after you had posted them. > > A the moment, we use "Mandrake Command Line Reference" dating back in > October 2004. Certainly, lots of things remained the same, but some > have changed. I can imagine things change quite quickly. Having access to the source would help keep subjects up to date. I wonder how much information in the User Guide we could break out and use for a guide that would help you. > > In order to make a new textbook for our students and new Fedora users > interested in command line in general, I applied to this group. > > I see there is already a draft of Command Line Survival Guide at > http://fedoraproject.org/wiki/Docs/Drafts/CommandLineSurvivalGuide and > it covers pretty much what I want. I tried contacting James McElhannon > who was working on it, but the domain of his mail adress is dead. I just looked at this history of that wiki page and it appears no one has touched it this year. > > That being said, I would like to take the work on this and continue > where he left it, if someone is willing to point me how to do it. Hope > we can create something great and useful (and ready in time for Fedora > 13 release!). Works for me! It might be best to move it into DocBook XML format for publication. Are you familiar with DocBook? I can get a repo setup on Fedora Hosted and you can keep the source there. > > Regards, > > -- > Vedran Mileti? > - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksBVHIACgkQfQTSQL0MFMFsngCfVeEmVI0RY88UE7gkrCGPRS86 uKoAnAlH1czDcmfqGKogddummqL8BFiG =tzDL -----END PGP SIGNATURE----- From ath.samaras at gmail.com Mon Nov 16 17:25:58 2009 From: ath.samaras at gmail.com (Athanasios E. Samaras) Date: Mon, 16 Nov 2009 19:25:58 +0200 Subject: Introduction and Command Line Survival Guide In-Reply-To: <20091116133234.GD2226@desk.christensenplace.us> References: <20091116133234.GD2226@desk.christensenplace.us> Message-ID: for a quick how-to take a look at this video (few days old:) http://mchua.fedorapeople.org/how%2520to%2520become%2520a%2520docs%2520contributor. mp4 ~Sakis On Mon, Nov 16, 2009 at 3:32 PM, Eric Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, Nov 16, 2009 at 12:14:00PM +0100, Vedran Mileti? wrote: > > Hi everyone, > > > > my name is Vedran Mileti? and I work as a teaching and research > > assistant at Department of informatics, University in Rijeka, Croatia. > > I teach lab exercises in Operating systems and auditory exercises in > > Computer networks, and in Operating systems we learn how to work in > > Linux environment. > > Welcome Vedran. I saw your questions on IRC this morning but only hours > after you had posted them. > > > > > A the moment, we use "Mandrake Command Line Reference" dating back in > > October 2004. Certainly, lots of things remained the same, but some > > have changed. > > I can imagine things change quite quickly. Having access to the source > would help keep subjects up to date. > > I wonder how much information in the User Guide we could break out and > use for a guide that would help you. > > > > > In order to make a new textbook for our students and new Fedora users > > interested in command line in general, I applied to this group. > > > > I see there is already a draft of Command Line Survival Guide at > > http://fedoraproject.org/wiki/Docs/Drafts/CommandLineSurvivalGuide and > > it covers pretty much what I want. I tried contacting James McElhannon > > who was working on it, but the domain of his mail adress is dead. > > I just looked at this history of that wiki page and it appears no one > has touched it this year. > > > > > That being said, I would like to take the work on this and continue > > where he left it, if someone is willing to point me how to do it. Hope > > we can create something great and useful (and ready in time for Fedora > > 13 release!). > > Works for me! It might be best to move it into DocBook XML format for > publication. Are you familiar with DocBook? I can get a repo setup on > Fedora Hosted and you can keep the source there. > > > > > Regards, > > > > -- > > Vedran Mileti? > > > > - --Eric > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAksBVHIACgkQfQTSQL0MFMFsngCfVeEmVI0RY88UE7gkrCGPRS86 > uKoAnAlH1czDcmfqGKogddummqL8BFiG > =tzDL > -----END PGP SIGNATURE----- > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcallawa at redhat.com Mon Nov 16 17:35:23 2009 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Mon, 16 Nov 2009 12:35:23 -0500 Subject: [Fedora-legal-list] Photographs of hardware in Fedora documentation In-Reply-To: <4B00CF51.7050308@redhat.com> References: <4B00CF51.7050308@redhat.com> Message-ID: <4B018D5B.9040000@redhat.com> On 11/15/2009 11:04 PM, Ruediger Landmann wrote: > The new Fedora Wireless Guide includes photographs of different types of > wireless adapter: > > http://sradvan.fedorapeople.org/Wireless_Guide/en-US/html-single/#sect-Wireless_Guide-Hardware-Types_Of_Cards > > > In each case, the manufacturer's logos and/or (obviously) the design of > the hardware itself is visible in the photograph. > > Some questions: > > 1. Are the manufacturer's labels on the hardware and/or the design of > the hardware itself (particularly the styling of the USB adapter in the > first picture) likely to be protected by copyright? Copyright? No. Trademark? Yes. > If so: > > * Is our use of the image to illustrate a generic component of a > particular type likely to be covered by "fair use" for publication in > the United States? I would think so. > * Is this protection likely to cause problems for people who want to > reuse our content? (I'm thinking in particular of places that have no > "fair use" or equivalent concept in their copyright law, or for reusers > who want to use the image in a completely different context) -- and if > so, do we care, or are reusers on their own here? It's possible that this could cause problems for people wishing to reuse our content where fair use is not an established legal concept (Europe comes to mind offhand). Specifically of concern is the logos, I am not aware of any situations where the design of the hardware itself is being trademarked. > 2. Could using specific pieces of hardware to illustrate a generic type > of hardware be construed to be an endorsement of this particular piece > of hardware or its manufacturer? If so, do we want to do this in our docs? It could be construed that way by some. I would advise that we do the following: 1. Add a disclaimer that any products pictured in the documentation are provided for reference only, and that no endorsement or guarantees of supportability are intended. 2. Edit the pictures so that any trademarked logos are either blurred out beyond recognition, or removed entirely. Be careful not to replace a trademarked logo with the Fedora logo, as that would be extremely problematic. Thanks, ~spot From rivanvx at gmail.com Mon Nov 16 19:39:46 2009 From: rivanvx at gmail.com (=?UTF-8?Q?Vedran_Mileti=C4=87?=) Date: Mon, 16 Nov 2009 20:39:46 +0100 Subject: Introduction and Command Line Survival Guide In-Reply-To: References: <20091116133234.GD2226@desk.christensenplace.us> Message-ID: Interesting. Is there a higher quality version of this? -- Vedran Mileti? On Mon, Nov 16, 2009 at 6:25 PM, Athanasios E. Samaras wrote: > > for a quick how-to take a look at this video (few days old:) > > http://mchua.fedorapeople.org/how%2520to%2520become%2520a%2520docs%2520contributor.mp4 > > > ~Sakis > > On Mon, Nov 16, 2009 at 3:32 PM, Eric Christensen > wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Mon, Nov 16, 2009 at 12:14:00PM +0100, Vedran Mileti? wrote: >> ?> Hi everyone, >> ?> >> ?> my name is Vedran Mileti? and I work as a teaching and research >> ?> assistant at Department of informatics, University in Rijeka, Croatia. >> ?> I teach lab exercises in Operating systems and auditory exercises in >> ?> Computer networks, and in Operating systems we learn how to work in >> ?> Linux environment. >> >> Welcome Vedran. ?I saw your questions on IRC this morning but only hours >> after you had posted them. >> >> ?> >> ?> A the moment, we use "Mandrake Command Line Reference" dating back in >> ?> October 2004. Certainly, lots of things remained the same, but some >> ?> have changed. >> >> I can imagine things change quite quickly. ?Having access to the source >> would help keep subjects up to date. >> >> I wonder how much information in the User Guide we could break out and >> use for a guide that would help you. >> >> ?> >> ?> In order to make a new textbook for our students and new Fedora users >> ?> interested in command line in general, I applied to this group. >> ?> >> ?> I see there is already a draft of Command Line Survival Guide at >> ?> http://fedoraproject.org/wiki/Docs/Drafts/CommandLineSurvivalGuide and >> ?> it covers pretty much what I want. I tried contacting James McElhannon >> ?> who was working on it, but the domain of his mail adress is dead. >> >> I just looked at this history of that wiki page and it appears no one >> has touched it this year. >> >> ?> >> ?> That being said, I would like to take the work on this and continue >> ?> where he left it, if someone is willing to point me how to do it. Hope >> ?> we can create something great and useful (and ready in time for Fedora >> ?> 13 release!). >> >> Works for me! ?It might be best to move it into DocBook XML format for >> publication. ?Are you familiar with DocBook? ?I can get a repo setup on >> Fedora Hosted and you can keep the source there. >> >> ?> >> ?> Regards, >> ?> >> ?> -- >> ?> Vedran Mileti? >> ?> >> >> - --Eric >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.10 (GNU/Linux) >> >> iEYEARECAAYFAksBVHIACgkQfQTSQL0MFMFsngCfVeEmVI0RY88UE7gkrCGPRS86 >> uKoAnAlH1czDcmfqGKogddummqL8BFiG >> =tzDL >> -----END PGP SIGNATURE----- >> >> -- >> fedora-docs-list mailing list >> fedora-docs-list at redhat.com >> To unsubscribe: >> https://www.redhat.com/mailman/listinfo/fedora-docs-list > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From ath.samaras at gmail.com Mon Nov 16 19:59:16 2009 From: ath.samaras at gmail.com (Athanasios E. Samaras) Date: Mon, 16 Nov 2009 21:59:16 +0200 Subject: Introduction and Command Line Survival Guide In-Reply-To: References: <20091116133234.GD2226@desk.christensenplace.us> Message-ID: Soon to be released, it is initial material 2009/11/16 Vedran Mileti? > Interesting. Is there a higher quality version of this? > > -- > Vedran Mileti? > > On Mon, Nov 16, 2009 at 6:25 PM, Athanasios E. Samaras > wrote: > > > > for a quick how-to take a look at this video (few days old:) > > > > > http://mchua.fedorapeople.org/how%2520to%2520become%2520a%2520docs%2520contributor.mp4 > > > > > > ~Sakis > > > > On Mon, Nov 16, 2009 at 3:32 PM, Eric Christensen < > eric at christensenplace.us> > > wrote: > >> > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> On Mon, Nov 16, 2009 at 12:14:00PM +0100, Vedran Mileti? wrote: > >> > Hi everyone, > >> > > >> > my name is Vedran Mileti? and I work as a teaching and research > >> > assistant at Department of informatics, University in Rijeka, > Croatia. > >> > I teach lab exercises in Operating systems and auditory exercises in > >> > Computer networks, and in Operating systems we learn how to work in > >> > Linux environment. > >> > >> Welcome Vedran. I saw your questions on IRC this morning but only hours > >> after you had posted them. > >> > >> > > >> > A the moment, we use "Mandrake Command Line Reference" dating back in > >> > October 2004. Certainly, lots of things remained the same, but some > >> > have changed. > >> > >> I can imagine things change quite quickly. Having access to the source > >> would help keep subjects up to date. > >> > >> I wonder how much information in the User Guide we could break out and > >> use for a guide that would help you. > >> > >> > > >> > In order to make a new textbook for our students and new Fedora users > >> > interested in command line in general, I applied to this group. > >> > > >> > I see there is already a draft of Command Line Survival Guide at > >> > http://fedoraproject.org/wiki/Docs/Drafts/CommandLineSurvivalGuideand > >> > it covers pretty much what I want. I tried contacting James > McElhannon > >> > who was working on it, but the domain of his mail adress is dead. > >> > >> I just looked at this history of that wiki page and it appears no one > >> has touched it this year. > >> > >> > > >> > That being said, I would like to take the work on this and continue > >> > where he left it, if someone is willing to point me how to do it. > Hope > >> > we can create something great and useful (and ready in time for > Fedora > >> > 13 release!). > >> > >> Works for me! It might be best to move it into DocBook XML format for > >> publication. Are you familiar with DocBook? I can get a repo setup on > >> Fedora Hosted and you can keep the source there. > >> > >> > > >> > Regards, > >> > > >> > -- > >> > Vedran Mileti? > >> > > >> > >> - --Eric > >> -----BEGIN PGP SIGNATURE----- > >> Version: GnuPG v1.4.10 (GNU/Linux) > >> > >> iEYEARECAAYFAksBVHIACgkQfQTSQL0MFMFsngCfVeEmVI0RY88UE7gkrCGPRS86 > >> uKoAnAlH1czDcmfqGKogddummqL8BFiG > >> =tzDL > >> -----END PGP SIGNATURE----- > >> > >> -- > >> fedora-docs-list mailing list > >> fedora-docs-list at redhat.com > >> To unsubscribe: > >> https://www.redhat.com/mailman/listinfo/fedora-docs-list > > > > > > -- > > fedora-docs-list mailing list > > fedora-docs-list at redhat.com > > To unsubscribe: > > https://www.redhat.com/mailman/listinfo/fedora-docs-list > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanlerch at gmail.com Mon Nov 16 23:09:56 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Tue, 17 Nov 2009 09:09:56 +1000 Subject: [Design-team] Documentation Logo Design In-Reply-To: <4B01A11F.6020206@fedoraproject.org> References: <671a617b0911151743s1c2be9b9i388fd17272f5c1d2@mail.gmail.com> <4B00B72F.8050609@fedoraproject.org> <4B00C969.3010808@redhat.com> <4B010ADD.2010506@fedoraproject.org> <4B014806.1050303@redhat.com> <4B01A11F.6020206@fedoraproject.org> Message-ID: <671a617b0911161509w726f899cxad53291d5393c60e@mail.gmail.com> Luya, Publican (the toolchain that produces these documents) has a tight structure built around Products (and their logos), Book Titles and Sub Titles. The elements that are seen in the first mockup are essentially the "Front Cover" of the book, and IMO are needed in this circumstance. Changing these elements is also a lot harder than changing the image that rudi requested, as the tool itself (Publican) would need to be changed. That said, i agree with the word "fedora" being used too much (especially with the non logotype "fedora" that was in my first design) So, with some help and guidance from Rudi and Mo, i decided to go with a simpler text only header to replace the "made with publican" image. A test book with the new image can be viewed here: http://ryanlerch.fedorapeople.org/fedora-docs-logo/html/index.html cheers, ryanlerch On Tue, Nov 17, 2009 at 4:59 AM, Luya Tshimbalanga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/16/2009 04:39 AM, Ruediger Landmann wrote: >> On 11/16/2009 06:18 PM, Luya Tshimbalanga wrote: >>> Here is illustration? the document: >>> http://luya.fedorapeople.org/images/mockup-redundancy.png >>> >>> You noticed there are at least four Fedora names on that page alone >>> which is an overkill >>> for header. >> >> Sorry Luya -- I get a 404 for that URL >> >>> I made illustration for suggestion below: >>> >>> http://luya.fedorapeople.org/images/mockup-suggestion.png >>> >> >> And 404 for this one too. >> >>> I understand about the ears. As highlighted, there are a lot of repeated >>> words. I made an alternate version that preserve "Fedora" wordmark >>> (original color and black version included) for image replacing "Made >>> with Publican" >>> >>> http://luya.fedorapeople.org/images/fedora-docs.png >>> >> >> This isn't bad; but I find the change in colour between the word >> "Fedora" and the word "Documentation" quite jarring. >> >>> http://luya.fedorapeople.org/images/fedora-docs-alt.png >>> >> >> 404 for this one >> >>> http://luya.fedorapeople.org/images/fedora-docs.svg > Links fixed. > > > - -- > Luya Tshimbalanga > Graphic & Web Designer > E: luya at fedoraproject.org > W: http://www.thefinalzone.net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAksBoR0ACgkQaS6HaNQHFTmOIgCfaiOWY6JiMzx0DHVR1w494zdW > 5qMAn0ZiPOoiA+v3QKUs4q5vQs68kXqQ > =cj9B > -----END PGP SIGNATURE----- > > > _______________________________________________ > design-team mailing list > design-team at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/design-team > > From stickster at gmail.com Tue Nov 17 01:01:03 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 16 Nov 2009 20:01:03 -0500 Subject: Announcement tomorrow Message-ID: <20091117010103.GI12310@victoria.internal.frields.org> I'll be using the text found here for tomorrow's announcement to fedora-announce-list: https://fedoraproject.org/wiki/Fedora_12_Announcement I noticed we've dropped our old legacy habit of producing a humorous preface, in favor of a more cut and dried approach. I'll likely precede the text with a short (promise!) thank-you note and a URL for http://get.fedoraproject.org at the top, for people who want to cut to the chase. Thanks to everyone who worked on the announcement text. -- 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 From sundaram at fedoraproject.org Tue Nov 17 01:13:43 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 17 Nov 2009 06:43:43 +0530 Subject: Announcement tomorrow In-Reply-To: <20091117010103.GI12310@victoria.internal.frields.org> References: <20091117010103.GI12310@victoria.internal.frields.org> Message-ID: <4B01F8C7.8050403@fedoraproject.org> On 11/17/2009 06:31 AM, Paul W. Frields wrote: > I'll be using the text found here for tomorrow's announcement to > fedora-announce-list: > > https://fedoraproject.org/wiki/Fedora_12_Announcement > > I noticed we've dropped our old legacy habit of producing a humorous > preface, in favor of a more cut and dried approach. I'll likely > precede the text with a short (promise!) thank-you note and a URL for > http://get.fedoraproject.org at the top, for people who want to cut to > the chase. > > Thanks to everyone who worked on the announcement text. I just realized that I didn't actually discuss that choice. I thought our Fedora 12 Beta announcement got good reactions and wanted to just improve on that with minor tweaks rather than use the humour approach. Hope that is ok with everyone. Rahul From eric at christensenplace.us Tue Nov 17 04:42:32 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 16 Nov 2009 23:42:32 -0500 Subject: Announcement tomorrow In-Reply-To: <4B01F8C7.8050403@fedoraproject.org> References: <20091117010103.GI12310@victoria.internal.frields.org> <4B01F8C7.8050403@fedoraproject.org> Message-ID: <1258432952.5463.1.camel@localhost> On Tue, 2009-11-17 at 06:43 +0530, Rahul Sundaram wrote: > On 11/17/2009 06:31 AM, Paul W. Frields wrote: > > I'll be using the text found here for tomorrow's announcement to > > fedora-announce-list: > > > > https://fedoraproject.org/wiki/Fedora_12_Announcement > > > > I noticed we've dropped our old legacy habit of producing a humorous > > preface, in favor of a more cut and dried approach. I'll likely > > precede the text with a short (promise!) thank-you note and a URL for > > http://get.fedoraproject.org at the top, for people who want to cut to > > the chase. > > > > Thanks to everyone who worked on the announcement text. > > I just realized that I didn't actually discuss that choice. I thought > our Fedora 12 Beta announcement got good reactions and wanted to just > improve on that with minor tweaks rather than use the humour approach. > Hope that is ok with everyone. > > Rahul > Works for me. I was just happy that someone had tweaked it for final! :) --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Tue Nov 17 12:54:36 2009 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 17 Nov 2009 07:54:36 -0500 Subject: Announcement tomorrow In-Reply-To: <1258432952.5463.1.camel@localhost> References: <20091117010103.GI12310@victoria.internal.frields.org> <4B01F8C7.8050403@fedoraproject.org> <1258432952.5463.1.camel@localhost> Message-ID: <20091117125436.GC20907@victoria.internal.frields.org> On Mon, Nov 16, 2009 at 11:42:32PM -0500, Eric Christensen wrote: > On Tue, 2009-11-17 at 06:43 +0530, Rahul Sundaram wrote: > > On 11/17/2009 06:31 AM, Paul W. Frields wrote: > > > I'll be using the text found here for tomorrow's announcement to > > > fedora-announce-list: > > > > > > https://fedoraproject.org/wiki/Fedora_12_Announcement > > > > > > I noticed we've dropped our old legacy habit of producing a humorous > > > preface, in favor of a more cut and dried approach. I'll likely > > > precede the text with a short (promise!) thank-you note and a URL for > > > http://get.fedoraproject.org at the top, for people who want to cut to > > > the chase. > > > > > > Thanks to everyone who worked on the announcement text. > > > > I just realized that I didn't actually discuss that choice. I thought > > our Fedora 12 Beta announcement got good reactions and wanted to just > > improve on that with minor tweaks rather than use the humour approach. > > Hope that is ok with everyone. > > > > Rahul > > > > Works for me. I was just happy that someone had tweaked it for > final! :) I just went through and did a final once-over for grammar/style tweaks. I'm now copying it for posting to the 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 From piotrdrag at gmail.com Tue Nov 17 17:49:00 2009 From: piotrdrag at gmail.com (=?UTF-8?B?UGlvdHIgRHLEhWc=?=) Date: Tue, 17 Nov 2009 18:49:00 +0100 Subject: Branch 'f12zeroday-tx' - po/pl.po In-Reply-To: <20091117174235.5ACC01201F5@lists.fedorahosted.org> References: <20091117174235.5ACC01201F5@lists.fedorahosted.org> Message-ID: <4B02E20C.7040003@gmail.com> W dniu 17.11.2009 18:42, Transifex System User pisze: > po/pl.po | 1305 +++++++++++++++++++++++++++++++-------------------------------- > 1 file changed, 656 insertions(+), 649 deletions(-) > > New commits: > commit 8070f99d6a7ad8c6419e88260b50d046eb2d66df > Author: raven > Date: Tue Nov 17 17:42:19 2009 +0000 > > Sending translation for Polish > We did proofreading a bit late because of some random real life troubles. Could you please re-generate Polish release notes with this new revision? -- Piotr Dr?g http://raven.pmail.pl From eric at christensenplace.us Tue Nov 17 19:54:17 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 17 Nov 2009 14:54:17 -0500 Subject: Check your guides! Message-ID: Please go to docs.fedoraproject.org and check your guides to make sure that they are being displayed properly and that the links are functioning properly. I know there are a couple of problems but I need to make sure that we find them all. --Eric From mel at redhat.com Tue Nov 17 22:19:45 2009 From: mel at redhat.com (Mel Chua) Date: Tue, 17 Nov 2009 16:19:45 -0600 Subject: [[DocsProject/Licensing/FAQ]] still refers to the OPL Message-ID: <4B032181.2080903@redhat.com> https://fedoraproject.org/wiki/DocsProject/Licensing/FAQ still refers to the old OPL license - I put a reminder on the talk page (https://fedoraproject.org/wiki/Talk:Docs_Project_licensing_FAQ) to revise it and linked to the https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA explanation page. This is the main page on docs licensing that you find if you follow https://fedoraproject.org/wiki/Legal/Licenses. I'd go and make the changes myself now if I weren't boarding a plane to Tokyo in a couple minutes. --Mel From r.landmann at redhat.com Tue Nov 17 22:30:14 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 18 Nov 2009 08:30:14 +1000 Subject: Check your guides! In-Reply-To: References: Message-ID: <4B0323F6.6080008@redhat.com> On 11/18/2009 05:54 AM, Eric Christensen wrote: > Please go to docs.fedoraproject.org and check your guides to make sure > that they are being displayed properly and that the links are > functioning properly. I know there are a couple of problems but I > need to make sure that we find them all. > I've just removed the draft tags from the Security Guide and fixed the links to the Managing Confined Services Guide From eric at christensenplace.us Tue Nov 17 23:38:15 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 17 Nov 2009 18:38:15 -0500 Subject: Check your guides! In-Reply-To: <4B0323F6.6080008@redhat.com> References: <4B0323F6.6080008@redhat.com> Message-ID: <1258501095.2214.1.camel@localhost> On Wed, 2009-11-18 at 08:30 +1000, Ruediger Landmann wrote: > On 11/18/2009 05:54 AM, Eric Christensen wrote: > > Please go to docs.fedoraproject.org and check your guides to make sure > > that they are being displayed properly and that the links are > > functioning properly. I know there are a couple of problems but I > > need to make sure that we find them all. > > > > I've just removed the draft tags from the Security Guide and fixed the > links to the Managing Confined Services Guide > Thank you! --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Tue Nov 17 23:43:54 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 17 Nov 2009 18:43:54 -0500 Subject: [[DocsProject/Licensing/FAQ]] still refers to the OPL In-Reply-To: <4B032181.2080903@redhat.com> References: <4B032181.2080903@redhat.com> Message-ID: <1258501434.2214.5.camel@localhost> On Tue, 2009-11-17 at 16:19 -0600, Mel Chua wrote: > https://fedoraproject.org/wiki/DocsProject/Licensing/FAQ still refers to > the old OPL license - I put a reminder on the talk page > (https://fedoraproject.org/wiki/Talk:Docs_Project_licensing_FAQ) to > revise it and linked to the > https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA explanation page. > > This is the main page on docs licensing that you find if you follow > https://fedoraproject.org/wiki/Legal/Licenses. I'd go and make the > changes myself now if I weren't boarding a plane to Tokyo in a couple > minutes. > > --Mel > I think I posted something about this on the Talk page of the Legal page but I can't change that. I'll get to work on the DocsProject page. There is a lot of information that will need to be changed there. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From ryanlerch at gmail.com Tue Nov 17 23:56:35 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Wed, 18 Nov 2009 09:56:35 +1000 Subject: Check your guides! In-Reply-To: <1258501095.2214.1.camel@localhost> References: <4B0323F6.6080008@redhat.com> <1258501095.2214.1.camel@localhost> Message-ID: <671a617b0911171556y57fea95cwb18f33c9c530090@mail.gmail.com> I am doing a check of all the guides (for f12 in all langs). Just did the Release Notes, and found that everything was good, apart from the following still having the DRAFT watermark: http://docs.fedoraproject.org/release-notes/f12/pt-PT/html/ http://docs.fedoraproject.org/release-notes/f12/pt-BR/html/ http://docs.fedoraproject.org/release-notes/f12/pt-PT/html-single/ http://docs.fedoraproject.org/release-notes/f12/pt-BR/html-single/ will post more issues as i come across them. cheers, ryanlerch On Wed, Nov 18, 2009 at 9:38 AM, Eric Christensen wrote: > On Wed, 2009-11-18 at 08:30 +1000, Ruediger Landmann wrote: >> On 11/18/2009 05:54 AM, Eric Christensen wrote: >> > Please go to docs.fedoraproject.org and check your guides to make sure >> > that they are being displayed properly and that the links are >> > functioning properly. ?I know there are a couple of problems but I >> > need to make sure that we find them all. >> > >> >> I've just removed the draft tags from the Security Guide and fixed the >> links to the Managing Confined Services Guide >> > > Thank you! > > --Eric > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From r.landmann at redhat.com Wed Nov 18 00:06:15 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 18 Nov 2009 10:06:15 +1000 Subject: Check your guides! In-Reply-To: <671a617b0911171556y57fea95cwb18f33c9c530090@mail.gmail.com> References: <4B0323F6.6080008@redhat.com> <1258501095.2214.1.camel@localhost> <671a617b0911171556y57fea95cwb18f33c9c530090@mail.gmail.com> Message-ID: <4B033A77.5000705@redhat.com> On 11/18/2009 09:56 AM, Ryan Lerch wrote: > I am doing a check of all the guides (for f12 in all langs). Just did > the Release Notes, and found that everything was good, apart from the > following still having the DRAFT watermark: > http://docs.fedoraproject.org/release-notes/f12/pt-PT/html/ > http://docs.fedoraproject.org/release-notes/f12/pt-BR/html/ > http://docs.fedoraproject.org/release-notes/f12/pt-PT/html-single/ > http://docs.fedoraproject.org/release-notes/f12/pt-BR/html-single/ > > These are still marked draft because the translation of the final version of the RN was not completed when they were published Since then, pt-PT has been completed; I'm republishing now From wb8rcr at arrl.net Wed Nov 18 00:21:05 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Tue, 17 Nov 2009 19:21:05 -0500 Subject: Branch 'f12zeroday-tx' - po/pl.po References: <20091117174235.5ACC01201F5@lists.fedorahosted.org> <4B02E20C.7040003@gmail.com> Message-ID: <406E5C77B3C247A1B8FAC507A3B73DBE@Aidan> Piotr When we switched to the f12ga-tx branch on release notes, I changed the job that was building the "beta" release notes to that branch. Unfortunately, when we switched to the f12zeroday-tx branch, I forgot. I have since changed it, and I ran the pl-PL which is now at http://fedora.is-sixsigma.com/F12beta/pl-PL/. All the languages will continue to get rebuilt each night (US time). It looks as if a few more errors have crept in during the week or so the job hasn't been running. I'll see if I can't identify them and post them to the trans-list. The schedule has us making a "final" RPM on Thursday, so any translations that want to be in the RPM will need to be complete by then. I don't see a reason that HAS to be Thursday, though, so if it looks like we might get a few more translations by dragging our feet a couple of days it might make sense to do that. Only a handful of languages went into the release. As more reach 100% we are posting them to docs.fedoraproject.org. We may well make additional update RPMs during the life of Fedora 12. How many depends on what errors we find, what translations become complete, etc. Some of you may have noticed a new f12-temp branch. We got quite a list of typos, and decided to correct them in that branch. Most were truly typos, not really likely to affect the translations. Eventually we will merge them back into the main branch. --McD ----- Original Message ----- From: "Piotr Dr?g" To: Sent: Tuesday, November 17, 2009 12:49 PM Subject: Re: Branch 'f12zeroday-tx' - po/pl.po W dniu 17.11.2009 18:42, Transifex System User pisze: > po/pl.po | 1305 > +++++++++++++++++++++++++++++++-------------------------------- > 1 file changed, 656 insertions(+), 649 deletions(-) > > New commits: > commit 8070f99d6a7ad8c6419e88260b50d046eb2d66df > Author: raven > Date: Tue Nov 17 17:42:19 2009 +0000 > > Sending translation for Polish > We did proofreading a bit late because of some random real life troubles. Could you please re-generate Polish release notes with this new revision? -- Piotr Dr?g http://raven.pmail.pl -- fedora-docs-list mailing list fedora-docs-list at redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list From wb8rcr at arrl.net Wed Nov 18 14:12:40 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 18 Nov 2009 09:12:40 -0500 Subject: Issues with Release Notes translations Message-ID: <614A0FCE5C984802B8DF044FB91FEF05@Aidan> This is really to set up a discussion probably between me and rudi when the sun comes up for him, but everyone should at least be aware of this problem. This morning I noticed that zh-CN had reached 100%, but that translation has been thick with errors for the past few weeks, so I decided to send a note to trans-list identifying the types of errors. I was later surprised to see that rudi had pushed the zh-CN to docs.fp.o, surprising since the document wouldn't build, at least, as of a job that started about an hour before rudi pushed it! Anyway, when I looked through the document, I noticed a number of entire sections that were untranslated. Odd, since Transifex shows it at 100%. Now I have to admit, I've been happy to see translations complete, and generally I take a quick peek to see that they look about right, but I haven't been going through documents in languages I can't read in their entirety. I looked at a couple of other docs on docs.fp.o and some of the same sections were untranslated. I was about to blame Publican for producing an incomplete pot (sure, blame it on Publican), but then I found some docs where those same sections were translated. That leads me to suspect that something in the interaction between git and Transifex is causing the issue. As you may or may not be aware, we have been branching liberally to try to keep the translations straight. I suspect what happened is that some of the pos were checked out from transifex when we branched, and the old po overwrote the new po. Normally git would scream bloody murder (and make your life miserable) if you tried to do this sort of thing, but depending on how Transifex interacts with git, it might work around this problem. I'm not sure the best way to correct this. I suspect we need to identify the problem pos and merge them with the current pot, but I don't know enough about Transifex to know what this might break. --McD From dimitris at glezos.com Wed Nov 18 15:13:07 2009 From: dimitris at glezos.com (Dimitris Glezos) Date: Wed, 18 Nov 2009 17:13:07 +0200 Subject: Issues with Release Notes translations In-Reply-To: <614A0FCE5C984802B8DF044FB91FEF05@Aidan> References: <614A0FCE5C984802B8DF044FB91FEF05@Aidan> Message-ID: <6d4237680911180713v7395d87q87a045194421028@mail.gmail.com> On Wed, Nov 18, 2009 at 4:12 PM, John J. McDonough wrote: > I noticed a number of entire > sections that were untranslated. ?Odd, since Transifex shows it at 100%. John, can you take a look at this FAQ and see if it helps out? http://fedoraproject.org/wiki/L10N/FAQ#My_file_is_100.25_but_when_I_test_the_application_I_still_see_English_strings.21_.28.23missing-strings.29 -d -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/ From wb8rcr at arrl.net Wed Nov 18 16:03:13 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 18 Nov 2009 11:03:13 -0500 Subject: More details on Issues with Release Notes translations Message-ID: Going through all the languages on docs.fp.o I find some interesting things. pt-BR is marked draft and is, in fact, older than the others. It is missing the sections that are not translated in the other languages. I think the discoonect here is that on the first push to docs.fp.o, I pushed all languages that were at greater than 90%. Since then we have only pushed 100%. pt-BR is still only at 92%. We probably should bring up on the trans list whether we want to wait for 100%. The French team in particular objected to pushing partly translated documents. I suspect some of the others may want to see mostly translated documents published. In all the other languages, 4.1.6, 5.2.2, 5.6.1, and 5.7.1 are not translated All are missing the revision history Titles for 7.5 and 8.9 are untranslated Title for 4.4 is untranslated in all except Chinese and Russian Title for 4.1 is untranslated in Dutch On the copies I ran last night (http://fedora.is-sixsigma.com/F12beta/), I only checked Dutch, Portuguese, Polish and Spanish. On those, all of the sections untranslated on docs.fp.o were translated. In Dutch, Portuguese and Polish, the title for 8.9 was translated. OK, so now I know less than I did before! --McD From wb8rcr at arrl.net Wed Nov 18 16:08:48 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 18 Nov 2009 11:08:48 -0500 Subject: Issues with Release Notes translations References: <614A0FCE5C984802B8DF044FB91FEF05@Aidan> <6d4237680911180713v7395d87q87a045194421028@mail.gmail.com> Message-ID: <6C677FE5CD57475B9A38F995C2F1823E@Aidan> Dimitris Since the versions I am running nightly have more translated than the docs.fp.o copies, I am thinking maybe the docs.fp.o copies used po files from one branch back. Still, there are some inconsistencies, like why are some titles translated in some languages and not others. --McD ----- Original Message ----- From: "Dimitris Glezos" To: "John J. McDonough" Cc: "For participants of the Documentation Project" ; "Ruediger Landmann" Sent: Wednesday, November 18, 2009 10:13 AM Subject: Re: Issues with Release Notes translations On Wed, Nov 18, 2009 at 4:12 PM, John J. McDonough wrote: > I noticed a number of entire > sections that were untranslated. Odd, since Transifex shows it at 100%. John, can you take a look at this FAQ and see if it helps out? http://fedoraproject.org/wiki/L10N/FAQ#My_file_is_100.25_but_when_I_test_the_application_I_still_see_English_strings.21_.28.23missing-strings.29 -d -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/ From eric at christensenplace.us Wed Nov 18 22:55:22 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 18 Nov 2009 17:55:22 -0500 Subject: Fedora Docs Meeting Reminder Message-ID: <1258584922.2544.1.camel@localhost> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From r.landmann at redhat.com Thu Nov 19 00:07:10 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 19 Nov 2009 10:07:10 +1000 Subject: More details on Issues with Release Notes translations In-Reply-To: References: Message-ID: <4B048C2E.90704@redhat.com> On 11/19/2009 02:03 AM, John J. McDonough wrote: > Going through all the languages on docs.fp.o I find some interesting > things. > > pt-BR is marked draft and is, in fact, older than the others. It is > missing the sections that are not translated in the other languages. I > think the discoonect here is that on the first push to docs.fp.o, I > pushed all languages that were at greater than 90%. Since then we have > only pushed 100%. pt-BR is still only at 92%. Correct -- this (and the Czech HTML version) are incomplete translations of an earlier version of the doc. > > We probably should bring up on the trans list whether we want to wait > for 100%. The French team in particular objected to pushing partly > translated documents. I suspect some of the others may want to see > mostly translated documents published. We also need to distinguish between parking partial translations somewhere for translators to proofread (at least until we get Transifex 0.7, which will make it much easier for translators to build the docs themselves) and publishing them on d.fp.o. While it's only docs maintainers publishing the docs, I think we can only hope to agree on a threshold (whether 100%, 95%, or whatever) to apply to all translations. Another (and I think, better) alternative is that once it becomes easy for translators to build the docs themselves, then the leaders (and possibly other members) of the various teams should get commit access to d.fp.o. This way, each team can be responsible for publishing their translation themselves. This way, each team has more control over how and when their work gets published. It also spreads the work around more ? what we're doing now is not really sustainable or scalable. > > In all the other languages, 4.1.6, 5.2.2, 5.6.1, and 5.7.1 are not > translated > All are missing the revision history > Titles for 7.5 and 8.9 are untranslated > Title for 4.4 is untranslated in all except Chinese and Russian > Title for 4.1 is untranslated in Dutch > > On the copies I ran last night > (http://fedora.is-sixsigma.com/F12beta/), I only checked Dutch, > Portuguese, Polish and Spanish. On those, all of the sections > untranslated on docs.fp.o were translated. In Dutch, Portuguese and > Polish, the title for 8.9 was translated. Thanks for the sleuthing, John. I have answers for some of these already ? I'll follow up on the others and post my findings shortly. Cheers Rudi From eric at christensenplace.us Thu Nov 19 01:02:14 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 18 Nov 2009 20:02:14 -0500 Subject: Docs Meeting 2009-11-18 IRC log Message-ID: <1258592535.2544.32.camel@localhost> 00:02:20 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:02:20 Meeting started Thu Nov 19 00:02:20 2009 UTC. The chair is Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:02:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:02:29 #topic Roll Call 00:02:30 * Sparks 00:02:32 * radsy is here 00:02:35 * rudi is here 00:02:38 * bcotton is here 00:02:48 * jjmcd . 00:04:41 * Sparks gives everyone a few more minutes 00:08:21 Okay, let's get started 00:08:41 #chair jjmcd 00:08:41 Current chairs: Sparks jjmcd 00:08:50 #topic Docs Project Leader Elections 00:09:18 When I took this job back in January(?) I wanted to make sure that we had elections for a new leader after F12 got released. 00:09:26 So here is my suggestion... 00:09:47 We take nominations starting tonight and vote next week. 00:09:51 Thoughts? 00:09:59 wikipage 00:10:22 That's a good place to start 00:10:41 sounds like a plan; and the wiki is the natural place for noms to go 00:10:55 Although, we could just agree to re-elect you by acclimation 00:10:55 rudi: Works for me. 00:11:12 I won't take the job unless someone else runs 00:11:13 :) 00:11:25 * Sparks votes for ---> that guy 00:11:41 And I won't run unless I can find a sucker ... errr ... leader for RNs 00:12:04 We should probably figure out if we want to do this yearly or releasely or... 00:12:32 Personally, I could argue for either 00:12:47 Yearly gives somebody a chance to get established 00:12:51 yes 00:13:04 releasely gives is a quicker way to get rid of a turkey 00:14:00 i'd think releasely would be a bit hectic 00:14:10 jjmcd: I think you should be able to get rid of me... err... a turkey at any point 00:14:20 * Sparks establishes https://fedoraproject.org/wiki/Docs_Project_Leader_Elections 00:14:28 So we need an impeachment process? 00:14:45 WE DON'T LIKE YOU ANYMORE... GET OFF THE STAGE! 00:15:14 * jjmcd prefers burning torches 00:15:22 Okay, I'll send out an email after the meeting 00:15:35 #action Sparks to send out email on nominations 00:15:52 Okay, anything else on this topic? 00:16:19 #topic Release Notes 00:16:39 You saw the notes to the list 00:16:42 First I'd like to thank jjmcd and rudi and everyone else who helped in getting the Release Notes completed. 00:17:10 You guys did an awesome job! 00:17:18 Now if our technology could keep up... :) 00:17:25 jjmcd: What are the translation issues? 00:17:27 Ta -- there are still some bugs in the process, but we're getting better :) 00:17:27 They do look nice on the new F12 background - but that's all on mo 00:17:46 rudi is tracking them down, I think most are explainable 00:18:00 We do need to decide when to publish 00:18:20 and I like rudi's idea of moving in a direction of translators publishing, or at least deciding when 00:18:43 And OBTW, as translations are committed, the built docs ARE available 00:18:53 jjmcd: I'd like it if the translators would join us on these meetings... especially around release time 00:19:01 But without building themselves, translators have no view into the errors 00:19:20 Yes, noriko at least was joining us for a while 00:19:25 jjmcd: So we need to do a classroom on how to use Publican? 00:19:32 but they are spread out across timezones 00:19:37 Sparks -- no, the problem is more deep-seated 00:19:42 Well, it is a major PITA until the new TFX 00:19:56 jjmcd: True. Maybe the lead translator for each lang could join us... TZs make it tough 00:20:02 yeah; Tx 0.7 is the blocker 00:20:12 rudi: more deep-seated? 00:20:26 Until then, translators not only need to know how to use publican, but how to wrangle the merging and splitting as well 00:20:45 And that isn't always obvious 00:20:47 yes 00:20:55 and the "how to use Publican" is the least of their worries. 00:21:00 it isn't obvious to me! 00:21:11 Even after all this time, *we* still bungle the merging and splitting 00:21:13 When everything is hunky-dory, we could script it. But things are rarely perfect 00:21:34 (which is the root of most of the English strings we're still seeing cropping up in the translations) 00:21:45 Yep, that was my suspicion 00:22:05 jjmcd -- yeah, confirmed. With yours truly being the chief bungler :) 00:22:43 I will remind docs and trans later where to find the nightly builds of f12zeroday-tx 00:23:11 But there are also some genuinely inexplicable ones, where strings we can see are definitely translated somehow don't get carried across the split... 00:23:11 jjmcd: When will the next batch ready to commit? 00:23:39 Sparks, jjmcd -- we need to make a decision about when and whether to refresh the POTs 00:23:49 rudi: yep. Sparks: Schedule says tomorrow, but I am poking L10N to ask if that makes sense 00:23:49 And we probably need some input from L10N on that 00:24:11 And with the latest flamebug, we may want to do that again real soon now 00:24:32 ya 00:24:39 The refresh would pull in the latest fixes (from f12-temp), plus the flamebug, plus assorted small glitches that are breaking translations 00:25:14 jjmcd -- did you want to do this before or after packaging the RN? 00:25:24 I would also like to get something authoratative on processors. We have an outstanding bug that disagrees with other experts, and I don't know who to believe 00:25:45 rudi, we have a package in the DVD, and a more recent package on updates 00:26:09 We will want to do another probably for the install thing first en then maybe all langs 00:26:16 jjmcd -- Ah OK! so any update is not going to interfere with thath 00:26:23 * that 00:26:25 I don't think we want to wait that one for the translations 00:26:42 yeah, Sparks has been great on getting these things to the repos 00:26:45 OK -- so regenerate today? 00:26:56 sounds good to me 00:27:25 There is more manual than I would like in the packaging, but it isn't some huge deal 00:28:08 The real problem is waiting hours and hours to build all the langs 00:28:16 Well, mostly to merge 00:28:28 BTW, I saw you committed some merged pos 00:28:44 If we can keep up with that, it could be a real help 00:29:16 NP -- I'm trying to make sure that the master branch stays current and ready to build 00:29:24 good, I like that 00:29:46 http://fedora.is-sixsigma.com/F12beta/ - regenerated every night, from t12zeroday even tho it says beta 00:29:58 So -- the other question is -- do we wait till we have an answer on the arches before rebuilding? 00:30:05 *regenerating 00:30:30 I think we need to deal with the install policy immediately 00:31:15 We have text on the policy change ready to insert? 00:31:19 As much as I would like an answer on the other, I think all those guys are burning their cycles on BZ534047 00:31:24 No 00:31:28 Well, there is text 00:31:35 and widespread agreement it is wron 00:32:09 OK -- well, we need something definitive in the f12-temp branch ASAP 00:32:19 radsy -- are you in a position to write it up? 00:32:24 So, I will craft some weasel words that try to avoid the emotion, but we still need a definitive workaround 00:32:43 Yeah -- whether the change is good, bad, or ugly is not relevant to the RN 00:32:58 The fix posted by Seth isn't even available to most people 00:33:03 Just its effects and what to do if you don't like it for whatever reason 00:33:20 You gotta be a policykit developer to even have the tool 00:33:27 It is the what to do that is the problem 00:34:03 Not too hard to describe the change 00:34:44 OK 00:34:51 Does that become 5.2.1, or 4.1? 00:34:55 So where are we going to get that from? 00:35:16 Well, the bug thread hasn't slowed yet 00:35:41 I'd say 5.2.1, with a pointer in 4.1 00:35:59 Oh maybe it has. I couldn't get a word in edgewise earlier, but now it's been an hour since someone commented 00:36:19 On the bug, I'm sure the mailing list is still lively 00:36:39 jjmcd: Would now be a good time to ask for a definitive answer on what needs to go in the RNs? 00:36:48 Or everyone got frustrated with the in-flight collisions on bugzilla 00:37:00 Ask where? 00:37:13 jjmcd: The more I think about it the more I think that PK should just be uninstalled on systems where users shouldn't be installing software... almost makes sense. 00:37:16 jjmcd: On the bug. 00:37:24 Seems like everyone has a horse in this race 00:37:25 jjmcd: you/we still need an answer 00:37:30 yep 00:37:44 * Sparks got hit twice on the same post with a collision 00:37:52 And we need to test it 00:38:09 Much of what has been talked about doesn't work for ordinary mortals 00:38:49 jjmcd: I agree 00:39:10 What I think we are saying, rudi, is that we aren't ready for a full rebuild 00:39:30 jjmcd: Well... work up some text saying what PK does and that a solution is in the works 00:39:31 I'll post en-US as soon as we get an answer, and we can do the big thing tomorrow 00:39:38 yeah, that's what I'm hearing. 00:39:44 jjmcd: If you get the solution before you crash for the night then put it in... 00:39:53 jjmcd: otherwise build it and let's do a push 00:40:02 ok 00:40:02 Yeah, at least on docs.fp.o I can put a warning 00:40:10 WORKSFORME 00:42:26 Okay, anything else on the Release Notes? 00:42:42 rudi, any clue why the rev history is missing from the trans? 00:43:11 jjmcd -- yeah; I turned them off 00:43:16 Oh, OK 00:43:18 when I was building 00:43:38 the changes that you had to make for yelp caused them to blow up when I was building the translated versions 00:43:47 I had no theory about that, as long as there's an answer and it isn't a mystery 00:43:57 And, strapped for time, that seemed like the best solution 00:44:06 oooohhhh, I thought I kept the yelp changes out of git except for the table length 00:44:10 Yeah; no mystery 00:44:38 Hmmm. 00:45:01 So the "xyz changes (cont'd)" shouldn't be in there either? 00:45:09 I cut the max table size down some in the hopes it might help - didn't 00:45:20 Oh yeah, just the tables were shorter 00:45:24 Oh OK 00:45:36 I think I was limiting them to like 250 entries or something, shortened to 100 00:46:05 didn't help,.. but I also hoped they might help you build, too 00:46:20 Well, *something* helped me build 00:46:40 I was finally able to build them on my machine without having to SSH into ryanlerch's :) 00:46:42 Don't you love a good mystery 00:49:29 Okay... Moving on... 00:49:38 #topic Guide Status 00:49:53 Anyone have any problems with their guide or want to talk about their guide? 00:50:37 i did lots of updates to the selinux user-guide yesterday, thanks to a BZ that slipped through the cracks of my memory 00:50:46 got it up in CVS overnight, it's fine now 00:50:55 radsy: Cool! 00:51:01 Anyone else? 00:51:10 basically the removal of setroubleshootd as a permanent daemon 00:52:18 :) 00:52:28 #topic New Guides 00:52:33 Any new guides in the works? 00:53:03 #topic Status on CC license rollout. 00:53:11 For those of you that didn't know... 00:53:28 We have officially changed over to the CC-BY-SA license! 00:53:34 All of these tasks are complete! 00:53:56 Thanks to everyone who made this possible... it was truly a team effort. 00:54:14 #topic All other business 00:54:28 And with six minutes left... does anyone have anything else they'd like to discuss? 00:55:10 https://bugzilla.redhat.com/show_bug.cgi?id=534047 ? :) 00:55:11 Bug 534047: high, low, ---, richard, ASSIGNED, All users get to install software on a machine they do not have the root password to 00:55:41 i'm starting to think we might want to wait for the dust to settle 00:56:04 security response team are trying to find out if it will be reverted 00:56:21 nobody knows it seems... 00:56:35 radsy: IMHO we need to get the word out that right now the vulnerability exists. 00:56:53 your call 00:57:02 if admins/owners don't know that there is a change then they are assuming that they are protected. 00:57:20 but, of course, that is my opinion... 00:57:31 we do have a lot of hits on the RN right now, being so close after release 00:57:54 Yeah 00:58:17 i guess it can't hurt, quick enough to pull if needed 00:58:27 anyone have any thoughts on how Docs should handle the PK ordeal within the next 24-hours? 00:58:42 I'm assuming that within 72-hours we'll know more and can stand down more. 00:58:55 radsy: ya... we can get text up and down very quickly 00:58:56 Well, we could add a note about the *existence* of the issue right now 00:59:08 rudi: Yeah, that's basically what I'm thinking right now 00:59:13 Even if we don't have a suggested fix 00:59:35 I kinda think that if there were a fix out there that most people could implement, we would have heard about it by now... 00:59:42 and mention it's still in contention 00:59:50 radsy +1 01:00:05 yep 01:00:33 Okay... it is the end of our hour. Anything else to discuss before we close? 01:00:55 nice timing :) 01:01:16 Thanks everyone for coming tonight! 01:01:19 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Nov 19 01:02:46 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 18 Nov 2009 20:02:46 -0500 Subject: Docs Meeting 2009-11-18 Summary Message-ID: <1258592566.2544.33.camel@localhost> =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by Sparks at 00:02:20 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2009-11-19/fedora-meeting.2009-11-19-00.02.log.html . Meeting summary --------------- * Roll Call (Sparks, 00:02:29) * Docs Project Leader Elections (Sparks, 00:08:50) * ACTION: Sparks to send out email on nominations (Sparks, 00:15:35) * Release Notes (Sparks, 00:16:19) * LINK: http://fedora.is-sixsigma.com/F12beta/ - regenerated every night, from t12zeroday even tho it says beta (jjmcd, 00:29:46) * Guide Status (Sparks, 00:49:38) * New Guides (Sparks, 00:52:28) * Status on CC license rollout. (Sparks, 00:53:03) * All other business (Sparks, 00:54:14) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=534047 ? :) (radsy, 00:55:10) Meeting ended at 01:01:19 UTC. Action Items ------------ * Sparks to send out email on nominations Action Items, by person ----------------------- * Sparks * Sparks to send out email on nominations * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * Sparks (76) * jjmcd (70) * rudi (44) * radsy (13) * zodbot (3) * bcotton (2) * buggbot (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Nov 19 15:43:19 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 19 Nov 2009 10:43:19 -0500 Subject: Docs Project Leader elections Message-ID: <1258645399.2200.4.camel@localhost> I've started a wiki page[1] to start the process of collecting nominations for the Docs Project Leader. I'd like to hold elections at next week's meeting. If you have a nomination please list it on the wiki! Thanks! [1] https://fedoraproject.org/wiki/Docs_Project_Leader_Elections --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Thu Nov 19 15:48:59 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Thu, 19 Nov 2009 21:18:59 +0530 Subject: Medialess installation Message-ID: <4B0568EB.4000201@fedoraproject.org> Hi, I remember filing a RFE for this long time back and the installation guide was updated. Refer http://docs.fedoraproject.org/install-guide/f8/en_US/ap-medialess-install.html This seems to have been dropped from the recent versions. Was this intentional? Can it be added back? Rahul From eric at christensenplace.us Thu Nov 19 23:25:04 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 19 Nov 2009 18:25:04 -0500 Subject: PK Fix isn't working Message-ID: <1258673104.2440.1.camel@localhost> I just tried the fix (should have done this hours ago) and it doesn't work. My recommendation is to take the fix out of the Release Notes and the Security Guide and say that more information is forthcoming. Thoughts? --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From a.badger at gmail.com Thu Nov 19 23:38:45 2009 From: a.badger at gmail.com (Toshio Kuratomi) Date: Thu, 19 Nov 2009 15:38:45 -0800 Subject: PK Fix isn't working In-Reply-To: <1258673104.2440.1.camel@localhost> References: <1258673104.2440.1.camel@localhost> Message-ID: <20091119233844.GA6665@clingman.lan> On Thu, Nov 19, 2009 at 06:25:04PM -0500, Eric Christensen wrote: > I just tried the fix (should have done this hours ago) and it doesn't > work. > > My recommendation is to take the fix out of the Release Notes and the > Security Guide and say that more information is forthcoming. > > Thoughts? > Is this the fix from skvidal's blog? Might want to ask him about it real quick in case it's something very simple. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Fri Nov 20 04:00:20 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 19 Nov 2009 23:00:20 -0500 Subject: PK Fix isn't working In-Reply-To: <20091119233844.GA6665@clingman.lan> References: <1258673104.2440.1.camel@localhost> <20091119233844.GA6665@clingman.lan> Message-ID: <1258689620.2296.2.camel@localhost> On Thu, 2009-11-19 at 15:38 -0800, Toshio Kuratomi wrote: > On Thu, Nov 19, 2009 at 06:25:04PM -0500, Eric Christensen wrote: > > I just tried the fix (should have done this hours ago) and it doesn't > > work. > > > > My recommendation is to take the fix out of the Release Notes and the > > Security Guide and say that more information is forthcoming. > > > > Thoughts? > > > Is this the fix from skvidal's blog? Might want to ask him about it real > quick in case it's something very simple. > > -Toshio No, I don't think it was. The fix posted came from the BZ ticket. I've verified the current fix functions and it has been added to the latest Release Notes and Security Guide. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Fri Nov 20 06:44:57 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 20 Nov 2009 01:44:57 -0500 Subject: [Bug 533741] License should be CC-BY-SA instead of Open Publication In-Reply-To: References: Message-ID: <200911200644.nAK6iv85019500@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533741 --- Comment #2 from Fedora Update System 2009-11-20 01:44:57 EDT --- publican-fedora-1.2-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-fedora-1.2-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. From eric at christensenplace.us Fri Nov 20 18:14:41 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 20 Nov 2009 13:14:41 -0500 Subject: Moving Docs Project to Category:Docs Project Message-ID: Does anyone have an opinion on moving the current Docs Project wiki page to Category:Docs Project? It would allow a one stop shop, basically, but I don't really see it as a need. Thoughts? --Eric From laubersm at fedoraproject.org Fri Nov 20 19:25:41 2009 From: laubersm at fedoraproject.org (Susan Lauber) Date: Fri, 20 Nov 2009 14:25:41 -0500 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: References: Message-ID: On Fri, Nov 20, 2009 at 1:14 PM, Eric Christensen wrote: > Does anyone have an opinion on moving the current Docs Project wiki > page to Category:Docs Project? ?It would allow a one stop shop, > basically, but I don't really see it as a need. > > Thoughts? At the moment I think there is too much stuff on Docs Project page to just move it to the Category. If it gets trimmed down and sub category names are obvious about where to get more information then sure... I am more interested in seeing the Category:Docs Project cleaned up - and especially if that is the "main" entry point. It currently has 133 pages in it (and 28 subcategories). I went looking for the guides table so I could find a link to whatever I reviewed for somebody and had to sift through a lot of noise. There are a lot of pages that are in sub categories AND the main category that I think should just be in a sub category - a few meeting related items, several events and hackfest notes, a bunch of guide pages (or draft guide pages), and mostly the RN beats... I would also like to see a name change to RH Beats - I don't think it encourages enough outside contribution. As I understand it the beats name came when there are a writer patrolling and adding content for that subject (beat). That was also a time when the content stayed in the wiki until the final move to be packaged. Currently I think the "beat writers" are writing in docbook directly and others can see that with the regular draft builds and add to the notes with bug report, email, or the wiki beats pages. So if the the wiki pages were RN contributions or Release Notes Staging for it might be easier for a new contributor to find a place to add a paragraph about the new features of their favorite app or updated package submission. Those are some of my thoughts... -Susan -- Susan Lauber, (RHCX, RHCA, RHCSS) Lauber System Solutions, Inc. http://www.laubersolutions.com gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 From ian at ianweller.org Sat Nov 21 01:17:15 2009 From: ian at ianweller.org (Ian Weller) Date: Fri, 20 Nov 2009 19:17:15 -0600 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: References: Message-ID: <20091121011715.GA9534@deathray.l.ianweller.org> On Fri, Nov 20, 2009 at 02:25:41PM -0500, Susan Lauber wrote: > At the moment I think there is too much stuff on Docs Project page to > just move it to the Category. If it gets trimmed down and sub > category names are obvious about where to get more information then > sure... > > I am more interested in seeing the Category:Docs Project cleaned up - > and especially if that is the "main" entry point. > It currently has 133 pages in it (and 28 subcategories). I went > looking for the guides table so I could find a link to whatever I > reviewed for somebody and had to sift through a lot of noise. There > are a lot of pages that are in sub categories AND the main category > that I think should just be in a sub category - a few meeting related > items, several events and hackfest notes, a bunch of guide pages (or > draft guide pages), and mostly the RN beats... > +1 from the wiki czar. If confusion will increase (from anybody), don't do it. -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Sat Nov 21 04:25:04 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 20 Nov 2009 23:25:04 -0500 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: <20091121011715.GA9534@deathray.l.ianweller.org> References: <20091121011715.GA9534@deathray.l.ianweller.org> Message-ID: <1258777504.2224.7.camel@localhost> On Fri, 2009-11-20 at 19:17 -0600, Ian Weller wrote: > On Fri, Nov 20, 2009 at 02:25:41PM -0500, Susan Lauber wrote: > > At the moment I think there is too much stuff on Docs Project page to > > just move it to the Category. If it gets trimmed down and sub > > category names are obvious about where to get more information then > > sure... > > > > I am more interested in seeing the Category:Docs Project cleaned up - > > and especially if that is the "main" entry point. > > It currently has 133 pages in it (and 28 subcategories). I went > > looking for the guides table so I could find a link to whatever I > > reviewed for somebody and had to sift through a lot of noise. There > > are a lot of pages that are in sub categories AND the main category > > that I think should just be in a sub category - a few meeting related > > items, several events and hackfest notes, a bunch of guide pages (or > > draft guide pages), and mostly the RN beats... > > > +1 from the wiki czar. If confusion will increase (from anybody), don't > do it. > So we clearly have an organizational problem. I agree that there is way too much stuff out there. From a management point of view I literally live off of the "Docs Project meetings" page. I've almost made it a dashboard of items that I need. So I don't actually sift through much of the other noise that's out there. But if people can't find something that is actually there then that's a problem. If I were to clean up the Docs Project pages I'd want to go through the Documentation category and clean it up/out. If information has been moved to Docbook then it can be archived. Draft documentation needs to be brought to light. New people want something to do, here's a great chance to get involved. Docs Project category... what's even in there? What do we really need in there? What's missing? I know... more questions, not enough answers. If I can catch up on my to do list I'll take a peek in there. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Sat Nov 21 05:21:40 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 21 Nov 2009 00:21:40 -0500 Subject: Medialess installation In-Reply-To: <4B0568EB.4000201@fedoraproject.org> References: <4B0568EB.4000201@fedoraproject.org> Message-ID: <1258780900.2224.9.camel@localhost> On Thu, 2009-11-19 at 21:18 +0530, Rahul Sundaram wrote: > Hi, > > I remember filing a RFE for this long time back and the installation > guide was updated. Refer > > http://docs.fedoraproject.org/install-guide/f8/en_US/ap-medialess-install.html > > This seems to have been dropped from the recent versions. Was this > intentional? Can it be added back? > > Rahul > Have you filed a bug on this? Can you provide the ticket number so I can properly follow up? --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From wb8rcr at arrl.net Sat Nov 21 12:57:37 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Sat, 21 Nov 2009 07:57:37 -0500 Subject: Moving Docs Project to Category:Docs Project References: <20091121011715.GA9534@deathray.l.ianweller.org> <1258777504.2224.7.camel@localhost> Message-ID: ----- Original Message ----- From: "Eric Christensen" To: "For participants of the Documentation Project" Sent: Friday, November 20, 2009 11:25 PM Subject: Re: Moving Docs Project to Category:Docs Project > So I don't actually sift through much of the other noise that's out > there. But if people can't find something that is actually there then > that's a problem. We need to take a harder look at what we want to do. When we got rid of the hierarchical naming so that "search could work", we changed "hard to find" into "impossible to find". And search is just as hopeless as it ever was. Susan mentioned a hundred and some pages in the Docs_Project category. That is a lot, but not totally unmanageable. Unfortunately, I suspect not all relevant pages are in the category. And, really, there are enough pages in the category that it is hard to find what you need. We already have a lot of subcategories; probably too many. Unfortunately, many pages, especially newer pages, aren't in the appropriate subcategory. That failure makes the subcategories mostly useless since they become repositories for documents you don't want to see, kind of like search. If we had a SMALL number of relevant subcategories, our odds of getting a page into the appropriate subcategory would increase. As it is we are lucky to remember to put something into the project category. The odds of knowing what the appropriate subcategory might be are vanishingly small. On top of that, I'm afraid we need a more aggressive wiki gardening effort. Just some thoughts --McD From eric at christensenplace.us Sat Nov 21 15:33:38 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 21 Nov 2009 10:33:38 -0500 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: References: <20091121011715.GA9534@deathray.l.ianweller.org> <1258777504.2224.7.camel@localhost> Message-ID: <1258817618.2192.9.camel@localhost> On Sat, 2009-11-21 at 07:57 -0500, John J. McDonough wrote: > ----- Original Message ----- > From: "Eric Christensen" > To: "For participants of the Documentation Project" > > Sent: Friday, November 20, 2009 11:25 PM > Subject: Re: Moving Docs Project to Category:Docs Project > > > So I don't actually sift through much of the other noise that's out > > there. But if people can't find something that is actually there then > > that's a problem. > > We need to take a harder look at what we want to do. When we got rid of the > hierarchical naming so that "search could work", we changed "hard to find" > into "impossible to find". And search is just as hopeless as it ever was. > > Susan mentioned a hundred and some pages in the Docs_Project category. That > is a lot, but not totally unmanageable. Unfortunately, I suspect not all > relevant pages are in the category. And, really, there are enough pages in > the category that it is hard to find what you need. > > We already have a lot of subcategories; probably too many. Unfortunately, > many pages, especially newer pages, aren't in the appropriate subcategory. > That failure makes the subcategories mostly useless since they become > repositories for documents you don't want to see, kind of like search. > > If we had a SMALL number of relevant subcategories, our odds of getting a > page into the appropriate subcategory would increase. As it is we are lucky > to remember to put something into the project category. The odds of knowing > what the appropriate subcategory might be are vanishingly small. > > On top of that, I'm afraid we need a more aggressive wiki gardening effort. > > Just some thoughts > > --McD > Okay, so what categories do we need? Docs Project Documentation Draft Documentation Docs Project Management? Docs Project SOP -> Docs Project Management Docs Project archives -> Archives Docs Project content tasks for experienced contributors Docs Project content tasks for new contributors Docs Project how to Docs Project meeting logs REMOVE Docs Project meetings Docs Project policies -> Docs Project Management Docs Project process -> ? Docs Project roles -> ? Docs Project tasks -> Docs Project ? Docs Project tools -> Docs Project ? Documentation CMS Option -> Archive Documentation Guide -> Docs Project how to Documentation beats Documentation tools -> Docs Project tools FDSCo -> ? Improving the Docs Project workflow -> ? Release Notes -> Draft Documentation SELinux Docs -> Archive? (Check with Radsy) Software Management Guide -> Archive? User Guide -> Archive Those are all the categories that are currently attached to Docs Project. If we can move stuff around here it might help clear out some of the noise. Maybe Ian can run Wikibot around to clean up this stuff, too. Some of these categories are empty, by the way. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Sat Nov 21 16:31:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 21 Nov 2009 11:31:52 -0500 Subject: Documentation hosted at Fedora Hosted Message-ID: <1258821112.2192.12.camel@localhost> If you have a project that is hosted at Fedora Hosted please add it to the list on the wiki[1]. [1] https://fedoraproject.org/wiki/Documentation_hosted_at_Fedora_Hosted Thank you! --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Sat Nov 21 17:30:42 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 21 Nov 2009 12:30:42 -0500 Subject: Instruction on how to attribute Fedora information in other guides Message-ID: <1258824642.2192.15.camel@localhost> Earlier this week I was editing our licensing FAQ[1] on the wiki (was still showing OPL instead of CC-BY-SA) and both Spot and Richard made some edits to clarify some points. One thing we need to publish is instructions for others who want to site Fedora documentation in their works. Anyone have any ideas? [1] https://fedoraproject.org/wiki/Docs_Project_licensing_FAQ --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Sat Nov 21 19:02:19 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 21 Nov 2009 14:02:19 -0500 Subject: Docs Project History Message-ID: <1258830139.2192.17.camel@localhost> It would be great if everyone could take a look at the Docs Project History[1] wiki page and populate where you can. If you worked on any projects throughout the years you should add your name where appropriate. [1] https://fedoraproject.org/wiki/History_of_the_Docs_Project --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From ian at ianweller.org Sun Nov 22 02:39:47 2009 From: ian at ianweller.org (Ian Weller) Date: Sat, 21 Nov 2009 20:39:47 -0600 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: <1258817618.2192.9.camel@localhost> References: <20091121011715.GA9534@deathray.l.ianweller.org> <1258777504.2224.7.camel@localhost> <1258817618.2192.9.camel@localhost> Message-ID: <20091122023947.GB29002@deathray.l.ianweller.org> On Sat, Nov 21, 2009 at 10:33:38AM -0500, Eric Christensen wrote: > Maybe Ian can run Wikibot around to clean up this stuff, > too. > If it can be scripted, it can be done (usually). -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From a.mani.cms at gmail.com Sun Nov 22 16:44:19 2009 From: a.mani.cms at gmail.com (A. Mani) Date: Sun, 22 Nov 2009 22:14:19 +0530 Subject: fedora documentation bugs work flow Message-ID: <78323d480911220844p536d0e8ax2a08dd4e94a9d8f4@mail.gmail.com> Where is the guide for this? It does not seem to be on the wiki It is obviously different from that indicated for fedora bugzilla in the wiki Thanks A. Mani -- A. Mani ASL, CLC, AMS, CMS http://www.logicamani.co.cc From eric at christensenplace.us Sun Nov 22 17:34:11 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 22 Nov 2009 12:34:11 -0500 Subject: fedora documentation bugs work flow In-Reply-To: <78323d480911220844p536d0e8ax2a08dd4e94a9d8f4@mail.gmail.com> References: <78323d480911220844p536d0e8ax2a08dd4e94a9d8f4@mail.gmail.com> Message-ID: <1258911251.2285.1.camel@localhost> On Sun, 2009-11-22 at 22:14 +0530, A. Mani wrote: > Where is the guide for this? > > It does not seem to be on the wiki > > It is obviously different from that indicated for fedora bugzilla in the wiki > > > Thanks > > A. Mani > > -- > A. Mani > ASL, CLC, AMS, CMS > http://www.logicamani.co.cc > I'm not familiar with that document. What information are you trying to find? --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From r.landmann at redhat.com Sun Nov 22 23:39:02 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 23 Nov 2009 09:39:02 +1000 Subject: Medialess installation In-Reply-To: <4B0568EB.4000201@fedoraproject.org> References: <4B0568EB.4000201@fedoraproject.org> Message-ID: <4B09CB96.3090900@redhat.com> On 11/20/2009 01:48 AM, Rahul Sundaram wrote: > Hi, > > I remember filing a RFE for this long time back and the installation > guide was updated. Refer > > http://docs.fedoraproject.org/install-guide/f8/en_US/ap-medialess-install.html > > This seems to have been dropped from the recent versions. Was this > intentional? Can it be added back? > This section was never dropped; although in the Fedora 11 Installation Guide and Fedora 12 Installation Guide, it's incorporated into the main body of the document, rather than included as an appendix. You can find this section in the current version of the guide here: http://docs.fedoraproject.org/install-guide/f12/en-US/html/ap-medialess-install.html Cheers Ruediger From poelstra at redhat.com Mon Nov 23 21:16:35 2009 From: poelstra at redhat.com (John Poelstra) Date: Mon, 23 Nov 2009 13:16:35 -0800 Subject: Schedule reminder Message-ID: <4B0AFBB3.5000106@redhat.com> Start End Name Tue 17-Nov Wed 18-Nov 0-Day rel-notes generate POT Tue 17-Nov Wed 18-Nov 0-Day rel-notes build updated rpm Tue 17-Nov Wed 18-Nov 0-Day rel-notes update docs.fp.org Thu 26-Nov Thu 26-Nov Add translated zero-day updates to docs.fp.org From bugzilla at redhat.com Tue Nov 24 07:44:52 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 24 Nov 2009 02:44:52 -0500 Subject: [Bug 533741] License should be CC-BY-SA instead of Open Publication In-Reply-To: References: Message-ID: <200911240744.nAO7iqFk014688@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533741 --- Comment #3 from Fedora Update System 2009-11-24 02:44:51 EDT --- publican-fedora-1.2-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. -- 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. From bugzilla at redhat.com Tue Nov 24 07:44:56 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 24 Nov 2009 02:44:56 -0500 Subject: [Bug 533741] License should be CC-BY-SA instead of Open Publication In-Reply-To: References: Message-ID: <200911240744.nAO7iuQ9014727@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533741 Fedora Update System changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Fixed In Version| |1.2-0.fc12 Resolution| |ERRATA -- 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. From mel at redhat.com Wed Nov 25 04:41:00 2009 From: mel at redhat.com (Mel Chua) Date: Tue, 24 Nov 2009 22:41:00 -0600 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: <1258777504.2224.7.camel@localhost> References: <20091121011715.GA9534@deathray.l.ianweller.org> <1258777504.2224.7.camel@localhost> Message-ID: <4B0CB55C.9060904@redhat.com> > So we clearly have an organizational problem. I agree that there is way > too much stuff out there. From a management point of view I literally > live off of the "Docs Project meetings" page. I've almost made it a > dashboard of items that I need. So I don't actually sift through much > of the other noise that's out there. But if people can't find something > that is actually there then that's a problem. I'm curious whether this might actually be something that could be tackled well in a sprint - not necessarily a full-blown FAD, but a few hours during which a bunch of Docs folks run through through this online and do enough cleanup that it's clear to any casual passerby what the wiki should look like at 100% completion[1] and what remains to make it look that way. A contingent of new-to-Docs-team-but-who-know-their-way-around-wiki-editing folks would probably be helpful from a "let's check out what information's findable and discoverable by people who don't already live in this section of the wiki" perspective. Random idea. --Mel [1] ...asymptotically reached ;) From eric at christensenplace.us Wed Nov 25 12:51:39 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 25 Nov 2009 07:51:39 -0500 Subject: Fedora Docs Meeting Reminder Message-ID: <1259153499.2231.0.camel@localhost> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Wed Nov 25 12:58:12 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 25 Nov 2009 07:58:12 -0500 Subject: Moving Docs Project to Category:Docs Project In-Reply-To: <4B0CB55C.9060904@redhat.com> References: <20091121011715.GA9534@deathray.l.ianweller.org> <1258777504.2224.7.camel@localhost> <4B0CB55C.9060904@redhat.com> Message-ID: <1259153892.2231.6.camel@localhost> On Tue, 2009-11-24 at 22:41 -0600, Mel Chua wrote: > > So we clearly have an organizational problem. I agree that there is way > > too much stuff out there. From a management point of view I literally > > live off of the "Docs Project meetings" page. I've almost made it a > > dashboard of items that I need. So I don't actually sift through much > > of the other noise that's out there. But if people can't find something > > that is actually there then that's a problem. > > I'm curious whether this might actually be something that could be > tackled well in a sprint - not necessarily a full-blown FAD, but a few > hours during which a bunch of Docs folks run through through this online > and do enough cleanup that it's clear to any casual passerby what the > wiki should look like at 100% completion[1] and what remains to make it > look that way. > > A contingent of > new-to-Docs-team-but-who-know-their-way-around-wiki-editing folks would > probably be helpful from a "let's check out what information's findable > and discoverable by people who don't already live in this section of the > wiki" perspective. > > Random idea. > > --Mel > > [1] ...asymptotically reached ;) > Mel, I got through a lot of the Docs pages the other day. This was basically the pages that were in Category:Docs Project. We still need to go through the other categories and see if those pages are still appropriately categorized and if anything needs to go to the Archive:. Last year we had a virtual FUDCon over the holidays where we had some teaching classes and some working periods. Maybe we can do the same thing this year. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Nov 26 00:40:58 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 25 Nov 2009 19:40:58 -0500 Subject: Docs Meeting 2009-11-26 IRC log Message-ID: <1259196058.2254.3.camel@localhost> =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by sparks at 00:01:14 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2009-11-26/fedora-meeting.2009-11-26-00.01.log.html . Meeting summary --------------- * Roll Call (sparks, 00:01:19) * Docs Project Leader Elections (sparks, 00:07:44) * Release Notes (sparks, 00:11:54) * ACTION: jjmcd to contact kernel and/or anaconda developers to figure out the processor question (sparks, 00:27:31) * ACTION: jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG (sparks, 00:27:55) * ACTION: jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. (sparks, 00:28:24) * Guide Status (sparks, 00:30:15) * ACTION: laubersm to do editorial review of Accessibility Guide. (sparks, 00:36:10) * New Guides (sparks, 00:37:56) * All other business (sparks, 00:38:56) Meeting ended at 00:40:13 UTC. Action Items ------------ * jjmcd to contact kernel and/or anaconda developers to figure out the processor question * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * laubersm to do editorial review of Accessibility Guide. Action Items, by person ----------------------- * jjmcd * jjmcd to contact kernel and/or anaconda developers to figure out the processor question * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * laubersm * laubersm to do editorial review of Accessibility Guide. * sparks * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sparks (54) * jjmcd (39) * laubersm (21) * radsy (3) * zodbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Nov 26 00:42:21 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 25 Nov 2009 19:42:21 -0500 Subject: CORRECTED Docs Meeting 2009-11-26 IRC log Message-ID: <1259196141.2254.4.camel@localhost> 00:01:14 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:01:14 Meeting started Thu Nov 26 00:01:14 2009 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:01:19 #topic Roll Call 00:01:20 * sparks 00:02:27 * jjmcd . 00:02:55 * laubersm . 00:04:05 looks like sparse pickins tonight, Eric. Do the Aussies have a holiday tomorrow, too? 00:04:15 jjmcd: Not sure! 00:04:31 * sparks was hoping ke4qqq would be in attendance tonight 00:07:09 Well... 00:07:15 Slim pickins indeed 00:07:44 #topic Docs Project Leader Elections 00:07:46 * radsy shuffles in 00:08:09 Being there are so few in attendance tonight, I'm going to push the vote back to next week. 00:08:22 Sounds like a plan to me 00:08:26 Right now jjmcd and I are the only ones nominated for the leader position... 00:08:40 Would anyone like to make an additional nomination? 00:08:48 And without someone for RNs, I have to decline 00:09:15 * laubersm thinks you two could just trade places.... 00:09:32 Eric has more sense than to take RNs 00:09:36 * sparks isn't that crazy 00:09:58 jjmcd: But you know, laubersm could take the RNs... 00:10:09 Yeah, I was thinking that 00:10:19 Did sparks see how much I was not around the last release?!? 00:10:37 Ahhh, but this is a new season 00:10:37 * laubersm is not that crazy 00:10:45 * sparks is hoping laubersm will be around for this release 00:10:55 * laubersm is not that crazy 00:11:04 okay... well, we'll revisit this next week 00:11:07 I do have a question for this cycle tho, and some input 00:11:13 go 00:11:23 for the leader or another topic? 00:11:34 Once we have some weasel words aroun the securoty thing 00:11:47 We will need to face L10N for a bigger update than we would like 00:11:54 #topic Release Notes 00:11:57 BUT, we have a bug on the list of processors 00:12:12 This is about the fifth opinion on the list of supported systems 00:12:23 so the question is, who is the canonical authority? 00:13:06 * sparks doesn't have a clue 00:13:39 who are the package maintainers for the kernel? 00:13:52 I would start there - and/or anaconda 00:13:58 I suppose that would be a good place to start 00:14:49 jjmcd: Since PK has been patched, can we now remove that text from the RN and the SG? 00:14:54 and/or ask stickster_afk 00:15:01 :) 00:15:03 I think we need to change the prose 00:15:11 * laubersm waves at stickster_afk 00:15:24 But people who install from the dvd will still have the feature until they update 00:15:52 jjmcd: Doesn't everyone know to run an update once you've installed from media like that? 00:16:02 mention that when you ask for input... they (developers/package maintainers working on kernel/install) may be able to help there too 00:16:03 I suspect not 00:16:35 Even if they do, some will not be comfortable having that on the network while they update 00:16:43 also - a lot of people - mostly outside the us - install from dvd and do not have easy access to updates 00:16:54 they may want to change it before they get access to updates 00:17:13 don't know if they would see the RN updates either though... :) 00:17:15 Yes, and even on DSL, that first update can be very slow, so many delay it 00:17:19 Well, at the very least we need to update the text better than what's there now. 00:17:24 yes 00:17:32 we need to say soemthing different 00:17:38 jjmcd: Whatever you put in the RN is what I'll put in the SG 00:17:39 we also have a few minor things 00:17:48 adding "or just get the update" (in nicer wording) would be good 00:18:00 but my main outstanding thing is the processor 00:18:41 I never checked, did we ever get index.php fixed? 00:19:05 I'm apparently not alone in noticing the behavior, the bug has 2 or 3 duplicates 00:19:18 Fixed? Like what rudi was going to work on? 00:19:28 yeah 00:19:42 fixed from our perspective 00:19:53 obviously we're not going to fix gecko 00:20:40 I know rudi was unhappy with it not validating and wanted to fix that, but I don't know whether he did anything 00:21:06 W3C is still showing 208 errors and 6 warnings so I'm guessing nothing has changed. 00:21:21 rudi's not in the office yet, i can follow up with him when he arrives 00:21:32 OK, well, at least the bug is posted and being passed from team to team :-) 00:21:41 It's almost 10:30! He really is sleeping in! 00:22:10 I notice ryanlerch is not on either, which makes me suspect they have something today, too 00:22:11 he's doing post office stuff this morning :) 00:22:53 I don't think I ever played post office as an adult 00:23:03 jjmcd: Did you see the schedule reminder for the RNs? 00:23:10 yes 00:23:24 But as I said, I think we need another cycle 00:23:39 That security thing is still only in en-US 00:23:49 Yeah 00:24:10 Did you see someone is starting an en-GB L10N team, surprised we haven seen an en-AU 00:24:11 Let's work on the text tonight so we can push it out to the translators 00:24:24 I did not 00:24:31 Still need to get the processors before we do, tho 00:24:57 There's probably a dozen small changes being hidden from L10N, and another half-dzen to make 00:25:01 jjmcd: Once we get the text squared away for the PK thing, let's make sure the trans-list gets a notice that the paragraphs are the same so the translation can be used in both places. 00:25:15 good point 00:26:40 * sparks has changes that need to be submitted to Transifex now. 00:27:31 #action jjmcd to contact kernel and/or anaconda developers to figure out the processor question 00:27:55 #action jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG 00:28:24 #action jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. 00:29:21 Okay, anything else on the Release Notes? 00:30:15 #topic Guide Status 00:30:52 The Accessibility Guide is coming along. I need to verify some software for GNOME and I should be done for F12. 00:31:06 laubersm: Are you going to have time to do an editorial review? 00:31:41 depends on when :) 00:31:53 I was supposed to ping you the other night... 00:32:20 Tonight/Tommorrow - no - Fri/Sat probably. Sun - probably not - Mon-Thur evenings - probably 00:33:16 Okay... Whenever you can. There isn't a lot of change since you last looked at it. I just want to make sure it is what it needs to be before I turn it loose to the translators. 00:33:18 actually - if it is ready for a git pull before I leave the house in the morning, I might do it while the turkey is cooking... and can push when I get home late tomorrow night 00:33:38 If I need internet access it has to wait until Fri 00:33:52 laubersm: That will be fine. I'll make sure everything is current in the f12 branch and I won't touch it 00:33:52 You shouldn't 00:34:04 so I should get the f12 branch - not master? 00:34:07 I can do that 00:35:18 Yeah, I'm going to make sure the f12 branch is the final version for f12. 00:35:22 devel is branch 00:36:10 #action laubersm to do editorial review of Accessibility Guide. 00:36:43 Okay, any other guide items? 00:37:56 #topic New Guides 00:38:02 Any new guides to discuss? 00:38:56 #topic All other business 00:39:07 Anyone have anything else they'd like to talk about? 00:40:01 Okay, well we'll close up shop earlier tonight. 00:40:06 Thanks for coming everyone! 00:40:13 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Nov 26 00:42:44 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 25 Nov 2009 19:42:44 -0500 Subject: Docs Meeting 2009-11-26 Summary Message-ID: <1259196164.2254.6.camel@localhost> =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by sparks at 00:01:14 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2009-11-26/fedora-meeting.2009-11-26-00.01.log.html . Meeting summary --------------- * Roll Call (sparks, 00:01:19) * Docs Project Leader Elections (sparks, 00:07:44) * Release Notes (sparks, 00:11:54) * ACTION: jjmcd to contact kernel and/or anaconda developers to figure out the processor question (sparks, 00:27:31) * ACTION: jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG (sparks, 00:27:55) * ACTION: jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. (sparks, 00:28:24) * Guide Status (sparks, 00:30:15) * ACTION: laubersm to do editorial review of Accessibility Guide. (sparks, 00:36:10) * New Guides (sparks, 00:37:56) * All other business (sparks, 00:38:56) Meeting ended at 00:40:13 UTC. Action Items ------------ * jjmcd to contact kernel and/or anaconda developers to figure out the processor question * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * laubersm to do editorial review of Accessibility Guide. Action Items, by person ----------------------- * jjmcd * jjmcd to contact kernel and/or anaconda developers to figure out the processor question * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * laubersm * laubersm to do editorial review of Accessibility Guide. * sparks * jjmcd and sparks to work out the final text for the PK fiasco and submit it to the RN and SG * jjmcd or sparks to send message to trans-list to notify them of the duplicate text for RN and SG. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * sparks (54) * jjmcd (39) * laubersm (21) * radsy (3) * zodbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Fri Nov 27 10:34:36 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 27 Nov 2009 05:34:36 -0500 Subject: [Bug 533737] Recommend changing the Feedback statement to include the component name. In-Reply-To: References: Message-ID: <200911271034.nARAYaSS003429@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533737 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jfearn at redhat.com |r.landmann at redhat.com --- Comment #1 from Jeff Fearn 2009-11-27 05:34:34 EDT --- The only issue I can see with this is that anyone using the Fedora brand who doesn't have a component would have incorrect instructions. This entity isn't used anywhere in the code, so it's purely a cosmetic decision. Cheers, Jeff. -- 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. From bugzilla at redhat.com Fri Nov 27 14:12:26 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 27 Nov 2009 09:12:26 -0500 Subject: [Bug 533737] Recommend changing the Feedback statement to include the component name. In-Reply-To: References: Message-ID: <200911271412.nARECQ4x013266@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=533737 --- Comment #2 from Eric Christensen 2009-11-27 09:12:25 EDT --- That's a good point. Although to get a component in Fedora Documentation's BZ product is fairly easy, just ask me for one and I make it happen. -- 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. From phrkonaleash at gmail.com Sat Nov 28 06:08:36 2009 From: phrkonaleash at gmail.com (Ryan Rix) Date: Fri, 27 Nov 2009 23:08:36 -0700 Subject: Fedora-tour: A Fedora Feature for new users Message-ID: <200911272308.40877.phrkonaleash@gmail.com> Hello Docs team, Ankur Sinha (fas username ankursinha, cc'd) and I have recently embarked on a new project that is set, at the moment, to be included as a Fedora 14, or possibly Fedora 13 feature, designed to give new and old users a tour of the Fedora Project, Fedora Linux and their recently installed software. It would add an option to the last form of Firstboot with the option to start this at first login, serving as an equivalent to Windows' "Welcome Center" (I don't have any pictures of this, unfortunately, for reference) and basically just introduce Fedora users to their new desktop, and the project as a whole, including ways to contribute, if they are interested. Naturally, such a project will take the involvement of many teams, including the Documentation team. When we have the final product nearing completion, we will need some content to put into it, naturally. Some of this will most likely come from the various SIGs within Fedora, but much of it will have to come from the Docs project. What Ankur and I were considering was to implement a visual introduction to the application, with a tree (like, an actual tree with branches, etc) where each leaf is a separate "part" of Fedora (General Overview, FAQ, Getting Help, GNOME overview, KDE overview, LXDE overview, Development Tools, Joining Fedora etc) all installable as separate packages, pulled in, most likely, by installing packages from that Group in anaconda. Naturally, we want to make it as easy for the docs team, and the various SIGs to add initial content and update/overhaul it each release. What tools would the Docs team recommend we use as a backend for this? We could possibly introduce some mediawiki-esque markup syntax, straight html, or Docbook XML, along with anything else that is suggested and agreed upon. We're still in the early design phase of this project and are open to any suggestions. Thank you for your time, Ryan Rix Fas user rrix -- Ryan Rix Fedora KDE SIG Member, Phoenix AZ Ambassador, News KDE Beat writer http://hackersramblings.wordpress.com | http://identi.ca/phrkonaleash XMPP: phrkonaleash at gmail.com | MSN: phrkonaleash at yahoo.com AIM: phrkonaleash | Yahoo: phrkonaleash IRC: PhrkOnLsh at irc.freenode.net/#srcedit,#plugaz,#fedora-kde and countless other FOSS channels. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From mel at redhat.com Sat Nov 28 06:34:53 2009 From: mel at redhat.com (Mel Chua) Date: Sat, 28 Nov 2009 00:34:53 -0600 Subject: Fedora-tour: A Fedora Feature for new users In-Reply-To: <200911272308.40877.phrkonaleash@gmail.com> References: <200911272308.40877.phrkonaleash@gmail.com> Message-ID: <4B10C48D.7060307@redhat.com> > Naturally, we want to make it as easy for the docs team, and the various SIGs > to add initial content and update/overhaul it each release. What tools would > the Docs team recommend we use as a backend for this? We could possibly > introduce some mediawiki-esque markup syntax, straight html, or Docbook XML, > along with anything else that is suggested and agreed upon. We're still in the > early design phase of this project and are open to any suggestions. They've also got a project wiki page up at https://fedoraproject.org/wiki/Fedora-tour with some more information. I think some of this email might have be inspired by Karsten's comments in https://fedoraproject.org/wiki/Talk:Fedora-tour (also noted in a comment to Ankur's first blog post about this, http://dodoincfedora.wordpress.com/2009/11/26/a-new-fedora-project/). Suggestions floated so far include: * the wiki (and then apply publican at the end of each release cycle) * text files versioned in git * zikula, once it's up --Mel From foss.mailinglists at gmail.com Sat Nov 28 06:40:02 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Sat, 28 Nov 2009 12:10:02 +0530 Subject: Fedora-tour: A Fedora Feature for new users In-Reply-To: <4B10C48D.7060307@redhat.com> References: <200911272308.40877.phrkonaleash@gmail.com> <4B10C48D.7060307@redhat.com> Message-ID: <35586fc00911272240y7fc35d41s71cdf0b8c8f0a370@mail.gmail.com> On Sat, Nov 28, 2009 at 12:04 PM, Mel Chua wrote: >> Naturally, we want to make it as easy for the docs team, and the various >> SIGs >> to add initial content and update/overhaul it each release. What tools >> would >> the Docs team recommend we use as a backend for this? We could possibly >> introduce some mediawiki-esque markup syntax, straight html, or Docbook >> XML, >> along with anything else that is suggested and agreed upon. We're still in >> the >> early design phase of this project and are open to any suggestions. > > They've also got a project wiki page up at > https://fedoraproject.org/wiki/Fedora-tour with some more information. > > I think some of this email might have be inspired by Karsten's comments in > https://fedoraproject.org/wiki/Talk:Fedora-tour (also noted in a comment to > Ankur's first blog post about this, > http://dodoincfedora.wordpress.com/2009/11/26/a-new-fedora-project/). > > Suggestions floated so far include: > > * the wiki (and then apply publican at the end of each release cycle) > * text files versioned in git > * zikula, once it's up A quick hack that could help capture the vision of the idea originators is a mind-map. It should come handy during the design phase as well. -- sankarshan mukhopadhyay From r.landmann at redhat.com Sun Nov 29 22:26:33 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 30 Nov 2009 08:26:33 +1000 Subject: A question about translation out of the freezing time frame. In-Reply-To: <4B1126D5.8030603@globaltek.pt> References: <4B1126D5.8030603@globaltek.pt> Message-ID: <4B12F519.7070905@redhat.com> On 11/28/2009 11:34 PM, Rui Gouveia wrote: > The guides are big. Usually, during the string freeze windows, we > concentrate our efforts mainly in the GUI interface and applications, > and these are left for last and never finished. Now that things are > slower, if we want to contribute work for these modules, whats the > proper way to do it? > Rui, the F12 guides remain stable and open for translation while writers continue to work in the "master" branch of each document. You can therefore continue your work on the F12 versions of the docs if you want to. Some of us are watching the translation statistics so that we can publish new translations as they reach completion; however, if you complete a translation and it doesn't show up on docs.fedoraproject.org within a few days, please post a note to fedora-docs-list and remind us :) [1] At some point after the Alpha version of F13 becomes available, the updated "master" branch of each document is combined with the latest updated PO files from the "F12" branch to create the new "F13" branch. This is then made available in transifex and submissions to the "F12" branch are disabled. The docs team tries to minimise changes to strings between releases as much as possible, so that the maximum number of strings in the old PO file will still apply to the new PO file. Thanks for your interest, and please let me know if there's any way I can help you out further. Cheers Ruediger [1] Yes, I know that I'm running late with the amazing effort of the Indic teams contributing to the Installation Quick Start Guide. There are so many new translations and they arrived so quickly one after the other! Thank you all for your efforts; I will bring docs.fedoraproject.org up to date this week with all your hard work. From sundaram at fedoraproject.org Mon Nov 30 05:54:11 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 30 Nov 2009 11:24:11 +0530 Subject: why make it so hard to download Fedora documentation? In-Reply-To: References: Message-ID: <4B135E03.6050509@fedoraproject.org> On 11/29/2009 07:55 PM, Brian R. Murphy wrote: > Sorry to bother you personally, but you seem to be responsible for the > FAQ, and there is no "feedback" link for the Fedora documentation page. > I don't really think this question should be in the FAQ; I think it > should just be fixed. But if not, perhaps you can add this question > (along with some answer) to the FAQ: > > * Why do you make it so hard to download Fedora documentation? > > I would like to download the Fedora 12 documentation for off-line > reference while I'm upgrading. > > Unfortunately, the documentation page > at http://docs.fedoraproject.org/ has a "clever" UI with select menus > that trigger navigations themselves (rather than a separate go/download > button), making it very arduous to "save as" the result. There also > doesn't seem to be any way to just grab the latest bunch (or even a > single one). There's not even a way to "save as" the PDF links, and > some quirky browsers (like the one I have at work) don't handle PDF > files too well directly. While it wouldn't be as pretty, a simple file > listing would be far more useful. If you're going to pretty it up, > please don't screw up basic usability. http://docs.fedoraproject.org/ - Select PDF which is the third option and Language. Rahul From thinklinux.ssh at gmail.com Mon Nov 30 06:57:36 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Mon, 30 Nov 2009 12:27:36 +0530 Subject: http://docs.fedoraproject.org/ needs minor css fix. Message-ID: Hi, I was having a look at http://docs.fedoraproject.org/ after Rahul's mail this morning. I found that the blue box in the content is overlapping the right side black border of the page. I tested both in Firefox and google chrome. Screeshot here: http://susmit.fedorapeople.org/Screenshot1.png Thanks. -- Regards, Susmit. ============================================= http://www.fedoraproject.org/wiki/user:susmit ============================================= From bob at fedoraunity.org Mon Nov 30 06:59:05 2009 From: bob at fedoraunity.org (Robert 'Bob' Jensen) Date: Mon, 30 Nov 2009 06:59:05 +0000 (UTC) Subject: why make it so hard to download Fedora documentation? In-Reply-To: <11370378.37021259564137285.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <17647884.37041259564345220.JavaMail.root@zimbra.cbccgroup.com> ----- "Rahul Sundaram" wrote: > On 11/29/2009 07:55 PM, Brian R. Murphy wrote: > > Sorry to bother you personally, but you seem to be responsible for > the > > FAQ, and there is no "feedback" link for the Fedora documentation > page. > > I don't really think this question should be in the FAQ; I think > it > > should just be fixed. But if not, perhaps you can add this > question > > (along with some answer) to the FAQ: > > > > * Why do you make it so hard to download Fedora documentation? > > > > I would like to download the Fedora 12 documentation for off-line > > reference while I'm upgrading. > > > > Unfortunately, the documentation page > > at http://docs.fedoraproject.org/ has a "clever" UI with select > menus > > that trigger navigations themselves (rather than a separate > go/download > > button), making it very arduous to "save as" the result. There > also > > doesn't seem to be any way to just grab the latest bunch (or even a > > single one). There's not even a way to "save as" the PDF links, > and > > some quirky browsers (like the one I have at work) don't handle PDF > > files too well directly. While it wouldn't be as pretty, a simple > file > > listing would be far more useful. If you're going to pretty it up, > > please don't screw up basic usability. > I agree with Brian, a simple list like what was available in the past as an option would be helpful. It seems that some older lesser maintained docs that were useful are now missing from the listings also. http://docs.fedoraproject.org/yum/en/ is an example. -- Bob ------------------------------------------------------------------------ | Robert 'Bob' Jensen || Fedora Unity Founder | | bob at fedoraunity.org || http://fedoraunity.org/ | | http://bjensen.fedorapeople.org/ | | http://blogs.fedoraunity.org/bobjensen | | http://www.facebook.com/people/Robert-Bob-Jensen/1332998420 | ------------------------------------------------------------------------ From eric at christensenplace.us Mon Nov 30 15:05:25 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 10:05:25 -0500 Subject: Publican SRPMs in Fedora Message-ID: Just wanted to point out that the current Publican build, 1.x, is creating SRPMs and spec files that are inline with the Fedora's packaging policy (using the --short_sighted mode). I submitted[1] a package for the Fedora Accessibility Guide for review and it passed without batting an eye. This should be helpful for other guides as well. I'm still pondering the best way to handle the different languages, though. [1] https://bugzilla.redhat.com/show_bug.cgi?id=533765 --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at christensenplace.us Mon Nov 30 15:19:09 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 10:19:09 -0500 Subject: why make it so hard to download Fedora documentation? In-Reply-To: <4B135E03.6050509@fedoraproject.org> References: <4B135E03.6050509@fedoraproject.org> Message-ID: On Mon, Nov 30, 2009 at 00:54, Rahul Sundaram wrote: > On 11/29/2009 07:55 PM, Brian R. Murphy wrote: > > Sorry to bother you personally, but you seem to be responsible for the > > FAQ, and there is no "feedback" link for the Fedora documentation page. > > I don't really think this question should be in the FAQ; I think it > > should just be fixed. But if not, perhaps you can add this question > > (along with some answer) to the FAQ: > > > > * Why do you make it so hard to download Fedora documentation? > > > > I would like to download the Fedora 12 documentation for off-line > > reference while I'm upgrading. > > > > Unfortunately, the documentation page > > at http://docs.fedoraproject.org/ has a "clever" UI with select menus > > that trigger navigations themselves (rather than a separate go/download > > button), making it very arduous to "save as" the result. There also > > doesn't seem to be any way to just grab the latest bunch (or even a > > single one). There's not even a way to "save as" the PDF links, and > > some quirky browsers (like the one I have at work) don't handle PDF > > files too well directly. While it wouldn't be as pretty, a simple file > > listing would be far more useful. If you're going to pretty it up, > > please don't screw up basic usability. > > http://docs.fedoraproject.org/ - Select PDF which is the third option > and Language. > > Rahul > > What format are you looking at saving the files? We provide html, html-single, and PDF. If you want to save the html-single it's simple enough to select the appropriate file and language and then save-as once the page loads. PDFs generally download on demand. --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at christensenplace.us Mon Nov 30 15:22:45 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 10:22:45 -0500 Subject: http://docs.fedoraproject.org/ needs minor css fix. In-Reply-To: References: Message-ID: On Mon, Nov 30, 2009 at 01:57, susmit shannigrahi wrote: > Hi, > > I was having a look at http://docs.fedoraproject.org/ after Rahul's > mail this morning. > > I found that the blue box in the content is overlapping the right side > black border of the page. I tested both in Firefox and google chrome. > > Screeshot here: http://susmit.fedorapeople.org/Screenshot1.png > > Thanks. > > -- > Regards, > Susmit. > > > What's your screen resolution? I'm not seeing this in 2560x1024. I think this may be an issue with lower resolution screen size. --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From thinklinux.ssh at gmail.com Mon Nov 30 15:52:14 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Mon, 30 Nov 2009 21:22:14 +0530 Subject: http://docs.fedoraproject.org/ needs minor css fix. In-Reply-To: References: Message-ID: > What's your screen resolution?? I'm not seeing this in 2560x1024. 1024 x 768 > I think > this may be an issue with lower resolution screen size. Hmm..then it must be so. But many people use similar setting. :) -- Regards, Susmit. ============================================= http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From eric at christensenplace.us Mon Nov 30 16:00:29 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 11:00:29 -0500 Subject: why make it so hard to download Fedora documentation? In-Reply-To: References: <4B135E03.6050509@fedoraproject.org> Message-ID: On Mon, Nov 30, 2009 at 10:42, Brian R. Murphy wrote: > On Mon, Nov 30, 2009 at 11:19 PM, Eric Christensen < > eric at christensenplace.us> wrote: > >> On Mon, Nov 30, 2009 at 00:54, Rahul Sundaram > > wrote: >> >>> On 11/29/2009 07:55 PM, Brian R. Murphy wrote: >>> > Sorry to bother you personally, but you seem to be responsible for the >>> > FAQ, and there is no "feedback" link for the Fedora documentation page. >>> > I don't really think this question should be in the FAQ; I think it >>> > should just be fixed. But if not, perhaps you can add this question >>> > (along with some answer) to the FAQ: >>> > >>> > * Why do you make it so hard to download Fedora documentation? >>> > >>> > I would like to download the Fedora 12 documentation for off-line >>> > reference while I'm upgrading. >>> > >>> > Unfortunately, the documentation page >>> > at http://docs.fedoraproject.org/ has a "clever" UI with select menus >>> > that trigger navigations themselves (rather than a separate go/download >>> > button), making it very arduous to "save as" the result. There also >>> > doesn't seem to be any way to just grab the latest bunch (or even a >>> > single one). There's not even a way to "save as" the PDF links, and >>> > some quirky browsers (like the one I have at work) don't handle PDF >>> > files too well directly. While it wouldn't be as pretty, a simple file >>> > listing would be far more useful. If you're going to pretty it up, >>> > please don't screw up basic usability. >>> >>> http://docs.fedoraproject.org/ - Select PDF which is the third option >>> and Language. >>> >>> Rahul >>> >>> >> What format are you looking at saving the files? We provide html, >> html-single, and PDF. If you want to save the html-single it's simple >> enough to select the appropriate file and language and then save-as once the >> page loads. PDFs generally download on demand. >> >> --Eric >> >> > I just want to quickly get something I can read off-line. If you had a > simple index page, I could just right click on each link I want (PDF or > one-page HTML), "save link as", and have them load in the background. If we > were lucky there might be a tar/tgz/zip or something similar and I can just > download one file and unpackage it myself at my leisure on the train. (See > http://tldp.org/docs.html for some ideas.) > > With your page design, with my high latency connection, I have to select > the appropriate file, busy wait for it to load, save-as, then go back and do > it again. I can't even choose to open each "in new tab" since your page > design precludes that. > > -Brian > > Our future rollout of Zikula should remedy this, I hope. There were more problems with the previous version of docs.fp.o, though, that had to be fixed. With so many languages available for some guides it was almost impossible to list everything appropriately. The link you provided doesn't take into consideration what language the person would like to read the guide in. We have eighty-nine possible language translations which would quickly make a page very crazy to load on a high-latency network connection. What would you expect to find in a tar file? A PDF? HTML? Raw XML? Everything? If you are after the html-single, yes you have to wait for it to load before saving but it doesn't take any more time than just downloading it in the first place. PDFs should download when you click them. --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb8rcr at arrl.net Mon Nov 30 16:08:23 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 30 Nov 2009 11:08:23 -0500 Subject: Publican SRPMs in Fedora In-Reply-To: References: Message-ID: <1259597303.25666.9.camel@Aidan> On Mon, 2009-11-30 at 10:05 -0500, Eric Christensen wrote: > Just wanted to point out that the current Publican build, 1.x, is > creating SRPMs and spec files that are inline with the Fedora's > packaging policy (using the --short_sighted mode). I submitted[1] a > package for the Fedora Accessibility Guide for review and it passed > without batting an eye. This should be helpful for other guides as > well. There is an advantage to "automatically" passing the package review. But the Publican-generated packages are not consistent with the rest of Fedora. When a user logs on in Dutch, everything he sees is in Dutch, until you install a Publican-generated document. Now you either need to wade through a menu choice per language, or only install one language per machine. This is inconsistent with the rest of Fedora. Producing the RPM manually, as we do with the release notes, really isn't a huge burden, but for consistency it would be a big win if Publican would produce something that meshed nicely with the rest of Fedora. --McD From eric at christensenplace.us Mon Nov 30 16:10:56 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 11:10:56 -0500 Subject: http://docs.fedoraproject.org/ needs minor css fix. In-Reply-To: References: Message-ID: On Mon, Nov 30, 2009 at 10:52, susmit shannigrahi wrote: > > What's your screen resolution? I'm not seeing this in 2560x1024. > > 1024 x 768 > > > I think > > this may be an issue with lower resolution screen size. > > Hmm..then it must be so. > But many people use similar setting. :) > > -- > Regards, > Susmit. > > I agree. I've seen pages that did just what you are seeing because they are using a fixed-width graphic or a fixed-width "space". Maybe Rudi can modify the code. --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb8rcr at arrl.net Mon Nov 30 16:26:25 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 30 Nov 2009 11:26:25 -0500 Subject: http://docs.fedoraproject.org/ needs minor css fix. In-Reply-To: References: Message-ID: <1259598385.25666.10.camel@Aidan> On Mon, 2009-11-30 at 11:10 -0500, Eric Christensen wrote: > > I agree. I've seen pages that did just what you are seeing because > they are using a fixed-width graphic or a fixed-width "space". Maybe > Rudi can modify the code. I think it has to do with improperly nesting containers, but as you recognized last week, we have a lot of work to do on that page --McD From eric at christensenplace.us Mon Nov 30 16:28:47 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 30 Nov 2009 11:28:47 -0500 Subject: http://docs.fedoraproject.org/ needs minor css fix. In-Reply-To: <1259598385.25666.10.camel@Aidan> References: <1259598385.25666.10.camel@Aidan> Message-ID: On Mon, Nov 30, 2009 at 11:26, John J. McDonough wrote: > On Mon, 2009-11-30 at 11:10 -0500, Eric Christensen wrote: > > > > > I agree. I've seen pages that did just what you are seeing because > > they are using a fixed-width graphic or a fixed-width "space". Maybe > > Rudi can modify the code. > > I think it has to do with improperly nesting containers, but as you > recognized last week, we have a lot of work to do on that page > > --McD > > > Yep. I'm hoping that we'll be able to get Zikula up and running real soon which should fix most of this mess. --Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac at fedorahosted.org Mon Nov 16 01:39:16 2009 From: trac at fedorahosted.org (Design Team) Date: Mon, 16 Nov 2009 01:39:16 -0000 Subject: [Design Team] #82: Need a logo for the Docs team In-Reply-To: <057.7d4cf03c5aaf9af8c859f92f4bb4e895@fedorahosted.org> References: <057.7d4cf03c5aaf9af8c859f92f4bb4e895@fedorahosted.org> Message-ID: <066.8a79d6286f52f08712fcd0c0e2439c08@fedorahosted.org> #82: Need a logo for the Docs team -------------------------+-------------------------------------------------- Reporter: rlandmann | Owner: ryanlerch Type: task | Status: assigned Priority: minor | Component: Artwork Severity: Quick & Easy | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by ryanlerch): * cc: fedora-docs-list at redhat.com (removed) Comment: Created an initial design. Here is a mockup of how it will look in a built publican book: http://ryanlerch.fedorapeople.org/fedora-docs-logo/mockup.png and here is the png and svg for the logo by itself: http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs-logo.png http://ryanlerch.fedorapeople.org/fedora-docs-logo/fedora-docs.svg -- Ticket URL: Design Team Fedora Design Team