Speech Transcript - Extreme containment measures: keeping your bug reports under control

0:00:10	this is a talk on extreme containment measures
0:00:13	phone and language will be might be used for those who don't know me an
0:00:18	example so i mean i don't know how like and i've been involved in one
0:00:22	way or another since roughly two thousand and five
0:00:25	and obviously with my first touch points for the gnome community have in panic no
0:00:31	and buttons it up i spend a lot of time filing and three icing bugs
0:00:39	and my character has level to well level reach the whole forty three in the
0:00:44	massively multiplayer online knowing that is complex a lot so in this talk i'm going
0:00:50	to present my analyses of the big issues that we face
0:00:55	and proposed methodology and a set of recommendations to solve these issues
0:01:02	i have some rather strong opinions and of course those are just my suggestions so
0:01:08	if you think that what i'm saying is completely evil well then feel free to
0:01:14	rage against my medical is an and i'd the talk is pretty going to be
0:01:18	rather short so we should have plenty of time to discuss in the
0:01:25	i would like to have a big debate at the end if i don't have
0:01:28	some kind of reaction i probably failed and then we just have to go to
0:01:33	the beach or something but well way there's no beach here
0:01:37	so
0:01:38	i have some assumptions that some of you might already have seen some of this
0:01:44	stuff that i wrote set couple months ago
0:01:49	but it's really if you want to know where mike kind of philosophy comes from
0:01:54	a summary of mine ways of thinking i have been strongly influenced by the mythologies
0:01:59	like getting things done or involve zero which is basically just getting things done but
0:02:04	apply to an e-mail really so if you haven't read those things i highly recommend
0:02:10	then in if you're the kind of person who likes to be organised
0:02:17	and
0:02:18	so
0:02:19	all based on actually
0:02:22	the sound doesn't work a
0:02:26	so it doesn't matter anyway so those books are interesting and everything but if you
0:02:30	really think about it
0:02:32	the core essence has always been about what's been going on in the world of
0:02:35	manufacturing for the last
0:02:37	thirty years so
0:02:40	lean and just in time manufacturing is it's a fascinating concept and
0:02:46	well i was doing studies in management
0:02:49	i started thinking about those things and how they applied pretty much everything we do
0:02:55	in life
0:02:56	from your personal to do this to managing a candy factory to managing a software
0:03:02	development project
0:03:04	so
0:03:05	and when you think about it everything is about slow
0:03:09	about good and adapting to change so you have something close in and you have
0:03:15	stuff that those out and you want this to be constant and so it and
0:03:20	and you want to avoid committing stuff because as soon as you have to make
0:03:23	stuff well things will below i can guarantee and
0:03:28	and there's this interesting thing from one of the books i've mentioned previously is the
0:03:34	only keeping that you should be retained from in the gold writes a book
0:03:38	in the context of but management is this
0:03:42	excess invent three is the liability it's not an asset
0:03:46	and
0:03:47	in that in the manufacturing world actually that means the stuff that you have produced
0:03:52	and now you think well okay wait that's just wrong the product is work something
0:03:58	right we're gonna sell it and then so it's and it's not set
0:04:01	it's natural to think that way
0:04:05	except that you don't know the market constraints until useful that you're not selling it
0:04:10	me immediately if you were you wouldn't be in the inventor E you will you
0:04:15	would you would just be selling it and making a profit
0:04:18	and so what this means is that is stuff that just sits around until it
0:04:24	might be sold
0:04:26	and then it devalues it waste this resources and it clogs up the system
0:04:32	so
0:04:33	in our context
0:04:35	that means connective wait
0:04:38	and
0:04:39	that's a concept that i took from getting things know that don
0:04:44	and
0:04:47	you think things know miss we can also that by the weights
0:04:51	so it's is it translates to wasted time searching for existing but reports split attention
0:04:58	on duplicates wasted energy looking for well it's good same bugs that were kept open
0:05:05	or because we were close to soon and
0:05:09	it all it's also feels like an incorrect indication of the quality of your software
0:05:15	and
0:05:16	we have a problem here
0:05:19	we are accumulating excess eventually
0:05:22	lots of it
0:05:23	and fast
0:05:25	and it's slowing us down
0:05:27	of course pretty much every project out there has this problem
0:05:31	and you to the fact that you know is such a large ecosystem
0:05:36	of this can ecosystem projects that have been going on for over fifteen years
0:05:42	well we and we don't have unlimited the mat time and manpower
0:05:48	the consequences is just going exponential
0:05:52	so allow non you're thinking well okay maybe is just exaggerating
0:05:56	so let me show you the problem we have in a very concrete way
0:06:02	this is the global amount of open but report thinking on since the beginning
0:06:07	i'm actually and missing data between two thousand and one or two thousand and five
0:06:11	but i'm pretty sure the amount of focus has not drastically going down during that
0:06:16	period so i just put some random guy on a bike right
0:06:20	feel the whole
0:06:22	so that's
0:06:23	forty five thousand bug reports that we have open right now and i'd argue that
0:06:30	this is not sustainable this stuff is often times so old and they see that
0:06:36	doesn't even represent to real amount bugs that users experience
0:06:41	so let me this is with it this way i don't know the but you
0:06:44	but
0:06:45	i as a user
0:06:48	if i was feeling the weight of forty five thousand bucks
0:06:53	every day
0:06:54	i wouldn't be using the computer that's all i would probably be crying in a
0:06:58	corner
0:07:00	and
0:07:01	so
0:07:03	well who's responsible for this would we point fingers to well pretty much everybody to
0:07:08	some extent
0:07:09	it's really easy to let things
0:07:12	slipped and rest of the time
0:07:15	and so i'm going to show you some examples and those are not meant to
0:07:20	be
0:07:21	finger pointing or anything like that they are just meant to in the illustrates how
0:07:25	different projects
0:07:27	and all their bug infantry differently
0:07:29	and well i think it's quite interesting really
0:07:35	so
0:07:37	first case it is really
0:07:40	it was fairly nice the under control is a can see and then the port
0:07:44	to webcat happened
0:07:48	and many things changed including the apps branding and positioning
0:07:53	because now epiphany is
0:07:56	this really mean stripped down a way more than it was before so that's
0:08:03	a different positioning you don't have the same kind of features that want to deal
0:08:08	with
0:08:09	and well we can infer that the green bugs were filed by the developers right
0:08:15	from the start because they were
0:08:17	that is new which means conferencing you know
0:08:20	and we see that we got the that green curve gradually declining in importance in
0:08:26	the past few years
0:08:28	but not that much
0:08:30	so well gradually declining
0:08:33	in absolute terms so some of those very old bugs that these files from the
0:08:37	beginning
0:08:38	some of them have been fixed in that's a great thing but there's this really
0:08:42	big red line that's goes that's going on and i think that in the case
0:08:49	of epiphany we have this huge cleanup opportunity
0:08:53	because support of web to work it
0:08:55	changes everything changes everything the backend so all those bugs were reported back when epiphany
0:09:01	was running on a call the well the last firefox that something engine they are
0:09:08	they need to be retested or
0:09:10	in many cases than we know that they are fixed we so you have this
0:09:14	cleanup opportunity and there is also the fact that the you why is so much
0:09:19	simpler and does not want to do everything that the old you white one did
0:09:24	that's also another clean up opportunity
0:09:28	so that was the case that you have epiphany
0:09:31	and well and that is just a generic example is fairly under control that bill
0:09:37	died but the end that was me because i started thinking up some stuff but
0:09:43	then
0:09:44	life happens and i didn't continue that much
0:09:48	so it looks like a typical glow module
0:09:52	and
0:09:53	evolution is a special case
0:09:56	notice that actually use the new status
0:09:59	and that there was this amazing improvement somewhere in the
0:10:05	somewhere in guess advocate and if i'm not mistaken a big part of that is
0:10:10	thanks to on the clapper is he here
0:10:13	yes
0:10:14	is that true
0:10:18	well thank you all day
0:10:21	i you that you that one
0:10:23	and
0:10:25	so but there's still this
0:10:28	huge amount of bug reports left to deal with so
0:10:32	that defined ahead all day and
0:10:36	no show
0:10:38	away
0:10:40	i have many things to say about the way the project handle it's bug reports
0:10:45	but i fear might hurt some feelings so maybe i'll keep that for discussions in
0:10:50	the hallways or maybe at the ways question period at the end so
0:10:55	but anyway it's gonna it's gonna just flow naturally with the
0:11:00	the techniques i'm suggesting in the rest of the stock and
0:11:05	G T K it needs help
0:11:09	it has a lot of old bugs so you as you can see so over
0:11:13	two thousand to a two thousand five hundred
0:11:16	no actually you have to you have to add up the lines actually it's not
0:11:21	there are cumulative
0:11:24	so it has a lot a lot a lot of old bugs that are certainly
0:11:28	not relevant anymore
0:11:30	it basically needs an army of testers
0:11:34	and i from a net contributor once said to me
0:11:39	i am not subscribe to did you to give about males
0:11:41	i don't look at the bug tracker
0:11:44	when it comes to fix in biology books in G T K
0:11:47	whoever catches me first on our C in the morning wins
0:11:52	we have a problem
0:11:55	so
0:11:57	and of our case to illustrate is a bit to be which is also another
0:12:01	special based
0:12:04	i'm arrogant enough to think that this is kind of how things should be at
0:12:08	least
0:12:09	i like at least like this or better and this
0:12:12	the new bugs are more numerous than the unconfirmed bugs
0:12:18	and they are kind of kept on the control so i the thing that i
0:12:23	actually haven't mentioned is that all those graphs they are not on the same scale
0:12:27	the are all related to their own
0:12:30	their own total so evolution you went from like five thousand to three thousand to
0:12:36	a little bit nicer i think it's about the thousand now and you take a
0:12:40	as you could see was the at two thousand five hundred B T V the
0:12:44	scale here is a hundred and fifty the upper bounds so if you add things
0:12:51	up it's about two hundred two hundred and forty fifty bucks half of that is
0:12:55	the feature requests
0:12:57	feature requests and
0:13:00	and this graph is going to eventually come crashing down in the next be to
0:13:05	be really switch it will happen any day now as i close a bunch of
0:13:10	those old bug reports
0:13:13	and i ching this advertising you might be interested in attending maybe to talk tomorrow
0:13:18	at the end of the for details
0:13:21	britain box is another it well it's in a similar situation to G T K
0:13:26	it needs help
0:13:28	it has at on of potential duplicates and in change book reports
0:13:36	i certainly don't feel like i'm encountering a thousand bug it i thousand four hundred
0:13:43	bucks when i'm listening to my music library
0:13:46	so i don't think there are that many buttons thing with some box it is
0:13:52	nobody closest box i think
0:13:55	so well let's talk about quality and let me shut up or while and think
0:14:00	of a bit a while what is quality this is an open question for you
0:14:05	folks to answer
0:14:08	how should we can own define how we measure quality
0:14:14	anyone
0:14:20	really
0:14:23	it's all about the users in the
0:14:29	the company incoming number of bug reports
0:14:39	i wonder
0:14:42	any other ideas
0:14:47	static and the statistical analysis
0:15:00	well it doesn't crash
0:15:02	the you know of an application that doesn't crash ever
0:15:07	it works once should it should it
0:15:12	well how do we know that we're
0:15:15	that we're better off as a whole
0:15:17	compared to two thousand five
0:15:23	in any case
0:15:26	we can probably agree that the amount of bug reports we hadn't noble to that
0:15:30	is not a strong indication of the quality of our software
0:15:37	and this is a partial quote from joe was able ski
0:15:41	at some point you start wondering what is people love my software
0:15:47	one hell have so many but reports
0:15:50	open then there waiting increase crashing down my soul
0:15:55	it in this article so argues that
0:15:59	force the actually advocate for something pretty rack radical he says
0:16:04	do not allow for more than two weeks in fixing time
0:16:08	of bugs to accumulate in the bug database
0:16:12	so if you have more than that you stop and you fix books until you
0:16:16	feel like you're fixing stupid bugs
0:16:19	and then you close all the remaining but reports
0:16:22	and he says don't worry december break this either bogs will come back
0:16:27	okay that's a crazy radical thing to do
0:16:31	that's not what applying to our if those as an as open source developers typically
0:16:37	especially if we're talking about volunteer work
0:16:40	where we don't necessarily have that seeing the regularity the manpower to fix bugs at
0:16:45	the steady pace
0:16:49	so how do we do it
0:16:51	you're thinking maybe well okay that's easy if you're only dealing with feature requests
0:16:57	or about then
0:17:00	what do you do with longstanding bugs
0:17:02	or what do you we do with the pickets
0:17:07	well we need to get serious about control
0:17:13	and by see resign mean many things
0:17:15	the right from the cards and philosophy in the manufacturing will
0:17:21	and cards and is basically this is also called five S system sadie sate on
0:17:27	say suppose and stick it so then it's okay it's translating to send it sizing
0:17:32	which is get rid of stuff
0:17:35	organising cleaning maintaining the D V cleaning less and disciplined enough to catering this methodology
0:17:46	we have forty five thousand bugs we need to start cleaning now and we need
0:17:50	just keep cleaning as we go in the future
0:17:54	so now we can apply some other things like inbox zero
0:17:58	and box there was basically just a mindset we say what is this mindset we're
0:18:03	dealing with email but we can apply to but management to some extent when you
0:18:07	receive an email you can either delete it you can transfer
0:18:11	to somebody else you can respond immediately
0:18:15	or you can market to be processed later because you're waiting on something else to
0:18:19	happen in the universe
0:18:21	or you do the action that you email sender requests
0:18:25	and we can apply that
0:18:26	to are but
0:18:29	mythology
0:18:30	and basically decision-making boils down to three possibilities
0:18:37	it's and you could see that
0:18:40	need info is not
0:18:43	actually this that there but it's really important
0:18:48	you have to use meeting full aggressively
0:18:52	you helps you identify obsolete bugs by simply running a search for bugs that have
0:18:57	been in them in the info state for
0:18:59	over two months or something
0:19:02	and confirming bugs is actually important
0:19:06	very few projects just actually confirmed the box
0:19:10	one thing i would strongly at of okay for tech actually is that we replace
0:19:14	the new statist by conference in can on box it up even though many people
0:19:20	will probably throw rotten fruit and me for saying that because i don't know many
0:19:24	people don't believe in confirmation about this
0:19:26	but
0:19:28	i think it could make an
0:19:30	add difference psychologically speaking
0:19:34	because
0:19:36	indecision is power lights is
0:19:39	if you leave at seven years old bug report open because it's in unconfirmed states
0:19:44	and because nobody has made a decision
0:19:47	it's not gonna help to attain a learning process
0:19:51	so whatever possible we want to clear yes or no if we don't decide now
0:19:57	we probably never will there's a question over there
0:20:01	we have a microphone
0:20:05	you can shop and
0:20:08	and are given the microphone or i will read tweed the question
0:20:14	hi i'm i guess possibly five maybe ten percent of the box it might box
0:20:20	of the overflow folder where i've set they lock and so this picture and i
0:20:25	say sorry ask a not about
0:20:28	and they rip in the back
0:20:30	and i say still i think still not still not gonna happen close the book
0:20:34	that in the park and i just pick of well
0:20:37	magically we box with the
0:20:39	the report just keeps reopening them
0:20:46	i think that so that's it comes that a little bit later
0:20:49	actually that's with the previous like to some extent
0:20:55	if it's a bug well okay a bogus should be fixed
0:20:59	but if it's a feature requests
0:21:01	well there are three types
0:21:04	either you agree with the thing is a absolutely i wanna do it so
0:21:08	yes confirmed and everything if you are confident that you can actually fix it
0:21:13	either your like not this really doesn't fit the vision so no out of scope
0:21:19	sorry
0:21:20	and there's a middle ground where side while i could like this feature but i
0:21:25	don't really care that much and i don't have them apart is that your case
0:21:31	we should be constant
0:21:34	so in the case where they suggest something this we could have anything that we
0:21:37	could have
0:21:39	and you say catches welcome and then nothing happens just close it
0:21:46	so what i would do
0:21:48	is
0:21:49	i would markets as enhancements
0:21:52	with and i would highly it with the goal of help want to do and
0:21:55	everything should but then is so it's not gonna as an enhancement it's not about
0:21:59	report and at some points
0:22:02	after three years you can't we all the patch
0:22:05	or after
0:22:07	i'm saying three years but maybe after one year or two years
0:22:11	if there is no clear indication if it's like one guy in the in some
0:22:17	faraway country we carry can strays it down so instead of
0:22:22	twenty people saying plus one plus one plus one and then you could say well
0:22:28	these your open this bug report this enhancement request when you have a patch because
0:22:32	i cut but then comes in the can replies which i will cover that there
0:22:37	there is out in with a question
0:22:48	but i know it's difficult
0:22:51	to come back to the question we do it in the form a we had
0:22:55	a czech cult your job
0:22:58	a dish in addition to the enhancement and we provides help to get it it's
0:23:04	a great it's like you know which files to you have to add it's by
0:23:07	do you have to start
0:23:11	then the other thing to remember is that
0:23:14	it's probably not useful to have
0:23:17	five hundred
0:23:18	yes would like this but we're not gonna work on that box because it's not
0:23:22	helpful from you contribute is either like is much better to have
0:23:26	these of the top twenty things we want you to do if you wanna contribute
0:23:31	and just maintain that list and you know we will still be in the database
0:23:35	even if you close then you can still kind of search for close but i
0:23:39	with no love the something the not gone forever
0:23:42	so you can you can manage a list that one
0:23:46	you could indeed have some kind of special search for
0:23:49	bugs that well feature requests
0:23:52	that times out because nobody has a bad
0:23:55	it could be done
0:23:58	the questions
0:24:01	i sell continue glorious past
0:24:08	so here yes i don't know whenever possible when you it's not possible
0:24:14	use this wonderful thing called time to figure out if there is actually real interest
0:24:20	that can help you
0:24:23	i mean part of the open source thing is that we want people to be
0:24:29	annoyed enough to contribute to our project
0:24:32	so if after three years nobody there is to make a patch for it
0:24:38	maybe it's not important enough
0:24:40	maybe it's not annoying enough
0:24:46	you either oppose it can from and something else
0:24:50	and using target milestones is actually pretty important and useful to and it allows you
0:24:57	to know
0:24:58	but maybe that's just a personal thing i do with the P T V about
0:25:03	it allows you to know which bugs were fixed for web version exactly
0:25:08	and it also helps a lot when you're releasing
0:25:12	because you just have to search for results bugs that were
0:25:15	attached to a given milestone and then you write the release notes or just point
0:25:20	to the link saying that was where the bugs that were fixed drink for this
0:25:23	release even if this book was ten years old it was finally fixed for this
0:25:27	release and you can see all that kind of information directly in the bug tracker
0:25:35	so when i was saying about yes-no fix it immediately are deferred or say just
0:25:40	know
0:25:41	when i say fix it into the i do mean fix it and then controls
0:25:45	the bug report
0:25:47	unless the feature is still broken and i mean really broken let me illustrate this
0:25:52	but i need sound for this to work and i'm not sure i do have
0:25:55	sounds
0:26:02	or is there anything that controls the somewhere here
0:26:11	not normally
0:26:15	well one what lot of speakers all i could like what microphone
0:26:20	that's gonna be also
0:26:49	that was a former so you're that
0:26:53	alright
0:26:54	ghetto blaster microphone like so
0:26:58	what do i mean by this
0:27:01	you've got a fixed for about that you have committed to your master brian what
0:27:05	you are a little bit unsatisfied with the cost quality
0:27:10	then you add some comments in your code and a to do item on your
0:27:14	personal this but do not keep your bug report open insisting because when you'd like
0:27:19	to come is a better implementation
0:27:22	you don't show some
0:27:25	by the way to not close bugs until the fix has been marriage
0:27:30	the main development branch
0:27:32	is the fix is only committed to a separate branch well you can market as
0:27:37	assigned another underused but reports that is
0:27:41	and then
0:27:43	you can market is assigned until it goes into monster and of course you said
0:27:47	yes find email because that's pretty
0:27:51	so
0:27:54	no is actually pretty famous for daring to say no out of scope
0:27:59	but saying you know without ending up on the front page of slashdot is actually
0:28:04	a very delicate art
0:28:06	you can't implement everything out there due to insufficient manpower or because feature X would
0:28:12	go against projects vision or intended user experience
0:28:16	and for that i can't miss i age helps a lot
0:28:21	people we with will respect your decision more if we know your constraints and why
0:28:26	you have to say no
0:28:29	so by can message
0:28:32	well
0:28:34	i kind of message is the message that you composed for something that's basically as
0:28:39	if you for book reports
0:28:41	if there is non available you create one and you save it as a text
0:28:45	file on your computer for reuse that way you don't end up
0:28:49	like
0:28:51	being super frustrated of always having to type the same explanation to why this cannot
0:28:57	be done or why this will not be done
0:29:00	and you don't and i'm just saying nope and ending up on news sites
0:29:06	for example you could have something that was like this
0:29:09	hi and thanks for reporting this bug
0:29:12	P T V score is currently being replaced by the distributing services which is a
0:29:17	major undertaking an overhaul and we suddenly can't investigate much bucks the talk sure on
0:29:22	the traditional core of it see
0:29:25	we will revisit this
0:29:27	a by the next please which will use gas and hopefully your issue may be
0:29:31	gone by that new release
0:29:33	otherwise we will appreciate your help in testing it out thanks
0:29:38	so that's the kind of thing i don't want to read be typing on the
0:29:41	spot ever again
0:29:43	so i keep it as a text file on my computer
0:29:47	so you should
0:29:51	you should
0:29:52	there we do have ten for advising them back to that but they don't
0:29:57	necessarily corner the specifics or of your project so it's nice to have those custom
0:30:02	kind replies on your computer
0:30:04	for example for the meeting full stuff with custom debugging instructions for your project
0:30:13	and
0:30:14	searching is every nice thing is you can see the bottom of the screen i
0:30:17	have a lot of special saved searches so that's
0:30:22	that seems a bit silly but it's really useful in taking away the pain of
0:30:29	money string the bugs and the patterns and the stuff that for example i want
0:30:33	to see all the bugs that are older than four hundred days and that have
0:30:36	dot have any patch
0:30:39	that's use of useful for finding that
0:30:43	and not just a little edits hyperlink in the book title
0:30:48	like and it's
0:30:50	super hard to spot actually
0:30:53	not many people know it actually exists
0:30:57	you can use that to rename the bug report as the same time as you
0:31:01	are commenting other changes
0:31:03	and then you can use a book good bug title slash summary
0:31:07	so you can make a complete sentence with exact words
0:31:11	and choosing the right words improve fired see it makes to bug user to find
0:31:17	prevents duplicates
0:31:19	makes coffee so it's
0:31:24	actually i go
0:31:25	i go a little bit tougher and that i use synonyms like and i think
0:31:30	of all maybe someone is gonna think of that for when searching so i use
0:31:35	multiple words that mean the same thing in that title
0:31:39	for example some example of good and back well good and bad
0:31:43	but titles
0:31:46	all the first one is not that compelling well old one was share my the
0:31:49	stuff the item in the menu lot of life you know is a registered hundred
0:31:52	immensely five
0:31:54	i nine we need to do all initially share make this a menu item if
0:31:57	you know is a well
0:32:00	the second one is more interesting it's a bug in them to this U which
0:32:04	was titled show where files come from no or maybe it was just what i
0:32:09	thought at first and then i thought well i'm i need a better it but
0:32:13	title instead provide context allow users to know the path slash location from where files
0:32:18	and folders and search results come from so that way if someone searches for past
0:32:24	or location or search or results
0:32:27	or context you they're gonna find that a real easily
0:32:33	and some other examples
0:32:35	for example the first example
0:32:39	people searching for words such as sound or ring tone or call will find that
0:32:45	about report easily
0:32:48	the
0:32:50	the one near the middle if you search for G E mail i not message
0:32:56	account you're gonna find this but before
0:33:01	so keywords a really nice
0:33:05	i use gnome love all the time i don't know might is normal of all
0:33:09	the time is make is
0:33:11	is really easy to just type every bugs that are kind of easy
0:33:17	that you don't really have time or motivation to tackle or that you actually you
0:33:22	could do it in two minutes maybe for feature request
0:33:26	but you have more urgent things to do and you kind of want to use
0:33:30	them to lure people into contributing your project
0:33:33	so i do that's
0:33:37	i'm not sure about help want to but i think it's just for stuff that
0:33:41	you are yourself
0:33:43	unable to tackle
0:33:46	and the distinction between usability and you want reviews of that youtube it send clear
0:33:52	but so i think the you wire if you is when you want to call
0:33:54	out and they to the rescue
0:33:56	and there's a bunch of other keywords that are less use
0:34:03	so divide and conquer
0:34:07	don't do it on if possible do it in teamwork maybe would but T I's
0:34:11	days
0:34:12	maybe to google hangouts
0:34:15	or but fests i don't know if that just actually something a word
0:34:22	there is also a to fill it moves are made the script
0:34:26	once some time and to force him to revisit ten bucks a day
0:34:32	i think this is five bucks a day but if you read the code this
0:34:35	is actually it's ten bucks today
0:34:39	so you can grab descriptive your if you need extra something in your face
0:34:46	and well to recap basically you want to need info everything your hands for unsure
0:34:52	about in six months with that special search query you close any remaining needed for
0:34:58	that has not been clearly answered
0:35:00	if the norm box quite doesn't do it for you for free
0:35:07	if you are a developer who knows the project vision
0:35:11	well you have to show some courage and say no or patch or it won't
0:35:17	happen
0:35:19	and if you're not a developer or if you like experience but have jobs
0:35:24	most project of appears would be very happy to have any kind of help interesting
0:35:30	the bug so
0:35:32	you can ask for yes slash no decision on any given bug
0:35:38	and then that way you getting some experience in know what's the vision what and
0:35:43	whatnot
0:35:46	so you also have to do render regular cleanup sessions every few months
0:35:51	or when there is a major technologist goal or
0:35:56	idealistic all change going on
0:36:00	so that means that you have to know the know the big projects on your
0:36:03	road map and
0:36:06	see that fortunate is popping up such as hold on touch bugs
0:36:10	core engine changes like P T Vs switch to T S or if you can
0:36:14	use which to web get
0:36:16	and or big you why redesigns
0:36:20	stuff like that
0:36:22	and you can run search queries to search and verify all the bugs that are
0:36:27	older and four hundred days eight hundred days
0:36:30	chances are that they are fixed already they are obsolete
0:36:35	let's go duplicates
0:36:37	or just plain crack
0:36:39	and i mean like wracked is probably like requesting features from the eighties that zero
0:36:44	point one percent of users actually care about
0:36:50	that's it it's nothing revolutionary it's just i hope that's somewhat useful now you can
0:36:56	probably questions comments and insults
0:36:59	and i'm pretty sure i must have overlooked or focus in something
0:37:04	and that's have a chance
0:37:19	but
0:37:20	i also you have very nice lines
0:37:24	and you sounds to do you made an example that people don't even know that
0:37:30	you can change the talking book so but i don't think that's the only problem
0:37:35	not the only a interface problem of books of the i think so it's a
0:37:41	all those stuff would improve the blue
0:37:45	then would it looks a little buttons took something move gonna
0:37:50	thing is that you would have to find the bug tracker that is much better
0:37:54	that numbers about any is if we an open source project actually free an open
0:37:58	source project and can handle huge buffaloes
0:38:02	and or the sysadmins are gonna hate us and
0:38:09	i mean these days many people many projects smaller projects the just to the but
0:38:16	that issues management on get hub or stuff like that but that's proprietary i don't
0:38:20	i don't think it's open source at all and some do it on know nobody
0:38:25	uses source forge are anymore it's so crap and
0:38:31	the thing
0:38:34	i few years ago i have was actually looking for a bug tracker that would
0:38:38	be at least equal in quality and versatility to bugs it out and that could
0:38:43	actually installed without that phd on and my home server and i didn't find anything
0:38:49	and actually a book sellers was it a bit too complex for me to install
0:38:54	but i didn't find anything
0:38:57	that i like really much more than books
0:39:02	like there's bookseller lunch but this is it's okay but many people created and there's
0:39:06	google codes
0:39:07	which is not open source i don't
0:39:11	we don't really have i don't know if we have an of the native out
0:39:16	there
0:39:17	if so
0:39:19	why not consider it
0:39:22	out of time
0:39:29	anyway if anybody else has questions or fruit rotten fruit to throw i will be
0:39:34	in the hallway
0:39:36	that's it

Extreme containment measures: keeping your bug reports under control

Developer Experience Track

Jeff Fortin