[19:49] <greg-g> with 10 minutes to go, anyone here coming to the How to Run a Bug Jam session?
[19:53] <rick_h_> no <3 for greg-g  :(
[19:53] <greg-g> guess not :)
[19:57] <greg-g> 3 minutes till go time
[19:57] <pep> "08 Jul 11:00 UTC: Asia and Oceania Ubuntu Membership Approval Board" is twice in the topic by the way.. :)
[19:59] <greg-g> popey: see above comment by pep
[19:59] <greg-g> thanks pep
[19:59] <pep> np :)
[20:00] <pep> I'm already in the channel for the ubuntu-marketing meeting later tonight... I thought it might be interesting on the bugjam too
[20:00] <greg-g> cool, welcome
[20:00] <greg-g> well, it is time!
[20:00] <pep> but I won't make the bugjam though as I have exams, so it's not a real participation :)
[20:00] <greg-g> Hello everyone!  Welcome to the second session of "How to Run a Bug Jam"
[20:00] <greg-g> my name is Greg Grossmeier and the leader of the Michigan (US) LoCo Team
[20:01] <greg-g> how many people are here for the session?
[20:01] <greg-g> raise your hands -   o/
[20:02]  * cactaur raises
[20:02] <Flannel> \o/
[20:02] <greg-g> hello cactaur and Flannel representing California
[20:02] <greg-g> well, if there is no one else we should get started
[20:03] <greg-g> this is the main page we're going to use for coordinating the jam - https://wiki.ubuntu.com/GlobalBugJam
[20:03] <greg-g> and this page is what we're going to discuss today  - https://wiki.ubuntu.com/GlobalBugJam/Prep
[20:04] <greg-g> so, first thing first to remember is..
[20:04] <greg-g> it doesn't matter how many bugs are triaged or how many people showed up, all that matters is that people have a good time
[20:04] <greg-g> that is what gets people participating
[20:05] <greg-g> so you should measure success by how good a time people had, and how you take notes to make things better next time, etc.
[20:05] <greg-g> So, venues..
[20:05] <greg-g> You need some place that has power, internet, and places to sit for everyone that is going to show up (obviously)
[20:05] <greg-g> but, it also needs to be conducive to listening to one person talking for a little bit and asking questions
[20:06] <greg-g> some good places are offices of Open Source Friendly businesses or even Library conference rooms (where Michigan had ours) or College/University rooms
[20:06] <greg-g> so really, anywhere that is comfortable and conducive to group work.
[20:06] <greg-g> (so many not a classroom if some people are afraid/scared from them ;) )
[20:07] <greg-g> any questions on venues? or other suggestions before we move on?
[20:07] <cactaur> Should the venues be places visible to others?
[20:07] <cactaur> Like, where people might get interested in Ubuntu?
[20:07] <greg-g> cactaur: they don't have to be, but they of course can be
[20:08] <greg-g> you of course want your advertising for the event to be in public places to get outside interest
[20:08] <greg-g> and promotion is the next topic :)
[20:08] <greg-g> most of the get togethers for the michigan team have been more "private" than public, except for our release parties at pubs
[20:09] <greg-g> for example our packaging jam was at someone's house and our bug jams have been at either college classrooms or library conference rooms
[20:09] <greg-g> but that is just one way of doing it
[20:09] <greg-g> any other questions on venues?
[20:10] <cactaur> nah, that's good for me.
[20:10] <greg-g> cool
[20:10] <greg-g> so the biggest thing to help with promotion is to ensure that your loco is on the wiki page
[20:10] <greg-g> since we'll be blogging/twittering, and generally pointing people to that page
[20:10] <greg-g> also, your local team mailing list
[20:10] <greg-g> and your local lug(s) mailing list(s) is another place where you might want to send a mail
[20:11] <greg-g> lots of LoCo people are also local LUG people so with that overlap it's easy to get the word out
[20:11] <greg-g> other places to get the word out include local computer stores and shows
[20:11] <greg-g> like, before they went out of business, our local CompUSA had a bulletin board where people could post stuff
[20:11] <greg-g> and in general, blogging about it on planet ubuntu, your blog, twitter, etc. etc. is a good way to promote it
[20:11] <greg-g> oh, your local area in the ubuntu forums if you have one
[20:12] <greg-g> any other ideas for promotion techniques?
[20:12] <greg-g> one idea from the last "howto" I ran was to get the local newspaper/magazine/radio station to help promote
[20:13] <greg-g> have them come and cover the event and just ask that they mention it a few times before it happens to promote it
[20:13] <greg-g> I've never done that personally, but it seems like it could work well
[20:13] <greg-g> we (the michigan team) are going to try and do it for the GBJ and see how it goes
[20:14] <greg-g> anything else for Promotion before we get to the "Pre-Bug Jam Checklist of Awesome"?
[20:15]  * greg-g waits as copy/pasting is fast :)
[20:15] <greg-g> ok..
[20:15] <greg-g> Checklist of Awesome:
[20:15]  * cactaur has nothign.
[20:15] <greg-g> Checklist of Awesome:
[20:15] <greg-g> whoops
[20:15] <greg-g> First thing that is critical on the Checklist of Awesome is: ensuring everyone has a Launchpad Account
[20:15] <greg-g> without that, the participants can't make any bugs better themselves
[20:16] <greg-g> Checklist of Awesome number 2: 5-a-day preparedness
[20:16] <greg-g> does everyone know what 5-a-day is?
[20:16] <cactaur> 5 bugs a day?
[20:16] <greg-g> yep
[20:16] <greg-g> 5-a-day is a way to have the amount of work you are doing on bugs to be recorded.  but not only for you, but your loco team as well
[20:17] <greg-g> there are instructions at wiki.ubuntu.com/5-a-day
[20:17] <greg-g> cactaur: did that answer your question?
[20:17] <cactaur> yeah
[20:17] <greg-g> it is a way to show progress for you and your team thus encouraging participation
[20:17] <greg-g> cool
[20:18] <greg-g> Checklist of Awesome number 3: what package(s) does your group love?
[20:18] <greg-g> to make things like this matter to the participants you don't want to triage bugs for a package no one uses.  Find popular packages that need some love, and get a list out for that package.  At the end of the day people will feel like they really helped
[20:18] <HereBePython> greg-g, pedro said he will prepare a list of bug triage examples for as many categories of bugs as possible so new comers can have a look and learn
[20:19] <greg-g> HereBePython: right on!
[20:19] <HereBePython> and infact, add it to HowToTriage page ;)
[20:19] <greg-g> good deal
[20:19] <greg-g> thanks HereBePython
[20:19] <HereBePython> :)
[20:19] <greg-g> a good idea is to break up into groups of ~4 people who are interested in similar things to work together
[20:20] <greg-g> Checklist of Awesome 4: irc channel for pasting links
[20:20] <greg-g> make sure everyone knows where the loco's irc channel is and how to get on
[20:20] <greg-g> and of course, #ubuntu-bugs will be rockin it during the GBJ with experienced triagers
[20:21] <greg-g> so, loco specific questions can go in your channel while requests for help from the experienced people can go in -bugs
[20:21] <greg-g> that is probably easier to do than setting up gobby etc
[20:22] <greg-g> oh, and there should be at least one person in #ubuntu-bugs from your group to coordinate with everyone
[20:22] <greg-g> we don't want another loco to come along and start working on the same list
[20:22] <greg-g> so we'll use #ubuntu-bugs for your loco to say "we're working on foo!" or whatever
[20:22] <greg-g> and, that Checklist of Awesome can be found on the GlobalBugJam/Prep wiki page.  So, go over that and send out instructions for the simple things before the day of the event
[20:23] <greg-g> at a previous session someone asked/mentioned to set up GPG keys at the event...
[20:24] <greg-g> those are not needed for triaging bugs, but if people want to set them up, that is fine.  Just know that a keysigning party can take a while :)
[20:24] <greg-g> so, the rundown of the checklist:
[20:24] <greg-g> Checklist of Awesome: 1) Launchpad 2) 5-a-day 3) Popular Packages 4) IRC channel information  5) FUN!
[20:24] <greg-g> anthing else that you can think of that should go there?
[20:25] <greg-g> so, running the Jam:
[20:26] <greg-g> OK, so something we've had success with was a presenter go over a few examples so new people get an idea of what to do
[20:26] <greg-g> if you have experienced triagers already there, you can break them off into groups with other peopole
[20:26] <greg-g> so new people have an experienced person in their group to help them
[20:26] <greg-g> or you can have one smart person up front answering questions
[20:26] <greg-g> what we did is started working on our own list of bugs
[20:27] <greg-g> and if someone had a question they would yell out the number, and then the person connected to the projector would load it up
[20:27] <greg-g> and we would look through it, and decide what to do
[20:27] <greg-g> And as HereBePython just let us know, pedro will have a list of good example bugs to go through as a group if you want
[20:28] <greg-g> at the very minimum, if you get lost, frustrated, or it's turning into a disaster, you can always concentrate on just teaching people little things.
[20:28] <greg-g> I suspect we'll get a few reports that start off with "We started triaging and then decided to go to the pub instead."
[20:28] <greg-g> So whatever works for you. :D
[20:29] <greg-g> Does Running the Bug Jam make sense now?
[20:29] <pep> I found it very instructive
[20:29] <pep> even for later bugjams
[20:29] <greg-g> I have one more section too :)
[20:30] <greg-g> pep: yeah, this is just general advice really
[20:30] <greg-g> not specific to the GBJ, but to Bug Jams in general
[20:30] <pep> yeah
[20:30] <greg-g> But yeah, after the bug jam be sure to put up pictures and blog it
[20:30] <greg-g> and of course, Plan Future Bug Jams ! :)
[20:31] <greg-g> from my experience it is a good way to get participation from your community by being a low enough bar for entry that more people will show up
[20:31] <greg-g> thus, having a good time and going out for socializing after (beers) is a good idea
[20:32] <greg-g> and with that, if there are no more questions/comments/suggestions, this is the end of the HowTo
[20:33] <cactaur> greg-g: Should our bug jams span the whole 3 days? Or would just doing it one of the days also work?
[20:33] <pep> yeah... I am going to investigate 5-a-day a little more on my side...
[20:33] <greg-g> cactaur: good question.  A one time event sometime during that span is probably good for a physical bug jam.  of course you are welcome to continue to coordiante virtually the rest of the span
[20:34] <greg-g> pep: 5-a-day is a good way to encourage your team's participation, I have found
[20:35] <greg-g> anything else?
[20:35] <pep> yeah.. but I have seen people reluctant to the system because they knew they wouldn't be able to triage 5 bugs a day... but this is on a more general basis really...
[20:36] <greg-g> pep: yeah, I can see that, but really, just do how much you can
[20:36] <greg-g> I havne't been doing 5 a day lately (MUCH less) but I am still participating
[20:36] <pep> well 5 bugs a day is ok, but 5 bugs a day *every* day is the part that scares ;-)
[20:36] <pep> but I suppose as long as you participate it has a sense
[20:36] <greg-g> pep: right
[20:37] <greg-g> it is just that 5-a-day sounds better than As-many-as-you-can-each-week ;)
[20:38] <pep> yeah :)
[20:38] <greg-g> anything else?
[20:38] <pep> not for me
[20:38] <pep> from*
[20:38] <greg-g> Well, thank you everyone for showing up and I hope this has helped you plan for a Great Bug Jam!
[20:38] <greg-g> you are of course welcome to ping me in #ubuntu-us-mi if you have any other questions/comments
[20:39] <pep> thank you!
[20:39] <greg-g> you're welcome!
[20:42] <Grantbow> so the logs are here?  http://irclogs.ubuntu.com/
[20:43] <greg-g> Grantbow: correct
[20:44] <greg-g> for this channel and other channels related to Ubuntu
[20:44]  * greg-g goes back to -us-mi
[22:00] <owh> Hello all.
[22:00] <pep> Hello
[22:00] <bbyever> hi
[22:00] <owh> #startmeeting
[22:00] <MootBot> Meeting started at 16:01. The chair is owh.
[22:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:00] <owh> Hello and welcome to the Ubuntu Marketing monthly meeting. The agenda for today is at https://wiki.ubuntu.com/MarketingTeam/Meetings/Agendas/2008-07-05
[22:00] <owh> Our first point of discussion are the minutes for last month's meeting: https://wiki.ubuntu.com/MarketingTeam/Meetings/Minutes/2008-06-07
[22:01] <owh> Is everyone happy with that?
[22:01] <pep> jupp
[22:01] <owh> Can I have a person to second that?
[22:01] <Flannel> I'll second
[22:01] <owh> [AGREED] Meeting minutes for 2008-06-07 accepted as is.
[22:01] <MootBot> AGREED received:  Meeting minutes for 2008-06-07 accepted as is.
[22:02] <owh> First action item from last month:  hubuntu and pep to investigate spreadubuntu.com and report to the list.
[22:02] <pep> Yes.
[22:02] <owh> Give us an update if you will.
[22:03] <pep> We have advanced, everything is viewable here: https://wiki.ubuntu.com/MarketingTeam/SpreadUbuntu
[22:03] <pep> There is the wiki, the mailing list archive, and the discussions held.
[22:03] <Flannel> We've been in contact with the old chairpersons from the various projects that were related to spreadubuntu
[22:03] <pep> In short: we are taking the project back, called SU, composed of a diy and a Site part.
[22:04] <pep> Yes, old involved have been contacted.
[22:04] <owh> What kind of reception did you receive?
[22:04] <pep> From the old team, we got one web developer motivate d to help so that's good news
[22:04] <pep> we got very positive reception
[22:05] <pep> as well as permission to delete the two old projects on launchpad end start again from scratch
[22:05] <pep> This is in process
[22:05] <Flannel> The new design is roughly: We have the DIY site (diy.spreadubuntu.com) that will be the repository of materials for various teams and people in general,
[22:05] <pep> projects are awaiting deletion from LP staff.
[22:05] <bbyever> I found a bazr branch with stuff related to SU
[22:05] <owh> Are there things that the Ubuntu Marketing team can provide to assist?
[22:05] <Flannel> and then the spreadubuntu.com site will be an "about" sort of site, explaining about Ubuntu, and linux, and things like that
[22:05] <bbyever> bzr
[22:06] <bbyever> here: https://code.edge.launchpad.net/~ubuntu-marketing/+branches?field.lifecycle=ALL&field.lifecycle-empty-marker=1&field.sort_by=by+project+name&field.sort_by-empty-marker=1
[22:06] <pep> bbyever: yes, it is old code, when Su was supposed to be written for wordpress.
[22:06] <pep> as well as for another cms
[22:06] <bbyever> pep: is it any use?
[22:06] <Flannel> bbyever: Theres actually a few old branches of varying completion
[22:06] <pep> no, I talked with the main contributor Dan Buch (who wrote almost everything) and he thought like me: delete and start again
[22:07] <owh> Was there any indication on why the project was abandoned?
[22:07] <Flannel> bbyever: We're taking bits an pieces of each, mostly design related.  The code itself will depend on what we decide to actually use
[22:07] <Flannel> owh: Lack of interest, attrition, etc.
[22:07] <bbyever> Flannel, pep: ok
[22:07] <Flannel> Or rather, lack of time for the people interested
[22:07] <owh> Are there any questions from the floor about pep and Flannel's summary?
[22:07] <pep> Yes, I suppose interest to develop just fell.
[22:08] <owh> On to the next item.
[22:08] <Flannel> owh: As per your "What can Marketing do"  The "spreadubuntu.com" section will be put together by the marketing team.  We're hoping to reach out to new users, etc.
[22:09] <Flannel> owh: So, it'll be a lot of writing content targetting "regular people"
[22:09] <owh> Cool. I'll volunteer for that when the time comes ;-)
[22:09] <owh> Moving on. We'll skip the hubuntu booking, since we're here :)
[22:09] <pep> Flannel: that's talking about the "Site" part right?
[22:10] <owh> [Topic] Summarise list discussion about team structure proposals
[22:10] <MootBot> New Topic:  Summarise list discussion about team structure proposals
[22:10] <Flannel> pep: Thats the spreadubuntu part, not the diy part, yeah.
[22:10] <pep> ah yes, srry
[22:10] <pep> (still asleep)
[22:10] <owh> I've not seen any proposals to the list beyond the one that JV provided. Is this now a moot point?
[22:11] <Flannel> owh: I don't believe theres been any follow up on that either.  The parties involved may have lost interest
[22:11] <pep> I don't believe the need for a restructuring so urgent personally...
[22:11] <pep> +1 Flannel
[22:12] <owh> Any counter opinions, since we had a rather large discussion about it last meeting and on the list?
[22:12] <pep> I don't understand why nobody showed up tonight since it seemed to worry many people...
[22:12] <Flannel> owh: I believe that renders the next agenda topic moot as well.
[22:12] <Flannel> Or at least, if it is the case
[22:12] <owh> [Idea] No requirement to change the team structure. No need for a leader. Continue as a collective.
[22:12] <MootBot> IDEA received:  No requirement to change the team structure. No need for a leader. Continue as a collective.
[22:13] <owh> Does that cover it?
[22:13] <pep> Good for me.
[22:13] <bbyever> +1
[22:13] <Flannel> +1
[22:13] <owh> [Agreed] No requirement to change the team structure. No need for a leader. Continue as a collective.
[22:13] <MootBot> AGREED received:  No requirement to change the team structure. No need for a leader. Continue as a collective.
[22:13] <owh> We can skip the voting.
[22:13] <owh> Right, onto bbyever's topic.
[22:13] <owh> [Topic] Decide what projects will be taken into action and actually start them.
[22:13] <MootBot> New Topic:  Decide what projects will be taken into action and actually start them.
[22:14] <owh> bbyever: Over to you.
[22:14] <bbyever> thanks
[22:14] <bbyever> ﻿well, there are many projects started, but i've only seen focus in SU... will we all concentrate on SU right now, or will the others also be taken into action
[22:15] <owh> Which other projects are you talking about?
[22:15] <Flannel> I don't see a reason why others wouldn't be considered.  We just only have one (SU) currently to my knowledge
[22:15] <bbyever> https://wiki.ubuntu.com/MarketingTeam/Projects
[22:15] <pep> Well any projects are still viable
[22:16] <pep> people just need to *do* them
[22:16] <Flannel> bbyever: The firefox menu bar seemed to be met with some enthusiasm, but I believe Mr Botscharow has had his freetime reduced
[22:16] <pep> wow, my name is in there o.O
[22:17] <owh> The plug-in can be simply created using a custom google search IIRC.
[22:17] <pep> Concerning diy: I believe the project is active, interested people should join the team on launchpad and the mailing list, I actually wanted to wait for the 2 old projects to be deleted and the new one to be created in launchpad to announce it to the list.
[22:17] <Flannel> bbyever: A lot of the Projects listed on that page are old.  That doesn't mean they need to be removed, or stopped, merely that no one currently is championing them
[22:17] <owh> I started one, but google refused to do a custom search with anything other than my private google gmail address.
[22:17] <bbyever> ok, so maybe we should update the page to reflect actual activity?
[22:18] <pep> well apart from the projects statuses, it reflects it ok...
[22:18] <Flannel> bbyever: It may be pertinent to change their status, or have a deferred section for projects.  An Active table and an inactive table.
[22:18] <bbyever> ok
[22:18] <owh> What about the discussions we had last month. Nothing in that is actually directly doing what we said we would be doing.
[22:18] <Flannel> owh: The spreadubuntu project is.
[22:19] <pep> yes
[22:19]  * owh hunts for a suitable copy/paste.
[22:19] <pep> I think it is too...
[22:19] <Flannel> owh: I assume you're referring to helping the LoCos etc do their thing?
[22:19] <owh> Yup
[22:19] <Flannel> owh: The DIY section of the spreadubuntu project does just that.
[22:19] <owh> Ah, you're sneeky :)
[22:19] <owh> I forgot :)
[22:20] <owh> Fine. So, where does this leave bbyever's topic?
[22:20] <bbyever> i had something else...
[22:20] <pep> well we're not al concentrating on SU
[22:20] <owh> A new topic bbyever?
[22:20] <Flannel> I think we should update the statuses of those projects to reflect their current activity.
[22:20] <pep> Yeah
[22:20] <bbyever> no, just like a sub point in my topic
[22:21] <owh> Cool Flannel. Any volunteers?
[22:21] <owh> bbyever: Bring it on :)
[22:21] <Flannel> They shouldn't be removed, because they have good ideas, and hopefully can be seen to fruition.
[22:21] <bbyever> ﻿i thought maybe it would be better in terms of organization, to assign (or update the current assignments of projects) to people who are interested in helping out
[22:21] <owh> What about adding a column that points to a progress report Flannel?
[22:21] <pep> The question is if people are active in our team, a part from SU working group. Maybe if they see that this SU is active, it will motivate others to start off other projects again, we are enough to do several once imo...
[22:22] <owh> bbyever: Well, when someone actively takes up such a role, that would be when that changes, would it not?
[22:22] <pep> ones*
[22:22] <Flannel> owh: I think the Status table covers that.  Also, each subsection (each Project) should include a checklist/todo list
[22:22] <bbyever> ok
[22:23] <owh> Flannel: How do you want to "encourage" that?
[22:23] <Flannel> I agree with pep.  Activity begets activity
[22:24] <pep> yes
[22:24] <owh> Flannel: I mean, the "check list/todo".
[22:24] <Flannel> owh: We should probably write up a quick "How to Start a Project" paragraph for that page
[22:25] <owh> That's what I was looking for :)
[22:25] <owh> You volunteering?
[22:25] <Flannel> I don't mind heading it up, sure.
[22:25] <owh> [Idea] Flannel to write a "How to Start a Project" paragraph for the UM/Projects page.
[22:25] <MootBot> IDEA received:  Flannel to write a "How to Start a Project" paragraph for the UM/Projects page.
[22:25] <owh> Happy with that?
[22:25] <Flannel> +1
[22:25] <pep> As soon as SU is ready, in a couple of days imo... somebody could write an encouraging email to the list... taking example on SU to encourage other projects of the marketing team..
[22:26] <pep> +1
[22:26] <owh> [Agreed] Flannel to write a "How to Start a Project" paragraph for the UM/Projects page.
[22:26] <MootBot> AGREED received:  Flannel to write a "How to Start a Project" paragraph for the UM/Projects page.
[22:26] <owh> Does that leave anything that's open?
[22:26] <pep> don't forget to mail i tto the list too... not sure that many check out the wiki very often
[22:26] <Flannel> pep: We'll work that out on our own
[22:27] <owh> That's more of an SU update really isn't it?
[22:27] <owh> bbyever: Are you happy with the outcome of that?
[22:27] <Flannel> yeah, and the SU project will take care of it
[22:27] <pep> yeah, I suppose... even if it covers the same role in a way
[22:27] <bbyever> yep
[22:27] <owh> [Topic] Other Issues
[22:27] <MootBot> New Topic:  Other Issues
[22:27] <owh> Any one got anything they wish to air?
[22:28] <owh> I'll add one. We should be actively providing status updates to the list to encourage activity.
[22:28] <bbyever> +1
[22:28] <pep> I find that we're not using the wiki enough too...
[22:28] <owh> Perhaps once a week, a single paragraph of what we did.
[22:29] <Flannel> Once a week is probably too frequent
[22:29] <owh> pep: You mean to document things?
[22:29] <bbyever> once every 2 weeks would be fine imho
[22:30] <owh> Is this going to be a personal update, or a project update?
[22:30] <pep> I mean in general for workflow and organization... task lists, todos, project descriptions, etc... I have the feeling it could be used better... but the source is probably a motivation/interest lack...
[22:30] <Flannel> It'll move at a different pace for most projects.  Whoever chairs said projects should have a good feel for how frequently they should be updating
[22:30] <pep> or just report substantial updates in a project...
[22:30] <owh> pep: To do that, you need to create infrastructure and put policies in place, otherwise it will not happen.
[22:30] <Flannel> yeah, a bunch of reports of "nothing much happened" isnt going to spur activity
[22:30] <bbyever> owh: i'd say project update
[22:31] <owh> Flannel: Can you add that to the paragraph you're writing?
[22:31] <Flannel> owh: I'll be sure to include it
[22:31] <Flannel> and pep, I'll mention keeping your wiki updated too
[22:31] <owh> So, is there anything else exciting happening in the UM sphere?
[22:32] <owh> [Idea] Projects should provide regular updates to the UM list.
[22:32] <MootBot> IDEA received:  Projects should provide regular updates to the UM list.
[22:32] <pep> Ok (I hope to be working alot with the wiki in an effective way for SU)
[22:32] <pep> I can't think of anything else...
[22:33] <owh> Everyone cool with that idea?
[22:33] <pep> +1
[22:33] <bbyever> +1
[22:33] <owh> [Agreed] Projects should provide regular updates to the UM list.
[22:33] <MootBot> AGREED received:  Projects should provide regular updates to the UM list.
[22:33] <owh> [Topic] Next meeting, time and place.
[22:33] <MootBot> New Topic:  Next meeting, time and place.
[22:34] <bbyever> could i say something else
[22:34] <Flannel> First Saturday of next month is the second
[22:34] <owh> Other than that I'll be on a stage MC-ing a few hours later, it's good for me :)
[22:34] <owh> bbyever: Of course.
[22:35] <owh> [Idea] Next meeting: 2 August 21:00 UTC
[22:35] <MootBot> IDEA received:  Next meeting: 2 August 21:00 UTC
[22:35] <bbyever> ﻿someone posted something about an ubuntu desktop course, which seemed interesting to me. i investigated and it seems the project is inactive... i was wondering if we could take it into the markeitng team and revive it, what do you think?
[22:35] <pep> +1, no reason for change....
[22:35] <owh> [Agreed] Next meeting: 2 August 21:00 UTC
[22:35] <MootBot> AGREED received:  Next meeting: 2 August 21:00 UTC
[22:35] <pep> sure bbyever, you are welcome to take up the lead of this project if it really is inactive!
[22:36] <Flannel> bbyever: What is an "Ubuntu Desktop Course"?
[22:36] <bbyever> let me find the link...
[22:36] <pep> it seems close enough to a marketing activity to me... :)
[22:37] <bbyever> https://edge.launchpad.net/ubuntu-desktop-course
[22:37] <owh> Remember, the idea is not for us to start writing marketing materials, but to coordinate other people's efforts so everyone benefits.
[22:37] <owh> Uh, that's not right.
[22:37] <owh> Carry on :)
[22:38] <Flannel> Just in passing, I'd like to mention that Global Bug Jam is coming up on August 8-10, https://wiki.ubuntu.com/GlobalBugJam  You might want to touch base with your LoCos and see if you can participate
[22:38] <owh> bbyever: Perhaps, rather than "take ownership", join the group and start helping?
[22:38] <bbyever> well sent a mail to Torsten Spindler asking about the activity of the project and he hasnt replyed..
[22:39] <bbyever> that was like 5 days ago
[22:39] <bbyever> i also sent a mail to their list and havent recived a reply
[22:39] <owh> What about other contributors?
[22:39] <pep> mhh..; give him another two days and contact another main contributor...
[22:40] <pep> how about you report us about this project for next meeting, or on the list as soon as you know more?
[22:40] <bbyever> there hasnt been any activity in 9 weeks
[22:40] <owh> bbyever: Remember, some people may be doing completely different things and may not be "Ubuntu" 24/7
[22:40] <Flannel> bbyever: He was on IRC a week ago
[22:40] <owh> bbyever: That's not a dead project, just slow :)
[22:40] <bbyever> ok, i'll try to contact more people in the project and i'll report back ehre
[22:40] <bbyever> here*
[22:40] <pep> yeah... looks not completely dead to me to...
[22:40] <owh> [Idea] bbyever to report back on the Ubuntu Desktop Course
[22:40] <MootBot> IDEA received:  bbyever to report back on the Ubuntu Desktop Course
[22:41] <owh> Also, note that there is a set of ubuntu course material flying around.
[22:41] <owh> bbyever: You happy with reporting back next month?
[22:41] <bbyever> yep
[22:41] <owh> [Action] bbyever to report back on the Ubuntu Desktop Course
[22:41] <MootBot> ACTION received:  bbyever to report back on the Ubuntu Desktop Course
[22:42] <owh> As we say in holland: Een Maal, Andermaal verkocht.
[22:42] <owh> That is, going once, going twice, sold :)
[22:42] <owh> Thanks in advance to bbyever for being our scribe today.
[22:42] <bbyever> np
[22:42] <owh> Thank you all for attending today.
[22:42] <owh> #endmeeting
[22:42] <MootBot> Meeting finished at 16:44.
[22:42] <owh> WhooT!
[22:43] <pep> quick
[22:43] <pep> :)
[22:43] <owh> No IRC interruptions, no fights, all good :)
[22:43] <pep> yeah
[22:43] <owh> Right, so lets get on with it :)
[22:43] <pep> owh: are you up-to-date with SU?
[22:43] <pep> now that we meet :)
[22:43] <owh> We should move to #u-m to continue this conversation.
[22:43] <pep> yeah!
[22:43] <pep> true!
[22:44] <bbyever> ok