IRC log, 28 Jun 2005

[Paul W. Frields]

<meeting>
<G2>	Welcome all ;-)
<quaid>	howdy, one sec while I get my notepad ready
<megacoder>	Hey, we have enough folks here that my user window is
scrolling!
<quaid>	ok, here's a quick agenda:
<quaid>	* website update
<quaid>	darn paste!
<quaid>	* tidy-bowl looking good!
<quaid>	* bugzilla ACLs update
<quaid>	* task process update
<quaid>	* website update
<quaid>	* update on docs trans discussions
<quaid>	* alexandria update
<quaid>	* AOB
<quaid>	so, megacoder, how ya feeling about the tidy-bowl and friends?
<megacoder>	I'd like a few more people to beat on it by changing files
in the "xml-normalize" project.
<megacoder>	Only files checked into that area will be normalized, er,
reformatted.
<megacoder>	IIRC, stickster was going to send an invitation to the list.
<quaid>	an invite to beta test?
<megacoder>	yup
<stickster>	Yes... still working on it, sorry... I had a number of other
things intervene since last evening unfortunately
<stickster>	I'll finish and send shortly after meeting
<quaid>	cool
<megacoder>	Good.  I'm done with it until something breaks.
<quaid>	suh-weet
<quaid>	stickster: anything else on this subj?
<stickster>	No, check commits list for some examples... appears to do
what we wanted the way we wanted :-)
<quaid>	ok
<quaid>	about bugzilla ACLs, which will help me and mether to deal with
bugs
<quaid>	I sent out a full request to dkl to upgrade everyone on FDSCo
<stickster>	cool
<quaid>	he later sent an email internally asking all managers to do
something similar, one email with the access levels included.
<quaid>	so he might be waiting to do them all at once, however
<Sopwith>	oh wait, what access do you need?
<quaid>	I have experienced him making changes as requested but not
telling us, so feel free to try "advanced" access rights stuff at any
time and let me know what happens if it works
<quaid>	Sopwith: all FDSCo members full rights to fedora-docs component
<quaid>	Sopwith: so we can all close, reassign, etc.
<Sopwith>	quaid: OK... Right now, joining the 'fedorabugs' group in
Fedora Account System will do the same thing (not just for fedora-docs,
but for all bugs I think)
<quaid>	wow, really?
<mether>	Sopwith, yes that does for all components
<quaid>	hmm, I wonder if we all -need- that level of access
<quaid>	I tend to be a least privilege type of person.
<mether>	quaid, well you can have this setup now till we get more
granularity
<quaid>	well, yeah, if that is the project mode, I can roll with it.
<quaid>	stickster: go ahead and join fedorabugs group through
admin.fedora.redhat.com
<stickster>	righty-o
<quaid>	ok, next thang
<quaid>	I didn't do anything more with the task tacking process, I am
pushing that off until next week (deadlines -n- all that)
<quaid>	I'll try to have something for us to discuss next week.
<quaid>	so, now, about the website
<quaid>	I have a small pile of updates that need to happen, and it's
getting bigger
<quaid>	I'm wondering if anyone is interested in helping update the
website?
<quaid>	it's easy stuff
<mether>	quaid, what is involved?
<stickster>	Do you need a FDSCo person in particular?
<quaid>	not per se, no
<quaid>	but it certainly needs to be someone who is up to speed with
mostly everything happening at a particular time
<quaid>	updates for the website are simple,
<quaid>	you check out the website and set up a local sandbox for
checking.
<quaid>	updates are checked into CVS and tagged LIVE, all live content
is swept in hourly.
<quaid>	our DocBook stuff needs to run through a tfox script and be
checked, it works 90% of the time but there are some odd corner cases
with HTML output from XML.
<quaid>	maybe a couple of people?  G2 from FDSCo, and mether, who
doesn't have enough to do already?
<mether>	quaid, Ya I could pick up *some* of the content
<G2>	I can get somethings sorted next week.
<quaid>	g2, mether: how about we do some training on it next week, after
the FDSCo meeting?
<mether>	quaid, ok. I need to learn to handle cvs properly
<quaid>	there's the tools and I want to capture some of the habitual
process I've used to this date.
<quaid>	mether: cool, we'll make that part of the training.
<quaid>	I can handle the current workload, but it's increasing and I
don't want to get caught with my drawers down :)
<quaid>	ok, moving on ...
<mether>	quaid, well the current content is outdated enough for that ;-)
<quaid>	btw, anyone else is welcome to the training and ACLs, just want
to get some designated people too
<mether>	quaid, we will document it
<mether>	quaid, others can pick it up
<quaid>	mether: yes, but not the content for this project, that is
fairly updated
<quaid>	right
<G2>	yeah, that would be great
<quaid>	FDSCo members should probably all have access to update, in case
of urgent needs, etc.
<quaid>	but in the future we will want one or two specific "Web
publishers" who go down a checklist for each document as part of
publishing it, etc.
<G2>	Fine.
<mether>	quaid, would you give us a better idea on what needs to be
updated specifically
<mether>	quaid, the content under the docs wing?
<quaid>	mether: yes, that is our focus
<mether>	quaid, ok
<quaid>	mether: I'm thinking specifically right now of publishing
tutorials that are waiting (mirror-tutorial) and translations.
<quaid>	ok, one sec while I dig up my notes on trans process.
<quaid>	yeah, only thing I can find is IRC log :/
<quaid>	here is the summary, I will go through the log and write up
something better:
<quaid>	we're going to make translation of the relnotes part of the hard
deadlines
<quaid>	this will enable them to be included in the release
<quaid>	so, for each test release, we will have a freeze several days
before the relnotes need to be in the test, and trans has a chance to
get as many in as they can.
<quaid>	the tools guy for the trans team is willing to work with us on
some automagic
<quaid>	for example, they use this
http://elvis.redhat.com/cgi-bin/i18n-status
<quaid>	that lets them keep track of who is translating what, and people
do CVS locks etc.
<quaid>	I want to keep all the trans in their CVS as canonical, just MHO
but it feels right.
<quaid>	so the process would be like this:
<quaid>	1. we write like crazy until doc freeze
<quaid>	2. we freeze and send a message to f-trans-l that the relnotes
are ready for trans
<quaid>	3. Bernd Groh (tools guy) opens the floodgate in their tools
that lets the system automatically pull our modules from our cvs tree
<quaid>	4. translators do their thing, and whatever is in the tree at
100% by the test trans freeze goes out with the test release
<quaid>	rinse, wash, repeat for each test up to release
<quaid>	by release time, they should be only having to translate a
smaller percentage.
<quaid>	by then, we will have a chance to look at xmldiff type stuff,
which will make a huge difference in how difficult trans is.
</nutshell>
<stickster>	Looks pretty reasonable... as long as we can coordinate with
$PERSON for our deadlines
<quaid>	also, the rh.com based translators will commit to being the
relnotes translators for the time being, considering the importance of
the materials, and move it into the community as we can.
<quaid>	the deal is, the trans team has big time processes that allow
them to get their shit down on time, every time.
<--	tcf has quit ("Leaving")
<quaid>	we benefit in efficiency by attaching into those processes.
<stickster>	sweet
<stickster>	Moving on then?
<quaid>	yep
<quaid>	alexandria update is, I haven't written up a better draft of the
staging server yet, also pushing out to next week.
<megacoder>	stickster: your tidy-bowl invidation has made it to the
list.  I added a short addendum.
<quaid>	from there it's a matter of engaging Sopwith in what can and
cannot work.
<quaid>	I'd like megacoder and stickster to work closely with Sopwith
and I on defining and implementing the staging server stuff.
<megacoder>	ok, fine, fer sure, fer sure
<quaid>	Valley Coder
<megacoder>	Tennessee Valley Coder ;-)
<stickster>	Like, gag me with a mouse
<stickster>	y'all
<quaid>	"Like, Java sucks, give me machine language, gawd!"
<stickster>	:-D
<megacoder>	Kung-fu? I know "tire tool"!
<quaid>	ok, open for other discussions and such
<quaid>	I probably forgot something with my off-the-cuff agenda
<stickster>	DocGuide status
<quaid>	run away!!
<quaid>	ah, yes
<stickster>	Um, I suck?  'Cause, like, that's *totally* the status.
<stickster>	No, what I mean to say is...
<stickster>	I am working on condensing the many disparate suggestions
into a more formal outline of the guide from which I will be able to ask
for volunteers for writing those sections... relying on, of course, the
expertise of tcf (hey, where'd she go?) for advice and assistance
<megacoder>	Maybe she was actually gagged, back there a moment or so.
<mether>	repeat: this is not related to any agenda but did anyone here
try out gplflash or swfdec?
<quaid>	not I
</meeting>


-- 
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: <http://listman.redhat.com/archives/fedora-dsco-list/attachments/20050630/a685d555/attachment.sig>