Bugzilla suggestion
by Paul W. Frields
I'd like to suggest an additional FDP component for Bugzilla -
"website," which would cover publishing goofs, bad linkages, or other
non-content driven bugs. While it is true that this bug might capture
entries from people that should go to separate docs, it's very easy to
reassign based on a preliminary review of the bug. Examples of bugs in
this component might include:
* An incorrect link on a doc index page (such as a missing link to the
newest version of the relnotes)
* Things that break as part of the web publishing process
* Problems with content that is not provided out of docs CVS, such as
original HTML from fedora CVS
Arguments? Agreements?
--
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/
18 years, 8 months
Bug moving complete
by Paul W. Frields
I have now finished moving all the bugs in the "Fedora Core/fedora-docs"
component in Bugzilla to more appropriate components. The *VAST*
majority ended up, as expected, in "Fedora Documentation/*" under their
respective doc components. I moved a very few -- mostly closed -- to
"Fedora Infrastructure/web" since they didn't involve any actual doc
content.
Thank you, everyone (especially you poor @RH'ers, who endured the bulk)
for putting up with the flood of email.
--
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/
18 years, 8 months
Minutes FDSCo 19-JUL-2005
by Karsten Wade
We focused on publishing, but a few other things came up, especially
around bugzilla usage. :)
FDSCo 19 July 2005
#fedora-docs on irc.freenode.net
Attendees:
==========
Paul Frields
Karsten Wade
Mark Johnson
Tammy Fox
Gavin Henry
Stuart Elliss
Reports/Updates:
================
* Targeting FC4 SELinux FAQ publishing for next week, call for FAQs
went out today.
* Ongoing work on publishing
* Updates to FC4 Release Notes published:
revision 1.4
date: 2005/07/19 23:10:39; author: kwade; state: Exp; lines: +233
-207
Moving of legalnotice is an important part of this commit, fixed bz
#162475, bz #162219, bz #160369, style and spelling fixes
throughout.
Actions:
========
Paul: Resolve our few bugs with xmlformat by asking the developer for
help.
Paul/Karsten: Draft and send announcement of xml normalization tools.
Paul: Create 'project tracking' bug tracker, have project bugs such as
'docs ready for publishing', 'docs without ideas', and so forth
block it.
Karsten: Ask for first draft in Wiki or structured text of a "Fedora
Screencasting HOWTO" from the Fedora Marketing interested.
It is more valuable as a living document in Wiki than being
hidden in FDP CVS while being written.
Karsten: Find out more about cross referencing between DocBook books.
## 30 ##
--
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/
18 years, 8 months
screencasts (was Re: Fedora review)
by Karsten Wade
The marketing group is very interested in the screencasts idea. The
summary of this thread is:
"If we had screencasts of the the top 10 most desired actions by tech
journalists ... we could help people and resolve writers penning
uninformed articles ... these would need to be active during testing,
and could be available to review during firstboot ... initial ones can
be rough, with notes taken on-screen in a text editor within the
screencast."
-------- Forwarded Message --------
> From: Jeff Spaleta <jspaleta(a)gmail.com>
> On 7/19/05, Greg DeKoenigsberg <gdk(a)redhat.com> wrote:
> >
> > If there's precedent for this being done easily and well, then let's
> > steal, steal, steal. :)
>
> thomasvs to the recue!!!!!
>
> instanbul which j5 has packaged.... and is trying to get it into extras now.
> http://people.redhat.com/johnp/istanbul/
>
> it encodes into theora by default... its a little cpu intensive on the
> encoding so i hear.. but for this purpose... that does not matter.
> Its soon to be an in Fedora tool, which means its available to the
> entire community to use... and by using it to build task videos we
> provide feedback on performance and additional testing of the theora
> encoding. As soon as j5 actually gets this into extras is pretty much
> the "good enough" solution to play with.
>
> I think j5 even had a blog entry showing how it works...but i cant
> find it at the moment.
>
> -jef
>
> --
> Fedora-marketing-list mailing list
> Fedora-marketing-list(a)redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-marketing-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/
18 years, 8 months
Re: packager-handbook
by Paul W. Frields
On Tue, 2005-07-19 at 19:33 +0300, Ville Skyttä wrote:
> On Mon, 2005-07-18 at 21:25 -0400, Paul W. Frields wrote:
> > On Mon, 2005-07-18 at 21:23 -0400, Paul W. Frields wrote:
> > > I see that we've suddenly "inherited" a new document from Ville Skyttä
> > > and Marius Jøhndal. Has someone agreed to maintain and/or edit this?
>
> I requested it to be imported somewhere in CVS after Warren asked
> whether there's something that needs to be saved in cvs.fedora.us.
> Elliot Lee imported it to docs.
>
> I think the packager's handbook, while very much work in progress and
> partially outdated, still does contain some useful information, and that
> having things in docbook format has some advantages over Wikis. Your
> thoughts?
I thought it might be a fine idea to get "spot's" stuff from the Wiki
integrated in it wherever necessary and reasonable; that may already be
done, but I haven't read through the whole thing. Certainly we're happy
to house it, as long as there's a mintainer! :-) There are a few docs
people who are maintainers in Extras CVS, so certainly someone can be
roped into helping out.
> The packager's handbook does not need anything right now, but if people
> see it being useful and fits the plans of the docs project, I'd be
> interested in contributing every now and then in order to "finish" it
> and make it generally better. But the primary reason right now in
> importing it *somewhere* is to get it out of the way when Warren needs
> to shut cvs.fedora.us down.
That sounds great to me.
We have a steering committee meeting this afternoon, and I'll work on
getting some additional components that are appropriate for this kind of
bug, and post here to the list with a Cc to you. Then you can file the
bug under Fedora Documentation with summary "New document: Packagers
Handbook" or some such.
> > And, out of curiosity, why don't we see a record of this on
> > fedora-docs-commits?
>
> It was a direct CVS repository copy from cvs.fedora.us in order to
> preserve history, not the usual add + commit.
Cool, thanks for the info. I am not a big CVS junkie, so I didn't even
realize one could do this!
> (Please Cc me in replies, I'm not subscribed to the docs list at the
> moment. And Marius is currently taking time off the project; I'm sure
> he wouldn't mind being dropped from Cc.)
I removed him from Cc on this thread, thanks.
--
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/
18 years, 8 months
Re: Taking up work (was: Re: No more right click terminal)
by Paul W. Frields
Forwarding this to fedora-docs-list for additional discussion.
On Fri, 2005-07-15 at 12:53 -0400, Toshio Kuratomi wrote, in response to
Rahul Sundaram:
[...snip...]
> > >2) Start a project to package different default values for Extras. We
> > >have redhat-rpm-config changing rpm and fedora-release changing the
> > >config of yum. Maybe there should be a poweruser-gconf-tweaks. (More
> > >seriously, it should probably be more like config-nautilus-nonspatial,
> > >config-rpmbuild-userdirs, config-metacity-focusfollows, etc) this can
> > >work for things that just require default config changes but will not
> > >work for compilation/upstream code changes.
> > >
> > >
> > I would prefer people working on documenting these. A good desktop users
> > guide and "power" user FAQ's for Fedora which details out the common
> > changes such as these would be useful. I dont think installing different
> > packages for trivial changes such as these is really a good idea. What
> > if you install this package and then change the configuration to a
> > conflicting value?
> >
> Good idea! Let's make that #4: Fedora Guide to Power-User Tweaks. Are
> you volunteering to create and edit it? (I wasn't volunteering to head
> a project to create defaults, so you can say no to this as well.)
Rahul agreed to edit if someone would write. Anyone care to start
compiling something? This would make a great starter project for
someone new to the docs process.
--
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/
18 years, 8 months
Introductions
by Stephen Davies
Name: Stephen Davies
Location: Aldershot, Hampshire, UK
Profession: Owner of IT Services/Consulting Company
Company: Ultra Consulting Ltd ( www.ultraconsulting.co.uk )
Expertise: IT Professional since 1975. Got into Unix in mid 1980's(Ultrix-32 & then TRU64). First installed Linux (slackware 1.?) way back when. Company is involced in Middleware Consulting (Websphere etc). I have used RedHat since 6.2 and run FC3/4 & RHEL on a variety of systems including Laptops. IBM Websphere MQ & WMQI Certified RHCE/RCHT as well. I also did about 50% of an Oracle DBA sometime in the past.
I'm proficient in C/C++ Delphi/Kylix, SQL, shell scripting etc.
Where I want to help:
Documentaion always lets down systems & solutions. I actually don't mind writing documentaion if it is going to be used rather than get ticks in a box. So helping make the documentation more applicable for commercial users can only help the acceptance of Linux in the commercial arena. Idiot proof installation & configuration guides seem to be quite popular at the moment.
To give you an example, If a company wants to run Oracle 9i, Websphere MQ and Websphere Message Broker on the same Linux box what do I need to install from the base RPMs. What additional RPMS are needed that are not included in the OS, what kernel tweaks are needed etc etc etc.
How Much time do I have to Offer?
This depends upon how bust the company is. If a contract comes along and its is worthwhile taking it then I'll do it. Between contracts then lots of time.
so, I'm open to offers.
Stephen Davies
18 years, 8 months