[00:00] <bodhi_zazen> mhall119: some people have asked about how you see working with forums / askubuntu
[00:00] <mhall119> we have already  been using and promoting askubuntu for app developers to ask for help with coding/packaging, etc
[00:00] <bodhi_zazen> I am active on askubuntu, so personally see no problems
[00:00] <bodhi_zazen> but other staff are not as active on askubuntu
[00:00] <mhall119> but askubuntu isn't a good place to seek advice, and it has no social interaction
[00:01] <mhall119> the primary reason for an app developer forum is to give them somewhere for form as a community
[00:01] <s-fox> mhall119:  why do you want to create a section on the ubuntu forums, but have all technical questions directed to askubuntu  ?
[00:01] <bodhi_zazen> http://askubuntu.com/users/35795/bodhi-zazen
[00:01] <s-fox> it seems very odd medium
[00:01] <mhall119> well AskUbuntu can't do it, and we haven't really gotten much acivity on the IRC channel
[00:02] <bodhi_zazen> mhall119: explain AU, and how forums integrates with discussion
[00:02] <mhall119> every other developer portal (android, windows, etc) has a forum for their app developer community
[00:02] <mhall119> bodhi_zazen: basically AU would be used for "How do I do X" and "Why isn't Y working?"
[00:03] <mhall119> but questions like "What's the best IDE to use?" or "Should I use Gtk or Qt?" would be directed to the forums
[00:03] <bodhi_zazen> So Forums gain - Visibility for developers , and a place for discussion
[00:03] <mhall119> anything social would happen on the forums
[00:03] <bodhi_zazen> AU is not so great with discussion
[00:03] <mhall119> right, AU is just a knowledge base
[00:03] <coffeecat> mhall119, sending app developers only to askubuntu for technical support limits their choice. They can ask technical questions on the forum as well.
[00:03] <mhall119> coffeecat: they  can, and they will (people still ask developer help on IRC too)
[00:04] <bodhi_zazen> AU community tends to use SE chat, not IRC
[00:04] <mhall119> but in general we want to build up the amount of support information in AU
[00:04] <mhall119> SE chat?  I didn't know there was such a thing
[00:04] <bodhi_zazen> http://chat.stackexchange.com/
[00:05] <bodhi_zazen> When I log in there, I get a list of the AU rooms
[00:05] <mhall119> well thats......yeah...
[00:05] <bodhi_zazen> http://chat.stackexchange.com/rooms/201/ask-ubuntu-general-room
[00:05] <bodhi_zazen> and on
[00:05] <bodhi_zazen> A few AU members are active on IRC, most are in chat rooms
[00:06] <bodhi_zazen> Any other questions about AU ?
[00:06]  * mhall119 has yet another place to lurk
[00:06] <mhall119> there was one more, but I don't remember it, and I can't find the email
[00:06] <s-fox> does au allow for community links mhall119 ?
[00:07] <mhall119> s-fox: community links?
[00:07] <bodhi_zazen> AU tends to direct discussion to forums, forums are more "social" that way
[00:07] <mhall119> s-fox: we're going to link to the forums on http://developer.ubuntu.com/community/
[00:07] <bodhi_zazen> AU also has meta - http://meta.askubuntu.com/
[00:07] <s-fox> we recently linked to other areas of the ubuntu community mhall119 , such as askubuntu and launched answers, it would be nice to see the link exchange returned
[00:08] <bodhi_zazen> AU links to forums commonly
[00:08] <mhall119> s-fox: I don't know about AU, but I plan on heavily promoting the use of the app developer forums
[00:08] <bodhi_zazen> The netiquette , however, on AU is to re-post forums post with link
[00:08] <bodhi_zazen> AU does not like it when you answer with a link to wiki or forums, and no content
[00:08] <s-fox> bodhi_zazen:  i was thinking akin to our nab bar menu items
[00:09] <s-fox> :)
[00:09] <s-fox> nab
[00:09] <s-fox> nav
[00:09] <bodhi_zazen> We could ask on meta
[00:09] <bodhi_zazen> http://meta.askubuntu.com/
[00:09] <bodhi_zazen> meta is sort of the place to ask for that s-fox
[00:09] <bodhi_zazen> but AU community makes fairly heavy use of forums
[00:09] <s-fox> bodhi_zazen:  i could speak with jorge
[00:10] <bodhi_zazen> so they would probably be open to it
[00:10] <bodhi_zazen> That too s-fox
[00:10] <bodhi_zazen> posting on meta either b4 or after would help ;0
[00:10] <bodhi_zazen> Other questions for mhall119 ?
[00:10] <bodhi_zazen> mhall119: do you have questions for us ?
[00:11] <bodhi_zazen> Next up - open floor - although s-fox has a topic
[00:11] <bodhi_zazen> [TOPIC]Open floor
[00:11] <mhall119> is there a way to make a link that will create a new forum thread if one by that name doesn't already exist?
[00:11] <bodhi_zazen> s-fox: topic
[00:11] <bodhi_zazen> I do not think so mhall119
[00:12] <cariboo907> there is an option to search if there is something similar, when creating a new thread
[00:12] <bodhi_zazen> Anyone else have any questions or issues ?
[00:12] <mhall119> ok, I would like to make a new thread for any new tutorials we add, I guess I can just make them manually and add the link
[00:13] <bodhi_zazen> mhall119: tutorials on wiki or askubuntu ?
[00:13] <s-fox> i request guidance on replies to the welcome message. i have been receiving 10ish email per day quoting message and then a series of stars. i assume this is spam filter in action, would it be okay to ban users who send these type of message ?
[00:13] <mhall119> bodhi_zazen: on developer.u.c
[00:13] <mhall119> dpm is putting together a collection of tutorials there
[00:13] <bodhi_zazen> OK
[00:13] <overdrank> s-fox +1
[00:13] <cariboo907> s-fox, I did, when I handled the welcome message
[00:14] <bodhi_zazen> s-fox that is one of the joys with welcome message =)
[00:14] <bodhi_zazen> If it seems like spam, I will ban
[00:14] <s-fox> bodhi_zazen:  it bites
[00:14] <s-fox> :)
[00:14] <bodhi_zazen> Who will take welcome message this month ?
[00:14] <cariboo907> I will
[00:14] <coffeecat> As a general point, I'm uncomfortable with using the censor list for spam domains. It removes the evidence.
[00:14]  * s-fox thinks we should have a welcome bot 
[00:14] <Iowan> With THAT kind of promo?
[00:15] <s-fox> seriously, noone should reply to welcome message
[00:15] <bodhi_zazen> cariboo907: do you know how to make that change in the admincp ?
[00:15] <cariboo907> Yes I do
[00:15] <bodhi_zazen> \o/
[00:16] <bodhi_zazen> OK, teach overdrank or Iowan or some other admin to do it
[00:16] <s-fox> bodhi_zazen:  welcome bot to send all welcome messages  ?
[00:16] <bodhi_zazen> Part of rotating tasks is getting everyone up to speed
[00:16] <cariboo907> Sure, no problem
[00:16] <bodhi_zazen> Thank you
[00:16] <bodhi_zazen> Any other topics
[00:16]  * bodhi_zazen adds Welcome message to monthly chores
[00:16]  * s-fox wants 4 weeks off adminny type things
[00:16] <s-fox> :)
[00:17] <Iowan> cariboo907: Show me...
[00:17] <bodhi_zazen> #endmeeting
[00:17] <meetingology> Meeting ended Thu May 24 00:17:26 2012 UTC.
[00:17] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-23-23.00.moin.txt
[00:17] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-23-23.00.html
[00:17] <s-fox> thank you all for coming to the meeting :)
[00:17] <bodhi_zazen> we are over our hour, bring any additional topics / questions to #ubuntuforums
[00:17] <bodhi_zazen> Thank you all for coming and participating in the community
[00:18] <mhall119> thanks everyone
[00:18] <moergaes> Bye and good night!
[00:20] <s-fox> au revoir
[15:20] <vibhav> Has the meeting started?
[15:21] <dholbach> vibhav, in 40m
[16:00] <dholbach> o/
[16:00] <l3on> :)
[16:00] <highvoltage> o/
[16:00] <dholbach> who else do we have here for the MOTU meeting?
[16:01] <micahg> o/
[16:01] <dholbach> perfect - we probably better get started - others might hop in in a few :)
[16:01] <dholbach> #startmeeting
[16:01] <meetingology> Meeting started Thu May 24 16:01:31 2012 UTC.  The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:02] <dholbach> this is the first MOTU meeting in a long while, so please bring up whatever you want to discuss, even if it's not yet on https://wiki.ubuntu.com/MOTU/Meetings
[16:02] <dholbach> #topic meeting times
[16:02] <dholbach> when we discussed this at UDS, the proposal was 2nd & 4th Thursday, 16 UTC
[16:03] <dholbach> back then we already realised that this might be bad for some
[16:03] <ajmitch> bad for a few :)
[16:03] <highvoltage> it's right over lunch time EST, but I can live with it.
[16:03] <dholbach> ajmitch, isn't it insane o clock where you are? :)
[16:03] <micahg> highvoltage: it's the middle of the night for ajmitch
[16:04] <broder> oh, o/ btw :)
[16:04] <ajmitch> 4AM
[16:04] <broder> looking at the wrong window
[16:04] <dholbach> geser dug out the meeting times of the last MOTU meetings and it seems we alternated between 4:00 UTC, 12:00 UTC and 20:00 UTC
[16:05] <dholbach> and AFAIK the new RMB teams will meet at 10 and 20 UTC to try to cover most of the world
[16:05] <dholbach> any strong feelings about either of the possibilities? :)
[16:05]  * ajmitch is still of the opinion that rotating meeting times is only useful if you'll have enough people show up
[16:05] <pleia2> dholbach: 12 and 22
[16:06] <dholbach> thanks pleia2 - I was close, wasn't I? :)
[16:06] <pleia2> :)
[16:06] <dholbach> we could trial one of the solution for a couple of months
[16:07] <dholbach> any strong feelings or should we move this to the mailing list?
[16:07] <vibhav> o/
[16:07] <asomething> to the list!
[16:07] <dholbach> alrightie
[16:07] <porthose> o/
[16:08] <dholbach> #action dholbach to mail list about meetings times
[16:08] <meetingology> ACTION: dholbach to mail list about meetings times
[16:08] <dholbach> moving on
[16:08] <dholbach> #topic MOTU School (Bhavani Shankar)
[16:08] <dholbach> it's unfortunate that Bhavani can't make the meeting, but he wanted us to briefly talk about MOTU school and ideas for this cycle
[16:09] <dholbach> I think there was a work item in the blueprint as well
[16:09] <dholbach> does anyone still have it in front of them?
[16:09] <tumbleweed> can't see a workitem https://blueprints.launchpad.net/ubuntu/+spec/other-q-motu-bof
[16:09] <highvoltage> bhavani is in UTC+6 right?
[16:10] <dholbach> I think the idea was to have a couple of training sessions throughout the cycle
[16:10] <dholbach> highvoltage, UTC+5h30m I think
[16:10] <vibhav> highvoltage: UTC+0530
[16:11] <dholbach> ok, I can't find the action right now, but I think it was Bhavani (and others)  who wanted to have some training sessions this cycle, not as often as weekly, but every now and then
[16:11] <dholbach> to provide an entry point for new contributors
[16:11] <asomething> I think we could probably swing a few sessions, I just don't want to start promising regular sessions again and then fail
[16:11] <ajmitch> it's a nice idea, as long as someone's willing to run them
[16:12] <dholbach> maybe we could discuss a few ideas and collect a list of people who won't volunteer, but at least want to be involved in the discussions?
[16:12] <tumbleweed> if it is only one or two sessions, that should be easier to staff, than a week-long UDW
[16:13] <dholbach> yes, it should be a lot easier, if we would for example do a Q&A session or a "demo a bug fix" session
[16:13] <dholbach> which doesn't huge amounts of preparation
[16:13] <dholbach> ... require ...
[16:13] <dholbach> do we have any reasonably new contributors here with some requests for training sessions?
[16:13] <vibhav> me
[16:14] <dholbach> vibhav, what would you like to see discussed in one of those sessions?
[16:15] <vibhav> The debian/rules file
[16:15] <highvoltage> maybe I'm going a bit off-cource, but it might be nice to have some kind of a list of people who'd like to attend beginners training, and every time there's 5 or so people in that list a session is scheduled. when there's small groups of enthusiastic people then google hangouts might be nice for that too. (and as I'm typing that I'm already dreading all the problems that come with google hangouts)
[16:15] <vibhav> It took me some time to understand it :)
[16:15] <dholbach> highvoltage, nice idea
[16:16] <dholbach> vibhav, yes - sounds good
[16:16] <dholbach> asomething, maybe we can even steal some of the content for the packaging guide :-)
[16:16] <dholbach> highvoltage, I'd really like to get semi-regular hangouts going - as an experiment this cycle
[16:17] <asomething> sure, there's also stuff that's been done before that we can update: https://wiki.ubuntu.com/Packaging/Training/Logs
[16:17] <dholbach> ah yes, that might serve as a great basis
[16:17] <highvoltage> dholbach: nice :)
[16:17] <dholbach> it really doesn't hurt to repeat topics
[16:17] <dholbach> everytime at UOW or UDW there's new folks who listen to the same "get started" sessions :)
[16:18] <dholbach> ok, that sounds like a good start for Bhavani and others :)
[16:18] <dholbach> everyone OK, if I mail Bhavani and CC the lot of you? :)
[16:19] <dholbach> ok :)
[16:19] <dholbach> #action mail Bhavani with info about MOTU School discussions, CC everyone who showed interest in the topic
[16:19] <meetingology> ACTION: mail Bhavani with info about MOTU School discussions, CC everyone who showed interest in the topic
[16:19] <ajmitch> sure
[16:19] <dholbach> #topic review https://wiki.ubuntu.com/MOTU/FAQ/New_Draft (Bhavani Shankar)
[16:19] <dholbach> Bhavani updated the MOTU FAQ and wanted us to have a look at it
[16:19] <vibhav> That FAq is a bit short
[16:20] <dholbach> I think it'd be good if we all quickly went through it and commented in here, so he can review the log later on
[16:20] <tumbleweed> there are definitly language issues to sort out (I almost sat down and edited it, but wanted to chat to him first)
[16:20] <dholbach> vibhav: if you have some questions you feel should be answered, feel free to ask them in here
[16:20] <dholbach> ... so they can be addressed
[16:20] <vibhav> I dont have any questions till now
[16:21] <dholbach> for "What prerequisites do I need to start off ubuntu development?" I think I could borrow some text from the packaging guide
[16:21] <highvoltage> it would be nice if it had a bunch of packaging related questions and answers.
[16:21] <tumbleweed> It may be worth leaving in a question on mentoring that maakes it clear that there isn't any, just use #ubuntu-motu
[16:21] <vibhav> "Is MOTU Rocket Science?"
[16:22] <dholbach> tumbleweed: good point :)
[16:22] <highvoltage> does motu get a lot of questions about what ubuntu is? if that's the case then perhaps that page should also link to a more generic ubuntu FAQ first
[16:22] <tumbleweed> highvoltage: that also occured to me
[16:22] <tumbleweed> we do get lots of questions from new users asking what programming languages they need to know, that could probably be better addressed in the FAQ
[16:23] <dholbach> yep
[16:23] <highvoltage> tumbleweed: *nod*
[16:23] <dholbach> it sounds like we can very easily fix a couple of things in there, and also merge the missing old content from https://wiki.ubuntu.com/MOTU/FAQ
[16:23] <vibhav> A question like: Do I need to know any programming languages for MOTU?
[16:23] <dholbach> yes
[16:24] <dholbach> I think if we all take just a couple of minutes after meeting we should be able to sort most of this out very easily
[16:24] <vibhav> dholbach: I thought it was no, one can contribute to MOTU by only bringing upstream changes to Ubuntu or backporting fixes
[16:24] <dholbach> vibhav: can you elaborate? I'm not quite sure I understand
[16:25] <dholbach> bringing upstream fixes in and backporting them is definitely a good way to contribute - not the only one, but definitely a good one
[16:26] <asomething> vibhav, I think dholbach was saying "yes, we need that question in the FAQ" not answering it yes
[16:26] <highvoltage> it would be nice if we could link to my "where's the right place to submit my fix!?" flowchart once it exists :)
[16:26] <vibhav> dholbach: Sure, For example: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/873784 , Fixing it in Ubuntu only requires one to copy the changes from upstream and preapre a debdiff
[16:26] <vibhav> hush you stuipid bot
[16:26] <dholbach> yes, that's definitely a good way to contribute
[16:27] <vibhav> SO, Apparently, You dont need to know any programming language
[16:27] <vibhav> Just a knowledge of the debian build toolchain :)
[16:27] <dholbach> it helps, but there are tasks where you don't need to know much yet and where you can learn as you go :)
[16:28] <dholbach> alrightie, we should probably just all take a look at it later on - I'm sure Bhavani will appreciate it
[16:28] <dholbach> shall we move on?
[16:28] <vibhav> sure
[16:28] <dholbach> #topic Update from Developer Advisory Team
[16:28] <highvoltage> in many cases it's more important to know the policies around the languages, like python or perl or ruby each have their own additional policies and tricks in addition to the usual packaging things
[16:29] <micahg> PHP, R, haskell...
[16:29] <dholbach> highvoltage, yep - I'm sure we can phrase it in a general and reassuring way still :)
[16:29] <dholbach> asomething, broder, huats: did any of you prepare anything update-wise? :)
[16:30] <ajmitch> micahg: dont forget C#
[16:30] <highvoltage> heh, I didn't even realise that that could sounds scary
[16:30] <broder> nope, i haven't had time to do anything :-/
[16:30] <broder> sorry
[16:30] <asomething> dholbach, I didn't get around to much DAT wise in the past week
[16:30] <dholbach> the only thing I have from the advisory team is: in the last 3-4 weeks we had 5 people joining ~ubuntu-dev which is great :)
[16:30] <dholbach> and also we have the first very new people contributing to quantal
[16:31] <dholbach> although I expect more new folks getting involved in fixing their pet bug in precise still
[16:31] <dholbach> asomething, broder: I didn't get much done either - more in the next week :)
[16:31] <dholbach> any questions for the advisory team people?
[16:31] <geser> what is the Developer Advisory Team? hearing it the first time
[16:32] <dholbach> oh ok
[16:32] <ajmitch> top-secret cabal
[16:32] <vibhav> http://daniel.holba.ch/blog/tag/developer-advisory-team/
[16:32] <dholbach> forgive me, if I quote from the wiki page
[16:32] <dholbach> This team in terms of UbuntuDevelopment, tries to fulfill the following tasks in the Ubuntu world:
[16:32] <dholbach>     Reach out to new contributors, thank them for their work and get feedback.
[16:32] <dholbach>     Reach out to people who might be ready to apply for upload rights and help them.
[16:32] <dholbach>     Reach out to contributors that went inactive and get feedback from them and offer help.
[16:33] <vibhav> A seperate channel dedicated for new contributors run the the DAT for questions might help
[16:33] <dholbach> the idea of it was to close some of the gaps in process by social means - currently on the team are asomething, huats, broder, bhavi, warp10 and myself
[16:33] <dholbach> the team has been in place since some time in the last cycle
[16:33] <vibhav> Does the DAT have a facebook page or something
[16:34] <ajmitch> -motu itself is quiet enough, I don't think a separate channel is necessarily a good idea
[16:34] <asomething> dholbach, is your lightning talk about DAT from UDS online?
[16:34] <dholbach> and a report of the outreach to new contributors has largely been put together by asomething here: http://people.ubuntu.com/~andrewsomething/dat/
[16:34] <vibhav> Or the Ubuntu Developer Page on G+ could congratulate people who have got their first fixes into Ubuntu
[16:34] <dholbach> asomething, I don't know
[16:35] <dholbach> vibhav: up until now the DAT has mostly been reaching out to new contributors on a personal level - we never wanted it to become a mentoring team
[16:35] <vibhav> ah
[16:35] <dholbach> we felt that #ubuntu-motu or the motu mailing list were much better candidates to answer all kinds of questions
[16:35] <dholbach> geser, does that sort of answer your question?
[16:36] <geser> yes
[16:36] <dholbach> ok cool
[16:36] <dholbach> any more questions?
[16:37] <dholbach> ok, moving on then :)
[16:37] <dholbach> #topic Review https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative (dholbach)
[16:37] <broder> hey guys - need to run early. don't give me too many actions ;)
[16:38] <dholbach> another thing we discussed at UDS was to have regular bug fixing initiatives during the cycle and to use some of the time of the MOTU meetings to review the list and announce if afterwards, so new contributors have some predictably easy tasks to get started with
[16:38] <ajmitch> broder: that's just asking for it..
[16:38] <highvoltage> that's like fixit fridays right?
[16:38] <dholbach> #action broder to update https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative with new thoughts and clever ideas
[16:38] <meetingology> ACTION: broder to update https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative with new thoughts and clever ideas
[16:38] <dholbach> thanks broder
[16:38] <vibhav> What about a sponser-it-$DAY ?
[16:39] <ajmitch> highvoltage: right, but getting the list together of things to work on beforehand
[16:39] <dholbach> highvoltage, yes, but we'd keep the list up until the next motu meeting - so more like a "fix it week" or "fix it 14 days" :)
[16:39] <highvoltage> heh, ok
[16:39] <tumbleweed> highvoltage: also deals with all the newbies coming into the channel saying "what can I help with"
[16:39] <dholbach> vibhav: I would hope that the patch pilots would handle that
[16:39] <vibhav> ah fine
[16:40] <dholbach> so does the page look generally alright to you? anything we should change or add?
[16:40] <ajmitch> it's a good start for the week, we don't want to overload people with 500 things to fix
[16:40] <dholbach> the speling-errors-in-description are just for ubuntu packages, so we should be able to more easily get them in
[16:41] <dholbach> ajmitch, any other tasks we should be featuring? (maybe for intermediate contributors)
[16:41] <micahg> dholbach: security CVE fixes :)
[16:41] <vibhav> dholbach: backporting fixes?
[16:41] <dholbach> vibhav: like which? from which list?
[16:41] <ajmitch> the perennial favourites of the rc bugs list which I'll rewrite any day now(tm)
[16:41] <dholbach> micahg, if we can curate a list of a few which should be reasonably easy - that'd be awesome
[16:41] <micahg> dholbach: https://wiki.ubuntu.com/SecurityTeam/HighlightedPackages
[16:42]  * micahg isn't sure if they're easy though
[16:42] <ajmitch> security fixes is a good one
[16:42] <vibhav> dholbach: I dont know any lists though, but we could create a list for backporting fixes
[16:42] <ajmitch> they don't have to be easy
[16:42] <dholbach> micahg, awesome - just to be sure we could pack it into the "experienced contributors" section
[16:42] <dholbach> vibhav: the problem with curating lists of easy tasks is that it's easier if you have a list you can pick them off
[16:43] <dholbach> micahg, would you be fine with those bugs being on the UbuntuDevelopment/BugFixingInitiative page?
[16:43] <vibhav> Eg: A bug reported from 1.04 is fixed in an SRU in 11.10; There could a list for "SRUs missing from the Ubuntu version they have reported"
[16:44] <micahg> dholbach: sure, though the list changes every week, so you might just want to link to the page
[16:44] <dholbach> micahg, nice
[16:44] <asomething> I liked the idea of teaching about patch systems by finding a few good patches from: https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-reviewers&field.tag=patch
[16:44] <asomething> I can take an action item to add a handful to the wiki page
[16:45] <dholbach> awesome
[16:45] <dholbach> #action asomething to review https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-reviewers&field.tag=patch and add a few to the bug fixing page
[16:45] <meetingology> ACTION: asomething to review https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-reviewers&field.tag=patch and add a few to the bug fixing page
[16:45] <vibhav> But that would require some help from Launchpad too :)
[16:45] <dholbach> I also added the lists you mentioned to https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative/Organisation so it will be easier next time to pick tasks :)
[16:46] <micahg> well, over half the archive should be source format 3.0 by now
[16:46] <dholbach> ok, I think that should have us set up to announce our first bugfixing initiative early next week - what do you think?
[16:46] <ajmitch> sounds good
[16:46] <asomething> +1
[16:46] <dholbach> awesome
[16:46] <vibhav> dholbach: A list for fixing easy lintian errors
[16:47] <vibhav> Like "Outdated Standards Version"
[16:47] <vibhav> changing the source format to 3.0
[16:47] <vibhav> ... etc
[16:47] <dholbach> the issue with many of them is that these changes would better be done in Debian
[16:47] <highvoltage> well... sometimes those are better to fix in debian
[16:48] <vibhav> I almost forgot that
[16:48] <dholbach> so we can sync the changes and not keep a delta just for a string change which almost has no impact
[16:48] <dholbach> vibhav: but if you can think of something really easy for new contributors, feel free to add it to https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative/Organisation
[16:48] <vibhav> sure
[16:48] <dholbach> thanks
[16:48] <dholbach> #topic any other business
[16:48]  * dholbach reloads agenda page
[16:49] <dholbach> no, nothing new on there -- does anyone have anything they'd like to talk about?
[16:49] <vibhav> let me think
[16:50] <vibhav> Could the packaging guide be translated?
[16:50] <asomething> yes!
[16:50] <dholbach> ha, great you're asking!
[16:50] <vibhav> (Though it sounds silly)
[16:50] <dholbach> https://translations.launchpad.net/ubuntu-packaging-guide/
[16:50] <micahg> dholbach: well, maybe towards the end of the cycle, helping Debian reduce their RC bug count once they're frozen
[16:50] <vibhav> Oh wait, it can be
[16:50] <dholbach> and the translations updates will automatically flow into trunk
[16:51] <ajmitch> micahg: that should be sometime next month, probably worth doing that after feature freeze
[16:51] <dholbach> we are currently figuring out how we can deliver these changes in Ubuntu (separate packages for separate languages, etc.) and to figure out how complete we want translations to be before we ship them
[16:51] <dholbach> https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/961936 has more of this discussions
[16:51] <dholbach> micahg, yes, totally
[16:51] <vibhav> dholbach: I agree
[16:52] <dholbach> micahg, on the bug fixing initiative page we have some instructions for how to submit fixes to debian for packages which are not ubuntu-only
[16:52] <dholbach> in the future we might want to collaborate with the debian-derivatives to pick a few targets we want to advertise
[16:52] <micahg> dholbach: yes, but I'm talking about gleaning the Debian RC bug list that's unfixed and submitting patches
[16:52] <vibhav> dholbach: Lintian error for Ubuntu-only packages
[16:53] <micahg> then we can sync the fixes to Ubuntu
[16:53] <dholbach> micahg, yep, exactly
[16:53] <dholbach> sounds great to me - would you like to start doing that now already or in one of the next bug fixing initiatives?
[16:53] <ajmitch> micahg: I've got some work items about the reverse RC bugs page, where we've fixed something in ubuntu
[16:53] <micahg> gah, I forgot to do my work item of writing the criteria for dropping universe packages not in Debian
[16:54] <dholbach> micahg, ^? :)
[16:55] <vibhav> "check for packages that are worth removing from the next release"
[16:55] <micahg> dholbach: I think later in the cycle is fine (once Debian is frozen and that RC bug list is the release criteria)
[16:55] <dholbach> vibhav: yes, that's an action in here: https://blueprints.launchpad.net/ubuntu/+spec/other-q-motu-bof :)
[16:55] <vibhav> dholbach: I think  https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/961936 should be for all packages in the Ubuntu Archive
[16:55] <ajmitch> micahg: run wild with that chainsaw, please :)
[16:55] <dholbach> micahg, ok, great - I'll keep you in mind for that :-)
[16:56] <dholbach> vibhav: maybe it'd be a good topic to discuss in #ubuntu-translators
[16:56] <dholbach> is there any other business?
[16:57] <dholbach> #action dholbach to update minutes and wiki page
[16:57] <meetingology> ACTION: dholbach to update minutes and wiki page
[16:57] <dholbach> do we want to pick a chair for next time?
[16:57] <micahg> dholbach: here's a handy link foe the Debian bug initiative: http://upsilon.cc/~zack/hacking/debian/rcbw/
[16:58] <dholbach> micahg, thanks, noted on the ..../Organisation page
[16:58] <tumbleweed> yeah, we can't make you chair them all :)
[16:58] <asomething> dholbach, not if we don't know what time next time is
[16:58] <ajmitch> broder volunteered, didn't he? :)
[16:58] <dholbach> especially if we should decide in the meantime that all meetings are going to happen at 4 my time :-P
[16:58] <dholbach> ajmitch, haha
[16:59] <dholbach> asomething, yes :)
[16:59] <dholbach> ok, let's leave it open until next time, then - I'm sure we'll find somebody
[16:59] <dholbach> but I'll add it as a standing agenda item
[16:59] <dholbach> thanks a lot everyone
[16:59] <vibhav> There should be an FAQ on how does one apply to be a maintainer for an orphaned package
[16:59] <dholbach> this was an awesome MOTU meeting
[16:59] <ajmitch> thanks
[16:59]  * dholbach hugs you all
[16:59] <dholbach> #endmeeting
[16:59] <meetingology> Meeting ended Thu May 24 16:59:44 2012 UTC.
[16:59] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-24-16.01.moin.txt
[16:59] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-24-16.01.html
[17:00] <vibhav> Good night everybody!
[17:00] <dholbach> night :)
[17:00] <highvoltage> broder: we should probably talk about those facebook ads some time :)