/srv/irclogs.ubuntu.com/2013/06/10/#ubuntu-meeting.txt

=== Logan_ is now known as Guest68
=== Guest68 is now known as Logan_
=== Sp4rKy_ is now known as Sp4rky
=== dholbach_ is now known as dholbach
=== Sp4rky is now known as Sp4rKy
=== doko_ is now known as doko
=== pgraner` is now known as pgraner
=== bdmurray_ is now known as bdmurray
=== mmrazik is now known as mmrazik|afk
=== Logan_ is now known as Guest75538
=== Logan__ is now known as Logan_
jdstrandhi!16:32
tyhickshello16:32
mdeslaur\o16:32
jdstrand#startmeeting16:33
meetingologyMeeting started Mon Jun 10 16:33:03 2013 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:33
meetingologyAvailable 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 #votesrequired16:33
jdstrandThe meeting agenda can be found at:16:33
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:33
jdstrand[TOPIC] Announcements16:33
=== meetingology changed the topic of #ubuntu-meeting to: Announcements
jdstrandChristian Kuersteiner (ckuerste) provided debdiffs for lucid-precise for xml-light (LP: #1186860). Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)16:33
ubottuLaunchpad bug 1186860 in xml-light (Ubuntu Precise) "Hash collision vulnerability in xml-light" [Undecided,Fix released] https://launchpad.net/bugs/118686016:33
chrisccoulsonhi!16:33
jdstrand[TOPIC] Weekly stand-up report16:34
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
jdstrandI'll go first16:34
jdstrandapparently I am in the happy place this week, which I am grateful for :)16:34
mdeslaur:)16:34
jdstrandI'm catching up from being off last week16:34
jdstrandI've got patch piloting to do16:34
jdstrandan embargoed update16:35
jdstrandvarious reviews and coordination surrounding application isolation, scopes and click packages16:35
jdstrandand I plan to do a preliminary install audit of the phablet image16:35
jdstrandmdeslaur: you're up16:35
mdeslaurI have an openchrome update I'll be releasing this afternoon16:35
mdeslaurand after that, I've got a bunch of stuff ready for testing in the secppa16:36
mdeslaurI'm also on triage duty this week16:37
mdeslaurthat's pretty much it...updates as usual :)16:37
mdeslaursbeattie: you're up16:37
sbeattieI'm again on apparmor this week16:37
sbeattieI'm currently working on the apparmor/sdk work in the https://blueprints.launchpad.net/ubuntu/+spec/security-s-appisolation-sdk16:37
jdstrandsbeattie: how is that going?16:38
sbeattieI've uploaded some of the easyprof policy group stuff to the dbus-dev ppa, along with versions of the calculator and calendar app that make use of them16:38
jdstrandah, cool16:38
mdeslauroh, cool16:38
* jdstrand makes note to play with that this week16:38
sbeattieI'm still working on getting json input to easyprof going and am continuing to look at what the click package emits16:38
sbeattieI think there's an apparmor upstream meeting this week that I need to prep for16:39
sbeattieoh, I should note that after this week, I'm off for two weeks16:39
sbeattieThat's it for me.16:39
jdstrandsbeattie: wrt click> maybe ask beuno/cjwatson?16:40
sbeattiejdstrand: sure, I've been playing around with the source a bit16:40
sbeattietyhicks: you're up16:40
jdstrandsbeattie: also, for clarity (since I've been off a week and still catching up), you're still going to work with debhelper correct?16:41
tyhicksI'm (finally) finishing my email to the apparmor list to compare the various dbus syntax proposals16:41
sbeattiejdstrand: yes. I didn't do that in the bits I uploaded.16:41
tyhicksI got sidetracked last week while chasing down some odd things I came across while preparing a profile for that email16:41
jdstrandsbeattie: ok, thanks. I think that shouldn't be too bad. we (you, me, mdeslaur) can talk more if anything is unclear16:42
jdstrandtyhicks: please continue (sorry to interrupt)16:42
mdeslauroh! forgot to mention I also plan on installing ubuntu on my nexus 4 this week16:42
tyhickslater today, I'll start prepping for my work items in https://blueprints.launchpad.net/ubuntu/+spec/client-1305-content-mgmt-picking16:42
tyhicksI'll begin work on that blueprint this week16:43
tyhicksand will continue working on the parser changes in the background16:43
tyhicksthat's it for me16:43
tyhicksjjohansen: you're up16:43
mdeslaurtyhicks: fyi, tvoss mentioned possibly having a command line first draft of that api this week16:44
tyhicksmdeslaur: ok, that would be good16:44
jdstrandtyhicks: also note, that the meeting is early tomorrow16:44
jdstrandtyhicks: did anything happen with rescheduling that16:44
mdeslaurI guess we'll find out more at tomorrow's meeting16:44
tyhicksjdstrand: no, I'm going to give it a shot for a week or two16:44
tyhicksif it kills me, I'll push for a reschedule16:45
tyhicksI think I'll be fine16:45
jdstrandtyhicks: sorry about that, but I appreciate it16:45
tyhicksno problem16:45
jdstrandI think jjohansen is afk atm16:45
tyhicksoh, yes16:45
mdeslaurtyhicks: please don't die16:45
jdstrandsarnold: you're up16:45
tyhicks:)16:45
sarnoldI'm on community this week; I'll also be reviewing some patches I expect from jjohansen soon. I'd like jdstrand or mdeslaur's help in pushing the openssl zlib environment variable to a -proposed for wider testing before pushing to the archive16:46
mdeslaursarnold: ah! yes, cool16:46
mdeslaursarnold: can I try and push what's in the ppa now?16:46
sarnoldmy bouncycastle test suite is starting to feel like there's something to it :) I've got symmetric ciphers and their modes of operations working; I can see adding assymetric ciphers and then finally some high level TLS servers/clients16:46
jdstrandsarnold: just put it in the ubuntu-security-proposed ppa and ping me to push it to -proposed when ready16:46
sarnoldmdeslaur: yes16:46
sarnoldjdstrand: it's already in the security ppa; would it need to be rebuilt in ubuntu-security-proposed before it could be pushed?16:47
mdeslaursarnold: nope16:47
jdstrandsarnold: no, I can do it from there too16:47
mdeslaurjdstrand: let me try first16:48
sarnoldah, cool :)16:48
* jdstrand defers to mdeslaur 16:48
sarnoldokay, I think that's me, chrisccoulson, you're up :)16:48
chrisccoulsonthanks sarnold16:49
chrisccoulsonso, last week, i pretty much finished off fleshing out the architecture for our chromium embedding api (tentatively named "oxide", thanks to mdeslaur) ;)16:50
chrisccoulsoni have a pretty good idea of how much work is involved now16:50
jdstrandtyhicks: (fyi, please feel free to poke me if I don't respond to your apparmor policy email-- I'd like to get those discussions moving and completed)16:50
tyhicksjdstrand: ack - same here16:50
chrisccoulsonand i've actually created a project branch locally to start some hacking on it :)16:50
jdstrandchrisccoulson: nice!16:50
mdeslaurchrisccoulson: oh, cool...looking forward to discussion that with you16:50
chrisccoulsonthis week, i've got an embargoed update to do16:51
chrisccoulsoni think that's me (other than that update, i'll be continuing work on https://blueprints.launchpad.net/ubuntu/+spec/client-1303-webkit-maintenance/)16:52
jdstrand[TOPIC] Highlighted packages16:52
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
jdstrandThe Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.16:52
jdstrandSee https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.16:53
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/boinc.html16:53
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/iscsitarget.html16:53
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/ruby-openid.html16:53
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/charybdis.html16:53
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/bcron.html16:53
jdstrand[TOPIC] Miscellaneous and Questions16:53
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
jdstrandDoes anyone have any other questions or items to discuss?16:53
jdstrandmdeslaur, sbeattie, tyhicks, jjohansen, sarnold, ChrisCoulson: thanks!16:57
jdstrand#endmeeting16:57
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Jun 10 16:57:21 2013 UTC.16:57
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-16.33.moin.txt16:57
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-16.33.html16:57
tyhicksthanks!16:57
mdeslaurthanks jdstrand!16:57
sarnoldthanks jdstrand :)16:57
sbeattiejdstrand: thanks!16:58
=== marlinc_ is now known as marlinc
=== balloons_ is now known as balloons
=== yofel_ is now known as yofel
=== TheDrums_ is now known as TheDrums
=== DGJones is now known as DJones
=== lifeless_ is now known as lifeless
=== davmor2_ is now known as davmor2
=== jpds is now known as Guest72281
kees\o19:52
cjwatsonhi19:56
keeslooks like a short meeting19:57
keesmdz, soren, stgraber: ready for (quick) tb meeting?19:59
keespitti has sent his apologies on the list19:59
soreno/19:59
kees#startmeeting20:01
meetingologyMeeting started Mon Jun 10 20:01:00 2013 UTC.  The chair is kees. Information about MeetBot at http://wiki.ubuntu.com/meetingology.20:01
meetingologyAvailable 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 #votesrequired20:01
kees[topic] Action review20:01
=== meetingology changed the topic of #ubuntu-meeting to: Action review
keesMartin to mail SRU team members about inordinate SRU waiting times in proposed queue20:01
keesdid this happen?20:01
cjwatsonThere's been a fairly decent thread, and I understand Brian's new sru-review tool is starting to gain traction20:02
keesyeah, the thread has been moving along. it wasn't clear to me if this action is considered "done". I guess so, since the thread is started.20:02
keesso, moving on:20:02
keesJorge to check whether brainstorm.ubuntu.com could be kept as a read-only archive, and otherwise shut it down.20:03
cjwatsonThere's been internal RT traffic about this20:03
keesokay, cool.20:03
cjwatsonRT#61484 for those with access20:03
* stgraber waves20:04
kees[topic] Scan the mailing list archive for anything we missed20:04
=== meetingology changed the topic of #ubuntu-meeting to: Scan the mailing list archive for anything we missed
cjwatsonIS have said they'll do the dump, although need to check it for personally-identifying information20:04
keesall I see on the ML is the SRU thread, so nothing extra in there.20:04
kees[topic] Check up on community bugs20:05
=== meetingology changed the topic of #ubuntu-meeting to: Check up on community bugs
kees0 boogs found20:05
kees[topic] AOB20:05
=== meetingology changed the topic of #ubuntu-meeting to: AOB
keesanything not in bugs or ML or wiki we need to take care of?20:05
jcastrokees: any questions for me wrt brainstorm?20:05
keesjcastro: I was just checking on the status of the brainstorm request, cjwatson found the RT. we're all good. :) thanks!20:06
stgraberkees: so we had a discussion a couple meetings back about the openssl exceptions for squid and mongodb but deferred as we felt cjwatson really should be present for that discussion20:06
keesstgraber: ah yes!20:06
cjwatsonThe mongodb discussion appears to be moot since upstream are (AIUI) adding the exception20:06
keesexcellent.20:06
keesseems like the same should be possible for squid too, I would hope.20:07
sorenNope.20:07
cjwatsonsquid have had problems tracking down copyright holders I think20:07
sorenMany, many contributors and copyright holders.20:07
stgrabersquid doesn't use copyright assignment, so getting all copyright holders to agree is a bit trickier20:07
ScottKAnd we should have a clear policy on this in any case since it comes up routinely.20:07
sorenIt's amazingly difficult to get them all to agree to such an exception (even though they probably pretty much all would, it's nearly impossible to track them down and get their sign off).20:07
kees"please send patches to remove your code if you don't agree". :P but yeah, I know I'm a crazy person.20:07
cjwatsonSo, I stand by my plain reading of the licences.  I would be happy to defer to the opinion of the licensors, but if they can't all be found then that's hard to achieve.20:08
ScottKIt seems to me that given the history of the system library exception, it's pretty clear what the intent is in the GPL text.20:09
keesso do we have a specific thing about this that we need to discuss at this time?20:10
keesthat sounds like "no", so I guess we're done here. :)20:11
cjwatson(I do recognise that this position is inconvenient, but I can't in good conscience sign off on a reading that looks like a violation based on the plain reading.)20:12
cjwatsonOr something better phrased.20:12
keescjwatson: so you don't agree that the system library exception matches these cases?20:12
cjwatsonI do not.20:12
cjwatsonI believe I laid out my position in https://lists.ubuntu.com/archives/technical-board/2013-May/001603.html20:13
cjwatson(I certainly believe that the licensors are entitled to jointly select a different reading)20:13
keesokay. but I don't think the TB needs to make a unified decision on this at this point.20:13
ScottKAs an archive admin, leaving it ambiguous is bothersome.20:14
cjwatsonDo we have archive admins who disagree?20:14
ScottKI thought we had a clear policy along the lines of what cjwatson suggests and I'd like to not leave it at DUNNO.20:14
cjwatsonOh, Dave is an archive admin, isn't he20:15
ScottKYes.20:15
stgraberI certainly agree with cjwatson on this and would be happy to make it policy if that makes things simpler for everyone (and we have consensus on this, at least for the TB if not TB+archive-admin)20:15
keesScottK: since several TB folks are missing currently, can you take this to the mailing list and rephrase it from the perspective of needing an official stance for archive-admin purposes?20:15
cjwatsonIf people disagree, I would appreciate it if they actually went to the trouble to refute my analysis ...20:16
ScottKkees: I can do that.20:16
keescjwatson: I'll see if I can refute it. you make it hard, though. :)20:16
keesokay, so anything else? otherwise, I think it's to mdz next meeting to chair (nick-alpha order)?20:18
sorenI have nothing else.20:20
keesokay, thanks!20:20
kees#endmeeting20:20
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Jun 10 20:20:45 2013 UTC.20:20
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-20.01.moin.txt20:20
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-20.01.html20:20
ScottKkees: My action is complete (sent the mail)20:25
=== Quintasan_ is now known as Quintasan
=== Logan_ is now known as Eating
bkerensahmm hmm hmm21:42
bkerensaWho is here for the Ubuntu Documentation Team Meeting?21:58
pleia2o/21:58
dsmythiesDoug Smythies is here for doc meeting.21:59
* godbyk is here for the ubuntu-docs meeting21:59
bkerensaGunnarHj and kotux too? :)21:59
bkerensa#startmeeting Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda22:00
meetingologyMeeting started Mon Jun 10 22:00:03 2013 UTC.  The chair is bkerensa. Information about MeetBot at http://wiki.ubuntu.com/meetingology.22:00
meetingologyAvailable 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 #votesrequired22:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic:
bkerensa#chair bkerensa22:00
meetingologyCurrent chairs: bkerensa22:00
bkerensaHello everyone and welcome to the Ubuntu Doc Team Meeting for June 2013 :)22:00
GunnarHjI'm here.22:00
bkerensaOur agenda is in the topic if you have not had a chance to read it yet22:00
kotuxhey bkerensa22:00
bkerensa#topic UDS Work Items Health Check22:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic: UDS Work Items Health Check
bkerensaSo the first thing on our agenda is to check on the progress of UDS 13.05 work items22:01
bkerensaI'm seeing right now we have only one done https://blueprints.launchpad.net/ubuntu/+spec/community-1305-doc-planning22:01
bkerensaany updates from those who have taken items?22:02
pleia2I sent the previous feedback emails to the list a couple weeks ago, hopefully that was helpful22:02
bkerensaMy "Review and update current documented processes" work item is nearly finished and I'm about half way done on a rough draft of "Update Getting Started Page"22:03
bkerensapleia2: excellent22:03
godbykMy item is dependent upon bkerensa's items.22:03
bkerensa:)22:03
dsmythiesthis page: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/BuildingDocumentation is reasobaly up to dete22:03
bkerensaSo it looks like I need to bang out my work by the end of the weekend22:03
bkerensa:)22:03
bkerensaIn regards to the getting started revamp22:04
GunnarHjIs everything "getting started related" included in the first item?22:04
bkerensado you think its important that we write out entire tutorials on DocBook or try and rely on a third party source for that?22:04
godbykbkerensa: I'd rely on a third party for the bulk of it, but if you're restricting the docs team to a subset of docbook, I'd note what that subset is.22:05
bkerensaGunnarHj: not really I think that covers some but does not give a A to Z of everything people will need to know to get started and feel somewhat comfortable with the process22:05
godbykTemplates, tips, etc. wouldn't be amiss either.22:06
dsmythiesNo, 90% of what I have learned is from example of stuff already done. Use 3rd party for anything else.22:06
bkerensakk22:06
GunnarHjI for one think it's not important to go too deep into DocBook or Mallard. To modify pages you can start with just looking at what the page looks like.22:06
bkerensaI was planning on deferring for example to developer.ubuntu.com for bzr configuration versus re-writing22:06
bkerensaGunnarHj: +122:06
bkerensaI just think a simple one page getting started with links to relevant tidbits is the best22:07
bkerensaI also think once we get this going we should offer mentoring22:07
godbykSort of..22:07
kotuxsame here, it should be in order too.22:07
godbykYou don't want a getting started page that just links everywhere, though.22:07
dsmythiesYes, suggest you use the serverguide single page as an example.22:07
godbykBecause as a new contributor, I don't want to read reference manuals for bzr, launchpad, docbook, mallard, etc.22:07
kotuxgodbyk, I'm in a similar situation actually22:07
bkerensaOk so since this is our next item22:07
godbykI want some step-by-step guides to get up and running quickly so I can fix the bug or make the improvement that I'm interested in making.22:08
bkerensa#topic  Discuss Collaboration on Final Draft Ubuntu Documentation Getting Started Wiki22:08
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic: Discuss Collaboration on Final Draft Ubuntu Documentation Getting Started Wiki
bkerensaWhy don't we have a etherpad up22:08
bkerensaand I will drop my rough draft in this weekend22:08
bkerensaand then we can polish it off as a team22:08
bkerensato the point we are all satisfied?22:08
godbykSure.22:09
dsmythiesO.K.22:09
kotuxno prob22:09
bkerensa#action bkerensa to push his rough draft to etherpad this weekend for final team polish effort22:09
meetingologyACTION: bkerensa to push his rough draft to etherpad this weekend for final team polish effort22:09
bkerensaSo I also want to have a hard deadline on which we can have it polished and on the wiki22:09
bkerensacan we say deadline being the 30th?22:09
GunnarHjSounds as a good idea. And I like the idea by godbyk with something that can make people get started quickly.22:10
kotuxGunnarHj, so do I.  All those readings are secondary to getting things done.22:10
GunnarHjFeel like you are switching topic a little too fast. ;-)22:10
dsmythiesPlease refer to the serverguide single page. It allows one to start in minutes. It is really good.22:11
kotuxbkerensa, it's a good date. Between 2 weeks to a month is ample time.22:11
bkerensadsmythies: will do22:11
bkerensadsmythies: and your input will be appreciated along the way22:11
dsmythiesO.K.22:11
kotuxdsmythies, the single page is not easy to find through navigation alone. But it's really handy.22:12
bkerensaany more concerns regarding getting started content?22:12
GunnarHjNope. An etherpad with what you got sounds fine.22:13
dsmythiesjust for reference for the minutes: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide22:13
GunnarHjdsmythies: tnx22:13
kotuxIt needs a place somewhere in the wiki SOON.22:13
dsmythiesYes it does.22:14
bkerensaok ready to move to the next item?22:14
kotuxok22:15
godbykyep22:15
dsmythiesyes22:15
bkerensa#topic Ubuntu 13.10 Doc TODO List: What do we want to accomplish in regards to the actual docs we ship22:15
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic: Ubuntu 13.10 Doc TODO List: What do we want to accomplish in regards to the actual docs we ship
bkerensaok22:15
bkerensaSo what do we want to and need to accomplish this cycle in regards to documentation we ship?22:16
bkerensaWhat do you consider essential?22:16
GunnarHjStarting working on it in good time before the release is the key point, I think.22:17
godbykI think it's important that we have up-to-date documentation.22:17
kotuxMore pictures22:17
bkerensaI think one of my biggest concerns is the screenshots22:18
GunnarHjAnother thing is that the GNOME docs must be imported in good time. It looks like we are moving to 3.8...22:18
kotuxhelp.ubuntu.com could be made compatible with mobile.22:18
godbykGunnarHj: Do we have instructions for importing the Gnome docs?22:18
dsmythiesAs you know, I work mostly on serverguide, which doesn't actually ship. However, we are considering to post all languages to help.ubuntu.com, just like desktop docs.22:19
GunnarHjI haven't. jbicha did it last time (far too late).22:19
godbykGunnarHj: Okay. We'll have to figure out how to do that, then.22:19
pleia2I'm inclined to keep our goals for this cycle as minimal as possible as I expect core members of the team will be spending their time onboarding new people22:19
GunnarHjgodbyk: right22:19
godbykpleia2: I agree.22:19
dsmythiesthere is already a bug report requesting epub format be available. I am not on board, becuase it is another thing to check that it compiles O.K.22:20
kotuxdsmythies, ok.  It is a good idea.22:20
GunnarHjdsmythies: Is it really a good idea to mess with yet another XML format?22:21
dsmythiesCurrently there issues for some langauges. I hope to spend time on the issues.22:21
godbykdsmythies: I'm not against it per se, but I don't think it should be a high priority at the moment.22:21
bkerensaexactly22:21
dsmythiesGunnar: It already happens, we just don't post it.22:21
bkerensaSo22:22
GunnarHjdsmythies: Can you elaborate on that?22:22
bkerensaDo we have someone who can make the screenshot script work?22:22
bkerensagodbyk: would you be willing to ping jbicha and find out about Gnome Doc Imports? Since thats like a majority of where our doc comes from22:23
godbykbkerensa: Sure.22:23
bkerensa#action godbyk to contact Jeremy Bicha to find out how Gnome-Doc Imports to Ubuntu-Doc works22:24
meetingologyACTION: godbyk to contact Jeremy Bicha to find out how Gnome-Doc Imports to Ubuntu-Doc works22:24
phillwbkerensa: if you use quickshot, it is being worked upon as we speak.22:24
dsmythiesThe .pot and .po tranlsation cycle already exists for serverguide. We just seem to leave it to the regions to deal with. We have had requests to post the other lanagusges. Desktop already does this22:24
godbykphillw: I suspect it'll be a while before Quickshot is up and running again, though.22:24
bkerensaphillw: we have in the past used a script but its broken... It would take vanilla screenshots22:24
dsmythiesMy paln was to post the prelim version of help.ubuntu.com for 13.10 much earlier than I did for 13.04 and provide examples. Without committing the required script changes to the main branch.22:26
bkerensaWell lets re-visit the screenshot issue at another time as I plan for us to have more meetings in advance of release22:26
phillwgodbyk: we'll see how Thomas gets on, I have offered an additional python programmer to assist.22:26
kotuxI think someone should report on launchpad the non-working script and its current problems.22:27
godbykkotux: I agree. Filing bugs for our own scripts and other to do items sounds like a good idea.22:28
GunnarHjHow do we identify new Ubuntu specific areas for the docs?22:29
GunnarHj(Ubuntu specific = not GNOME)22:29
kotuxOrganization from the start goes a long way. ;)  That's how I felt while I was sifting through the launchpad bugs the past few days; so many of them (pretty old) did not get the attention they deserved.22:30
bkerensaShall we move on to the next item?22:30
bkerensawhich is bugs22:30
bkerensa:)22:30
GunnarHjI think the question I just asked is important...22:31
kotuxcan anyone answer GunnarHj?22:31
dsmythiesearlier Kevin said: "I think it's important that we have up-to-date documentation." I could not agree more. It is becoming difficult to call help.ubuntu.com the "official documentation".22:31
bkerensaGunnarHj: Well most of Ubuntu uses Gnome system apps22:32
dsmythies... sorry for my chime in on that one...22:32
bkerensaGunnarHj: if you look at the doc files they have authors and such and most of the gnome doc has gnome authors22:32
bkerensawhere the Ubuntu specific is Jeremy or someone else with an @ubuntu.com e-mail22:32
GunnarHjYes, but Ubuntu is not only GNOME admin tools.22:32
bkerensabut there is not a specific tag necessarily that I know of22:32
GunnarHjIf nobody knows a good answer, maybe there is another task that should be put on the blueprint?22:33
godbykGunnarHj: I'll ask Jeremy about that, too. When we do the import from Gnome, we can probably get the list of files at the same time.22:33
kotuxI second that.22:34
bkerensa#action godbyk to check with jbicha to see about identifying Ubuntu specific doc22:34
meetingologyACTION: godbyk to check with jbicha to see about identifying Ubuntu specific doc22:34
GunnarHjgodbyk: May be a good start.22:34
bkerensaOk we have to move along as other people will need this channel ;)22:34
bkerensa#topic Addressing Bug Triage Questions22:34
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic: Addressing Bug Triage Questions
bkerensaSo godbyk wanted to have Ubuntu Doc Bug Triage up for discussion since kotux has been doing an epic amount of tidying of Ubuntu Doc bugs22:35
bkerensagodbyk I will let you start this discussion off22:35
godbykbkerensa: Thanks.22:36
godbykkotux and I have been working on the ubuntu-doc bugs lately.22:36
godbyk(Though it's been mostly kotux -- thanks!)22:36
godbykWe just wanted to check in and see if we've been handling them correctly.22:36
godbykA few questions:22:36
kotuxyup.  Yeah, more tidying left to go.22:36
godbyk1. If a bug is misfiled under ubuntu-doc, and we're not sure where it should be reassigned, how do we handle it?  Assign it to ubuntu generally?22:37
godbyk2. Are there and project-wide tags or project names that we should use for the various projects that reside under the ubuntu-docs umbrella?22:37
godbykFor example, docs for other *buntu flavors.. do they have different projects or tags?22:37
godbykI know the serverguide project is separate.22:38
bkerensajbicha: Quick Q: How did you import gnome doc into ubuntu doc?22:38
godbykAnd we've been trying to switch from ubuntu-doc to serverguide as appropriate.22:38
godbykkotux: Feel free to jump in with other questions you have or issues you've come across.22:38
jbichabkerensa: sudo apt-get install meld http://meldmerge.org/22:39
* kotux nods.22:39
GunnarHjAs regards the first question: Yes, reassign to Ubuntu if you can't figure out anything more specific.22:39
dsmythiesYes, thanks... for the serverguide added tags. Many bug reports never get seen by serverguide contributors, yet would be easy to fix.22:39
jbichabkerensa: and then just line up your git checkout of gnome-user-docs with your ubuntu branch22:40
bkerensajbicha: is there any tagging in docs to let us know what is upstream doc and what is Ubuntu Doc?22:41
godbykjbicha: Okay, thanks. I may ping you about it again in the future if I run into problems or have more questions about it.22:41
kotuxI've seen some bugs reported in non-English languages22:41
kotuxShould the descriptions be updated in English?  Google translate comes in quite handy.22:42
GunnarHjkotux: I would ask the bug reporter to add an English description.22:43
bkerensakotux: so for the bugs your triaging those are being reported on ubuntu-docs because help.ubuntu.com has ambigious footer22:43
jbichabkerensa: no, meld is really the only clue as to original source22:44
bkerensaok22:44
dsmythieshad an ambigious footer. It has been updated, for 13.04. Both serverguide and desktop.22:44
kotuxRight. I've noticed mostly bugs on wiki or system doc.  But some have been reported via apport, which was weird.22:45
bkerensahmm22:45
kotuxwell, a handful22:45
GunnarHjAs a general approach: As long as you understand what the bug reporter is saying, don't put too much effort on the triaging process. Better to just fix it. ;-)22:45
bkerensaI'm unsure why apport would send to ubuntu-doc22:45
kotuxbkerensa, It's a point to ponder.22:46
bkerensaindeeed22:46
kotuxGunnarHj, when it comes to fixing, sometimes, I have the impulse to test them.22:46
GunnarHjkotux: That's good, of course. So do I.22:47
kotuxBut I can't at times.  For instance, I don't have any Ubuntu server in my home to run from.22:47
GunnarHjAha, you are talking server... I think it's possible to set up a virtual thing for testing, but I'm not able to tell how.22:49
bkerensaIf the bugs are erroneously filed on ubuntu-docs they should be flagged incomplete and ubuntu-docs should be dropped and they should be moved to whatever they really effect22:49
bkerensaideally Ubuntu Bug Squad should be doing this work22:49
bkerensa;)22:49
* bkerensa pokes bdmurray 22:49
bkerensabut anyways lets get this last item discussed22:50
bkerensathe next team will need the channel22:50
kotuxk, thanks for bringing that up bkerensa22:50
bkerensa#topic Discussion surrounding requests to join team22:50
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Agenda: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Current topic: Discussion surrounding requests to join team
bkerensaSo22:50
GunnarHjbkerensa: Uhm.. I don't think that's a good way to use "incomplete".22:50
bkerensaI wanted to quickly discuss how we will continue to direct people in regards to joining the team22:51
bkerensaright now the process is   1. Get some commits in to show your contributions 2. Mail the list 3. Wait for mdke to add you22:51
kotuxThis is where marketing and publicity come into play.22:52
kotuxmdke?22:52
godbykbkerensa: I think that process is okay for now except step 3 should be replaced with more people having rights to add people to the team.22:52
bkerensaI think having mdke be the gate keeper for that is akward since he is not officially involved in any part of Ubuntu anymore and has not been for some time22:52
pleia2godbyk: +122:52
godbykAnd I'm guessing that the CC doesn't want to keep their role in step 3 either. :)22:53
bkerensaso my thoughts on that are that we could create subteam22:53
bkerensalike22:53
pleia2godbyk: yeah, we want to get off the team asap ;)22:53
bkerensa"Ubuntu Doc Leaders"22:53
bkerensaor something22:53
bkerensaand that team could add Ubuntu Doc Committers22:53
godbykbkerensa: Well, that's what the committers team is for, right?22:53
pleia2bkerensa: couldn't we just make 3 people admins and be done with it?22:53
jbichabkerensa: you don't need a subteam to add people, just make people admins22:53
godbykpleia2: +122:53
dsmythiesAs I have mentioned before, do not confuse administrsation with team leader.22:54
bkerensapleia2: +122:54
bkerensajbicha: +122:54
pleia2I really don't want to see another lp team :)22:54
kotuxpleia2: +122:54
bkerensapleia2: +122:54
pleia2good, #agreed!22:54
bkerensaso pleia2 would the CC ideally be ok with Dough Smythies, Kevin and myself to start and see how that goes?22:55
kotuxIs there a certain threshold for commits to be eligible?22:55
pleia2bkerensa: let's vote on that now, CC will respect the team's vote22:55
godbykkotux: There's no hard number at the moment.22:55
bkerensakotux: not currently22:55
godbykkotux: The idea is that we just want to know that the person requesting commit rights won't break everything. :)22:55
bkerensaok22:55
bkerensaso lets get a vote started22:55
kotuxgodbyk, right.22:55
bkerensa#voters godbyk kotux bkerensa dsmythies pleia2 GunnarHj22:56
meetingologyCurrent voters: GunnarHj bkerensa dsmythies godbyk kotux pleia222:56
GunnarHj+122:56
kotux:D22:56
dsmythiesSorry, I am IRC challenged and do not know how to vote. Sounds O.K. to me.22:56
godbykWhat are we voting on?22:56
bkerensa#vote Remove mdke and add dsmythies, godbyk and bkerensa to admin for onboarding22:56
meetingologyPlease vote on: Remove mdke and add dsmythies, godbyk and bkerensa to admin for onboarding22:57
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)22:57
bkerensa+122:57
meetingology+1 received from bkerensa22:57
pleia2+122:57
meetingology+1 received from pleia222:57
kotux+122:57
meetingology+1 received from kotux22:57
godbyk+122:57
meetingology+1 received from godbyk22:57
dsmythies+122:57
meetingology+1 received from dsmythies22:57
GunnarHj+122:57
meetingology+1 received from GunnarHj22:57
bkerensa#endvote22:57
meetingologyVoting ended on: Remove mdke and add dsmythies, godbyk and bkerensa to admin for onboarding22:57
meetingologyVotes for:6 Votes against:0 Abstentions:022:57
meetingologyMotion carried22:57
bkerensaok22:58
bkerensawell that concludes the agenda22:58
dsmythiesThanks everyone...22:58
* kotux takes a stretch. 22:58
bkerensa#endmeeting22:58
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Jun 10 22:58:35 2013 UTC.22:58
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-22.00.moin.txt22:58
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-10-22.00.html22:58
kotuxYes, thank you everyone!22:58
bkerensa:s22:58
GunnarHjThanks all!22:58
bkerensaI have thee more meetings today22:58
bkerensa;P22:58
bkerensait never ends22:58
kotuxhaha22:59
kotuxglad I'm not THAT busy. :P22:59
godbykThanks, everyone, for coming.22:59
godbykWe can continue discussing things in #ubuntu-doc if you like.22:59
godbykBut we should probably get out of #ubuntu-meeting to free it up for the next meeting.23:00
=== Eating is now known as Logan_
=== Logan_ is now known as Lafawnduh
=== Lafawnduh is now known as log
=== biostudent_ is now known as biostudent

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!