QA/Meetings/20130422

Attendees

• adamw (94)
• dan408 (40)
• tflink (23)
• kparal (22)
• j_dulaney (14)
• jreznik (14)
• pjones (6)
• zodbot (4)
• brunowolff (3)
• nirik (2)
• satellit_e (2)
• martix (1)
• j_dulane1 (1)
• mkrizek (1)
• Southern_Gentlem (1)
• pschindl (1)

Agenda

• Previous meeting follow-up
• Fedora 19 Alpha status/recap
• Beta release criteria
• Test Days
• Open floor

Previous meeting follow-up

• adamw to send out another call for UEFI testing with TC6 - this was done, and we got a good amount of UEFI testing before go/no-go
• jreznik to follow up on status of Translations (l10n) test day- jreznik did so, and the event went off well

Fedora 19 Alpha recap

• Alpha was signed off and ready to go
• adamw created and populated the Common_F19_bugs page
• kparal noted the tracker bug aliases are kind of long at present (kparal); adamw explained the old-style aliases are only going to be used for F19 as a 'backwards compatibility' measure, from F20 onwards bugs will have only the new-style aliases
• There was a vote of thanks to all Alpha testers

Beta planning

• anaconda recently revised how containers (LVM, btrfs) are handled in custom partitioning: we will get some images to do some testing of those changes shortly
• The first blocker review meeting was scheduled for 04-24, Beta TC1 for 04-30
• The new-style Beta release criteria still needed to be finished off

Test Days

• Test_Day:2013-04-17_Power_Management went ahead successfully: the power management team blogged about it
• FreeIPA test day seems to have gone ahead and produced useful results
• martix was working on graphics test week preparation, adamw would help out with publicity

Open floor

• tflink reported that the blocker bug proposal webapp should go into production during the week

Action items

• adamw to complete Beta criteria update
• adamw to add iscsi test case back to the matrix

IRC Log

