IRC Log FDSCo Meeting Dec 13 2005

Stuart Ellis stuart at elsn.org
Tue Dec 13 22:34:27 UTC 2005


(21:03:13) quaid: <meeting>
(21:05:12) megacoder: Welcome back TCF!
(21:05:34) megacoder: Good to see your avatar ;-)
(21:06:20) quaid: aye, for sure
(21:06:48) quaid:
http://fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule
(21:08:01) quaid: so, let's see, a short discussion was had about
DocsRawhide enhancemetns
(21:08:46) quaid: the discussion quickly fell OT
(21:08:47) quaid: :)
(21:09:00) G2: yo
(21:09:09) quaid: so, whilst we are all here
(21:09:22) quaid: are there any specific things we want to ask enhanced?
(21:09:31) quaid:
http://fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule
(21:09:35) quaid: oops
(21:09:39) quaid: http://webtest.fedora.redhat.com/docs/
(21:09:53) quaid: the links there are relatively static, or rather, are
definable by us through CVS
(21:10:17) quaid: my thoughts: build error output goes where? what can
we do about that?
(21:10:29) quaid: builds based on specific tags or branches
(21:11:07) quaid: guess that's it :)
(21:11:14) G2: get an e-mail like on extras?
(21:11:22) quaid: yeah
(21:11:35) quaid: with a URL to stdout
(21:11:37) G2: that should be fine then
(21:11:47) megacoder: Are the rawhide docs considered cast-in-jello?
(21:12:06) G2: build error out to a folder in the same one as "en"?
(21:12:10) quaid: the builds based on branches could be defined in the
file that we use to define what appears in DocsRawhide
(21:12:11) megacoder: I mean, is it "normal" for a CVS checkin (interim)
to break the build.
(21:12:21) elliss: Nope
(21:12:32) megacoder: I think just a nag email about the build failure
should go the doc owner.
(21:12:32) quaid: one should build before check in
(21:12:32) quaid: but
(21:12:40) quaid: yes, nag mail to just owner
(21:12:47) quaid: or, definable in our module file
(21:12:57) quaid: one should build before check in, but that is not
always possible
(21:13:09) quaid: this gives people a chance to edit content without a
working build system, which does happen.
(21:13:19) megacoder: Incremantal check-in's can make that awkward.
(21:13:22) quaid: i.e., sitting on another OS or a broken toolchain
locally, etc.
(21:13:44) quaid: too many nags, you mean?
(21:13:47) megacoder: I'm mean, build failures should be noted, but no
alarums should go off.
(21:13:53) quaid: oh, right
(21:14:00) quaid: well, every failure will gen an email
(21:14:09) quaid: but right now, I think it's building hourly
(21:14:19) quaid: that's another RFE: rolling builds
(21:14:29) megacoder: Shazam! Put some hysterisis on the nag!
(21:15:23) quaid: hmm
(21:15:23) quaid: ok
(21:16:03) quaid: elliss: minutes note -- if you'll compile these RFEs
into a list, we can use those as specific task request of Sopwith 
(21:16:17) elliss: OK
(21:16:33) quaid: or ... wonder if the docsrawhide tool/script is
available for us to hack upon?
(21:17:00) G2: should be
(21:17:02) quaid: or otherwise help :)
(21:17:07) quaid: yeah, just don't know where
(21:18:42) elliss: docs-common/bin/bulkbuild ?
(21:19:21) elliss: Don't know if that's the live version
(21:20:21) megacoder: It's not, it's there as an archive. The real
script is only sopwith'able
(21:20:56) Sopwith: I'm working on moving the fedora-config cvs repo to
a place where more people can hack on it (e.g. nman64)
(21:21:10) quaid: cool
(21:21:51) quaid: and everyone knows that we have some control through
docs-common/bin/active ?
(21:22:39) quaid: for example, that would be where we want to add
tag/branch as a configurable
(21:24:36) quaid: ok, we'll compile a wish list 
(21:24:54) quaid: our prime usage for this is to populate places such as
Docs/Drafts/ on the Wiki with links to this
(21:25:07) quaid: and that sort of thing
(21:25:23) quaid: I don't see it being primarily for people to just
browse through the directory structure, although they can do that.
(21:26:16) quaid: if there's nothing else on this?
(21:28:32) quaid: alright
(21:28:44) calennert left the room (quit: "heading home").
(21:29:41) quaid: Paul is unavail, megacoder any packaging stuff you
want to discuss?
(21:30:35) megacoder: There has been a spurt of activity about how
document images are found. I've written a "bin/copy-figs" file to handle
that and am currently updating the docs guide.
(21:31:09) megacoder: I did see a new self intro from a guy that does
java...
(21:31:26) quaid: yeah, he just left ^
(21:31:48) megacoder: Was it something I said ;-)
(21:31:57) quaid: maybe he {felt} the vibe
(21:32:15) quaid: feel free to reply to his self-intro and show him what
we are doing in those areas
(21:32:45) megacoder: OK, I'll give Paul a bit more time since he
usually does that. If not, I will.
(21:32:52) quaid: all righty!
(21:33:01) quaid: yeah, Paul the Face Man :)
(21:33:20) quaid: and you are BA Barracus, I'm Hannibal Smith ...
(21:33:28) megacoder: He does claim to be the handsome one.
(21:33:28) quaid: anyway, moving on
(21:33:48) megacoder: Gotta pick a muldoon, though.
(21:34:16) quaid: nice segue, since I am about to reply to Chris Lennert
and accept his taking the ServerTools beat
(21:34:35) quaid: time is running toward test2
(21:34:38) quaid: we could use to fill our holes
(21:34:47) quaid:
http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats
(21:34:53) megacoder: I pity the fool that tries to... wait... drop it.
(21:35:51) quaid: Chris is added
(21:39:18) quaid: for the record, the open slots are:
(21:39:25) quaid: s/slots/beats/
(21:40:16) quaid: kernel, file systems (arguably part of kernel),
DevelTools, Samba, SystemDaemons, x86 specific content, x86_64 specific
content, database servers, backwards compat, and legacy
(21:40:25) quaid: time for more nagmails
(21:40:39) quaid: gregdek tells me that "automated guilt management" is
the way to go
(21:44:30) mether: quaid, legacy is different backwards compat?
(21:44:42) mether: quaid, does legacy mean fedora legacy?
(21:44:43) quaid: Legacy == Fedora Legacy Project ?
(21:44:47) quaid: not sure, I think so
(21:45:01) mether: ok do we need space for fedora extras then?
(21:45:02) quaid: unclear how that fits, I forget where it came form
(21:45:13) quaid: ah, yes, Extras would be a great beat
(21:45:23) mether: if its fedora legacy ask ender I guess
(21:45:47) quaid: ender can assign someone, perhaps
(21:45:50) mether: he or anyone in the legacy build team would be better
candidates
(21:46:30) mether: and I heard legacy repo is going to be included
enabled or disabled by default in FC5. so its fairly important.
(21:46:46) mether: and for extras post to the fedora-extras list
(21:46:59) mether: thl might be willing to do it
(21:47:19) quaid: I'm going to cross-post :)
(21:48:33) mether: I am not sure samba, database servers etc get notable
enough change for every release
(21:48:38) mether: to warrant a seperate beat for them
(21:49:15) elliss: I guess the main issues there are compatibility
breaks
(21:49:17) quaid: when there is content, it should come from somewhere
designated and not fall between the cracks
(21:49:22) mether: is the colophon going to be included within the
published release notes?
(21:49:31) quaid: should be
(21:49:40) quaid: did I miss that in the last one? probably did, huh
(21:49:57) mether: yes it has been missed out
(21:50:10) quaid: damn, that's right, it's only on the Wiki still
(21:50:17) quaid: I can kick that to XML, I suppose
(21:54:03) quaid: ok, nagmail being written
(21:56:04) quaid: anyone had any luck with contacting SelfIntro'd
people?
(21:57:32) elliss: Awaiting a response on one.
(21:57:51) ***quaid hasn't done any :)
(21:58:20) elliss: I'd like to encourage people to look at user docs
(21:58:31) quaid: I'll excuse myself, but if anyone wants to do as Paul
did, feel free to Cc: me into any conversation, if I can provide the
warm fuzzies from the @redhat.com side
(21:59:01) elliss: Good idea
(21:59:13) elliss: So I've pinged Matt Bird, who has been doing some
work on the Desktop User Guide
(21:59:43) quaid: yeah, cool, that's adding ideas
(21:59:58) elliss: And I'll write to few more people who've expressed an
interest in user docs
(22:00:13) quaid: yeah, it would be great to get Matt some help
(22:00:41) quaid: and it's certainly our most painful location
(22:01:20) mether: what about Andrew Hudson
(22:01:55) mether: Getting Started Guide hasnt got any updates for the
past 2 months or so
(22:02:17) elliss: mether: I wanted to talk to Matt first
(22:02:34) elliss: Before approaching a professional writer
(22:02:47) mether: ok
(22:03:33) elliss: Didn't want to sideline him
(22:08:09) elliss: That was all I was going to say :)
(22:08:21) quaid: that's cool, thanks
(22:08:30) quaid: that was a concern of mine, not sidelining no one
(22:08:48) quaid: one note, as we end
(22:09:01) quaid: we need to do some work on how to handle translation
of the wiki
(22:09:08) quaid: a streamlined process, as mether said
(22:10:20) quaid: something we need to discuss with nman64 and other
f-websites folks
(22:10:35) quaid: so, let's consider, work on ideas on list, etc.
(22:10:40) quaid: anything else?
(22:10:42) quaid: AOB?
(22:15:58) quaid: </meeting>

-- 

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


More information about the fedora-dsco-list mailing list