[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

IRC log 16 August 2005 meeting



catching up :)

Aug 16 13:03:21 <quaid>	<meeting>
Aug 16 13:03:24 -->	megacoder
(n=reynolds adsl-065-005-229-109 sip lft bellsouth net) has joined
#fedora-docs
Aug 16 13:03:25 <stickster>	G2: hi
Aug 16 13:03:33 <elliss>	hi stickster
Aug 16 13:03:41 <quaid>	hi elliss, megacoder, g2, stickster 
Aug 16 13:03:46 <stickster>	tcf: Hi
Aug 16 13:03:48 <quaid>	hi tcf, who was here already :)
Aug 16 13:03:51 <stickster>	oops
Aug 16 13:03:59 <megacoder>	hi
Aug 16 13:04:14 <tcf>	stickster: hi
Aug 16 13:04:20 <G2>	hi
Aug 16 13:04:23 <tcf>	hi quaid
Aug 16 13:04:24 <stickster>	We're such a friendly bunch
Aug 16 13:04:32 <quaid>	megacoder: did you say recently that you are
actually writing code these days?  I thought you were going to be stuck
in an evangelical role or sumethin'
Aug 16 13:04:35 <tcf>	I've been watching the clock all day to make sure
I didn't miss it this week
Aug 16 13:04:37 <quaid>	stickster: it's been so long!
Aug 16 13:04:43 <quaid>	tcf: heh, me too
Aug 16 13:05:00 <tcf>	quaid: I'm usually around, but the time just slips
my mind when I'm busy editing or something
Aug 16 13:05:08 <megacoder>	Writing (righting!) code in support of some
training classes.
Aug 16 13:05:20 <G2>	me too
Aug 16 13:05:36 <megacoder>	In addition to that, I just speak ex
cathedra.
Aug 16 13:05:46 <stickster>	I have to leave work early to make the
meeting, so that helps
Aug 16 13:06:11 <tcf>	stickster: good point
Aug 16 13:06:25 <quaid>	agenda was sent to the list
Aug 16 13:06:59 <stickster>	Did any docs stuff come up at LWCE as part
of Fedora BoF, etc.?
Aug 16 13:07:15 <quaid>	yeah, it was definitely discussed somewhat iin
the BoF
Aug 16 13:07:37 <quaid>	that started with lots of lame technical
questions, and I finally turned the tide by asking the room how the
community process was working for them.
Aug 16 13:07:44 <quaid>	we discussed mainly how to get involved, what
that means.
Aug 16 13:08:00 <quaid>	Uli was particularly hard-nosed about
contributing v. feature-requesting :)
Aug 16 13:08:25 <quaid>	within that, we discussed docs as being one of
the first places new FOSS contributors are pointed to, Uli at least
sends people our way
Aug 16 13:08:41 <quaid>	which brings in an interesting recruiting idea,
making sure the developers know where to send people ...
Aug 16 13:09:06 *	quaid makes an action note
Aug 16 13:09:47 <quaid>	I also discussed generic Linux documentation for
a while with Greg Kurtzer of cAos Linux.
Aug 16 13:10:16 <quaid>	he was surprisingly supportive of Red Hat with
the whole CentOS mess recently, and what we discussed was the idea of a
Linuxpedia that would have distro-generic documentation.
Aug 16 13:10:23 <quaid>	something we could all reference or pull from.
Aug 16 13:11:01 <quaid>	back at the booth, Spot suggested that was
nonsense, the distros are too far apart for that to work, and it would
be a bunch of hassle with all the Deb and Gentoo people wanting this and
that
Aug 16 13:11:48 <tcf>	isn't tldp supposed to be distro-generic?
Aug 16 13:11:51 <quaid>	so, we left it with Greg going to talk with
Debian folks and others, and I'm to talk with you all, and see what we
think.
Aug 16 13:11:56 <stickster>	The main problem I see is that all the
gentle intro admin tools in Fedora (system-config-*) are not to be found
in many distros, or there are very different interfaces (YaST)...
Aug 16 13:11:57 <quaid>	tcf: yes, exactly
Aug 16 13:12:06 <elliss>	CLI-only documentation might work - the GUI
stuff is definitely way too fragmented
Aug 16 13:12:15 <stickster>	elliss: there ya go
Aug 16 13:12:34 <stickster>	What about chkconfig, service, etc.?
Aug 16 13:12:37 <tcf>	elliss: exactly, generic term definition, command
line config would work
Aug 16 13:12:51 <megacoder>	cli! yes! If the machine is busted, how ya
gonna get X11 tools working?
Aug 16 13:12:53 <tcf>	but the "how to install" sections would be a mess
Aug 16 13:13:14 <G2>	What Centos mess?
Aug 16 13:13:31 <stickster>	G2: I think it was a trademark issue,
resolved eventually
Aug 16 13:13:40 <quaid>	G2: where RHAT asked CentOS to stop infringing
on trademarks, and instead of just fixing it, a whole stink was risen.
Aug 16 13:14:01 <G2>	ah
Aug 16 13:14:16 <G2>	I missed that in the press
Aug 16 13:14:37 <quaid>	however, what about best practices?
Aug 16 13:14:43 <G2>	We should can some idea together for FudCON london
Aug 16 13:14:53 <quaid>	and SYSV v. Berkeley style for config files,
service starting, etc.
Aug 16 13:15:05 <stickster>	quaid: My personal opinion is that Spot is
often wise
Aug 16 13:15:10 *	quaid nods
Aug 16 13:15:21 <megacoder>	define:spot
Aug 16 13:15:22 <quaid>	yeah, and he threw his water with some extra ice
in it, 'twas chilling.
Aug 16 13:15:30 <quaid>	megacoder: Tom 'spot' Callaway
Aug 16 13:15:47 <quaid>	troublemaker and ne'er do well
Aug 16 13:16:30 <megacoder>	(but spoken with reverence, no doubt)
Aug 16 13:16:35 <stickster>	no doubtr
Aug 16 13:16:43 <quaid>	well, it think that's how he'd describe himself.
Aug 16 13:17:27 <stickster>	I think we could probably all agree that
with the amount of time we have to spend on process figgering already,
the amount of work that we can really get done would plummet if we
suddenly had to negotiate the cross-distro minefield
Aug 16 13:17:42 <stickster>	I would say tcf is right, TLDP serves this
purpose already
Aug 16 13:18:14 <G2>	yeah. EVery distro has their own version
Aug 16 13:18:16 <megacoder>	Well, this _is_ the FEDORA project, after
all.
Aug 16 13:18:18 <stickster>	Er... if that's what tcf said :-)
Aug 16 13:18:28 <quaid>	I'll keep my ears open with Greg, see where it
goes ... idea was to help generate a useful pool, not create much more
work :)
Aug 16 13:18:44 <quaid>	ok, thanks, that was my major LWCE report for
docs
Aug 16 13:18:52 <quaid>	oh, we did have a Free Documentation BoF
Aug 16 13:19:05 <quaid>	conclusion that matters:  we are techies and
need to think for end users
Aug 16 13:19:16 <quaid>	which is a major theme these days in FP
Aug 16 13:19:17 <stickster>	If we could find out what our hundreds of
subscribers are up to, that would be a useful pool too! (and thanks
quaid for the delurkathon post)
Aug 16 13:19:45 <tcf>	stickster: yes, I said that ;-)
Aug 16 13:19:58 <stickster>	tcf: OK, didn't want to misquote you or put
words in your mouth
Aug 16 13:20:52 <tcf>	stickster: although I have seen a few distro-
specific guides in tldp
Aug 16 13:21:05 <tcf>	stickster: but as a whole, seems like it is
supposed to be distro-neutral
Aug 16 13:21:28 <tcf>	it is a bit of a shame that there is duplication
of effort between distros
Aug 16 13:21:48 <tcf>	if we could somehow have "generic" content the
specific distro-docs could build from, that would be ideal
Aug 16 13:22:03 <tcf>	kind of like everyone builds from the generic
kernel to build a distro
Aug 16 13:22:06 <elliss>	We do...at the application level
Aug 16 13:22:12 *	tcf keeps dreaming
Aug 16 13:22:23 <StillBob>	doing things "the Fedora/RedHat way" is fine
but there are times when knowing the "real way" is nice, if the docs can
cover that I think it would be a good idea
Aug 16 13:22:24 <tcf>	elliss: right, so why not apply that to docs?
Aug 16 13:22:31 <quaid>	I think one point of this discussion with Greg
was to do it as a Wiki, harnessing the larger # of contributors.
Aug 16 13:22:37 <tcf>	docbook as the ability to create modular docs
Aug 16 13:22:55 <quaid>	Rick Moen pointed out how blindingly easy it is
to get a doc into TLDP, but people don't do it.
Aug 16 13:22:59 <elliss>	tcf: I meant that Samba etc. already ship
content good for all distros
Aug 16 13:23:17 <elliss>	But much of the UI is distro-specific
Aug 16 13:23:25 <tcf>	elliss: oh, right, I see what you are saying
Aug 16 13:23:27 <tcf>	elliss: that is true
Aug 16 13:23:44 *	megacoder attempts to return to reality
Aug 16 13:24:00 <megacoder>	Does this mean that we are adequately
covered on the Fedora-centric documents?
Aug 16 13:24:17 <megacoder>	Focus, focus, focus
Aug 16 13:24:58 <nman64>	There are certainly areas where generic docs
are possible, but most docs would require so many changes for each
distro that it wouldn't be worth creating generic docs.
Aug 16 13:25:07 <stickster>	Ack, there's that Wiki word again
Aug 16 13:25:21 <quaid>	nman64: that was the summary of spot's point, I
think
Aug 16 13:25:35 <quaid>	ok, let's table this for now, I'll let you all
know what develops
Aug 16 13:26:01 <stickster>	tidy-bowl up next
Aug 16 13:26:10 <quaid>	what do you think about it?
Aug 16 13:26:42 <elliss>	No problems to report, here :)
Aug 16 13:26:43 <stickster>	It's ready as far as I can tell... The
xmlformat-fdp.conf file has (AFAICT, again) all of our often-used
tags...
Aug 16 13:27:01 <G2>	I think I need to check out the latest fedora-docs
tree
Aug 16 13:27:08 <stickster>	G2: a must
Aug 16 13:27:20 <quaid>	esp. since it's no longer the fedora-docs
tree :)
Aug 16 13:27:33 *	quaid gets all semantical about CVS modules
Aug 16 13:27:44 <G2>	remind me, it's been while
Aug 16 13:27:44 <quaid>	;-D
Aug 16 13:28:03 <quaid>	G2: just that all of the docs have their own
modules at the top of /cvs/docs
Aug 16 13:28:13 <quaid>	cvs co -c reveals all
Aug 16 13:28:42 <stickster>	megacoder: Do you have a problem with having
one extra flag in tidy-bowl?
Aug 16 13:28:47 <quaid>	stickster: can you or megacoder put together a
short how-to for us dummies, and we can include that as part of the
example-tutorial if need be.
Aug 16 13:29:00 <megacoder>	what flag?
Aug 16 13:29:13 <G2>	quaid: Very funny ;-) You should see my terminal
now!!!!
Aug 16 13:29:20 <stickster>	megacoder: a "-n" to *not* change the doc in
place... to be used manually by individuals as needed
Aug 16 13:30:10 <quaid>	so it's like a test output?
Aug 16 13:30:18 <stickster>	Right, to stdout only
Aug 16 13:30:20 <megacoder>	Why would you wanna filter without a backup
anyway.
Aug 16 13:31:26 <stickster>	Sorry, I'm not grokking your syntax
Aug 16 13:31:34 <quaid>	does that mean ... we should have an auto-
backup?
Aug 16 13:31:35 <G2>	what's the main module name again?
Aug 16 13:31:40 <megacoder>	We could add the flag, but heaven help us if
it ever gets activated during a CVS checkin
Aug 16 13:31:55 <stickster>	It shouldn't unless the CVSROOT/commitinfo
file suddenly changed
Aug 16 13:32:12 <stickster>	Which is only edited by the people in this
room... hmmm...
Aug 16 13:32:18 *	stickster strokes nonexistent beard
Aug 16 13:32:32 <megacoder>	But I'll do it if Sopwith doesn't object.
Aug 16 13:32:55 <megacoder>	After all, in the wrong hands it could wreck
havoc on his server
Aug 16 13:33:00 <stickster>	Err... huh?
Aug 16 13:33:18 <G2>	can't find the name on the wiki
Aug 16 13:34:01 <quaid>	G2: cvs.fedora.redhat.com:/cvs/docs
Aug 16 13:34:30 <quaid>
CVSROOT=:ext:ghenry cvs fedora redhat com:/cvs/docs
Aug 16 13:34:33 <nman64>	G2: http://cvs.fedora.redhat.com/docs.shtml
Aug 16 13:34:35 <G2>	found it on the main site. I need to pull my finger
out cand get up to date.
Aug 16 13:34:50 <quaid>	megacoder: I also don't understand
Aug 16 13:35:47 <megacoder>	If this '-n' gets triggered somehow, the
reformatted document will be blasted to stdout; I'm not sure how happy
the CVS server is gonna be about that.
Aug 16 13:36:30 <stickster>	Yeah, but it can only be triggered if one of
us suddenly decided in a fit of insanity to change the
CVSROOT/commitinfo to do that... 
Aug 16 13:36:49 <quaid>	side question, does every module that receives
tidy-bowl treatment need to be listed in CVSROOT/commitinfo?
Aug 16 13:37:02 <stickster>	The reason it would be there is so Joe
Contributor can type "/path2docs/docs-common/bin/tidy-bowl -n mydoc" to
see what it will look like
Aug 16 13:37:17 <stickster>	quaid: It can be another DEFAULT rule as far
as I can tell
Aug 16 13:37:25 <megacoder>	The point I was really making was that
before editing the script, I'd like Sopwith to agree; just protocol
Aug 16 13:37:34 <quaid>	ok, then it's relative to $CVSROOT
Aug 16 13:37:47 <stickster>	np with that here... I just think it's not a
really big risk
Aug 16 13:38:06 <quaid>	megacoder: can you write up the patch and run it
by sopwith?
Aug 16 13:38:23 <quaid>	stickster: can you take the job of resurrecting
the how-to details for this?
Aug 16 13:38:31 <quaid>	then we can pull ye olde trigger soonest
Aug 16 13:38:31 <stickster>	Yes
Aug 16 13:38:45 <megacoder>	Hm... this feature already exists with the
"-t tool-args" switch, so it can't be that much more dangerous. OK, I'll
do it.
Aug 16 13:38:50 <quaid>	this will happen automatically, we need to warn
people, "On your next commit this will happen" right?
Aug 16 13:39:01 <stickster>	megacoder: right, this one would just strip
the "-i" option
Aug 16 13:39:11 <quaid>	tidy-bowl needs a man page!
Aug 16 13:40:08 <stickster>	megacoder: I just mailed you a diff
Aug 16 13:40:23 <megacoder>	too late; I'm committing as we speak
Aug 16 13:40:24 <stickster>	quaid: Yes, this should come with a warning
to f-docs-l
Aug 16 13:40:27 <stickster>	megacoder: Ha!
Aug 16 13:40:34 <stickster>	Too efficient for your own good
Aug 16 13:40:39 <quaid>	hoo-ha!
Aug 16 13:41:09 <quaid>	ok, you two roll with that, activity in CVS
isn't so crazy that you can't just define a window and make it happen.
Aug 16 13:41:41 <quaid>	on to next fun topic
Aug 16 13:42:01 <quaid>	I'm considering tabling recruiting, or moving it
to the mailing list, because I want to discuss mentoring.
Aug 16 13:42:02 <megacoder>	wait! wait! Where do I send the man page?
Aug 16 13:42:06 <quaid>	oh, sorry
Aug 16 13:42:29 <quaid>	megacoder: I think it's time you or Paul
considered packaging it for Extras :)
Aug 16 13:42:59 <quaid>	otherwise, docs-common/docs/ ?
Aug 16 13:43:08 <stickster>	Problem is xmlformat license
Aug 16 13:43:11 <quaid>	oh, right
Aug 16 13:43:15 <quaid>	was that never resolved?
Aug 16 13:43:18 <stickster>	Why not just put tidy-bowl stuff in
docguide?
Aug 16 13:43:30 <megacoder>	OK, that'll take me a bit, I'm absolutely
snowed in me real work.  Gimme a couple of hours...
Aug 16 13:43:31 <stickster>	quaid: Resolution was, OK to use, not easy
to get in Extras
Aug 16 13:43:39 <quaid>	yes, that's the right place, but meanwhile, we
can have a man page in docs-common/docs
Aug 16 13:43:49 *	megacoder dumps idea of an RPM
Aug 16 13:43:51 <stickster>	sho nuff
Aug 16 13:44:20 <quaid>	ok, we'll see ... xmlformat is getting popular,
maybe someone will pursue getting the problems resolved upstream.
Aug 16 13:44:27 <quaid>	ready to move on?
Aug 16 13:44:29 <stickster>	yup
Aug 16 13:44:41 <megacoder>	fer sure
Aug 16 13:45:04 <quaid>	I am moving to table recruiting and take it to
the list as an ongoing discussions ... it was sort of a carryover from
before ... mainly because I want to discuss mentoring with our time
left.
Aug 16 13:45:38 <quaid>	s/am moving/move/
Aug 16 13:45:44 <G2>	Checkout all my fav modules. I have been slow.
Aug 16 13:45:58 <quaid>	G2: cool, eh? :)
Aug 16 13:46:06 <elliss>	Quaid: Are the two separable, though ? 
Aug 16 13:46:13 <quaid>	G2: like a real project now
Aug 16 13:46:15 <G2>	Very.
Aug 16 13:46:18 <G2>	cvs co owners install-guide securing-filesystems
scripts proxy-guide hardening developer-guide
Aug 16 13:46:28 <G2>	this is what I got plus docs-common.
Aug 16 13:46:33 <G2>	We have been busy.
Aug 16 13:46:48 <quaid>	elliss: no, not really, but I guess mentoring is
a subset with a dotted-line to other areas.
Aug 16 13:46:57 <G2>	WE are missing LDAP and IPSEC. Samba, Postgresql,
and others.
Aug 16 13:47:01 <G2>	s/WE/we
Aug 16 13:47:12 <G2>	best get finishing an d writing
Aug 16 13:47:12 <StillBob>	Mentoring, stickster agreed to be my mentor
at the last meeting, I hope to get my first round of questions out to
him via the list tonight. 
Aug 16 13:47:31 <quaid>	any objections to moving to mentoring for
discussion?
Aug 16 13:47:38 <G2>	nope.
Aug 16 13:47:39 <stickster>	G2: I usually just "cvs co ." and get the
whole docs shebang
Aug 16 13:47:45 <tcf>	quaid: nope
Aug 16 13:47:48 <nman64>	n
Aug 16 13:47:48 <quaid>	ok
Aug 16 13:47:55 <quaid>	this came up at the Fedora BoF last week
Aug 16 13:47:57 <G2>	Just got my 1MB ADSL upgraded to 2MB for free
Aug 16 13:48:00 <G2>	ok
Aug 16 13:48:01 <stickster>	StillBob: Sweet! Thanks
Aug 16 13:48:03 <quaid>	much enthusiasm for the idea of mentoring
Aug 16 13:48:04 <G2>	stickster: cheers
Aug 16 13:48:14 <quaid>	Rahul (mether) has put up some resources, etc.
Aug 16 13:48:40 <stickster>	I put my name up on the list, esp. for docs
stuff but also generic things
Aug 16 13:48:59 <G2>	quaid: on the wiki
Aug 16 13:49:04 <quaid>	the idea seems to be, a person who can help new
people navigate into the project.  Contributors, mainly
Aug 16 13:49:56 <quaid>	http://fedoraproject.org/wiki/Mentors
Aug 16 13:50:31 <quaid>	I was going to suggest we connect that together
with contacting people who had self-intro'd
Aug 16 13:50:44 <quaid>	i.e., offer to be those people's mentors
Aug 16 13:51:24 <elliss>	Not sure about this
Aug 16 13:51:43 <nman64>	I've gotten many of the 'getting started' style
wiki pages thoroughly interconnected.  They'll probably see the mentors
page long before they introduce themselves.
Aug 16 13:51:54 <elliss>	I suspect many don't have a project in mind
Aug 16 13:51:56 <stickster>	Keeping in mind for docs stuff -- wherever
possible, coax the mentored to be mentored on-list so others benefit
Aug 16 13:52:06 <quaid>	ok
Aug 16 13:52:28 <quaid>	elliss: hard to know what they are experiecing,
since they are so quiet
Aug 16 13:52:49 <stickster>	Thus the delurkification post
Aug 16 13:53:10 <quaid>	which promptly got discarded as spam
Aug 16 13:53:13 <quaid>	because of the subject
Aug 16 13:53:15 <stickster>	?
Aug 16 13:53:18 <stickster>	Haa!
Aug 16 13:53:37 <quaid>	stickster: sorry, ignacio|NotHere came by last
night and teased me because he almost discarded my email because of the
subject line "this is for you" :D
Aug 16 13:53:41 <nman64>	Yeah, it was a bit too spam-ish.  Saw your name
and knew it was okay.
Aug 16 13:53:57 <quaid>	nman64: just my kind of sideways humor
Aug 16 13:54:23 <quaid>	it's the kind of provactive subject that USED to
work before spam was prevalent
Aug 16 13:54:39 <stickster>	quaid: Wow, why not just use Re: Bored in
bed?
Aug 16 13:54:51 *	stickster just lost us our PG rating, sorry
Aug 16 13:54:58 <StillBob>	lol
Aug 16 13:54:59 <megacoder>	Yeah, any Subject: with "You" is probably
spam.
Aug 16 13:55:00 <quaid>	stickster: we had a PG rating?
Aug 16 13:55:05 <stickster>	PG-13
Aug 16 13:55:13 <quaid>	f3d0r@ for you
Aug 16 13:55:19 <stickster>	LOL
Aug 16 13:55:33 <nman64>	'This is for her.' would have been much worse.
Aug 16 13:55:34 <tcf>	quaid: well, there are a few kids around the
keyboard at the meetings
Aug 16 13:55:35 <megacoder>	How about "Why are you lurking on the
Document Project"
Aug 16 13:55:37 <stickster>	all right... so, we hope people see that
post and speak up... I think Bob's questions will help too
Aug 16 13:55:39 <tcf>	quaid: don't think they can read yet though
Aug 16 13:56:05 <stickster>	tcf: Sorry, will keep sly entendres to a
minimum (some would say zero so far)
Aug 16 13:56:06 <megacoder>	I know! I know! "Get your mommy to read this
email to you!"
Aug 16 13:56:08 <quaid>	tcf: working on it over here :)
Aug 16 13:56:31 <stickster>	megacoder: I like the first one
Aug 16 13:56:33 <quaid>	how about this:
Aug 16 13:56:47 <quaid>	* If you have time to mentor, add your name at
http://fedoraproject.org/wiki/Mentors
Aug 16 13:56:51 <quaid>	... or don't ...
Aug 16 13:57:12 <quaid>	* If you want to mentor, you can pick up a name
from http://fedoraproject.org/wiki/DocsProject/Contributors to contact
Aug 16 13:57:23 <StillBob>	If you don't know where to start...speak up
Aug 16 13:57:27 <stickster>	"Kids! Grow giant mushrooms in YOUR cellar!"
Aug 16 13:57:28 *	nman64 likes megacoder's first suggestion.  Let's them
know where it's coming from, in case they've forgotten about us.
Aug 16 13:57:34 <quaid>	just Cc: the initial contact email to f-dsco-l
so we don't double-up
Aug 16 13:58:02 <quaid>	nman64: yeah, the straight approach would have
been a better catch
Aug 16 13:58:10 <stickster>	quaid: OK, so we should be doing this 1-on-1
with the S-I people we have already?
Aug 16 13:58:14 <elliss>	BCC may be better 
Aug 16 13:58:46 <elliss>	Visible CC to an offficial committee may look
odd
Aug 16 13:58:50 <stickster>	elliss: Problem with bcc is there's a sneaky
factor; cc lets people get the lay of the land
Aug 16 13:59:00 <stickster>	Open == open
Aug 16 13:59:27 <elliss>	OK, but it may be worth saying why an official
committee is being CC'd in
Aug 16 13:59:33 <stickster>	elliss: Absolutely
Aug 16 13:59:53 <quaid>	yes, 
Aug 16 14:00:26 <quaid>	it'd be cool to specify who you are mentoring on
the Contributors or Mentors page, but it needs to be accepted first.
Aug 16 14:00:28 <quaid>	alternately
Aug 16 14:00:28 <stickster>	At bottom: "FDSCo members were asked to
contact people on the self-introduction list as part of their official
duties. A copy of this letter is going to f-dsco-l to record action"
Aug 16 14:00:38 <quaid>	we could just send a separate email to the list
to let us know what's up.
Aug 16 14:00:56 <StillBob>	talking about us behind our back?
Aug 16 14:00:56 <quaid>	but I like the two-birds approach :)
Aug 16 14:00:59 <StillBob>	LOL
Aug 16 14:01:59 <elliss>	It has to look personal, I think
Aug 16 14:02:06 <stickster>	Everyone who contacts folks on the
http://fedoraproject.org/wiki/DocsProject/SelfIntroduction page should
mark that name as "contacted by XXX on MM/DD/YY"
Aug 16 14:02:25 <quaid>	s/SelfIntroduction/Contributors/
Aug 16 14:02:30 <stickster>	Oh yeah, sorry
Aug 16 14:02:32 <stickster>	:-)
Aug 16 14:02:39 <quaid>	elliss: +1
Aug 16 14:02:49 <G2>	Yeah. We've not heard much from people on that
Aug 16 14:03:00 <elliss>	Nowt, in fact
Aug 16 14:03:19 <elliss>	They may be waiting on us to announce something
- I don't know
Aug 16 14:03:22 <quaid>	how about, "I Cc:'d the docs project committee
so we can keep track of who we each contact.:
Aug 16 14:03:37 <stickster>	quaid: thank you, that's what I meant :-)
Aug 16 14:03:48 <elliss>	If you have to CC, then yeah
Aug 16 14:04:13 <elliss>	But CC means "for official record" in many
cases
Aug 16 14:04:14 <stickster>	Great, so action item for this is -- let's
get busy contacting people on the list... right?
Aug 16 14:04:16 <quaid>	elliss: I thought about Bcc:, but it is a public
archive
Aug 16 14:04:30 <quaid>	elliss: if you prefer, just send a separate note
to the list so we know who contacted whom, that's the real point.
Aug 16 14:04:38 <quaid>	stickster: right
Aug 16 14:04:46 <quaid>	I am putting these how-to details in the minutes
Aug 16 14:04:52 <stickster>	sweet
Aug 16 14:05:51 <G2>	If you can't be bothered updating the Contributors
page for contact time, BCC me on it and I'll do it.
Aug 16 14:05:58 <stickster>	G2: attaboy
Aug 16 14:06:27 <quaid>	and that brings us to ... any more recruting?  
Aug 16 14:06:39 <quaid>	re-cutting
Aug 16 14:06:42 <quaid>	and AOB'
Aug 16 14:07:20 <elliss>	I think recruiting stuff is best on-list 
Aug 16 14:07:38 <elliss>	Because it's kind of fruitless without the
feedback
Aug 16 14:07:52 <quaid>	'zactly true
Aug 16 14:08:24 <G2>	Well, that' sme. Chat tomorrow.
Aug 16 14:08:45 <elliss>	Night.
Aug 16 14:08:49 <stickster>	G2: night
Aug 16 14:08:52 <tcf>	glad to see so many people show up for this
meeting (the reminder helped me)
Aug 16 14:08:57 <tcf>	good night everyone
Aug 16 14:09:04 <elliss>	night
Aug 16 14:09:07 <stickster>	tcf: G'night and bye
Aug 16 14:09:16 <quaid>	yeah, I need to get the agenda out the night
before
Aug 16 14:09:16 <megacoder>	so long until tomorrow
Aug 16 14:09:17 <quaid>	ciao
Aug 16 14:09:22 <quaid>	</meeting>
-- 
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/

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]