randomuser	#startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings	14:00
zodbot	Meeting started Mon Apr 22 14:00:40 2013 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.	14:00
zodbot	Useful Commands: #action #agreed #halp #info #idea #link #topic.	14:00
randomuser	#meetingname Fedora Docs	14:00
zodbot	The meeting name has been set to 'fedora_docs'	14:00
randomuser	#topic Roll Call	14:00
* Capesteve is here		14:01
randomuser	good morning to those it applies to	14:01
randomuser	and hello to the others :)	14:02
Capesteve	Good morning	14:02
Capesteve	GDTY covers all	14:02
* randomuser nods		14:02
randomuser	i've heard that one... it seems so generic	14:02
jjmcd		14:03
Capesteve	from the days of Telex	14:03
* pkovar is here		14:03
randomuser	i see bcotton lurking	14:05
randomuser	Sparks, Sparks_t1o , are you here?	14:05
* bcotton is here		14:05
* jjmcd is working a widespread flooding incident - only partly paying attention		14:05
randomuser	thanks for turning out, jjmcd	14:07
randomuser	#topic follow up on action items	14:07
randomuser	one item here - I was to mail the list about using bugs to track Changes	14:07
randomuser	which I did - it seems like a good place to start discussion	14:07
randomuser	#topic Using Bugzilla to track Changes	14:08
randomuser	The idea is to give us, and other groups, a centralized way to track rthe Changes process. bugzilla appears to be the best tool we have in production to do this.	14:08
randomuser	Any thoughts? unnecessary work, or wonderful idea?	14:09
randomuser	Capesteve, pkovar how do you guys track your upcoming work?	14:11
Capesteve	bugzilla mostly	14:11
Capesteve	more and more using bugzilla	14:11
randomuser	tracking bugs / assignments as much as user-driven reports, then?	14:12
pkovar	tracking bugs, yes	14:12
Capesteve	Some planing was done in using other tools, but we turn our tasks into bugs	14:13
randomuser	does it seem effective? any obvious pitfalls to it?	14:13
Capesteve	brain storming, wish lists can be done in a collab tool of choice, but distill the action items into bugs	14:14
randomuser	i like that idea, but out scale doesn't really require it for general use	14:15
randomuser	s/out/our	14:15
Capesteve	I think etherpad for a week or so, then store the agreed action in a wiki page might be enough for you	14:16
* randomuser nods		14:16
Capesteve	but don't use wiki for things that change a lot	14:16
randomuser	there probably is a wiki page, somewhere, we could use	14:16
Capesteve	wait till you agree its at "1st draft" stage	14:17
pkovar	it looks like etherpard is not used that much in fedora.. for some reason. is there a fedora instance of etherpad somewhere?	14:18
randomuser	we have a gobby instance, though it doesn't get much use	14:18
randomuser	at least not by docs people	14:18
pkovar	aha	14:18
pkovar	ah, i see it's a desktop app	14:19
randomuser	I've only used it a couple times	14:20
pkovar	a web app works better for this purpose i think	14:20
randomuser	yeah, the barrier to use would be less	14:20
randomuser	with etherpad, you can just share a link	14:21
* randomuser isn't seeing any reason not to use BZ for tracking Changes		14:21
randomuser	#topic Beat Assignments	14:23
randomuser	#link https://fedoraproject.org/wiki/Category:Documentation_beats	14:23
randomuser	Beats are still open	14:23
randomuser	people are working on them, i see	14:24
randomuser	i've been doing some research on the unclaimed ones, it's a daunting task	14:24
randomuser	...	14:25
randomuser	#topic Search for fp.o	14:26
jjmcd	Is there a Tech Notes available?	14:26
randomuser	jjmcd, not at this point, but I could spin one up today	14:27
jjmcd	I plan to hit embedded, circuits, etc. But I could use other tools	14:27
jjmcd	Tech notes makes it easier, tho	14:27
randomuser	sure, I'll take care of that this evening	14:28
jjmcd	thanks	14:28
randomuser	jjmcd, I'm more willing to do things like that than I am likely to remember what needs to be done :P	14:28
jjmcd	I resemble that!	14:28
* randomuser smirks		14:29
randomuser	nirik, are you around to talk about search stuffs?	14:29
nirik	I'm here (barely), but don't have much news to report on that...	14:29
randomuser	fair enough, thanks	14:29
* randomuser slides a mug of coffee over to nirik		14:29
randomuser	hmm.. the author representation in the brand could use some more list time, i think	14:30
randomuser	pkovar, would you like to talk about the user guide?	14:31
pkovar	randomuser: ok	14:31
randomuser	#topic retiring the user guide	14:31
pkovar	i think we got mostly positive feedback	14:31
nb	+1	14:31
pkovar	on retiring the guide	14:31
* Sparks is here		14:32
pkovar	that is: closing the bugs	14:32
pkovar	and	14:32
pkovar	updating the guide table	14:32
randomuser	I'm +1 for this	14:33
pkovar	(and point people to DE's user help when appropriate)	14:33
randomuser	expecially with gnome-initial-setup	14:33
pkovar	right	14:33
randomuser	pkovar, are you planning on handling the bugs?	14:34
pkovar	randomuser: yes, i will close them (all) :)	14:34
randomuser	pkovar, cool, thanks. Keep an eye out for bugs that might conceivably apply to guides we *do* maintain, please	14:35
pkovar	sure	14:35
randomuser	Sparks, hello, do have anything for us?	14:36
randomuser	#chair Sparks	14:36
zodbot	Current chairs: Sparks randomuser	14:36
randomuser	we'll touch on bugs in the meantime	14:37
randomuser	#topic outstanding BZ tickets	14:37
randomuser	http://tinyurl.com/lbrq84	14:38
randomuser	we have some bugs	14:38
randomuser	any of concern?	14:38
Sparks	.	14:41
Sparks	I know of an easy way to close all the user-guide bugs if you'd like me to do so	14:41
pkovar	me too :-)	14:41
Sparks	pkovar: Okay, just checking	14:42
randomuser	heh, glad I didn't volunteer for it, then	14:42
kushal	Sparks, may be a python script	14:42
Sparks	No, bugzilla lets you modify multiple bugs at once	14:42
Sparks	kushal: Make it do the work for you	14:42
randomuser	#topic Open Floor	14:44
randomuser	alright, folks, go nuts	14:44
randomuser	I'm sure there's something I've forgotten	14:44
jreznik	ops, /me missed docs meeting :( sorry guys	14:46
randomuser	jreznik, the floor is yours, if you have anything	14:46
jreznik	randomuser: just re-read the tracking part - do you have a plan how to proceed?	14:47
jreznik	for alpha - anything still needed from docs? I see release notes now links to announcement, I'd say it makes sense	14:47
randomuser	jreznik, I'm thinking that when the time comes, we assign someone to create bugs for each Change and wrangle writers for them	14:48
randomuser	I'm not sure what else we need to plan in that context	14:49
randomuser	jreznik, I don't have much ready for alpha, regrettably, but I don't see why that should hold anything up	14:50
jreznik	seems reasonable, the same I do for devels and I can help you too with wrangling docs (just I don't have an overview of who to assign what but ... definitely I'm here)	14:50
randomuser	jreznik, we can use the beats table as a rough guide, but it might be best to ask for volunteers	14:51
randomuser	at least until we ease people into the idea of checking for bugs assigned to them	14:52
jreznik	beats owner + asking people if they are willing to do it is probably the best thing - at least for beginning	14:52
jreznik	thank you very much randomuser, I think docs are pretty well covered - I'd like to start as soon as possible, now to make marketing meeting today and ;-)	14:53
* randomuser nods		14:54
randomuser	You're an excellent wrangler, jreznik, thanks for your help	14:54
* randomuser really benefits from the occasional prodding		14:55
randomuser	just a few minutes left, last call on the open floor	14:55
randomuser	thanks for coming, everyone!	14:59
randomuser	#endmeeting	14:59

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!