[01:01] <mspencer> Hi, I'm new to bug fixing. Approximately how long does it take until someone reviews my bug fix merge proposal?
[02:38] <mspencer> a bug is listed for both a project and dist+package. when assigning the bug to myself, do I assign both to myself or just one?
[02:40] <mspencer> and can I work on a bug marked as confirmed, or must it be marked triaged?
[02:44] <trinikrono> hey mspencer not like im a expert or anything but i can give you my opinion
[02:45] <mspencer> any help would be great, I'm new to bug fixing
[02:45] <trinikrono> normally if a bug is triaged its because it is complete and ready to be worked on
[02:45] <trinikrono> meaning all the log files etc
[02:45] <trinikrono> are you going to fix the bugs yourself mspencer?
[02:46] <trinikrono> also can you post one of the bugs so that the people in the channel have an idea of what you are working on
[02:48] <mspencer> I'm considering working on LP #1019457, it would be only my second bug fix so I don't know how hard it would be.
[02:48] <ubot2> Launchpad bug 1019457 in unity (Ubuntu) "The Dash closes when trying to switch to the Command lens (Alt+F2)" [Low,Confirmed] https://launchpad.net/bugs/1019457
[02:51] <trinikrono> the other bug you worked on was a unity bug also? mspencer
[02:52] <trinikrono> normally a bug would need apport info too be considered complete and sent upstream, but as ubuntu is upstream that isnt necessary
[02:52] <mspencer> I've submitted a proposal for a fix to LP #1058059 and am waiting for it to be merged.
[02:52] <ubot2> Launchpad bug 1058059 in software-properties (Ubuntu) "Menus are misaligned: "When there are other updates" and "Notify me of a new Ubuntu version"" [Medium,In progress] https://launchpad.net/bugs/1058059
[02:54] <trinikrono> i think you should get intouch with someone from unity and make sure it wasnt designed that way
[02:54] <trinikrono> one persons bug is a next persons feature
[02:55] <mspencer> so would this be something to ask on the ubuntu-devel-discuss mailing list?
[02:55] <Aaron> sorry for my newbie question. do you guy's have any type of web sites to look for packages tahat need love
[02:55] <trinikrono> i was looking to see if there are duplicates
[02:55] <Aaron> so i can adopt the packages
[02:56] <trinikrono> Aaron: start with one you love :D
[02:56] <Aaron> i just want to make sure .... no one it's the upstreamer
[02:56] <Aaron> the packages i really love it's evolution
[02:56] <trinikrono> you are thinking about a particular package Aaron
[02:56] <trinikrono> well for evolution there is prolly the mozilla team
[02:57] <Aaron> don't have nothing in mind but evolution
[02:57] <Aaron> yeah...
[02:57] <trinikrono> thats good
[02:57] <Aaron> then i'll take another easy package to handle
[02:57] <Aaron> but i really want to start helping around more..
[02:58] <trinikrono> gimme a sec Aaron ill find that wikipage for you
[02:58] <Aaron> ok
[02:58] <mspencer> trinikrono: how would I contact unity to find out if this really a bug?
[02:59] <trinikrono> mspencer: to finish with you, can you test the fix on your system and see if it fixes the problem
[02:59] <Aaron> mspencer, on launchpad
[02:59] <trinikrono> maybe submit a patch for now
[02:59] <mspencer> Aaron: thanks!
[02:59] <trinikrono> but i think you should wait to hear from someone from the unity team
[02:59] <trinikrono> so what we can do is too make the bug triaged
[03:00] <trinikrono> this bug should just need apport info
[03:00] <trinikrono> you know the command apport-collect
[03:00] <trinikrono> and we need to find someone that can mark the bug as triaged
[03:00] <trinikrono> if anything you can send a email to the list if they are no bug triagers online
[03:01] <trinikrono> having the bug triaged would help with getting it noticed, there are alot of bugs for unity
[03:01] <trinikrono> i saw ~1700
[03:01] <trinikrono> but in the mean you can subscribe to the bug and work on a patch for it
[03:02] <mspencer> trinikrono: what list?
[03:02] <trinikrono> the email list for the bugsquad
[03:02] <trinikrono> gimme a sec
[03:03] <Aaron> they should have a package like debian where it tells you which package need adoption
[03:03] <trinikrono>  ubuntu-bugsquad@lists.ubuntu.com
[03:03] <trinikrono> they always answer emails
[03:03] <trinikrono> even if triagers arent always online
[03:03] <Aaron> lol
[03:03] <trinikrono> and they will know better than me :)
[03:04] <mspencer> trinikrono: thanks! should I work on a patch vs a branch proposal?
[03:04] <trinikrono> i think a patch is fine for now
[03:04] <trinikrono> until we make sure it is a bug!
[03:05] <trinikrono> Aaron: https://wiki.ubuntu.com/MozillaTeam here you go
[03:05] <trinikrono> whoops
[03:05] <trinikrono> did i mix them up
[03:05] <trinikrono> evolution is mozilla, i was thinking about thunderbird
[03:06] <Aaron> cool
[03:06] <Aaron> i'll go with xchat?
[03:06] <Aaron> ;)
[03:06] <Aaron> even better it's a client that i use
[03:07] <trinikrono> Aaron: wait one sec
[03:07] <trinikrono> https://wiki.ubuntu.com/DebuggingEvolution use this page Aaron
[03:07] <trinikrono> this is to debug evolution
[03:07] <Aaron> ok
[03:07] <trinikrono> evolution is not with the mozilla team that was my mistake
[03:09] <Aaron> ubuntu sucks... in the packaging part. they should be like debian with the adoption...
[03:09] <Aaron> of a package
[03:09] <Aaron> so i can upload my ppa
[03:09] <trinikrono> and check this page aswell Aaron i believe this is what you looking for https://wiki.ubuntu.com/BugSquad/AdoptPackage
[03:09] <trinikrono> well Aaron thats the funny thing , if you get them to update the version in debian
[03:10] <trinikrono> it will get updated in ubuntu aswell
[03:10] <trinikrono> remember we use debian unstable
[03:11] <Aaron> yeah
[03:11] <Aaron> i know..
[03:11] <persia> Aaron: The idea is that we don't have any maintainers in Ubuntu, so *anyone* can fix bugs or uplaod a package.
[03:11] <Aaron> we upload them to launchpad?
[03:11] <Aaron> and how do you make it official that you are the maintainer ?
[03:11] <persia> Yep.
[03:11] <persia> You don't.
[03:11] <trinikrono> good the big guns arrived
[03:11] <persia> A long time ago in Debian (it's not that way now), there were lots of maintainers refusing to upload bugfixes.
[03:12] <Aaron> oh.
[03:12] <persia> And the Ubuntu model was developed during that bad time, so err on the other side: no maintainers at all.
[03:12] <Aaron> so how can i maintain a package just put it on launchpad?
[03:12] <persia> It's considered polite to chat with folks who worked on the package before.
[03:13] <persia> You can't maintain a package, except maybe by fixing everything in it faster than anyone else can notice.
[03:13] <Aaron> oh
[03:13] <persia> If you want to try this, triage all the bugs, and prepare candidates for upload.
[03:13] <persia> In the beginning, you'll need to get sponsored, but if you've been doing it for a while, you can ask the DMB for upload permission.
[03:13] <persia> !sponsoring
[03:13] <ubot2> You can find out about the package sponsorship process here http://wiki.ubuntu.com/SponsorshipProcess - For !UDS sponsorship see http://uds.ubuntu.com/participate/sponsorship/
[03:13] <persia> Which package?
[03:13] <trinikrono> evolution
[03:15] <Aaron> or. xchat
[03:15] <persia> I don't think that's on any of the images, for for historical reasons, I'd recommend chatting with the Desktop Team about it (in #ubuntu-desktop).  They can probably tell you the current status better, and help determine the best fix or be sponsors.
[03:16] <persia> I think xchat is part of the Xubuntu Desktop and Ubuntu Desktop images, so either the Desktop team again, or the Xubuntu team (#xubuntu-devel) would likely know about that.
[03:16] <persia> In general, you can check if a package is used in an image by looking at the output of `apt-cache show ${PACKAGE}` for the Task: field.
[03:17] <mspencer> how do I use apport-collect to add info to a bug? the bug is LP #1019457
[03:17] <ubot2> Launchpad bug 1019457 in unity (Ubuntu) "The Dash closes when trying to switch to the Command lens (Alt+F2)" [Low,Confirmed] https://launchpad.net/bugs/1019457
[03:17] <persia> If it's in a task, there's probably a team who wants it to be in good shape with whom you could collaborate.
[03:18] <trinikrono> apport-collect 1019457 mspencer
[03:18] <trinikrono> can you take a look at that bug aswell persia
[03:18] <trinikrono> mspencer: wants to fix the bug i was suggesting we triage the bug first
[03:19] <persia> I know nothing about the dash (my main interaction with it involves trying to figure out how to remove it from my interface without breaking other things)
[03:19] <Aaron> sorry persia the other question was. is how do you set up the email account that was forward to my account so i can write with my ubuntu email
[03:20] <mspencer> I ran that, but I'm not sure what to answer when I got to this question "Thanks for reporting this bug on unity.  Is the issue you are reporting purely graphical (will report more information about your graphic configuration and will report the bug against compiz)?"
[03:20] <persia> Aaron: I believe that @ubuntu.com mail is sent to the default address registered in launchpad for Ubuntu Members, but you can verify in #launchpad.
[03:20] <trinikrono> maybe its the wrong bug number lol mspencer
[03:21] <mspencer> trinikrono: it's the correct number
[03:21] <persia> mspencer: What happens if you say "no" to that prompt?  I suspect that some folk report problems with tearing or icon corruption against the dash, hence the question.
[03:22] <Aaron> there was a bug, on this package "podbrowser"
[03:22] <Aaron> it does not want to open
[03:23] <Aaron> it say's *** sorry, I Tried my best but i still can't find a usable icon theme!
[03:24] <mspencer> persia: I answered no and it takes me to the send report dialog. should I send the report? does it matter what version I'm running (precise)?
[03:27] <mspencer> by the way, this is probably a bug, not a feature, because pressing Alt takes me directly to the app menu from the dash or command lens.
[03:29] <persia> mspencer: Sending the report should add information to the bug on LP
[03:30] <mspencer> persia: but does it matter what version I'm running?
[03:30] <mspencer> persia: should I run this from quantal or raring instead of precise?
[03:31] <persia> It depends on how you want to report the bug.  Replicating it in raring and collecting information there is more likely to get a fix, as someone has to be convinced it's critical to get a fix into quantal or precise.
[03:32] <persia> If you believe it to be critical for precise, and believe it to be fixed in quantal and raring, then precise is the version from which you should collect information.
[03:36] <mspencer> persia: it still exists in quantal and I don't think it is important to get fixed in precise or quantal, so I'll report it from raring.
[03:36] <mspencer> once I send the report, how do I get it triaged?
[03:37] <persia> Do as much as you can, then ask for help here.  Best practice is not to be the one to set status and importance for one's own bugs, as one may be biased.
[03:38] <mspencer> persia: I can't set either, launchpad doesn't let me.
[03:39] <persia> !bugsquad
[03:39] <ubot2> Factoid 'bugsquad' not found
[03:39] <persia> Grrr....
[03:40] <persia> That's because it thinks you're new.  Try triaging other folks bugs and ask here for someone to review your triage and set the status for you.
[03:40] <persia> Once you've done 5-10, dig up the bugsquad application procedure from the wiki, and you can be granted permission to set those.
[03:40] <mspencer> persia: I am new to launchpad, I joined last week, and the bug isn't my own.
[03:41] <persia> Welcome then!  Since you're triaging someone else's bug, once you've added all the information, and think it's ready, determine what you think the importance and status should be, and ask someone here to set it.
[03:41] <persia> !importance
[03:41] <ubot2> You can learn about setting bug importance at https://wiki.ubuntu.com/Bugs/Importance
[03:41] <persia> !status
[03:41] <ubot2> Factoid 'status' not found
[03:42] <persia> (it's probably Bugs/Status or something)
[03:42] <mspencer> persia: Okay, I will.
[03:43] <persia> Make sure there's enough information that someone else can easily reproduce the bug, and that there is current system information about it (debug symbols, stacktraces, whatever apport wants), to make it easy for the developer to understand what needs fixing.
[03:45] <mspencer> persia: There's already enough info on how to reproduce it, so would the data from apport-collect be enough? I plan on fixing it myself if I can.
[03:46] <persia> mspencer: If you're planning to fix it, you're being the developer, and so are in the best position to decide if it is well-triaged.  If it has enough information for you to fix it, it's triaged.
[03:47] <persia> Once you have a fix, I'd recommend chatting with the Desktop Team to help get it uploaded.
[03:51] <mspencer> So when I have enough info, I just ask here for the bug to be triaged?
[03:55] <persia> Or, if you're planning to fix it quickly, don't bother with the official status, and just assign it to yourself and post the fix when it's ready.
[03:56] <persia> Triaging bugs is most useful when you can describe the problem in close detail, but need someone else to actually fix it.
[03:56] <mspencer> persia: Since I'm new to bug fixing, it might take awhile.
[03:58] <mspencer> Thanks for all the help, I'll just assign myself to the bug and work on it.
[04:05] <mspencer> persia: Since I'm just working on a patch and then will talk to the Desktop Team to get it uploaded, would I still set the status to In Progress?
[04:08] <persia> I would, if I was working on it, just to let others know to ask me if they want to know the current status
[04:10] <mspencer> persia: thanks for all the help!
[04:10] <persia> Also, unless you specifically need me, I'd recommend just asking questions in the channel without highlighting anyone.  Someone else may be faster to answer than I, or I might have walked away for a bit.
[04:11] <persia> No problem, and thanks for helping make Ubuntu better.
[04:12] <mspencer> one more question - the bug is tied to a project and dist+package: am I going to assign myself to both?
[04:13] <mspencer> 'Unity', and '(unity) Ubuntu'
[04:16] <persia> You decide: the former involves working directly with the developers who wrote the software in the first place, and may require special arrangements.
[04:17] <persia> The latter involves creating a patch for Ubuntu: it's good practice to also make the patch available upstream when doing so, but the desktop team is likely the only group with who you must coordinate.
[04:18] <persia> If you have an interest in Unity specifically, and expect to be doing more with that, I'd recommend the former.
[04:18] <persia> If you have an interest in Ubuntu and expect to have other patches for other programs, the latter might be a better introduction to our procedures.
[04:18] <mspencer> I did the second because I'm interested in fixing bugs in Ubuntu in general.
[11:07] <JohnLea> a
[11:08] <bkerensa> e
[19:23] <TheLordOfTime> iou.  anything of relevance here, or can i go back to lurking?