New tracker

[Tammy Fox]

On Thu, 2004-08-12 at 19:07, Karsten Wade wrote:
> On Wed, 2004-08-11 at 22:07, Colin Charles wrote:
> > Since no one else started it, the tracker now is:
> > 
> > 	https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129722
> > 
> > I've added various docs that should be on the site, so to speak.
> > Comments, etc.. welcome (on the bug)
> 
> Saw Tammy this afternoon, she cleared through a few bugs (if you filed
> them, you saw the resolution, changes coming to the website) and moved
> some stuff along.  We discussed the doc tracking process, and she
> expanded the doc tracker bugs, so there is now:
> 
> 1. http://bugzilla.redhat.com/129784 Docs ideas without owners - a
> general bucket for ideas for new documents or conversions that come
> _first_ through the list
> 
> 2. http://bugzilla.redhat.com/129807 Docs in progress - for tracking
> documents actively being written/developed/edited
> 
> 3. http://bugzilla.redhat.com/129722 Docs ready for going to
> fedora.redhat.com - when it is done with 129807, it comes here while it
> undergoes final editing to go to the website.
> 
> This means the process of idea -> publication is: 
> 
> 1. File a bug report for your document, or carry the on the one with the
> idea in it.
> 
> 2. Move the bug through the tracker in this order
> 
> idea 	-> 	develop 	<-> 	publish
> 129784		129807			129722
> 
> Note: there is a double-arrow between develop <-> publish because a
> document should stay alive after it is published.  Once you have
> published a version and have moved to writing for the next version of
> Fedora Core, your document's bug moves back to 129807.
> 
> I'll add this into the process document, which Dave converted to XML and
> I am editing for reposting back here for more comments.
> 

Karsten,

It seems like we have some duplication of effort here. Before I knew you
had started a process document in XML, I started 

http://fedora.redhat.com/participate/documentation-quick-start/

Seems like we should combine our efforts and decide whether to use XML
for this or just post it on the website. Since it isn't very long, I
started it as a straight webpage thinking it would be faster to update.
Which do you prefer? I do like your explanation here of the lifecycle of
a tutorial so I'll incorporate it into my page as soon as I get a chance
(within the next few days).  We could even draw up a flow chart in Dia.
Like I said previously, my page needs organization. I was just trying to
get it up for everyone to see as soon as possible while everyone was
interested in discussing the idea.

Tammy


> cheers - Karsten
> -- 
> Karsten Wade, RHCE, Tech Writer
> a lemon is just a melon in disguise
> http://people.redhat.com/kwade/
> gpg fingerprint: 2680 DBFD D968 3141 0115  5F1B D992 0E06 AD0E 0C41