[10:08] <GiulioC> hello
[15:34] <rod> exit
[15:48] <maheshmohan> Hi, I think it's almost time to start the meeting
[15:49] <UndiFineD> o/
[15:49] <Muscovy> Hello.
[15:53] <Omega> Almost meeting time/
[15:53] <Omega> Too bad I'm still sick.
[15:54] <aprilg> hi everyone
[15:54] <Omega> I was wondering where you were.
[15:54] <Omega> Hey.
[15:54] <aprilg> my internet connection's choppy. so I might get disconnected any time :(
[15:54] <aprilg> hey Omega
[15:55] <aprilg> a lot of people getting sick nowadays
[15:55] <Muscovy> Hello, you two.
[15:55] <aprilg> hey Muscovy
[15:59] <Muscovy> Are we just about ready?
[16:00] <Omega> I think we are.
[16:00] <UndiFineD> making a cup of coffee
[16:01] <aksharpatel47> Just arrived.. Has the meeting started?
[16:01] <Muscovy> Almost.
[16:02] <fieldse_> greetins
[16:02] <fieldse_> the time is?
[16:02] <Muscovy> If anyone hasn't pulled their branches in the last 12 hours or so, pulling it would be suggested.
[16:02] <fieldse_> hm, weird. I seem to be still logged in, wtf. brb
[16:04] <UndiFineD> :)
[16:05] <Muscovy> http://openetherpad.org/UbuntuTourAgenda
[16:06] <Omega> !meeting start
[16:06] <Omega> :>
[16:06] <Muscovy> akshrapatel, aprilg, brandonj, Crisco, Dykam, fieldse, jeremymikkola, maheshmohan, Omega, popey, UndiFineD
[16:07] <UndiFineD> present
[16:07] <aksharpatel47> present
[16:07] <aprilg> here
[16:07] <Omega> present
[16:07] <maheshmohan> present
[16:07] <jeremymikkola> sort of here (-:
[16:07] <Muscovy> Let the meeting begin!
[16:07] <Muscovy> Shall we cover the branches first?
[16:08] <fieldse_> present, sort of. Don't know how I manage to be logged in twice, ehh
[16:08]  * Dykam is here, but only for 25%
[16:08] <fieldse_> Link to agenda, please?
[16:08] <aprilg> http://openetherpad.org/UbuntuTourAgenda
[16:08] <Omega> http://openetherpad.org/UbuntuTourAgenda
[16:08] <Muscovy> I'll topic it for now.
[16:09] <Dykam> it was already in the topic :]
[16:09] <fieldse_> doh. thx.
[16:09] <Muscovy> Now it's unmissable.
[16:09] <Muscovy> So, we've got two branches currently, https://code.launchpad.net/~ubuntu-tour/ubuntu-tour/maverick for writing, https://code.launchpad.net/~ubuntu-tour/ubuntu-tour/code-development for code.
[16:10] <Omega> I wish more of the programmers were here.
[16:10] <aksharpatel47> I'm a python programmer
[16:10] <aksharpatel47> though learning gtk
[16:10] <aksharpatel47> along with my MBA exams
[16:10]  * UndiFineD is a php programmer
[16:10] <Omega> As am I.
[16:10] <Omega> Okay, braches.
[16:10]  * Dykam is, not python, but that is not a problem. just busy
[16:10] <UndiFineD> willing to learn python though
[16:10] <maheshmohan> am into pyGTK
[16:11] <Muscovy> The two propositions in the agenda are to make a translation branch, and to merge the existing branches.
[16:12] <Muscovy> Personally, I think we should keep everything all in one branch, now that the code is stable.
[16:12] <Omega> Yeah
[16:12] <maheshmohan> yes. Why we have two branches? Any advantage with that? Correct me if I'm wrong
[16:12] <Muscovy> More than one branch just means manual merges, and people putting things in the wrong one.
[16:12] <Omega> maheshmohan: The code in the other branch was experimental.
[16:12] <Muscovy> It was done because in the first two days or so, the code for the tour was getting wacky.
[16:12] <UndiFineD> I prefer one branch too
[16:13] <aksharpatel47> I'm all for one branch
[16:13] <Muscovy> Any objections?
[16:13] <Omega> No, okay, decided.
[16:14] <Muscovy> Alright. We can get that updated later.
[16:14] <Omega> A definitive list of tours and categories
[16:14] <Muscovy> I'd say we need that.
[16:14] <aksharpatel47> The question would then be, why are we making this tour
[16:15] <aksharpatel47> to whom are we targeting
[16:15] <Omega> New users.
[16:15] <aksharpatel47> Absolutely Newbies?
[16:15] <Muscovy> Transitional or brand new users.
[16:15] <aksharpatel47> Okay
[16:15] <UndiFineD> beginners, kids, transitional
[16:15] <Omega> People that don't know their way around yet.
[16:16] <Muscovy> Which also means the tour needs a good UI.
[16:16] <aksharpatel47> Then we can create levels of our tours
[16:16] <aksharpatel47> Like Absolutely beginners, Transitional
[16:16] <aksharpatel47> and so on
[16:16] <aksharpatel47> And about a Good UI, the new Ubuntu Image Slideshow is a great design
[16:17] <Muscovy> The installer one?
[16:17] <aksharpatel47> ya
[16:17] <Omega> https://wiki.ubuntu.com/UbuntuTour/Todo#List of Pages
[16:17] <aprilg_> got disconnected. which topic are we on now?
[16:18] <aksharpatel47> Good UI for the app
[16:18] <Omega> Actually, we were talking about the list of categories.
[16:18] <Omega> But we got diverged.
[16:18] <Omega> So, back to the list.
[16:18] <aksharpatel47> okay
[16:19] <Omega> The UI comes later.
[16:19] <Omega> https://wiki.ubuntu.com/UbuntuTour/Todo#List of Pages
[16:19] <aksharpatel47> Onto the list of categories then
[16:20] <Muscovy> Some topics like Nautilus certainly need expanding.
[16:20] <fieldse_> List of ideas for "needs for expanding"?
[16:21] <aksharpatel47> Also, people coming over from linux need to learn a little bit about the file system organization
[16:21] <UndiFineD> and there are some 33000 packages in the repositories, hard to do them all
[16:21] <Muscovy> I'm not sure this is the place to explain the contents of /, if that's what you mean.
[16:22] <aksharpatel47> Nopes, not in detail
[16:22] <aksharpatel47> But a certain overview
[16:22] <Muscovy> fieldse: Nautilus ought to explain stuff like the UI and basic permissions too.
[16:22] <UndiFineD> yes, general overview, of LSB and filesystem access rights
[16:22] <Omega> Or we can point to the manual ofr that.
[16:22]  * fieldse_ nods @ muscovy 
[16:23] <fieldse_> muscovy, if you can think of a short list and pass it to me I can add it to the wiki
[16:23] <maheshmohan> No. a big NO. I think, thw tour will cover how to use the default apps & how to get extra packages. that's all. he will gradually learn about the filesystem.
[16:23]  * fieldse_ agrees with maheshmohan - Filesystem structure is beyond the scope of our project, IMO
[16:23] <aksharpatel47> I understand, it might get too techy for a new user
[16:23] <UndiFineD> maheshmohan, yes, but it will have to be in there at some point
[16:23] <Omega> We should provide the users with the basic tools he needs to survive.
[16:24] <aksharpatel47> I wrote that from a transitional users point of view
[16:24] <Muscovy> Filesystem structure is for more of Ubuntu Manual level of users, I feel.
[16:24] <fieldse_> Also, aksharpatel47 , while I agree with the need to teach new users about this, I think we have to keep our tutorial fairly short so as not to lose them.
[16:24] <Omega> Yeah.
[16:24] <fieldse_> Maybe a list of "learn more about" links at the end?
[16:24] <fieldse_> * idea ^
[16:24] <Muscovy> There isn't a really non-technical reason go anywhere other than /media, IMO.
[16:24] <Omega> We need to teach them what they want to learn.
[16:24] <maheshmohan> fieldse_ ya.right. he may get lost after seeing the filesystem thing!
[16:24] <aksharpatel47> @fieldse :Learn more about would be great
[16:25] <jeremymikkola> Just a random though: perhaps it would make more sense for it to be task-oriented, rather than application-oriented?
[16:25] <jeremymikkola> *thought
[16:25] <Omega> That's what I meant with pointing to the ubuntu manual project.
[16:26] <Muscovy> evince ./ubuntu-manual.pdf --page-label=X
[16:26] <Muscovy> If we download the manual, we could use that to link to specific pages.
[16:26] <fieldse_> Hey, all? A point that's probably covered already, but who's taking minutes?
[16:27]  * UndiFineD has all
[16:27]  * fieldse_ blinks
[16:27] <fieldse_> undifined, you mean you're taking?
[16:27] <Muscovy> Minutes or logs?
[16:28] <fieldse_> Minutes for the meeting, now. I see "alexander" is signed up for this
[16:29] <fieldse_> Ok, I'm assuming the silence  means no one is doing it - so, I guess I am. Where / how do I need to post these?
[16:29] <aksharpatel47> Allright
[16:29] <aksharpatel47> I'm doing it
[16:29] <Muscovy> Post what?
[16:30] <fieldse_> aksharpatel47, thanks.
[16:30] <aksharpatel47> sorry, didn't see your post
[16:30] <Muscovy> Once ubuntulo1 gets to it, logs will be at http://irclogs.ubuntutour.org/2010/09/18.html if that's what you mean.
[16:32] <fieldse_> muscovy, no, didn't mean to derail conversation, sorry, but what I meant was is anyone actually taking meeting minute notes, and posting them somewhere, aside from the IRC log.  Seeing this request in the EtherPad agenda: Somebody also needs to be responsible for taking minutes.  Any voulenteers? Alexander Lancey
[16:32] <fieldse_> http://irclogs.ubuntutour.org/2010/09
[16:32] <Muscovy> I said I'd do it.
[16:32] <fieldse_> aite, apologies, continue.
[16:32] <Muscovy> Do we have more to say about the tour topics?
[16:33] <UndiFineD> I am not clear on the list for that
[16:33] <aksharpatel47> I'd say the tour topics are pretty solid
[16:34] <Muscovy> Fairly.
[16:34] <Omega>                           pretty solid
[16:34] <fieldse_> It sounds like mostly everyone thinks the topics are solid, if you're seeing holes that you think need filling, why not suggest them and we'll add it to the list?
[16:34] <Muscovy> I can definitely see some small level tweaks, but on the whole it's pretty good.
[16:34] <Muscovy> Alright.
[16:34] <Omega> Consider what the user will be wanting to do first, and how we should be organising tools.
[16:34] <Muscovy> Nautilus UI and permissions should be mentioned.
[16:35] <Muscovy> Maybe add bookmarks/history to Firefox.
[16:35] <UndiFineD> I see a whole bunch of launchpad issues, most are on audio, it would be great if users can learn a bit about that
[16:36] <fieldse_> undifined, like what?
[16:36] <Omega> That should be in the "getting help" tour.
[16:36] <UndiFineD> I was silly enough to subscribe to the kernel list, and most issues I get are on alsa pulse oss
[16:37] <Muscovy> For troubleshooting, this would be another good manual referral.
[16:37] <fieldse_> agh. Yeah, I think we have that covered with "get help" section links, correct?
[16:37] <fieldse_> Is there specifically a link to launchpad help mailing lists being included? 'cause if not, it needs to be.
[16:38] <Muscovy> I don't think there is yet.
[16:39] <aprilg> We need to update the 'get help' section
[16:39] <aprilg> to include those links
[16:39] <aprilg> Are there any other tour topics we should include?
[16:40] <UndiFineD> getting an email address
[16:40] <UndiFineD> totally new people would have none
[16:40] <Muscovy> Good idea.
[16:41] <Omega> How to Get involved with Ubuntu/Contribute
[16:41]  * fieldse_ blinks: undifined , like how would you suggest to get an email address?
[16:41] <UndiFineD> one of a list of free mail providers
[16:42] <fieldse_> Oh, right- do we have "setting up an email account" covered in the Empathy section?
[16:42] <aksharpatel47> ya
[16:43] <UndiFineD> :)
[16:43] <Muscovy> Yes, so we should link the two, perhaps.
[16:43] <mahesh_> yes.right
[16:43] <fieldse_> IE, 'how to set up your existing email address with evolution/whatever'? Because this would be appropriate place for a link to 'creating a new email account' if you don't have one already
[16:43] <aprilg> there's a few topics for Evolution
[16:43] <Muscovy> Emaothy only mentions making a new one, not who, so it should link to wherever that oage is.
[16:44] <UndiFineD> getting help : LoCo support
[16:44] <Omega> But I don't want us to advertise any particulat email provider.
[16:45] <fieldse_> Yeah, I agree - this has been one of my long-standing "papercut" gripes with Ubuntu experience: they include Evolution by default, but not a very good intro to setting up your mail accounts, that the fact that it defaults as the "mailto" client without previously asking you for your choice is a pain.
[16:45] <UndiFineD> I just use webmail
[16:45] <fieldse_> Is setting up alternate default mail client covered in Empathy/Evolution section?
[16:46] <aprilg> fieldse_ I don't think so
[16:46] <fieldse_> undifined, same here - that's why I'd want to show them how to change "mailto" program.
[16:46] <Muscovy> As in webmail or as in Thunderbird or something?
[16:46] <fieldse_> Okay, add ^ to topics list
[16:46] <UndiFineD> Muscovy, no I am worse I forwarded my own domain to gmail
[16:46] <fieldse_> muscovy, as in either webmail or thunderbird.
[16:47] <Muscovy> UndiFine: same here!
[16:47] <aprilg> by the way, should Evolution have be a stand-alone topic or should we change it to something more general, maybe e-mails ?
[16:47] <Muscovy> We could easily link to a handful of mail providers, without endorsing one.
[16:48] <aprilg> *should Evolution be
[16:48] <Muscovy> I'm not sure, it depends how much we want to talk about browser mail.
[16:48] <fieldse_> aprilg, is it currently a just-touched-upon subtopic of the Empathy/chat client section?
[16:48] <fieldse_> muscovy, agreed
[16:48] <aprilg> if we use the topic email, we can just say htat the default eemail client for ubuntu is evolution. provide an overview for that, how to set up an account, etc. and then at the end, tell the user that ther are other options. and provide the list
[16:49] <Muscovy> Probably conglomerate the two though.
[16:49] <aprilg> fieldse_ right now, Evolution is its own separate topic
[16:49] <Omega> I also forward my own domain to gmail :>
[16:49] <aprilg> it isn't under Empathy
[16:50] <fieldse_> aprilg, Agreed - I move we set up "email" topic as its own section, include empathy + mailto setup problem + setting up an email address in this section
[16:50] <UndiFineD> seems good
[16:51] <fieldse_> Ok, any objections?
[16:51] <fieldse_> Moving on ...
[16:51] <maheshmohan> ok.goog.
[16:51] <Muscovy> None, I like it.
[16:51] <maheshmohan> sorry.good
[16:51] <aksharpatel47> agreed
[16:51] <maheshmohan> any other topic suggestions? can we now talk about coding
[16:51] <aprilg> ok. any other topics that need to be included or modified?
[16:51] <Muscovy> I don't think so.
[16:51] <fieldse_> Not here.
[16:51] <UndiFineD> getting help : LoCo support
[16:52] <fieldse_> Oh, that's a good one.
[16:52] <fieldse_> ok.
[16:52] <aprilg> ok. update getting help, and reorganize empathy and evolution.
[16:52] <aprilg> next topic?
[16:52] <aprilg> on the agenda, I mean :D
[16:52] <fieldse_> Ok. If nothing else? "Consider what the user will be wanting to do first, and how we should be organising tools?"
[16:53] <fieldse_> What does "oranising tools" refer to?
[16:53] <Muscovy> I was thinking about having a "home page" that lists the tours, in a "suggested" order.
[16:53] <fieldse_> Ah.
[16:54] <fieldse_> Sounds sensible.
[16:54] <Muscovy> I think order beyond desktop-apps-help is mainly opinion.
[16:54] <fieldse_> Personally, recommendation: Do not greet the user with this list / menu for first screen. Just put them right into the first tour after an intro.
[16:55] <Muscovy> That seems better.
[16:55] <fieldse_> Personally, when I'm greeted with a menu of subjects 5 miles long, it deters me from ever starting.
[16:55] <aprilg> doesn't the current left pane/navigation thing provide the same functionality as a home screen listing all the tours?
[16:55] <Muscovy> It takes up more space, and looks a little scary.
[16:55] <fieldse_> So, if you present them with a first few (short) tours quickly, they can navigate to the "list of tours" menu if they're interested in skipping ahead
[16:56] <aprilg> ok..
[16:56] <fieldse_> thoughts/contentions, muscovy ?
[16:56] <aprilg> im thinking we can directly launch the welcome to ubuntu/about ubuntu tour
[16:56] <aksharpatel47> Or we can have round buttons corresponding to each of the topic heads
[16:56] <aksharpatel47> and then have the Ubuntu Installer Slideshow kind of tour
[16:56] <aprilg> and then after that, direct the user to the list of tours
[16:57] <fieldse_> aksharpatel47, I like that idea. I don't want to keep adding to the programmers / UI designers' workload, but sounds nifty.
[16:57] <maheshmohan> akshar, yes.nice
[16:57] <fieldse_> Are we going to discuss the Ubuntu Slideshow model later in the meeting?
[16:58] <Omega> Yes, when we get to UI.
[16:58] <fieldse_> Ok.
[16:58] <fieldse_> I'm going to have to split in 30, I'd like to be in on the UI discussion briefly.
[16:59] <Muscovy> Sorry, I was away for a moment.
[16:59] <jeremymikkola> Perhaps we could also have some kind of quick start page that tells people what tutorial to follow in order to accomplish the thing that they are trying to do (i.e. "browse the web -> firefox")
[17:00] <fieldse_> jeremymikkola, this is a good idea.
[17:00] <Muscovy> I was thinking about a button that toggles you between your page and a list like that.
[17:01] <fieldse_> muscovy, okay, so question is if it goes to a menu of every subject on the tour, or if it goes to an "overview" page like aksharpatel47 was suggesting, with "main topic" buttons leading the user to subtopics from there
[17:02] <Muscovy> Hmm.
[17:02] <Muscovy> Maybe overviews.
[17:02] <Omega> We need to pick up the pace a bit.
[17:02] <Omega> We're one hour in.
[17:02] <fieldse_> Overviews, less intimidating. Menus, more informative.
[17:02] <Muscovy> And make the sidebar complete, but shrinkable.
[17:02] <fieldse_> omega, agreed.
[17:02] <UndiFineD> spoken details in the tours ?
[17:03] <fieldse_> undifined, I dunno, was this intended to be within the scope of the project?
[17:03] <Muscovy> Maybe at some point.
[17:03] <Muscovy> Shall we move to difficult ratings?
[17:03] <fieldse_> Suggest first finishing the project with text-only, then maybe later releases add in spoken details.
[17:04] <Muscovy> Or jump to docs team stuff?
[17:04] <fieldse_> docs team.
[17:04] <fieldse_> muscovy, In the interests of keeping our meeting fairly efficient, I have a suggestion I've used from other organizational meetings:
[17:04] <UndiFineD> speech requires timing
[17:05] <UndiFineD> if you speak the text at normal rate, you get the right timing for the slides
[17:05] <fieldse_> For those subjects where there seems to be a range of options, just set up a poll at the wiki (or at the Launchpad page, or elsewhere) and invite members to vote on their opinion for the choice.
[17:06] <fieldse_> muscovy, ^ will mean less time spent in deliberation in this meeting.
[17:06] <jeremymikkola> +1 to fieldse's idea
[17:06] <Omega> I will try to communicate with the Docs team about Ubuntu Tour.
[17:06] <fieldse_> Can this be done?
[17:06] <Muscovy> Hmm, good idea.
[17:06] <Omega> When I am less sick.
[17:06] <fieldse_> Ok, omega signs up for the task. =)
[17:06] <Muscovy> Yay.
[17:07] <fieldse_> Moving on.
[17:07] <Muscovy> Screenshots next?
[17:07] <fieldse_> Screenshots?
[17:07] <aprilg> screenshots
[17:07] <fieldse_> Okay, so what's the deal w. the screenshots / consistency question?
[17:07] <jeremymikkola> question about screenshots: should they be from 10.04, or 10.10?
[17:07] <Muscovy> 10.10
[17:08] <mahesh_> it should be from 10.10
[17:08] <aprilg> yep. 10.10
[17:08] <jeremymikkola> k
[17:08] <fieldse_> I suggested a naming format in the email thread aprilg started -
[17:08] <Muscovy> And are we using pngs or jpgs?
[17:08] <fieldse_> jpg
[17:08] <UndiFineD> I prefer png
[17:08] <mahesh_> we have to update it for 11.04
[17:08] <fieldse_> Doh!
[17:08] <fieldse_> Why png, undifined?
[17:08] <Muscovy> I would suggest pngs. If we need jpgs, we can make a converter script.
[17:09] <jeremymikkola> png images look a lot better if they have text in them
[17:09] <fieldse_> muscovy, reason? I just suggest jpeg because of size issues. How big is this tour going to be?
[17:09] <UndiFineD> png is free, has better quality, but besides png, I like to see scaleable graphics
[17:10] <fieldse_> And, muscovy: Are you hoping to get this tour included in future Ubuntu releases default installation? Because the size is going to be a large factor in that.
[17:10] <Muscovy> fieldse_: I was thinking .png partially because we can go to jpg easily from there, should we need to.
[17:10] <Muscovy> Wait, yeah.
[17:10] <Muscovy> :|
[17:10] <fieldse_> Heh.
[17:10] <UndiFineD> my res is 1950x1080
[17:10] <fieldse_> Ah, yeah. There's another issue.
[17:10] <Omega> We can implement tour compression.
[17:11] <fieldse_> Resolution for screenshot.
[17:11] <UndiFineD> my avg joe or jane might have 1024x786
[17:11] <UndiFineD> which is why i said scaleable
[17:11] <Omega> svg then?
[17:11] <fieldse_> Okay, and considering the "tour window" is going to be minus area for toolbars, etc, it's goin to be about size of an average webpage.
[17:11] <fieldse_> undifined, how are you going to make scaleable screenshots?
[17:12] <UndiFineD> you can't :p
[17:12] <fieldse_> undifined, Well, technically we *can*.
[17:12] <Omega> But it won
[17:12] <Omega> But it won't scale the way we want it to
[17:12] <fieldse_> Sort of - I can trace bitmaps in Inkscape pretty well.
[17:12] <fieldse_> So, we *could* have scaleable "screenshots" in SVG format. Seems like overkill, but ...
[17:13] <fieldse_> Can we just choose a sane default image size? Or will the application be capable of scaling the images to fit within like 50% of the window?
[17:14] <fieldse_> muscovy, you know the answer to this ^?
[17:14] <Muscovy> I feel in the vicinity of 300x300 would do.
[17:14] <Muscovy> fieldse: we could scale, but I don't know how to set a max scaled size.
[17:15] <Muscovy> Maybe we could link the images to open larger versions in the image viewer.
[17:15] <fieldse_> Would vote slightly higher res for some detail, plus fact "square" isn't best form-factor for average screen layout
[17:16] <fieldse_> Okay, so what's the decision? Can we put this via email vote to the UI/graphics team?
[17:16] <Muscovy> I think so.
[17:16] <Omega> Should we moce onto programming now?
[17:16] <UndiFineD> and if you choose 400x300, it will not look right on wide screens
[17:16] <Muscovy> Yep.
[17:16] <Omega> Programming team leadership
[17:16] <mahesh_> Can we move on to translation & then to programming?
[17:17] <aprilg> oh ya, what about where the images are to be stored?
[17:17] <Omega> Okay, translation is short anyway.
[17:17] <Omega> Lauchpad translation support?
[17:17] <aprilg> there was a bug filed about that
[17:18] <Muscovy> I don't know how LP translations work.
[17:20] <Omega> Me neither.
[17:20] <UndiFineD> neither
[17:20] <Muscovy> Perhaps we should look into asking someone who does.
[17:21] <UndiFineD> brandonj, you suggeted it ?
[17:22] <aprilg> maybe we should set this topic aside for now?
[17:22] <aprilg> since no one here really has any answers :)
[17:22] <fieldse_> Ok.
[17:22] <fieldse_> Good reason to do so. ;)
[17:22] <fieldse_> I've got 15 minutes left with you here.
[17:22] <fieldse_> Programmin?
[17:22] <Muscovy> Yep.
[17:22] <fieldse_> *Programming
[17:23] <fieldse_> Muscovy, what is the current "leadership model"?
[17:23] <Omega> Programming team leadership
[17:23] <Muscovy> I'm not quite sure.
[17:23] <Omega> I nominate MadnessRed.
[17:23] <Omega> He's the most active programmer currently.
[17:23] <Muscovy> I do too. He's been very useful, we couldn't have the GUI without him.
[17:24] <UndiFineD> alright with me, but does he want to
[17:24] <fieldse_> We definitely need project leaders for each section.
[17:24] <Omega> We'll ask him when he get's here.
[17:25] <fieldse_> There needs to be one head at the top of each section, or at least one, or this thing isn't going to happen because no executive decisions will be made.
[17:25] <Omega> fieldse_: Muscovy leads Design, aprilg leads writing, brandonj currently leads programming, I am the organizational leader.
[17:25] <fieldse_> This is part of the reason for gathering the volunteers list - so a project leader can then "tap" his volunteers for whatever undone that needs filling.
[17:25] <fieldse_> omega, ah, thanks.
[17:26] <fieldse_> This would also greatly simplify things for the volunteers to know that there's one contact person at the head of each team.
[17:26] <Omega> Okay, let's move onto User Interface
[17:26] <Omega> User interface. We need a clear descision on what people want to be changed with the gui, preferably pre-prepared mockups could be presented.
[17:27] <Muscovy> I threw one in ./mock-ups in both branshes last night.
[17:27] <Muscovy> Here: http://i.imgur.com/PJdZa.png
[17:27] <Muscovy> It's missing some sort of Home/Menu button.
[17:28] <fieldse_> Cool.
[17:28] <Muscovy> I think we should try to decentralize the sidebar for more space.
[17:28] <UndiFineD> I like the ubiquity style
[17:28] <Muscovy> Like decreate the ont a bit, or make it hidable.
[17:28] <Muscovy> font*
[17:28] <Muscovy> decrease the font*
[17:29] <fieldse_> Okay, needs: home button, collapsible "list of topics" sidebar
[17:29] <fieldse_> muscovy, I'd be happy seeing the image bigger.
[17:30] <fieldse_> eh, the screenshot image, that is.
[17:30] <fieldse_> Another suggestion?:
[17:30] <Muscovy> I figured there could be 4 or so curves, that are placed based of screenshots size, instead of forcing the screenshot to be that size.
[17:31] <fieldse_> Add a "search for topics on..." bar at the bottom
[17:31] <Muscovy> That would be good.
[17:31] <fieldse_> Can we / are we able to implement a search function?
[17:31] <Omega> It shouldn't be difficult.
[17:31] <fieldse_> muscovy, what do you mean by curves?
[17:32] <Muscovy> The section where the grey curves around the screenshot.
[17:32] <fieldse_> ah
[17:32] <fieldse_> hm
[17:33] <fieldse_> Another suggestion:
[17:33] <fieldse_> If this thing is using CSS styling .. (is it?) ...
[17:33] <fieldse_> You can have two "end piece" curves on either side.
[17:33] <fieldse_> With a flat middle section, expandable
[17:33] <fieldse_> So if user expands the window, the middle area will just stretch between endpieces.
[17:34] <Muscovy> Ooh, that would be cool.
[17:34] <fieldse_> solves need for different curves for different resolutions
[17:34] <UndiFineD> :D
[17:34] <fieldse_> =)
[17:34] <Muscovy> And useful, since the top of the curve will be more flat than at present.
[17:34] <fieldse_> Ok.
[17:35] <fieldse_> So, mind if I take your mockup and hack it up a little tonight?
[17:35] <aprilg> so its gonna end up looking like a square/rectangle with rounded edges, right?
[17:35] <Muscovy> Not at all.
[17:35] <aprilg> *corners instead of edges
[17:35] <Muscovy> Unfortunately, I didn't think to make a .xcf.
[17:35] <fieldse_> Ok, np.
[17:36] <fieldse_> So, regarding a previous topic unresolved:
[17:36] <fieldse_> There's an item on the agenda under screenshots of using "Quickshot"?
[17:36] <fieldse_> As in the email I responded earlier, does this matter?
[17:36] <aprilg> I checked with quickshot, I think its only available with 10.04
[17:36] <Muscovy> We could port it.
[17:37] <Muscovy> But I'm not sure it really matters.
[17:37] <fieldse_> Is there any reason it matters what screenshot util we are using, as long as it comes out same resolution and quality?
[17:37] <Muscovy> It's just reputed as easy.
[17:37] <Muscovy> Not really, fieldse_.
[17:37] <fieldse_> a PNG is a PNG
[17:37] <fieldse_> Ok, just checking I wasn't missing something.
[17:37] <fieldse_> So, we didn't resolve naming format.
[17:37] <fieldse_> and I have to ask this, bc I have to leave now.
[17:38] <fieldse_> so, example screenshot for, say rhythmbox selection dialog:
[17:39] <fieldse_> gnomepanel-mainmenu-soundandvideo-rhythmbox.png ?
[17:39] <fieldse_> Or can we use spaces in the filenames without screwing up the programmers?
[17:39] <UndiFineD> i would want to avoid spaces
[17:40] <Muscovy> We could probably use spaces, but I'd say we should avoid it if possible.
[17:40] <UndiFineD> or you must like _\
[17:40] <fieldse_> Ok, anyone want to suggest a less-ugly naming system?
[17:40] <fieldse_> gnome-panel_main-menu_sound-and-video_whatever.png
[17:40] <fieldse_> yes, no, any objections?
[17:41] <Muscovy> Is the screenshot of a Rhythmbox window?
[17:41] <aprilg> fieldse_ I'm fine with what you suggested
[17:41] <Omega> We'll get the same problem if there's a _ in the name
[17:41] <UndiFineD> maybe add preseeding integer index
[17:41] <fieldse_> muscovy, this would be screenshot of the dialog selection from the gnome main menu
[17:41] <Muscovy> Ah.
[17:41] <fieldse_> undifined, what do you mean index integer?
[17:42] <UndiFineD> 000- gnomepanel-mainmenu-soundandvideo-rhythmbox.png
[17:42] <UndiFineD> without the space
[17:42] <Muscovy> The code looks for _'s to add tour pages.
[17:42] <Muscovy> I think.
[17:42] <fieldse_> ah, crap.
[17:42] <fieldse_> Okay, so ... no spaces, no underscores.
[17:42] <Muscovy> We could make it eclude .jpgs though.
[17:42] <Muscovy> exclude*
[17:42] <fieldse_> some of our description names are going to need separation between words to be readable
[17:43] <UndiFineD> with the integer index you can set the images in specifivc order
[17:43] <fieldse_> for ex. gnome-panel > main menu > sound and video would be the path here.
[17:43] <fieldse_> Ok, let's use undifined's suggestions, and we can add the index numbers later.
[17:44] <fieldse_> So 000-gnomepanel-mainmenu-soundandvideo-rhythmbox.png
[17:44] <Muscovy> Sounds good.
[17:44] <fieldse_> Ok, that's it for me, I'm out of here for today
[17:44] <Muscovy> Thanks for your help!
[17:44] <UndiFineD> thanks for being here fieldse
[17:45] <Omega> Cya.
[17:45] <aprilg> bye fieldse_ :)
[17:45] <aprilg> seeyah
[17:45] <aprilg> what's next on the agenda?
[17:45] <Muscovy> Ok, next: website updates.
[17:45] <fieldse_> laters, all. muscovy, will you just post the meeting notes to the listserv?
[17:46] <Muscovy> I know we need wikilinks.
[17:46] <Muscovy> fieldse_: SUre.
[17:46] <fieldse_> aite, thanks, Peace!
[17:46] <Muscovy> In particular, http://ubuntutour.org/contribute/ needs changing.
[17:47] <Muscovy> Should we treat that page as a verbose link to https://wiki.ubuntu.com/UbuntuTour and https://wiki.ubuntu.com/UbuntuTour/Volunteers ?
[17:48] <aprilg> Muscovy maybe the todo list instead of the volunteers
[17:48] <aprilg> the volunteers page keeps changing
[17:48] <Muscovy> Ok.
[17:49] <Muscovy> And I guess later we should merge the branches and removed references of lp:~ubuntu-tour/ubuntu-tour/code-development
[17:50] <aprilg> but lets not include everything on the to do list. maybe keep it to the first two levels ? maybe just these: overview, the Sections (writing, graphics, programming, translation, editing)
[17:50] <aprilg> yes, once the branches have been merged
[17:51] <Muscovy> Ok, that will be done today.
[17:51] <aprilg> is there anything else we need to discuss?
[17:51] <aprilg> we're approaching two hours :)
[17:51] <aprilg> there's a few more topics listed under programming for today's agenda
[17:52] <Muscovy> Should we start with interactivity framework (bottom)? That one's fairly important.
[17:52] <Muscovy> Luckily, we've already skimmed/covered a bunch of stuff in the programming list.
[17:53] <Omega> It is, but the programmers should really be here for it.
[17:53] <Muscovy> Hmm.
[17:54] <Muscovy> It seems we are done for now?
[17:54] <Omega> I believe we are.
[17:54] <UndiFineD> yeah I am ok with it, going to translate a bunch of files into dutch
[17:54] <Muscovy> Thanks for being here, everyone. :D
[17:55] <Omega> Roep me als je me nodig hebt.
[17:55] <UndiFineD> ;)
[17:56] <Muscovy> Ok, so I'll send a minutes list and a link on the mailing list in a bit.
[17:56] <aprilg> wee :)
[17:56] <aprilg> thanks for being here everyone!
[17:58] <Omega> :)
[17:58] <Muscovy> Well, we've certainly come a ways.
[17:59] <UndiFineD> I liked that we can get things done
[22:01] <UndiFineD> Omega, hmmm, doen we dubbel vertaal werk ?
[22:01] <Omega> Hoezo?
[22:02] <Omega> Also, English please.
[22:02] <UndiFineD> I see Ivo did translations in "nl" folder and I did in "nl_NL"
[22:04] <Omega> Well they should be mostly the same