From ghenry at suretecsystems.com Tue Jul 5 09:00:16 2005 From: ghenry at suretecsystems.com (Gavin Henry) Date: Tue, 5 Jul 2005 10:00:16 +0100 (BST) Subject: Unavailable tonight - Going on holiday to Ireland Message-ID: <62318.193.195.148.66.1120554016.squirrel@webmail.suretecsystems.com> Dear Guys, Sorry, I'm out for tonight. I will be back in time for next weeks meeting though. Have a good one ;-) Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E ghenry at suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/ From Tommy.Reynolds at MegaCoder.com Tue Jul 5 15:45:34 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Tue, 5 Jul 2005 10:45:34 -0500 Subject: Unavailable tonight - Going on holiday to Ireland In-Reply-To: <62318.193.195.148.66.1120554016.squirrel@webmail.suretecsystems.com> References: <62318.193.195.148.66.1120554016.squirrel@webmail.suretecsystems.com> Message-ID: <20050705104534.336c3a57.Tommy.Reynolds@MegaCoder.com> Uttered "Gavin Henry" , spake thus: > Sorry, I'm out for tonight. > I will be back in time for next weeks meeting though. I, too, will be traveling today. Alas, not to Ireland though; some folks think just because they pay my bills they are entitled to some of my time ;-) Should be available for next week's meeting, if all goes well. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Tue Jul 5 19:32:47 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 05 Jul 2005 12:32:47 -0700 Subject: Agenda 5 July 2005 Message-ID: <1120591967.5937.19.camel@erato.phig.org> We're shy a few folks this week, but let's see what happens with the following: * Does tidy-bowl need help attracting beta testers? - All of us should test with our current guides * Task tracking process discussion http://fedoraproject.org/wiki/DocsProject/Tasks * f.r.c how-to training session postponed for Gavin - Karsten to still show Rahul and anyone else after the meeting * Postpone DocG discussion until next week? * AOB -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 5 20:18:36 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 05 Jul 2005 13:18:36 -0700 Subject: Agenda 5 July 2005 In-Reply-To: <1120591967.5937.19.camel@erato.phig.org> References: <1120591967.5937.19.camel@erato.phig.org> Message-ID: <1120594716.5937.22.camel@erato.phig.org> On Tue, 2005-07-05 at 12:32 -0700, Karsten Wade wrote: > We're shy a few folks this week, but let's see what happens with the > following: In fact, we were so shy we didn't get a quorum, so we postponed. Agenda will carryover until next week, plus whatever in the meantime. - Karsten > > * Does tidy-bowl need help attracting beta testers? > - All of us should test with our current guides > > * Task tracking process discussion > http://fedoraproject.org/wiki/DocsProject/Tasks > > * f.r.c how-to training session postponed for Gavin > - Karsten to still show Rahul and anyone else after the meeting > > * Postpone DocG discussion until next week? > > * AOB > > > -- > fedora-dsco-list mailing list > fedora-dsco-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-dsco-list -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Sat Jul 9 06:35:29 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 08 Jul 2005 23:35:29 -0700 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] Message-ID: <1120890929.5937.258.camel@erato.phig.org> -------- Forwarded Message -------- > From: Dave Lawrence > the product name, a list of components, description > for each and initial devel owner for bugs for each product. Optionally > you can also provide a initial qa contact and cc list members. Please > give me the components in the form of: > > component:description:initialdevelowner:initialqacontact:initialcclist > > Also please provide a brief 3 or 4 sentence description of the product > as well. Can you all help me put this together? Build the list in this thread and I'll submit it. Before doing so, I'll run through f-docs-l and see if anyone wants to step up with some content. Hoping there is some work going on that is ready for CVS. :) - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stuart at elsn.org Sat Jul 9 15:21:57 2005 From: stuart at elsn.org (Stuart Ellis) Date: Sat, 09 Jul 2005 16:21:57 +0100 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] In-Reply-To: <1120890929.5937.258.camel@erato.phig.org> References: <1120890929.5937.258.camel@erato.phig.org> Message-ID: <1120922517.6289.7.camel@Vigor10> On Fri, 2005-07-08 at 23:35 -0700, Karsten Wade wrote: > -------- Forwarded Message -------- > > From: Dave Lawrence > > > the product name, a list of components, description > > for each and initial devel owner for bugs for each product. Optionally > > you can also provide a initial qa contact and cc list members. Please > > give me the components in the form of: > > > > component:description:initialdevelowner:initialqacontact:initialcclist > > > > Also please provide a brief 3 or 4 sentence description of the product > > as well. Most of the current CVS modules have tracking bugs. Would the bug settings and/or comments be transferable to over the new components? From cvs co -c: desktop-up2date developer-guide documentation-guide example-tutorial hardening install-guide jargon-buster mirror-tutorial proxy-guide release-notes selinux-apache selinux-faq sudo-tutorial translation-guide translation-guide-windows updates usb-hotplug xml-normalize yum-software-management -- Stuart Ellis stuart at elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Sun Jul 10 16:35:53 2005 From: kwade at redhat.com (Karsten Wade) Date: Sun, 10 Jul 2005 09:35:53 -0700 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] In-Reply-To: <1120922517.6289.7.camel@Vigor10> References: <1120890929.5937.258.camel@erato.phig.org> <1120922517.6289.7.camel@Vigor10> Message-ID: <1121013353.5937.270.camel@erato.phig.org> On Sat, 2005-07-09 at 16:21 +0100, Stuart Ellis wrote: > On Fri, 2005-07-08 at 23:35 -0700, Karsten Wade wrote: > > -------- Forwarded Message -------- > > > From: Dave Lawrence > > > > > the product name, a list of components, description > > > for each and initial devel owner for bugs for each product. Optionally > > > you can also provide a initial qa contact and cc list members. Please > > > give me the components in the form of: > > > > > > component:description:initialdevelowner:initialqacontact:initialcclist > > > > > > Also please provide a brief 3 or 4 sentence description of the product > > > as well. > > Most of the current CVS modules have tracking bugs. Would the bug > settings and/or comments be transferable to over the new components? Yes. Within each bug, we first change the Product to Fedora Documentation Project, then the Component to the new component. > From cvs co -c: For RHEL guides, the components are part of the RHEL product and the bugzilla components follow a pattern, e.g., rhel-selg. This helps them stand out. I suppose we don't need such a thing. > desktop-up2date > developer-guide > documentation-guide > example-tutorial > hardening > install-guide > jargon-buster > mirror-tutorial > proxy-guide > release-notes > selinux-apache > selinux-faq > sudo-tutorial > translation-guide > translation-guide-windows > updates > usb-hotplug > xml-normalize > yum-software-management So, should we have components that match 1:1 with the names in CVS? Seems OK to me. :) - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stuart at elsn.org Mon Jul 11 09:30:09 2005 From: stuart at elsn.org (Stuart Ellis) Date: Mon, 11 Jul 2005 10:30:09 +0100 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] In-Reply-To: <1121013353.5937.270.camel@erato.phig.org> References: <1120890929.5937.258.camel@erato.phig.org> <1120922517.6289.7.camel@Vigor10> <1121013353.5937.270.camel@erato.phig.org> Message-ID: <1121074209.15896.238177607@webmail.messagingengine.com> On Sun, 10 Jul 2005 09:35:53 -0700, "Karsten Wade" said: > On Sat, 2005-07-09 at 16:21 +0100, Stuart Ellis wrote: > > On Fri, 2005-07-08 at 23:35 -0700, Karsten Wade wrote: > > > -------- Forwarded Message -------- > > > > From: Dave Lawrence > > > > > > > the product name, a list of components, description > > > > for each and initial devel owner for bugs for each product. Optionally > > > > you can also provide a initial qa contact and cc list members. Please > > > > give me the components in the form of: > > > > > > > > component:description:initialdevelowner:initialqacontact:initialcclist > > > > > > > > Also please provide a brief 3 or 4 sentence description of the product > > > > as well. > > > > Most of the current CVS modules have tracking bugs. Would the bug > > settings and/or comments be transferable to over the new components? > > Yes. Within each bug, we first change the Product to Fedora > Documentation Project, then the Component to the new component. OK. If we go for one-for-one matching then we could just copy the information required from those bugs for the CC list etc. as a start point. > For RHEL guides, the components are part of the RHEL product and the > bugzilla components follow a pattern, e.g., rhel-selg. This helps them > stand out. I suppose we don't need such a thing. We do have currently have a document which has the same name as a RHEL document - "Installation Guide", and it's labelled "fedora-install-guide" in most places. Theoretically I suppose that we could end up with other identically named documents too. Since we may be maintaining docs for packages for Core and Extras (some documents might reference packages from both), I guess the best component prefix would be just "fed-", if we use one. > So, should we have components that match 1:1 with the names in CVS? > > Seems OK to me. :) I like simple :). We'll probably need something for toolchain bugs/requests as well, separate from docs-common, but perhaps that should just be a tracker bug (as it is now), rather than a component. Odd idea: Should tracker bugs live in a separate component, since they potentially link to bugs in multiple components ? -- Stuart Ellis stuart at elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA From stickster at gmail.com Mon Jul 11 13:38:14 2005 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 11 Jul 2005 09:38:14 -0400 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] In-Reply-To: <1121074209.15896.238177607@webmail.messagingengine.com> References: <1120890929.5937.258.camel@erato.phig.org> <1120922517.6289.7.camel@Vigor10> <1121013353.5937.270.camel@erato.phig.org> <1121074209.15896.238177607@webmail.messagingengine.com> Message-ID: <1121089094.3332.51.camel@localhost.localdomain> On Mon, 2005-07-11 at 10:30 +0100, Stuart Ellis wrote: > > > > -------- Forwarded Message -------- > > > > > From: Dave Lawrence > > > > > > > > > the product name, a list of components, description > > > > > for each and initial devel owner for bugs for each product. Optionally > > > > > you can also provide a initial qa contact and cc list members. Please > > > > > give me the components in the form of: > > > > > > > > > > component:description:initialdevelowner:initialqacontact:initialcclist > > > > > > > > > > Also please provide a brief 3 or 4 sentence description of the product > > > > > as well. > > > > > > Most of the current CVS modules have tracking bugs. Would the bug > > > settings and/or comments be transferable to over the new components? > > > > Yes. Within each bug, we first change the Product to Fedora > > Documentation Project, then the Component to the new component. > > OK. If we go for one-for-one matching then we could just copy the > information required from those bugs for the CC list etc. as a start > point. > > > For RHEL guides, the components are part of the RHEL product and the > > bugzilla components follow a pattern, e.g., rhel-selg. This helps them > > stand out. I suppose we don't need such a thing. > > We do have currently have a document which has the same name as a RHEL > document - "Installation Guide", and it's labelled > "fedora-install-guide" in most places. Theoretically I suppose that we > could > end up with other identically named documents too. > > Since we may be maintaining docs for packages for Core and Extras (some > documents might reference packages from both), I guess the best > component prefix would be just "fed-", if we use one. Aren't these components all under the "Fedora Documentation" product? If so, isn't such a component prefix redundant? After all, the "Fedora Core" or "Fedora Extras" products don't call their components "fed-kernel" or "fed-yum-utils." I can't see the FDP ever doing anything *other* than Fedora docs, but if my logic is flawed, someone please beat me with the cluestick. > > So, should we have components that match 1:1 with the names in CVS? > > > > Seems OK to me. :) > > I like simple :). We'll probably need something for toolchain > bugs/requests as well, separate from docs-common, but perhaps that > should just be a tracker bug (as it is now), rather than a component. I was going to say that "docs-common" needed a component, thanks for remembering for me! > Odd idea: Should tracker bugs live in a separate component, since they > potentially link to bugs in multiple components ? It should be easy to simply have an "other" component to capture toolchain or miscellaneous requests. Only the highest level tracker bugs are going to be dissociated from specific components, like "docs in progress," or trackers of that nature. There should be few enough of those that they can live in "other" without a problem, I would think. Since any bug can conceivably become a tracker by having other bugs block it, making a separate component for tracker bugs could create needless confusion, couldn't it? This reminds me to ask: How hard is it to add components later? With one component per doc, as more docs are added (here's where I start dreaming again), we will need to continually add more components. Don't get me wrong, I like that idea best; I'm just wondering whether this presents a potential delay. I'm not very familiar with how the administration of BZ works from an "inside RH" perspective. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Mon Jul 11 16:10:53 2005 From: kwade at redhat.com (Karsten Wade) Date: Mon, 11 Jul 2005 09:10:53 -0700 Subject: [Fwd: Re: making Fedora Documentation Project a stand-alone Fedora Product] In-Reply-To: <1121089094.3332.51.camel@localhost.localdomain> References: <1120890929.5937.258.camel@erato.phig.org> <1120922517.6289.7.camel@Vigor10> <1121013353.5937.270.camel@erato.phig.org> <1121074209.15896.238177607@webmail.messagingengine.com> <1121089094.3332.51.camel@localhost.localdomain> Message-ID: <1121098253.5937.282.camel@erato.phig.org> On Mon, 2005-07-11 at 09:38 -0400, Paul W. Frields wrote: > On Mon, 2005-07-11 at 10:30 +0100, Stuart Ellis wrote: > > Since we may be maintaining docs for packages for Core and Extras (some > > documents might reference packages from both), I guess the best > > component prefix would be just "fed-", if we use one. > > Aren't these components all under the "Fedora Documentation" product? > If so, isn't such a component prefix redundant? After all, the "Fedora > Core" or "Fedora Extras" products don't call their components > "fed-kernel" or "fed-yum-utils." I can't see the FDP ever doing > anything *other* than Fedora docs, but if my logic is flawed, someone > please beat me with the cluestick. I didn't get an answer about globally unique IDs for components, so I'm going to assume they must be unique. I think we don't *have* to use a prefix, but if we do need for an occasional component to be clear, how about "fdp-*"? > > > So, should we have components that match 1:1 with the names in CVS? > > > > > > Seems OK to me. :) > > > > I like simple :). We'll probably need something for toolchain > > bugs/requests as well, separate from docs-common, but perhaps that > > should just be a tracker bug (as it is now), rather than a component. We can have a component for 'docs-toolchain' or similar. > I was going to say that "docs-common" needed a component, thanks for > remembering for me! Aye. > > Odd idea: Should tracker bugs live in a separate component, since they > > potentially link to bugs in multiple components ? > > It should be easy to simply have an "other" component to capture > toolchain or miscellaneous requests. Only the highest level tracker > bugs are going to be dissociated from specific components, like "docs in > progress," or trackers of that nature. There should be few enough of > those that they can live in "other" without a problem, I would think. > Since any bug can conceivably become a tracker by having other bugs > block it, making a separate component for tracker bugs could create > needless confusion, couldn't it? No tracker component. Trackers belong to a specific product and component. Some of the trackers are going to be redundant, in that they won't be needed anymore. > This reminds me to ask: How hard is it to add components later? With > one component per doc, as more docs are added (here's where I start > dreaming again), we will need to continually add more components. Don't > get me wrong, I like that idea best; I'm just wondering whether this > presents a potential delay. I'm not very familiar with how the > administration of BZ works from an "inside RH" perspective. This is my first time with this, and I asked Dave about that. Currently, the process is manual. We need one, we ask for one. There may be some tools in the future, as this is going to get more common. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 12 07:35:10 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 Jul 2005 00:35:10 -0700 Subject: Agenda 13 July 2005 meeting Message-ID: <1121153711.26925.12.camel@erato.phig.org> Here's what I have, anything to add? * Update - bugzilla product and owners.list How does the initial list look? * Push To Publish Week Week long focus on getting all of our docs from CVS to the website. - good idea? - or? * Task tracking process discussion http://fedoraproject.org/wiki/DocsProject/Tasks * DocG discussion this week? Anyone prepared? Preliminary discussion * f.r.c how-to training session following meeting? * AOB -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From ghenry at suretecsystems.com Tue Jul 12 14:33:38 2005 From: ghenry at suretecsystems.com (Gavin Henry) Date: Tue, 12 Jul 2005 15:33:38 +0100 (BST) Subject: Agenda 13 July 2005 meeting In-Reply-To: <1121153711.26925.12.camel@erato.phig.org> References: <1121153711.26925.12.camel@erato.phig.org> Message-ID: <56526.193.195.148.66.1121178818.squirrel@webmail.suretecsystems.com> > Here's what I have, anything to add? > > * Update - bugzilla product and owners.list > How does the initial list look? > > * Push To Publish Week > Week long focus on getting all of our docs from CVS to the website. > - good idea? > - or? > > * Task tracking process discussion > http://fedoraproject.org/wiki/DocsProject/Tasks > > * DocG discussion this week? > Anyone prepared? > Preliminary discussion > > * f.r.c how-to training session following meeting? > > * AOB Sounds good. > > -- > Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ > gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 > Red Hat SELinux Guide > http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ > -- > fedora-dsco-list mailing list > fedora-dsco-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-dsco-list > From kwade at redhat.com Tue Jul 12 20:09:44 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 Jul 2005 13:09:44 -0700 Subject: [Fwd: Bugzilla note] Message-ID: <1121198984.26925.40.camel@erato.phig.org> FYI, this was why I did the work on owners/owners.list. -------- Forwarded Message -------- > From: Elliot Lee > To: cvsfedora-members at fedora.redhat.com > Subject: Bugzilla note > Date: Mon, 11 Jul 2005 15:52:48 -0400 (EDT) > Hi Fedora Infrastructure hackers, > > Just a note to let you know that the bugzilla-related items for Fedora > Infrastructure (components, component owners, etc.) should now be edited > via checkins to the 'owners.list' file in the 'owners' module of > /cvs/fedora. Please let me know if you have any questions. > > Best, > -- Elliot -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 12 21:15:03 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 Jul 2005 14:15:03 -0700 Subject: FDSCO meeting IRC log 12 July 2005 Message-ID: <1121202903.26925.47.camel@erato.phig.org> hello friends quaid, Hello --> mrj (~mjohnson at nat-pool-rdu.redhat.com) has joined #fedora-docs from now on, I am going to include anyone in the notes as present if they are camping here :) * mrj is here now... hi, mrj, just getting started hou dee megacoder: if you are presente, did you get a chance to see the owners.list I checked in last night? Yes, but I didn't have much context for it. Why for? for those that didn't catch the news, sopwith updated some process widgetry so that we can edit our bugzilla components from cvs/foo/owners/owners.list Vert handy Very, very let me fwd his email spiffy idea I thought it to owners of /cvs/docs but it might have been /cvs/fedora instead ok, fwd'd to f-dsco-l for the record I guess dkl still has to actually designate the new Fedora Documentation product in bugzilla, but once that happens, we can update that file and hourly it updates bugzilla. --> Sopwith (~sopwith at nat-pool-rdu.redhat.com) has joined #fedora-docs hi, I'm here ;-) sorry I'm a little late quaid: The product should automatically be created if you specify it in the file. ah Does it autogen the bug numbers ? Sopwith: burning ears? :) Sorry, I meant to be hear on time. elliss: this is Product and Component D'oh err here Mental readjustment required I'll get used to it Sopwith: how do you specify the product info in the file? I didn't see a ref. in the comments ok, now that everyone has the context ... take a chance to look at the file /cvs/docs/owners/owners.list :) quaid: The only info that could theoretically be specified is a description for the product, and nobody reads those anyways, so... :) or in the commit message https://bugzilla.redhat.com/bugzilla/enter_bug.cgi I don't see it in the Fedora Products section, for example which does have a description, fwiw --> stickster (~pfrields at pool-70-17-99-195.res.east.verizon.net) has joined #fedora-docs Hi gang, sorry I'm late * quaid looks around more in bugzilla stickster: no worries, just talking about the first item, you'll get some background on the file /cvs/docs/owners/owners.list in a fwd. I just made to f-dsco-l Sopwith: it is also not within the Product dropdown in a bug report, so it is not in bugzilla afaict. OK, my bug then :) so, everyone else, how does the initial owners.list look? as I said in the commit, I did a few assignments of writer or editor based on proximity, i.e., you touched it last or most. these were partially just to fill the blank. OK. I was puzzled why I'm listing against the USB tutorial there are some editor assignments, such as for elliss and G2, that are assignments, though :) ... so look for yourself and let me know if you disagree with anything. I see my address is suddenly @RH? :-D elliss: that is the initialqacontact, designated as "editor" in the comments stickster: I had such a hard time with that! I couldn't stop from doing that last night I must have started @re a dozen times * quaid fixes Damn, I thought that 2nd paycheck was in the mail... oh well ;-) ha! four times I'll shoot you email with any other gripes :-) ok, updated all right Sopwith: note that I added additional comments and whitespace, that may have goofed something up in your automagic ok, if that is all on that for now ... * quaid pauses ok, so that experience led me to realize a few things: 1) we have a few too many documents on updating systems and perhaps they could be combined or reviewed for repetition and more importantly 2) we have docs ready or close to ready to publish and need to have some sort of Push to Publish Week. * tcf seconds Push to Publish Week do all the docs on updates still have maintainers? No... The "updates" is unmaintained that's right and fairly old, iirc The other two will supercede it elliss: my thoughts exactly the other two also appear to be complementary, right? or -could- be complementary should we have a way to mark modules in CVS as "unmaintained" Yes. quaid: Yes... the only glitch I see is that up2date in FC4 is a bit queasy still IIRC... rather, there are three - yum-s-m, desktop-up2date, and mirror- tutorial I say, document yum! :) mirror-tutorial is not about using software management... it is only about building a mirror Yes - mirror is very useful So any sections in it that are y-s-m or d-u duplicative should be checked against those two and removed stickster: can't the mirror be useful for yum repo? ok, right The overlap is that not all repos are mirrors Absolutely... there is info in it about using createrepo I think ok, this was one reason I put you two in writer-editor combo, let's do the same for the updates module, and you can sort it out. * quaid changes the owner for updates what week would be a good week? or rather, what weeks are bad? :) elliss: I have been a little delinquent of late with editing, simply because of other commitments... you can help by going over your tutorials and checking them for style, against the Installation Guide if the style stuff in DocGuide is too much Already done. elliss: But I will try and cover a few sections by the end of this weekend if possible Bad: Aug 8-12 The up2date tutorial is complete. The yum one will see some churn over the next few days (new developments with FC4). OK. up2date is now complete - just commited some alterations. Hopefully the yum tutorial will be done by the weekenbd can anyone -not- do a Push to Publish next week? we can always do it again :) I can after tues (mon and tues are bad for me) The week after (25-29) is awesome for me, no commitments But the 18-22 is do-able how about this, we do 18 - 22 and preannounce that we might do a follow-up on 25 - 29 <-- G2 has quit ("oops") wfm the idea being, activity in the first week + announcement may get some people to hurry up and finish. like me :-D ok, I'll do the announcement on that following the meeting * quaid too Note that the only active author not present here is Charles Heselton oops, I'll be out of town on the 22, but I'll help before I leave next week elliss: *ssh* We had a few other people who said they were working on docs, but no mail to list... whoops elliss: there are others who I think are lurkingly active, that is, they are working not in CVS, etc. quaid: jinx (per usual) aye so, hoping the flurry of activity on list (keep all work on list), with lots of CVS usage and bugzilla reports under new product, etc., will make us look all interesting and real. Fernando says, it is better to look good than to feel good, dahling you've noticed that I've followed this philosophy in the FDP for a while :) ok, moving along ... http://fedoraproject.org/wiki/DocsProject/Tasks this arose from a discussion right here a few meetings ago, you may recall still in whiteboard stage, something to include in the DocGuide, methinks Yes... I am putting some notes in the outline right now this also needs to be updated to reflect our new product status, I'll do that following the meeting mrj: how does this task process sound? too cumbersome? assume it's adjusted for new bz status Just my $0.02, I think it *sounds* more cumbersome than it *is* yeah, maybe that's it Use fewer words :) ok :) Like in Amadeus ("use fewer notes") When you think about it... you simply take notes on the wiki, figure out how to make bugs out of it, enter the bugs, and make sure it's on the schedule The rest is just making sure the wiki & bugs follow a format that's useful coo' I'll update that page with these suggestions, we'll see how it improves. any other thoughts? (on that subj.) Nope. ok nada * quaid has to allow for IRC lag :) last on agenda item was, did anyone want to train on how-to update the fedora.redhat.com website? might help the push-to-publish :) I'll ask g2 if he comes back ok yes Are we punting the Doc Guide ? Could you send a transcript to fdsco? have time following the meeting? should be quick, if you have a machine with an unused http srever oh, did I skip that? elliss: shhh !*$(% ah, I had part of my agenda get eaten in Emacs Emacs would never do that to anyone Lisp is the language of AI Be afraid it was my own fault, I reckon AI presuposes NI, a false premise. ha! true dat megacoder: yeah, I'll post IRC log to fdsco Before we leave, I have an AOB. go ahead * quaid supposes that stickster would have let quaid know if there was something to talk about for the docg already, no big thang Has anyone (TCF?) tried building example-tutorial under CYGWIN? I've tried and looks like all we need to is to mangle the "/usr/share..." prefixes into "/usr/share/docbook-xsl" prefixes. Has anyone done that yet? * stickster has taken too long to deal with turning burgeoning outline into useful division of tasks but will try to tackle now I've gotten the HTML stuff to build, but haven't tried parameterizing the CYGWIN customizations. Not sure how many people use Cygwin with FDP stuff. Perhaps some translators ? Since there is a Windows setup guide for them megacoder: Sorry for ignorance... That would involve what, changing the XSL stuff in docs-common? Abstracting out the locations or something? Well, you caught me ;-) It was an OT. Sorry. stickster: exactly. Maybe adding an and replacing all the absolute paths with a {doc.filename.prefix} or something. gotcha Very sensible and cool idea stickster: you're volunteering then? I tend to shy away from non-FC solutions, but if we can somewhat painlessly help out our OS-bound friends, I'm all for it. No, I know roughly 0.001 about XSL quaid: There is a translation-guide-windows, iirc although why not just download PuTTY and be done with it, I don't know ... stickster: well, I didn't put it there :) tee hee tcf is conspicuously silent. Ahem! stickster: IMHO, it is out of scope for FDP, but not really my issue, I think. I figure sarahs owns it and it's part of the Fedora Translation Project :) we just happen to have it in our CVS tree :) OK. Withdrawn. I would think that if megacoder or someone can do it with a minimum of fuss and it doesn't make our life any more difficult, no reason not to do it agreed But we are too late, withdrawn! :-D ok, a last AOB for the heck of it. I was trying to solicit a volunteer. Maybe a newbie would be suckered in... :) I'll keep it in mind if I get into the XSL this Thu. is the first Fedora marketing meeting, been lots of activity on list I have an AOB too when you get done I was asked in to represent the FDP, etc., and of course pull my weight :( heh as part of that, we began work on the Fedora booth for LWCE SF Like you didn't have enough to do already so that is happening, and logos and such, as some of you have seen already. so, if you have something for Fedora marketing but don't want to join the list/discussion, I'm happy to front for you as your chairdude. stickster: I actually volunteered for booth bunny duty last January :) Speaking of 0.001, did anyone look at the XSL tinkering I did to make legalnotice inclusion do what I thought everyone wanted? who what where? this was a while ago... maybe 1-2 weeks? I did not notice that :) maybe that's good then! Legalnotice was coming out linked in "nochunks" builds, now it's not ah I think I did the right thing, but would love someone to confirm or slap <-- megacoder has quit ("I worship His Shadow") um, I think so actually, just confirm or gripe well, see, I have to think about this Is the licence specified elsewhere in the doc ? jlaska did this whole process of making the new nochunks stuff, and I thought there might have been a reason weleft html-common.xsl as is .. like, you are supposed to use a nochunks version instead? elliss: this also came up because I hacked to move it to an but megacoder pointed out that doesn't fly. what I wanted to do was get it inline, but -below- the ToC Ah stickster: doesn't removing the separate file making from html- common.xsl mean that the license is not a separate file in the chunked html? Could it be at the end as a
, but not an appendix ? possibly just calling it an appendix may be the problem. sorry... checking cvs as in, appendix = non-essential, which doesn't describe the legalnotice :) Right... it needs to be in the actual doc; I think someone mentioned this onlist somewhere gotta go guys! ttyl <-- tcf has quit ("Leaving") yeah, that was Tommy Yes - it may be that not using the word appendix would be OK. right, and the container :) bugt
instead ok Or having a one line link to the text, and put the full text somewhere else. Ah, I see I made a mistake... I think the change from r1.4- >r1.5 of main-html.xsl should have been in main-html-chunks.xsl instead So it doesn't clutter the doc It works, but it's essentially doing "all HTML docs will do X" except when overridden, as in main-html-nochunks.xsl... I think XSL makes my head spin, I don't get it yet meeting is essentially done, but we can continue working on this topic Oh wait a minute, I see I noted this in my change at lesat elliss: yes, good point, that's what I did with the relnotes errata, put in a one liner similar to what is in the header of source code that referes to LICENSE *least -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Mon Jul 18 17:24:46 2005 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 18 Jul 2005 13:24:46 -0400 Subject: Bugzilla product Message-ID: <1121707486.2887.3.camel@localhost.localdomain> Now that we have a Bugzilla product and components for FDP materials, would it be wise to move our bugs there? Is there any value to retaining the old product and components (i.e. product Core, component fedora-docs for all bugs)? My preferred answers are "yes" and "no," especially given our very low bug rate compared to some of the other products, but I'm looking for input. I have a little free time today that I could move bugs but I don't want to do so without a few other people agreeing, especially @RH folks who are more frequent BZ users. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at redhat.com Mon Jul 18 17:26:26 2005 From: sundaram at redhat.com (Rahul Sundaram) Date: Mon, 18 Jul 2005 22:56:26 +0530 Subject: Bugzilla product In-Reply-To: <1121707486.2887.3.camel@localhost.localdomain> References: <1121707486.2887.3.camel@localhost.localdomain> Message-ID: <42DBE642.7030803@redhat.com> Paul W. Frields wrote: >Now that we have a Bugzilla product and components for FDP materials, >would it be wise to move our bugs there? Is there any value to >retaining the old product and components (i.e. product Core, component >fedora-docs for all bugs)? My preferred answers are "yes" and "no," >especially given our very low bug rate compared to some of the other >products, but I'm looking for input. > >I have a little free time today that I could move bugs but I don't want >to do so without a few other people agreeing, especially @RH folks who >are more frequent BZ users > > It makes sense to me atleast for now until we get a lot of independant documents to manage regards Rahul From tfox at redhat.com Mon Jul 18 17:28:59 2005 From: tfox at redhat.com (Tammy Fox) Date: Mon, 18 Jul 2005 13:28:59 -0400 Subject: Bugzilla product In-Reply-To: <1121707486.2887.3.camel@localhost.localdomain> References: <1121707486.2887.3.camel@localhost.localdomain> Message-ID: <1121707739.5789.21.camel@localhost.localdomain> Seems preferable to move them since the new product and components have individual owners. We can add standard text in each tutorial about which Bugzilla component to file against with a link, similar to what we do in the enterprise docs. Tammy On Mon, 2005-07-18 at 13:24 -0400, Paul W. Frields wrote: > Now that we have a Bugzilla product and components for FDP materials, > would it be wise to move our bugs there? Is there any value to > retaining the old product and components (i.e. product Core, component > fedora-docs for all bugs)? My preferred answers are "yes" and "no," > especially given our very low bug rate compared to some of the other > products, but I'm looking for input. > > I have a little free time today that I could move bugs but I don't want > to do so without a few other people agreeing, especially @RH folks who > are more frequent BZ users. > > -- > fedora-dsco-list mailing list > fedora-dsco-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-dsco-list From stickster at gmail.com Tue Jul 19 02:40:04 2005 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 18 Jul 2005 22:40:04 -0400 Subject: BZ email flood Message-ID: <1121740804.5488.2.camel@localhost.localdomain> Sorry about all the email, everyone. I am moving the old FC/fedora-docs bugs to new FD/* components, and have no way of stopping the email. I did realize partway through the process that I should have probably reassigned each set of bugs to the new owner/QA contact, but I failed to do so. Maybe we could split that work up between the owners. Bugzilla seems to be *really* slow, or is it just me? -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 19 08:07:31 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 19 Jul 2005 01:07:31 -0700 Subject: agenda 19 July 2005 FDSCo meeting Message-ID: <1121760452.5590.13.camel@erato.phig.org> This one is easy: * P2PW work party - Come prepared to solve publishing problems - Let's get some stuff published * AOB -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Tue Jul 19 12:10:47 2005 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 19 Jul 2005 08:10:47 -0400 Subject: agenda 19 July 2005 FDSCo meeting In-Reply-To: <1121760452.5590.13.camel@erato.phig.org> References: <1121760452.5590.13.camel@erato.phig.org> Message-ID: <1121775047.3725.2.camel@localhost.localdomain> On Tue, 2005-07-19 at 01:07 -0700, Karsten Wade wrote: > This one is easy: > > * P2PW work party > - Come prepared to solve publishing problems > - Let's get some stuff published > * AOB I'd like to enter suggestions for AOB while I'm thinking of it: - Ready to expand tidy-bowl to whole repository? - Bugzilla - may need some new components Either or both of these could be put off until next week if otherwise they might get in the way of P2PW. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 19 19:00:20 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 19 Jul 2005 12:00:20 -0700 Subject: agenda 19 July 2005 FDSCo meeting In-Reply-To: <1121775047.3725.2.camel@localhost.localdomain> References: <1121760452.5590.13.camel@erato.phig.org> <1121775047.3725.2.camel@localhost.localdomain> Message-ID: <1121799620.5590.52.camel@erato.phig.org> On Tue, 2005-07-19 at 08:10 -0400, Paul W. Frields wrote: > On Tue, 2005-07-19 at 01:07 -0700, Karsten Wade wrote: > > This one is easy: > > > > * P2PW work party > > - Come prepared to solve publishing problems > > - Let's get some stuff published > > * AOB > > I'd like to enter suggestions for AOB while I'm thinking of it: > > - Ready to expand tidy-bowl to whole repository? We can and should discuss this, yes. Part of P2PW, IMO. > - Bugzilla - may need some new components Same as above, yes. Let me add an unrelated: * Jef Spaleta is going to test some screencast solutions, do we have any typical first-user tasks for him to capture? Quick discussion. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Jul 19 21:49:35 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 19 Jul 2005 14:49:35 -0700 Subject: IRC log FDSCo meeting 19-JUL-2005 Message-ID: <1121809775.20245.9.camel@erato.phig.org> Having problems pasting the IRC log inline in the body of the message, going to do an attachment and see how that looks in the online archives. If not, it's debugging time. IRC log attached. -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- # FDSCo meeting 19-JUL-2005 how about reversing the agenda? do the quick AOB first, then get into publishing some stuff Good idea goferit stickster: any barriers to expanding tidy-bowl? * quaid can't recall if he had a bug in it ... something about new lines for ? The ulink is the only drawback, but it's important to remember it's only a bug as long as we think of it that way :-) aye By which I mean, if the commit is consistent, and the content of the doc is unchanged, it really doesn't matter true Although I made every effort to mirror the way I thought it should look the bugginess is -not- being able to affect it's behavior, that's all ... There's one other "bug" in it which is also exceedingly minor since it's consistent After tags open, the next line (usually where the url gets placed due to fill-width considerations), spacing is wrong from left-margin. I think I know *what* it's doing, but I have no chance of figuring out *why* ok, the deal is, once we deploy it, we have to deal with resolving these bugs in an orderly manner. Again, probably matters very little since it (1) is consistent, and (2) doesn't change the doc content that is, we can fix it, but we have to warn people to do a special normalizing-then-commit I think these should be stand-alone commits with zero other content changes ... just something we'll make part of the process, I reckon. but ok any other concerns about rolling out tidy-bowl officially? and did Tommy and Paul 's write-ups suffice for how-to? Is xml-normalize staying as a test area ? Or should it be dropped ? yes, I guess, for the development of the normalization tools so we can use it for testing new changes, etc. We should definitely hold on to it ok, in that case ... quaid: I can see if the xmlformat author can help resolve the strangeness... I haven't contacted him at all stickster: do you want to do that -before- a full rollout, then? Sure, why not... if he can/will help, it shouldn't take him long I think if I give him sample docs he can probably find the problem easier than any of us we can shoe-horn this into the publishing as soon as it's ready, it's just a step to add and doesn't change content or publishing details. exactomundo stickster: ok, do that when you can, and then we'll prepare an announcement of what to do and how to do it, to be mirrored in the DocG eventually :) all right, next item bugzilla components I wrote up an email for the list to ask for additions to that, which Versions to add, and a full description aka The Great Email Flood of 2005 Paul thought of adding a 'docs-request' for non-document specific RFEs I have a couple others, and an apology to make first to Stuart (I think?) fight! fight! He suggested a master tracking bug, and I think maybe we need *almost* such a thing a "project-tracking" bug to hold things like "docs without ideas" tracker, "orphaned docs" tracker... Things which can't be tied to toolchain or any specific CVS module ah, that's a good idea that's where the trackers make sense, where you don't have an existing search field That may be what he meant and I misinterpreted it -- or more likely, I'm just foolish and didn't realize how good the idea was until I started going through BZ it's the user configurable field :) OK... so "project-tracking" is good Also... "umaintained" or "orphaned-docs" component for things where we want to log bugs, but the doc has either not yet made it to CVS or dropped out and might return one day Hmm Now that I write that, I'm not sure it's very smart This happens a lot to me yeah, it should be in CVS no matter what? I don't think we should use Bugzilla for that right... if it was ever there, it should stay there we can't support other repositories, can we? if we drop a doc, bugs are closed as WONTFIX * quaid answers his own question, "cvs.fedora is the One True Fedora CVS' stickster: right, and we have the Version field for docs that only go so far and are gone to Legacy * stickster notices quaid has "I'm With Stupid" shirt pointing this way stickster: the finger on that shirt spins stickster: I got you down for creating the project tracking tracker bug and blocking it with the other project bugs, k? the rest of this, let's do on list. OK, will do... so, does making new entries in owners/owners.list automatically give us new BZ components? Or does Sopwith have to do some magic on it? automatically :-) He's like the ghost in the machine, this guy aye sorry, moving on then.. stickster: ok, so commit away :) all right just wanted to make sure all who were on screencasting caught the discussion on fedora-marketing and I saw Stuart pop in there earlier that was all I wanted, if anyone else wants to comment about it, or thoughts, etc. The screencasting HOWTO is a good idea Absolutely I'll be fascinated to read it myself * quaid lols We could use Wiki to start documenting experiments I'll push that back onto the Marketeers, ask them to at least write up a structured text or Wiki version for someone to start with and consider owning it themselves :) Yes. In our CVS it wouldn't be so visible until it was complete good point ok, anything else on that? * quaid prepares to move on ... wait for it ... * quaid is cvs up'ping in preparation for publishing something stickster: if you have anything in your local f.r.c/docs that you want to commit and have me review/sanity check, go ahead or ask away. otherwise, I can handle the Web publishing to keep things moving along. * quaid notes that he doesn't have anything to publish yet, probably next week with the SELinux FAQ I made trivial changes in relnotes this morning, just speling errors and a term change to standard English I haven't pushed it to the web site yet, so if you want to... ok, there are other fixes in there good for publishing speling errrors ? :) elliss: it's a joke, get it? :) elliss: you got the joke, then ;-) q.v. Apache module yeah, I saw that one :) * quaid recently fixed his b0rked aspell I am working on yum-software-management and will have it done by end of week I think we had discussed merging this with desktop-up2date... what's the story on that? They were part of the same doc I split it because yum CLI is more technical Although we're forced to recommend it for desktop users for software installation right now Right... are you able to "commonize" (my new word, no need to thank me) some of the sections to make upkeep easier? btw, there -is- a way to xref across guides, jlaska was doing that iirc maybe leave in the XML for once we figure this out The only commonalities would be "Abouts elliss: That's not bad, though... I can think of at least one other document that would be useful for (mirror-tutorial) could go in docs-common for instance yeah! Worth trying. Is there a link for the cross-document xref ? That makes the cross-doc linking less of an issue for now I have an Installation Servers chapter sat on my hard drive So there will be a few overlaps, or possible discussion on merging some docs later Make sure you read mirror-tutorial first and see what we can just include in there I have I think if we put PXE stuff in there, we'll be in pretty good shape Mmm. Well, just bounce something to f-docs-l and talk about what's *not* in common, and we can go from there I'll find out about the cross-ref stuff and report back I just hate having to maintain overlapping docs wherever possible That's why it's still sat on my hard drive :) hmm, that sentence doesn't parse (mine, I mean) Didn't want to make a muddle With the mirror doc you are writing What other docs are pending ? I think quaid sent something to f-dsco-l or f-docs-l, sorry Ah, here you go: * Hardening Fedora * Yum Software Management * Mirror Tutorial * Proxy Guide * FC4 Release Notes (updated) * SELinux FAQ * Sudo Tutorial * USB Hotplug (out of date?) so Move usb-hotplug to legacy what we need is everyone to grab dibs on something in that list to edit, then edit, CVS in the changes, and we publish udev has superseded it stickster: thought so :) we can get the low hanging fruit (sudo tutorial, mirror tutorial, proxy guide) to get the hang of it That leaves 7 docs... I have "yum" :-) * quaid is publishing the relnotes right now tcf: Whaddaya say, docs lady? :-D G2: have you seen the Hardening tutorial? is that a topic you feel conversant with? because we do need to do technical and writing edits. stickster: sorry, I totally didn't realize it was past 4, some surge fried a bunch of our machines, and I am trying to do damage control stickster: what do you need me to do? 's ok, just being friendly sorry to bug oh, crum I updated the wrong RELEASE-NOTES-en.xml in CVS this is why branching is Good and little directories to get forgetful in is Bad whoops anyone with how I revert a file in CVS? oh wait... just to previous version quaid: cvs up -pr 1.1 filename.xml > filename.xml Damn, she's good quaid: that just gets you version 1.1, you still have to commit it back to CVS quaid: not yet, I would be interested in that stickster: thanks ;-) tcf: so you revert by just recommitting a copy of the previous version, it's not an actual rollback? that's fine with me :) yes it is bizarre, but that works the best there is a way to co a specific version with a sticky tag, but then it only works for your local repo and you have that darn sticky tag to deal with that sometimes prevents you from getting the actual latest revision crap^2 I just noticed we've all been working in release-notes/FC4 this is why branching is Good and little directories to get forgetful in is Bad Yes. Perhaps ask megacoder about moving the layout to branches ? good lord yes or, rather we can just start doing that moving forward all right the FC-4 tag has been applied, so I can rely upon that to represent the as-released version I never did apply the FC-4-ERRATA1 tag for the content that went into the errata Sopwith: what is the status on fedora-release errata? I don't recall seeing it anywhere but I can go back and recreate that somehow, I think so ... this afternoon I'll merge the changes from that errata into the new content and make that HEAD quaid: Looks like it got built for a testing update and possibly work out the ERRATA1 point ... though unlikely since those changes never landed on the same files that are in FC4/ Do you have new content to push as an erratum? Sopwith: OK, that's fine, then I know it's worth preserving the state of that data in CVS as a tag somehow sure could Sopwith: but I was just going to update the Website I was just wondering if you wanted to push a new erratum, or find out about the existing one. Sopwith: my point with the fedora-release was to get the default Firefox page to look prettier :) aha Sopwith: find out about the existing one although Tommy's point about the almost makes it necessary to do another, since that leaves us accidentally in a potentially weird legal spot. Sopwith: so I may follow up with a request for a new erratum right now we are updating the f.r.c/docs/release-notes/fc4/errata/ <-- mariusm has quit (Client Quit) What's on HEAD of release-notes/FC4 right now is what you'd like released? close I need to troll the bug reports, too I need to run... gig soundcheck at 6:00 local kewl, ciao night bye all <-- stickster has quit ("And then the CHUDs came.") ok, I'm going to work on the release notes Time for the gavel ? and will be here if anyone else wants to continue chatting/working to publishing. aye -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From ghenry at suretecsystems.com Mon Jul 25 08:13:45 2005 From: ghenry at suretecsystems.com (Gavin Henry) Date: Mon, 25 Jul 2005 09:13:45 +0100 (BST) Subject: Possible Fedora author? Message-ID: <61878.193.195.148.66.1122279225.squirrel@webmail.suretecsystems.com> Seen this: http://www.howtoforge.com/perfect_setup_fedora_core_4 -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E ghenry at suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/ From stickster at gmail.com Mon Jul 25 11:47:27 2005 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 25 Jul 2005 07:47:27 -0400 Subject: Possible Fedora author? In-Reply-To: <61878.193.195.148.66.1122279225.squirrel@webmail.suretecsystems.com> References: <61878.193.195.148.66.1122279225.squirrel@webmail.suretecsystems.com> Message-ID: <1122292047.3012.6.camel@localhost.localdomain> On Mon, 2005-07-25 at 09:13 +0100, Gavin Henry wrote: > Seen this: > > http://www.howtoforge.com/perfect_setup_fedora_core_4 Just took a look. I don't know about "perfect," since the writing leaves something to be desired, and one of the first steps is to install apt. ;-) I also notice there's some superfluous use of CPAN when the author could just "yum install perl-HTML-Parser" and so on. Another item of note is that the tutorial in question is marked "All rights reserved," thus legally encumbering the material. Why don't you see if you can (1) convince the author to FDL the contents, and (2) edit it yourself into a more coherent narrative that uses Fedora technical standards? The subject matter itself seems like a good idea for coverage. Followups to fedora-docs-list please, the FDSCo list should be reserved for steering committee matters wherever possible, and has fewer readers in any case. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From ghenry at suretecsystems.com Mon Jul 25 20:03:21 2005 From: ghenry at suretecsystems.com (Gavin Henry) Date: Mon, 25 Jul 2005 21:03:21 +0100 Subject: FUDCon London? Message-ID: <200507252103.21496.ghenry@suretecsystems.com> I've just registered. Anyone else make it? -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E ghenry at suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/ From kwade at redhat.com Tue Jul 26 00:40:09 2005 From: kwade at redhat.com (Karsten Wade) Date: Mon, 25 Jul 2005 17:40:09 -0700 Subject: FUDCon London? In-Reply-To: <200507252103.21496.ghenry@suretecsystems.com> References: <200507252103.21496.ghenry@suretecsystems.com> Message-ID: <1122338409.26275.71.camel@erato.phig.org> On Mon, 2005-07-25 at 21:03 +0100, Gavin Henry wrote: > I've just registered. Anyone else make it? Not I, said McFly. However, I am going LWCE in San Francisco, and will be at the Fedora booth there. We aren't doing a FUDCon SF 2005. :( - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: