/srv/irclogs.ubuntu.com/2005/11/10/#ubuntu-meeting.txt

mdkegood evening12:05
=== robitaille is around...but half listening (middle of my work day)
Burgundaviaok12:05
jeffschhello docteam peoples12:05
mdkehands up who is here12:05
mdkehi there jeffsch 12:05
mdke<-- matthew east12:06
robitaille<-- Daniel Robitaille12:06
=== Burgundavia is Corey Burger
Burgundaviamadpilot is likely at work or just getting home now12:07
mdkecool, we should wait a few minutes i think12:07
Burgundaviaok12:08
Burgundaviamight thought was that we discuss https://launchpad.net/distros/ubuntu/+spec/docteam-projects first12:08
Burgundavias/might/I thought12:09
mdkeerm12:09
mdkethere is no spec on the linked wiki page12:09
mdkeis that a spec, or just an excuse to make another LP page?12:09
Burgundavianot really12:09
Burgundaviathere is no spec because it should take a very short time, ie, one meeting12:10
mdkeok well stick it on the agenda12:10
mdkeperhaps explain what it is that it is getting at12:10
Burgundaviathe idea was that we should decide as early in the cycle as possible so that we could base decisions on that12:11
Burgundaviadecide what we want to do, that is12:11
mdkebut isn't that what we already do?12:11
mdkewe agreed 6 months ago to do that12:11
Burgundaviayes, I just codified it12:11
=== judax [n=judax@adsl-68-91-193-252.dsl.austtx.swbell.net] has joined #ubuntu-meeting
bhuvanbhuvan -> Bhuvaneswaran12:11
Burgundaviasalut bhuvan 12:12
bhuvansalute!12:12
judax<- Troy Williams12:13
judaxis there a meeting, why so quiet?12:16
Burgundaviaare we expecting Jerome or Rob?12:16
mdkeyes, both12:16
Burgundaviajudax, we are waiting for Jerome and Rob12:16
judaxok, sounds good12:16
BurgundaviaI will clean up the DocteamProjects page after the meeting, based on what we decide12:17
jeffschBurgundavia: when you do that, can you change the style guide to wip?12:18
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
jeffschit should go to version 1.5 for now, then 2.0 at time of dapper release12:18
mdkeok we should probably start i guess12:18
Burgundaviajeffsch, yep12:19
Burgundaviasounds good12:19
jeffschthanks12:19
mdkeagenda is here: https://wiki.ubuntu.com/DocteamMeetingAgenda12:19
mdke1. Repository layout12:19
Burgundaviafirst item is https://wiki.ubuntu.com/DocteamRepositoryLayout12:19
mdkethe layout is pretty similar to what is already there12:19
mdkewith a few differences, i.e. the absence of teamstuff, debian folders etc12:20
mdkeany thoughts?12:20
judax+1 on layout12:20
mdkefine by me too12:21
judaxthink the wrench was the stuff from Sean on Kubuntu, right?12:21
judaxthink we can move on quickly from that12:21
mdkeguess so12:21
mdkeme too12:21
mdkedoes anyone think we should change "kde" to "kubuntu" and "gnome" to "ubuntu" as per the structure on that wiki page?12:21
mdkeno big deal, but if we are gonna do it, we should do it soon12:22
=== phig [n=pedro@20150078090.user.veloxzone.com.br] has joined #ubuntu-meeting
bhuvanimo, we should. it makes things more clear12:22
judaxmatters not to me12:22
mdkefine with me too12:22
jeffschwe will have to revise the build scripts and whatnot, but i suppose we have to do that anyway12:23
mdkeyeah12:23
mdkethat will need redoing anyway12:23
mdkethe debian folder needs to go in "gnome" i guess12:23
mdkekde/debian is already there12:23
Riddellmdke: yes but ubuntu covers stuff that kubuntu uses too like serverGuide12:23
BurgundaviaI like the new layout, don't see any reasons not to adopt it12:23
Burgundaviaok, move on to item 2?12:24
Burgundavia2nd item is ServerGuide spec12:24
Burgundaviado we want to identify authors of specific things before we move onto specific docs?12:24
mdkeRiddell, if we have documents which apply to both we'll put them in a generic folder at the top of the tree12:24
mdkeright?12:24
mdkeRiddell, i'm right to say there should be a gnome/debian and a kde/debian, rather than a debian/ and a kde/debian, yeah?12:25
Burgundaviaare we planning any generic docs?12:25
mdkethe server guide would be generic i think12:25
Burgundaviayes12:25
mdkeand there may be more, such as docs ported from the wiki12:26
Burgundaviawhat about a top level server directory12:26
mdkei think generic/ is the best way to go12:26
Riddellmdke: no, w il sare debian packaging12:26
=== mdke blinks
Riddellno, we will share debian packaging12:26
RiddellI talked about this with dholbach12:26
mdkeRiddell, so kde/debian needs to move?12:26
Riddellyes12:26
mdkeRiddell, could you run us through that?12:27
mdkeit's the first we've heard12:27
judaxdamn, I have to go, sorry will read the logs12:27
Riddellwe should be ubuntu/ kubuntu/ common/ and debian/12:27
mdkeRiddell, sure, i mean can you run us through the reasons?12:28
=== corey_ [n=corey@209.104.102.193] has joined #ubuntu-meeting
=== jane_ [n=JaneW@209.104.102.193] has joined #ubuntu-meeting
=== einheit_ [n=steve@209.104.102.193] has joined #ubuntu-meeting
=== ogra_ [n=ogra@209.104.102.193] has joined #ubuntu-meeting
=== mez_ [n=Mez@209.104.102.193] has joined #ubuntu-meeting
mdkebecause i think that is likely to prevent ubuntu-docs from moving to gnome-doc-utils build process12:28
=== doko_ [n=doko@209.104.102.193] has joined #ubuntu-meeting
corey_bloody hell12:29
ajmitchthe usual conference fun12:29
corey_mdke, why?12:29
RiddellI don't know about gnome-doc-utils12:29
Riddellnetwork here is terrible12:29
corey_Riddell, I mentioned it to you12:29
=== mdz [n=mdz@66.103.220.155] has joined #ubuntu-meeting
mdkeRiddell, we have been talking about moving to it with jbailey 12:29
Kamionmdke: mdz and I think that your comment about a documentation string freeze on DapperReleaseProcess is pretty much at the discretion of the doc team12:30
corey_mdke, jbailey will no longer be involved with packaging12:30
Kamionit seems perfectly reasonable to me12:30
mdkecorey_, so?12:30
mdkeKamion, cool thanks12:30
corey_mdke, dholbach and riddell will be doing it12:30
Kamionmdke: except that pushing it back a week makes it collide with the distro's string freeze12:30
mdkecorey_, i know, but what does that mean?12:30
mdkeKamion, we'll have to give it some more thought12:31
corey_mdke, jbailey is moving into support completely, away from half distro, half support12:31
Kamionmdke: ok, I don't think it needs to be decided immediately12:31
Kamionanyway, apologies for interrupting your meeting12:31
mdkecorey_, you've said that on the mailing list, but what has that to do with gnome-doc-utils?12:31
corey_mdke, not much12:31
mdkeKamion, np thanks for the indication12:31
corey_but we are straying far from the agenda12:31
mdkei disagree12:32
mdkethe position of debian in the tree is part of the repository structure12:32
mdkeanyhow, we can come back to it maybe?12:32
corey_we can talk about packaging at the next meeting, when it matters more12:32
corey_or in between12:32
mdkeok, we'll just leave the debian stuff where it is for now then12:33
mdkeitem 2?12:34
corey_moving the debian stuff will not majorily affect the writing of docs12:34
mdkeno one is talking12:34
mdke:/12:34
corey_yes12:34
corey_shall we pass over the specific doc specs until we decide who is writing what?12:34
mdkei hope people will feel free to write anything12:34
=== kjcole [n=kjcole@66.103.220.236] has joined #ubuntu-meeting
corey_yes, but having one person that says they are working on one thing makes certain it is going to get written12:35
rob^sorry here12:35
corey_salut rob^ 12:35
mdkenot that certain :p12:35
rob^hi corey_ 12:35
corey_yes, but more chance12:35
mdkeanyhow, we should continue the current system of people being responsible for docs12:35
kjcoleWell, that took bloody forever!  (Wireless being uncooperative.)12:35
corey_kjcole, you want to introduce yourself?12:36
rob^brb12:36
kjcoleNah.  ;-)  Kevin Cole from Gallaudet University, Brain-Washington, DC.12:36
corey_an LTSP guy12:36
mdkehello12:36
kjcoleHi all.12:36
corey_too bad jerome is not here12:37
mdkeitem 2: has everyone looked at the spec server guide?12:37
corey_mdke, did here what I said?12:37
=== davidj_ubz [n=david@66.103.220.158] has joined #ubuntu-meeting
corey_davidj_ubz, welcome12:37
mdkecorey_, tbh if you eliminate specific docs, there is not gonna be much left on the agenda12:37
corey_davidj_ubz, you want to introduce yourself?12:37
kjcolemkde: Nope.  I'm relatively new here, and will probably watch, as I have much catching up to do12:37
davidj_ubzcorey_: thank you.  I'm sorry I couldn't join you sooner.12:37
davidj_ubzI am the ltsp translations lead.12:38
mdkehi davidj12:38
davidj_ubzmdke: Hello.12:38
corey_mdke, not really. We can talk about what specifically each of us want to do, which helps the LTSP people and others a good idea of who to talk to12:38
corey_and people can begin drafting specs for docs12:38
=== mdke is totally confused as to what is going on
corey_mdke, I propose we swap the desktop/server guides to after the decision of the who is doing what12:40
mdkejust go ahead12:40
corey_ok12:40
mdkeif you put something on the agenda page or say something here, it'll help me understand12:40
corey_ok12:41
corey_my thought was that people would say what they wanted to do for dapper12:41
corey_I want to work primarily on the wiki and the launchpad landing pages12:41
corey_after they said that, I would edit the docteamprojects page accordingly12:42
rob^a half a slab of beer and greezy bacon and eggs at the hotel bar plays havac on your insides12:42
mdkeheh12:42
mdkeis the DocteamProjects page out of date?12:42
mdkei updated it only last week12:43
mdkeand the kde stuff is quite up to date too i think12:43
bhuvanbut, couple preview/status pages were broken12:43
rob^what are we up to?12:43
bhuvans/couple/couple of/12:43
mdkerob^, we're off-agenda for the moment12:43
rob^ah12:43
mdkebhuvan, yes, it is so early in the cycle that previews won't work properly right now12:43
corey_rob^, we are discussing what each person is doing for the dapper release cycle12:44
bhuvani meant, it was leading to wrong url12:44
rob^ok12:44
bhuvancouple of links had been corrected12:44
mdkebhuvan, no big deal, but we can remove links if they are broken12:44
rob^well I'm happy to keep working on the desktop guide and help contribute to the server guide12:45
mdkebrb, switching computers12:45
corey_excellent12:45
corey_bhuvan, what would you to work on for the dapper release?12:45
mdkerob^, will you be working on kubuntu docs?12:45
bhuvani must contribute to server guide spec12:46
corey_bhuvan, do you want to be the primary author of the server guide?12:46
mdkeerm12:46
mdkehe hasn't got commit access yet12:46
corey_that is fine12:46
rob^mdke, most likely not, I offered some help to the kubuntu desktop guide/faqguide but jjesse said he had it under control12:46
corey_commit access is not a major barrior12:46
corey_s/barrior/barrier12:47
mdkeperhaps some patches first corey_ ?12:47
corey_mdke, sure12:47
rob^+1 to that12:47
bhuvani can submit patches to server guide12:47
corey_what I am trying to have by the end of this meeting is a clear idea of who is working on what12:47
mdkethe requirement is to enable us to see that the new contributor is serious, which I am sure is not a problem in bhuvan's case, but i think it should remain12:47
corey_so if other people come to ask, we can point them to the correct person12:47
mdkeperhaps asking newcomers to take responsibility for a whole doc is unrealistic12:48
corey_and we can thus create specs before the next meeting to be talked about12:48
rob^mdke, agreed12:48
mdkeanyhow, i hope to contribute to the desktopguide, and continue working on translations and taking care of the server. Also I am gonna push the better-wiki-docs spec12:48
rob^I think they should start by just submitting small patches that fix typos, bugs etc12:48
rob^mdke, are you still going to take the lead on the server guide?12:49
mdkeno, i never intended to really12:49
mdkeyou are heaps more technically proficient, and bhuvan too12:49
kjcoleAs I mentioned to Corey and Jane, I'm leaning towards involvement with Edubuntu docs, particularly stuff based on the Tuxlab Cookbook... I think.12:49
rob^oh, I kind of assumed you were..12:49
rob^np12:50
mdkekjcole, that is awesome12:50
rob^yes, edubuntu can use some love12:50
Burgundaviajeffsch, are you going to be working on the style guide again?12:50
jeffschyep12:51
Burgundaviaare we going to drop the learn linux stuff from our repos?12:51
rob^if (and I mean IF) I get time I'll do something for xubuntu too, but it is very low priority12:51
rob^Burgundavia, we 12:51
rob^grr12:51
mdkeBurgundavia, let's keep to the agenda as much as we can12:52
BurgundaviaI am12:52
mdkethat is last12:52
Burgundaviawe are discussing specific people and specifc docs for dapper12:52
mdkeok12:52
mdke-1 on learn linux12:53
mdkeit is being actively developed elsewhere12:53
rob^so why do we need it?12:53
mdkewe don't12:53
=== mdy [n=mdy@209.104.102.193] has joined #ubuntu-meeting
rob^so why do we need to keep it?12:53
mdkewe don't12:53
Burgundaviaok12:53
mdkeeveryone ok with scrapping that?12:53
Burgundaviays12:54
rob^np here12:54
mdkeok, on we go12:54
rob^lazerjock expressed intrest in working on the motu/packaging doc12:54
BurgundaviaI spoke with motus about moving to our repos12:54
rob^he works with motu already iirc12:54
Burgundaviathey liked the idea12:55
mdkeLaserJock!12:55
rob^I think it would be excellent12:55
LaserJockI am a MOTUWannabe kinda but I have more interest in new user documentation12:55
mdkewelcome12:55
mdkeLaserJock, are you only interested in working on a packaging guide, or also other docs?12:55
kjcoleLaserJock, we may be in the same boat...12:56
LaserJockwell, I don't know. I don't have much time (I just started a MOTUScience team)12:56
mdkefair enough12:56
bhuvanok. with regard to server guide, as i'm new, if someone takes the lead, i'm sure to back them consistently and stand responsible for dapper release12:56
LaserJockI really don't know how much time is required, etc.12:57
LaserJockI don't want to bite off more than I can chew ;-)12:57
mdkebhuvan, that's great news, rob^ has also said he will work on it12:57
Burgundaviaok, added the packaging guide to DocteamProjects12:57
rob^bhuvan, well I can do that for now as I know the guide12:57
mdkeLaserJock, no obligations :) whenever you wanna submit a patch, we'll check it out and apply it12:57
BurgundaviaLaserJock, you want to speak with Unfrgiven to get us the doc so we can put it into our repos?12:57
LaserJockmdke: thanks12:57
LaserJockBurgundavia: will do12:57
mdkethank you12:57
Burgundaviathanks12:58
=== fabbione [i=fabbione@66.103.220.245] has left #ubuntu-meeting ["Leaving"]
rob^bhuvan, when your ready we can organise a commit account and you can take over12:58
bhuvanok12:58
mdkeshall we talk about the server guide a little?12:58
rob^sure12:58
mdkedoes anyone have any comments on the spec?12:58
rob^I just did a brain dump on there a few days ago12:58
rob^I think some of the AD stuff could go though12:59
mdkeI'd like to see the section titles a little more user friendly12:59
bhuvanok12:59
mdkealthough obviously a server guide will be targeted at experienced users...12:59
bhuvanimo, we can be more specific12:59
mdkei think that some bits will be very relevant to new users12:59
mdkeand we should make em accessible12:59
rob^so would I, but I just wanted to get the relevent parts we need to cover on the page12:59
mdkesure, the material rocks01:00
mdkebhuvan, go on01:00
rob^so its pretty raw01:00
bhuvanwe can add few more sections under under services section (for example, under http we can add howto configure module)01:00
bhuvanif need be, we may also add details about webmin01:01
bhuvanagain under ftp, we can add pros/cons various ftp servers01:01
mdkegood idea01:01
rob^bhuvan, I thought about webmin myself, it should be there as well01:01
mdkealthough there is a module section under http01:01
bhuvanok01:01
mdkebhuvan, feel free to work on it and expand it before the writing starts01:01
rob^bhuvan, feel free to go nuts on that wiki page01:01
bhuvanok01:02
rob^heh01:02
bhuvansure01:02
mdkei'd like to see it as user-accessible as possible, personally01:02
bhuvanok01:02
mdkeelse, people will complain that we cut stuff out of the faqguide and made it hard to get at01:02
Burgundaviacan everybody check DocteamProjects, as I have updated it quite a lot01:02
bhuvanok01:02
rob^mdke, sure but as everything will be done on the command line you still need to get everything across, just explain it properly01:03
bhuvananyhow, server guide is meant for admin/experieced users, imo01:03
rob^what is Docs on the wiki?01:03
mdkerob^, it's the section titles I'm really concerned about, because that will be the key to allowing people to access the simpler sections01:04
rob^and Launchpad Landing pages?01:04
mdkeBurgundavia, yeah the docs on the wiki section is redundant, we have wiki pages01:04
=== jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
mdkemorn01:04
jsgotangcosorry *blushes*01:04
rob^hi jsgotangco 01:04
jsgotangcoi slept at 3am01:04
jsgotangco:)01:04
ajmitchhi jsgotangco 01:04
Burgundaviamdke, we need a person that people can talk to about the wiki01:04
BurgundaviaI am volunteering for that person01:04
mdkeBurgundavia, there is a wikiteam section on that page01:04
=== uniq [n=frode@213.184.199.55] has joined #ubuntu-meeting
mdkeBurgundavia, we also have a mailing list, and irc01:05
Riddellcan DocteamProjects please reference KubuntuDocs01:05
rob^maybe just make the pointer to the wiki team more obvious01:05
mdkei don't see a need for a specific person01:05
Burgundaviamdke, I don't completely understand01:05
Burgundaviamdke, I do01:05
jsgotangcoRiddell: sure I'll update it now01:05
rob^Riddell, it does01:05
Burgundaviarob^, I will clean that up01:05
mdkeRiddell, all the kubuntu docs are there01:05
mdkeBurgundavia, go ahead01:05
rob^great :)01:05
mdkewhy is there a need for a single point of contact for the wiki?01:06
Burgundaviamdke, currently the wiki pages are second class citizens. I want to remove that01:06
mdkesure, we all do01:06
mdkethere are loads of ways to try and do that, but how will a SPOC help?01:06
Burgundaviathat is why we have someone who says "I am working on the wiki as my primary doc'01:06
rob^maybe a more obvious pointer on the main wiki page to the wikiteam is needed too01:07
mdkewe have a whole team that says that corey01:07
Burgundaviayes01:07
=== jsgotangco just suggest use the wiki lp team
Burgundaviayes, but most of them do only very small amounts01:07
mdkeBurgundavia, my question is, how does a SPOC help? I'm not saying that you shouldn't do loads of work on the wiki01:07
=== Burgundavia is baffled about the objections
=== jsgotangco then make the most out of the current lp team
bhuvanor, we can maintain a list of things to do on wiki. whoever has time or inclined can take it and close it ?01:07
mdkebhuvan, absolutely01:08
Burgundaviabhuvan, we already have a list of things to do01:08
bhuvani meant, it must be active01:08
Burgundaviabhuvan, it is, CategoryCleanup01:08
jsgotangcocan LP be used to manage the work?01:08
mdkeBurgundavia, i just wanna understand why you think having one person who appears to be, for the purposes of the outside work, "in charge" of wiki work, will help01:09
rob^Burgundavia, no objections to having a pointer to wikiteam and yourself, but it doesn't belong in the table as a "book"01:09
mdkeoutside work/outside world*01:09
Burgundaviarob^, but is a docteam project01:09
bhuvanimo, its one of them. for example, if we come accross a wiki page with broken links as such, we can make an entry in the todo page and address it when we get time01:09
rob^Burgundavia, that table is for books01:09
=== jsgotangco thinks it would only be applicable if the wiki had ACLs
Burgundaviaok, I removed the header at the top that mentioned books01:09
Burgundavianow the page is all about the general projects we do, regardless of where they are developed01:10
rob^eh01:10
mdkebut why is one person in charge of the wiki? that's not what the wiki is about01:10
Burgundaviamdke, no, not one person in charge, one person who is going to devote most of their time to the wiki01:10
=== rob^ mumbles something about the docteam not having control of acls on thw wiki..
mdkeyou are free to devote that time, and I encourage it, but why SPOC? the wiki is an alive nest of contribution from all01:11
Burgundaviabecause a SPOC creates order01:11
Burgundaviathe wiki needs order, very badly01:12
jsgotangcoa team doesn't?01:12
Burgundaviayes01:12
=== jsgotangco thinks its just a matter of communication
BurgundaviaI am basically already that person, I am just talking the role01:12
Burgundaviafor all pratical matters, it will matter very little01:12
jsgotangcosure01:12
mdkehmm01:12
mdkei'm slightly concerned by this01:12
mdkebut let's move on01:12
=== jsgotangco still doesn't get the idea of wiki master unless there are ACL rights involved
Burgundaviaif it becomes a problem, lets raise the specific issue01:13
rob^if we had control of the acl and moin settings for the wiki then sure we would need a person who can devote time, otherwise its meaningless01:13
mdkeeven then01:13
Burgundaviawell, lets get that01:13
mdkehenrik is the admin of the wiki01:13
robitailleand he is on that wiki LP team...01:13
mdkeand having a volunteer as "wiki king" is a bit odd01:13
Burgundaviayes he is01:13
Burgundaviabut the current wiki doesn't work, I am going to devote myself to understanding why it doesn't and where we can go to make it work01:14
rob^the wiki is a community thing..01:14
mdkei would prefer a group to be the contact for the wiki01:14
mdkerob^, +101:14
Burgundaviabloody hell, I am not going to stop people writing on the wiki01:14
rob^mdke, +101:14
robitaillepersonally I think on that DocteamProjects table we should simply put WikiTeam as the contact "person".01:14
mdkeBurgundavia, we are not going to stop you either01:14
Burgundavianor am I am going to tell people to shove off01:14
rob^Burgundavia, we never said that01:14
=== jsgotangco still thinks the lp team is more than enough, just make it active
mdkeok well there is a reasonable consensus about this01:14
robitailleis there a way to send to send an email to all themember of a LP team?01:15
Burgundaviajsgotangco, communites usually form around one key person01:15
mdkerobitaille, we have a mailing list01:15
jsgotangcosure in the end, that person becomes overwhelmed01:15
mdkeBurgundavia, dictatorships do anyhow01:15
jsgotangcowell anyways, im not that much of a wiki person, i guess i'm not the right person to say it01:16
robitaillemdke,  true.  01:16
Burgundaviacurrently I have no different rights than anyone else and I don't expect tath will change very soon01:16
rob^we should move on, either way there is nothing we can do about it as we don't control the wiki01:16
mdkeok let's move on01:16
mdkeBurgundavia, i think you've seen that the team prefers the wikiteam to be the contact01:16
rob^Burgundavia, if that changes, then sure I'm happy for you to lead it01:16
=== Burgundavia is completely baffled
Burgundaviawe are yelling at ghosts01:16
jsgotangcoBurgundavia: go ahead with the plan if you think it's the right path, we don't have ACLs at the moment, i don't think it'll change much :)01:17
Burgundaviano, I don't think it will either01:17
jsgotangcolet's see how this pans out :)01:17
Burgundaviabut we need someone who says "I work on the wiki"01:17
jsgotangcoyes01:17
mdkeBurgundavia, we have a group who says that01:17
Burgundaviaotherwise it will continue towards entropy01:17
mdkeah well, this is stale01:17
Burgundaviamdke, they are not stopping the entropy01:17
jsgotangcoat least i'll have someone to yell at when something gets borked :)01:17
mdkelet's move on01:17
=== rob^ points at the agenda
Burgundaviajsgotangco, that is primary reason why I stepped up01:18
jsgotangcook good enough for me then :)01:18
mdkei've always hated the idea of team leaders in Ubuntu01:18
mdkethey don't work01:18
jsgotangcomdke: well the distro works :)01:18
rob^heh01:18
mdkeyes01:18
=== jsgotangco is in a nice saturday morning cartoons mode
Burgundaviayes, but neither does a completely anarchy01:18
mdkeagreed, hence the team01:19
Burgundavialike the current wiki01:19
=== rob^ bashes head against wall
Burgundaviayes, but the team is currently not helping01:19
mdkethat has nothing to do with having a SPOC01:19
mdkethe problems on the wiki are deeper than that01:19
Burgundaviayes it is01:19
rob^(less painful you see)01:19
mdkerob^, :)01:19
=== mdke shuts up
jsgotangcoquit it guys :)01:19
Burgundaviamdke, I agree, hence why I am going to devote all of my doc team time to it01:19
rob^Burgundavia, cool go nuts01:20
=== mdy [n=mdy@209.104.102.193] has left #ubuntu-meeting ["Kopete]
rob^anyway..01:20
jsgotangcook so we have Burgundavia do all the wiki work sounds good01:20
rob^have we done repository layout?01:20
jsgotangcoBurgundavia: go nuts on the LP team as well, slave them up if possible, they didn't sign up for nothing :)01:20
rob^even if we don't change much around, some redundant stuff needs to go01:21
Burgundaviamdke, I don't have my freenode password here on this laptop, and thus cannot talk back to you in a /query01:21
=== robitaille hides in a corner since he hasn't done a lot of wiki work lately
rob^or at least sectioned off01:21
mdkeah crap01:21
=== rob^ goes an makes a coffee
bhuvannext its desktop guide ?01:22
mdkeyes, ok01:22
mdkeqanda format?01:23
mdkei'd like to scrap it, any views?01:24
Burgundaviamdke, scrap which?01:24
mdkethe phrasing of the questions in the desktop guide01:24
mdke(agenda)01:24
Burgundaviaah01:24
jsgotangcoqanda sets01:24
BurgundaviaI am don't know either way01:25
BurgundaviaI would like to get some real feedback01:25
bhuvandesktop guide. it's going to be q/a format or book format ?01:25
mdkeme too01:25
mdkehow?01:25
jsgotangcothe qanda works, why change it totally?01:25
mdkehang on01:25
mdkei like the qanda, i just don't like the patronising way it the questions are phrased01:26
mdkei think qanda could be continued, but without questions01:26
mdketell me if I didn't explain that properly on the agenda01:26
rob^back01:26
jeffschok, i have to go. cya later01:27
bhuvanok01:27
rob^mdke, I think it could still be a book anyhow01:27
bhuvanbut without questions01:28
rob^the qanda format is more for a faq type doc but the guides are moving away from that01:28
rob^the faq guide is a bloody big faq too01:28
mdkei think the qanda format preserves clarity and keeps things to the point01:28
rob^yes but it doesn't leave as much room for explination imo01:28
=== kjcole [n=kjcole@66.103.220.236] has joined #ubuntu-meeting
rob^ie it doesn't suit the format, as you said qanda is to the point01:29
rob^can we have a mix?01:30
mdkeis it not possible to separate the explanation from the answers in some subtle way?01:30
mdkethe reason people like the faqguide is that it is quick and easy01:30
mdkeif we get bogged down, another ubuntuguide will spring up01:30
rob^mdke, usually with <note> tags01:30
BurgundaviaMatthew Thomas likes the idea of dropping the q/a style for the faqguide01:30
rob^thats true01:30
mdkeyou can't combine <para> and qanda?01:30
rob^yes01:30
mdkeok...01:31
rob^but the how many faqs have you seen that have lots of paragraphs for each answer?01:31
bhuvanwhy are we retaining the q/a type, because its from faqguide ?01:31
mdkei think we are falling into the error of being tied to the terminology of "faq"01:31
jsgotangcobecause it works as is01:31
mdkethe qanda thing works IMO01:31
mdkejust because there is no longer going to be a document called faq, that is no reason not to use helpful technology01:32
rob^well what would be the best way to form the questions?01:32
jsgotangcoits basically "snappy answers to stupid questions" kind of thing01:32
mdkeok lemme give you an example01:32
mdkewhat is a question in the guide?01:33
rob^the "how do I" format reminds me of an idiots guide 01:33
mdke"How can I setup apache" -> "setting up apache"01:33
mdkeno need to change anything technical01:33
rob^whist we are on this topic, what are peoples thoughts about installing packages (gai/synaptic/aptitude)?01:34
jsgotangcoi'd stick to gai01:35
mdkemy view is that we should explain various ways01:35
Burgundaviagai is getting much simpler for dapper01:35
rob^I really hope gai gets a way to install packages without the .desktop files (most of them)01:35
Burgundaviarob^, not going to happen01:35
Burgundaviarob^, file bugs on packages that don't have .desktop files01:35
rob^then what is the point of it?01:35
mdkeand when documenting a specific program, refer back to the installation instructions, and specify the package and the repository01:35
rob^thats 95% of the packages01:35
=== mpt [n=mpt@66.103.220.241] has joined #ubuntu-meeting
mptyo01:35
jsgotangcoyo01:36
Burgundaviarob^, because we can fix that01:36
Burgundaviarob^, anyway, offtopic now01:36
=== jsgotangco thinks stick to gai then go console if its not in gai yet
mdkeguys, guys01:36
rob^how? we need to figure out how we are going to write about it01:36
mdkewhat is wrong with documenting all installation methods?01:36
Burgundaviamdke, because we confuse users?01:36
mdkein any case, each individual section will not repeat the instructions, they will be in one place01:36
mpt"You can do this or do this or do this or do this" isn't good help01:36
jsgotangcobecause it defaats the purpose of creating gai in the first place?01:36
mdkempt, that is not how I would envisage doing it01:37
mptfor a complicated thing that people don't want to do often01:37
rob^mdke, because having to switch installation methods makes Linux and Ubuntu look stupid and hacker-ish01:37
mdkeyou dont' have to switch01:37
mdkeyou just explain the relative advantages and disadvantages01:37
mdkeits a guide, people can learn01:37
jsgotangcomdke: then its better off as a book01:37
=== mdke blinks
mdkewhat is the difference?01:38
mdkebook, guide, faq, whatever01:38
mdkeit's the same01:38
kjcoleMultiple choices confuse newcomers.  If you're going to offer all, recommend one more strongly, and make sure it's the first...01:38
rob^yes I agree01:38
mdkeoh sure01:38
mdkethat i take for granted01:38
kjcole(The first listed in the doc I mean.)01:38
=== jsgotangco didn't see Fedora or RHEL document various installation methods
mdkejsgotangco, if Fedora told you to jump off a cliff... 01:39
rob^heh01:39
mptNot all distro problems have a documentation solution01:39
mptConfusion about installation methods is a distro problem01:39
kjcoleI dunno...  Seems when I installed fedora I encountered references to both up2date and yum pretty quickly.01:39
mptSo just make the best of it.01:39
jsgotangcomdke: that's not the point, these new installation methods were made with a specific mindset and a general audience...01:39
rob^but installing packages is pretty important and solves most of our problems01:39
rob^in the docs01:39
kjcoleCould just be my faulty memory and a lot of pre-exposure to other RH variants.01:40
mdkejsgotangco, i agree. however the desktop guide addresses LOADS of things that you can't use gai to sort out01:40
rob^mdke, and thats the problem01:40
mdkei think it should be offered as the general means to install things, and then the alternatives should be explained and the advs/disadvs noted01:40
jsgotangcomdke: if you don't rally around gai, which is an ubuntu specific app, then whats your priority then01:40
mdkemy priority would be teaching users how things work01:41
jsgotangcomdke: gai still uses synaptic for all its worth, which can do most things that aptitude does (only aptitude is cleaner imo)01:41
robitailleactually you can call synaptic from within GAI, so technically most things can be done from gai01:41
rob^but then we can't stick to the point, we have to explain things01:41
mdkeand allowing them to try apt-get and see if they prefer it01:41
=== robitaille still still apt-get should off limits for official docs
jsgotangcomdke: sure but your guides must have scope in the first place, otherwise, you'll end up in a mess01:41
=== Lathiat [i=lathiat@ubuntu/member/lathiat] has joined #ubuntu-meeting
jsgotangcothe keywords here are "scope & limitation"01:42
mdkejsgotangco, yes, i think this can be done with minimal confusion, along the lines of what kjcole outlined01:42
mdkewe will lose a lot of readers if we don't explain how to use apt-get01:43
mdkeIMHO01:43
jsgotangcomdke: that's why google is our friend01:43
rob^but the thing is we did in the faq guide in Breezy, and listed the packages, and people still complained01:43
mdkejsgotangco, that is also why forked guides happen01:43
mdkerob^, yeah I don't think the approach of the faqguide is a long way off what I'd like to see01:44
jsgotangcomdke: you can't avoid those, people scratch their own itch01:44
mdkejsgotangco, we need to listen to people's itches01:44
mdkenot just our own01:44
Burgundaviamdke, we can talk about apt-get in the server guide01:44
rob^yep01:44
BurgundaviaI would remove it from the desktop guide01:44
jsgotangcomdke: in my opinion, it would take a full-time job to do such01:44
kjcoleIn fact, since it's HTML, a "surface document" that offers the most useful, simplest straightforward way for everything, and then a deeper layer for edge cases, or "challenging" stuff.01:44
=== jsgotangco thinks forking is good, after all the docs are licensed in a way that encourages them to use and modify it
mdkehmm01:46
mdkejsgotangco, so you don't like the current section in the faqguide about installing?01:46
rob^well I guess we will go gai then launch synaptic from gai when needed, and mention apt-get in the preface like the faqguide kind of did?01:46
=== Mez [n=Mez@66.103.220.192] has joined #ubuntu-meeting
mdkehmm01:46
mdkegai, then launch synaptic when needed is pretty lame, thinking about it01:47
bhuvanok. in addition, we must remove couple of sections from desktop guide which already exists in server guide01:47
bhuvanthey should not overlap01:47
rob^mdke, yep01:47
mdkebhuvan, yes, we haven't started doing that yet, they are currently identical copies01:47
rob^mdke, I know01:47
bhuvanok01:47
rob^well almost identical01:48
jsgotangcomdke: i didn't say i don't like it, its just not written in a way that ubuntu make it so, which is gai/synaptic, these apps were developed with a purpose of simplification, as much as possible, we as official documentors should focus on such projects, after all, what we write are part of the distro, as much as personal preferences on our side matter, it shouldn't01:48
mdkebut if gai is the only tool to install things from the menu, we have no choice01:48
mdkejsgotangco, the problem is that the desktopguide doesn't deal with things like "how to install gnome-blog" it deals with things like "install gstreamer0.8-plugins" or "gdesklets-data"01:49
Burgundaviamdke, synaptic is not going away for dapper and can be launched from within gai01:49
mdkeBurgundavia, yeah but if we ask people to search through gai for a package, then to open synaptic if they don't find it, they are gonna be pissed off at us01:49
Burgundaviamdke, yes, there is no clean solution01:50
rob^Burgundavia, not as far as I can see either01:50
mdkeunless we tell them where every single package is01:50
mdkeor use apt-get for everything :)01:50
Burgundaviaouch01:50
jsgotangcomdke: in the first place, gai isn't properlty documented yet, hence people will definitely assume a lot, that's why synaptic is mentioned as an advanced tool01:50
mdkeor synaptic for everything01:50
bhuvanwe can instruct to use gai in the beginning and continue to use synaptic01:50
kjcoleOops.  Time's flying, and I need to catch someone before 8:00 (Montreal time).  Ta-ta.01:50
bhuvaniirc, similar to debian dselect first and continue with apt-get01:51
jsgotangcolater kjcole 01:51
rob^I think this is more an issue of gai itself, heck even us documenters can't even figure this out!01:51
=== kjcole [n=kjcole@66.103.220.236] has left #ubuntu-meeting ["Konversation]
bhuvan:)01:51
mdkebhuvan, jsgotangco, but the problem is that the desktop guide does not only deal with installing mainstream programs, but rather installing niggly packages needed to configure stuff like dvds and such01:51
rob^all gai needs is a better way to install packages that are not in its lists, even just a simple dialog box where you could type the package names would suffice01:51
rob^then it is a one stop shop01:51
bhuvanwe are clear that couple of packages cant be found by gai. so we must look for an alternative, right ?01:52
mdkedoes it have a search tool?01:52
rob^its gai that is lacking here imo01:52
jsgotangcomdke: i'd really want to define scope and limiation for the docs atm, or else, it'll never end we're just trying to cover too much in my opinion01:52
mdkejsgotangco, ok are you suggesting scrapping the desktopguide? a lot of work went into it last release01:52
jsgotangcomdke: i didn't say anything about scrapping, i said scope01:53
mdkesure, but a doc with a scope which is tailored for gai would mean a radically stripped down desktopguide from what it is right now01:53
jsgotangcowhat's your scope? who's your audience? everyone? that's a pretty hefty task in my opinion even if you are faced a 3 year support cycle for desktop01:53
rob^getting my multimedia to work properly is within its scope..01:53
mdkewe'd have to remove most of the useful stuff actually01:53
rob^cant do that just using gai alone though01:54
mdkeno01:54
mdkethings that can't be resolved using gai need MORE documentation, not less01:54
=== mdke tries the search in gai
rob^I think the opposite is true here though, gai needs MORE work.. 01:55
jsgotangcorob^: give some credit to the devels, for 6 months work (or less), its pretty good01:55
rob^as a package installation tool I find it useless as it is limited in what it can do01:55
mdkejsgotangco, i totally agree about scope, but I just disagree with the scope that the desktopguide should have01:55
bhuvanso, let our document not depend on it tooo much..01:55
mdkethe document really can't depend on it too much01:55
jsgotangcowell in another POV, the sources.list contains all the repos really so go figure :)01:56
mdkeor we'll have to remove most of multimedia, and loads of tips and tricks01:56
rob^then we will have another ubuntu guide on our hands01:56
Burgundaviathere is going to be a completely new repo dialog for dapper01:56
mdkeexactly01:57
rob^forking is not always a good thing01:57
mdkeno01:57
Burgundaviabut gai will not deal with the corner cases until dapper+101:57
bhuvanyeah01:57
=== jsgotangco opinion in gai is simply how linspire uses its click-n-run if you're going to marketi something be firm on it, instead of having 1, 2 or 3 ways of doing the same action
rob^Burgundavia, if we get lucky :)01:57
mdkeunless gai can install gstreamer0.8-mad, we are going to HAVE to include other methods of support01:57
mdkeor remove vital stuff from the guide01:57
=== jane_ [n=JaneW@66.103.220.209] has joined #ubuntu-meeting
mdkeOR specify in every case which package manager to use01:58
Burgundaviarob^, no, it will happen for dapper+101:58
bhuvanwe must not remove vital stuff from doc just due to inability of gai01:58
rob^mdke, thats how I see we are going to have to do it01:58
mdkebhuvan, 100% agreed with you01:58
BurgundaviaI think it might be better to list that we need to use synaptic to install the non-gai stuff01:58
bhuvanlets give an introduction about gai and move on using another convenient tool01:58
rob^Burgundavia, it could happen now if they implemented the suggestion I mentoned earlier01:58
Burgundaviaand list gai general01:59
Burgundaviarob^, what was that?01:59
bhuvanas Burgundavia said, it would be stablilized in dapper+1, so we can make amendments by that time01:59
rob^Burgundavia, just a simple dialog in gai where you could type the package names, it could then use apt-get to install them, problem solved for now :)01:59
mdkei think we are going to have to see how it develops, to a certain extent01:59
=== jsgotangco dunno we're going circles gai isn't meant to replace all known installation methods, but most people won't bother using synaptic as much as possible
Burgundaviarob^, hmm, might be an idea02:00
rob^heck I could dodgy something up with python that would do it in a few hours02:00
mdkeyes it is a good idea02:00
mdkeget onto -devel about it02:00
rob^then users could just copy/paste from our guide02:00
bhuvanimo, now, lets propose a method, conduct voting and close it at the earliest!02:00
mdkebhuvan, i think it is too early, we will need to see how gai develops02:00
bhuvanok02:01
rob^yep02:01
bhuvanok02:01
bhuvanthen, we can let it boil till next meeting ?02:01
mdkeare we going to come to a decision on whether to use "questions"?02:01
=== jsgotangco would still go for gai then synaptic for advance use as gai recommends so
=== mdke is looking to see if anything on the agenda has been decided
rob^mdke, I think just drop "how do I02:01
rob^"02:01
mdkerob^, +102:01
davidj_ubz'night02:01
rob^still keep qanda as changing it will be too much work for not much benifit02:02
mdke+102:02
rob^s/benifit/benefit02:02
mdkecouldn't agree more02:02
rob^ok problem sovled I guess02:02
rob^s/sovled/solved02:03
mdkei hope to also integrate a bit of the old userguide into the desktop guide02:03
rob^grr bloody hangover02:03
rob^yes02:03
rob^that is what I'm planning on doing where possible, no need to reinvent the wheel02:03
mdkecool02:04
=== mpt [n=mpt@66.103.220.241] has joined #ubuntu-meeting
mdkei have a question on serverguide, everyone agrees it can be common to ubuntu/kubuntu?02:04
mdkei do02:04
rob^I'll just have to add the userguide authors to the desktop guide 02:04
rob^mdke, yes02:05
rob^mdke, as its command line based it doesn't matter much02:05
jsgotangcoa server has no X so it's common02:05
bhuvanagreed02:05
jsgotangcounless we have X tools02:05
rob^and they use the same repos so everything is exactly the same02:05
mdkewell, that's not true, but I know what you mean :D02:05
rob^?02:05
mdkethe serverguide can be used by people who run X02:05
mdkelots of desktop users want to install apache02:06
jsgotangcosure 02:06
mdkeok cool, moving on02:06
rob^they can using apt-get regardless what they use02:06
jsgotangcowhat i meant is that a server guide would only use CLI tools as we don't have gtk/qt server apps atm02:06
jsgotangconot the actual usage02:06
bhuvanyeah, in desktop guide we can point them to server guide if need be02:06
mdkeyeah absolutely02:07
mdkeright, can we talk about kubuntu docs a bit?02:07
rob^sure02:07
mdkejjesse isn't here :/02:07
rob^yeah 02:07
jsgotangcoKubuntuDocs is available though02:07
rob^I mentioned kudos/kubuntu desktop guide but was told it was under control02:07
mdkethe KubuntuDocs page is very good02:07
mdkevery well organised02:07
jsgotangcoit already got BOF'ed and speced so that'll be ths scope of work02:08
mdkeWe should get it integrated with DocteamProjects if possible02:08
rob^umm, isn't that the reason we have docteamprojects page?02:08
mdkealthough the kubuntu docs are there already, it's annoying to have 2 frames of reference02:08
jsgotangcoKubuntu is a natural desktop oriented release so there is tighter scope02:08
jsgotangcorob^: KubuntuDocs is an ubz spec, yes it can be added to DocteamProjects02:08
rob^cool02:09
mdkei think it should be merged in02:09
mdkeok last couple of agenda items02:09
mdkeinstallation guide?02:09
rob^I've seen some intrest in this by people02:09
=== mdke nods
rob^but we really have to wait and see what happens with ubuntu express02:09
mdkehopefully they will come forward again02:09
rob^because there won't be an "install cd" then02:10
mdkeyeah ok02:10
mdkelast thing02:10
mdkecleaning up trunk02:10
mdkelearnlinux we decided is going02:10
mdkewhat else is there that shouldn't be?02:11
jsgotangcokde upstream if posssible02:11
rob^do we need the upstream stuff?02:11
rob^I don't really use it02:11
mdkei don't think so02:11
jsgotangcono one uses it02:11
mdkewe certainly don't need it for the docs as they are defined right now02:11
mdkeso they can go too!02:11
mdkeyay02:11
rob^if I wanted to I'd get the latest copy from the relevent repos02:11
bhuvanok. kde/debian ?02:11
jsgotangcosean added them before for vendor drops i believe02:11
mdkebhuvan, we can talk about that later on in the cycle i believe02:12
bhuvanoh, fine02:12
=== mdke deleted learnlinux
rob^can gnome and kde be renamed to ubuntu and kubuntu instead?02:12
mdke:D02:12
mdkerob^, yeah we thought on balance that would be a good idea02:12
mdkejsgotangco, any objections?02:13
rob^same02:13
bhuvanrob^, +102:13
mdkewe had a brief chat before you turned up about it02:13
rob^at least new people will know where to look02:13
mdkeno one else objected02:13
rob^cool02:13
jsgotangconone at all02:13
mdkejerome?02:13
mdkecool02:13
=== mdke does it now
jsgotangcoholler us when we can svn up02:13
mdkewill do02:14
rob^and generic can probably go altogether02:14
mdkerob^, we'll need it for serverguide02:14
bhuvanwhen we talk about clean-up, we have couple of invalid docs in trunk02:14
rob^mdke, oh yeah true02:14
bhuvani meant, ./validate.sh fails02:14
mdkebhuvan, yes02:14
mdkedoes anyone know why?02:14
bhuvancan you have a script to validate all docs at end of day02:15
bhuvan??02:15
rob^there is a problem with a few docs I think02:15
rob^the desktop/server guides validate properly iirc02:15
bhuvanif any of them are invalid, an email should be sent02:15
bhuvanmay be to our mailing list02:15
bhuvansomeone can poke into to address it02:15
mdkethe current invalid docs are kquickguide and kuserguide iirc02:16
bhuvanok02:16
rob^bhuvan, if you run into any problems just ask02:16
jsgotangcoBurgundavia: what is Launchpad Landing Pages about? its an LP thing right so why add it as a project?02:17
rob^jsgotangco, I was thinking the same thing02:17
mdkeyeah me too02:17
bhuvannot really, but i want all docs to be valid all the time. if its not, it should be brought to notice02:17
mdkeyes02:17
jsgotangcoLP is supposed to give different support options, its a business oriented approach02:17
mdkebhuvan, the problem is, no one knows how to fix it02:17
mdkejsgotangco, yeah i think it will be mainly paid support02:17
rob^is not really a docteam project02:18
rob^we don't do the help pages for it02:18
jsgotangcook can someone mail to the list what specific docs are not validating02:18
jsgotangcoso we can triage them02:18
bhuvanmdke, ok02:18
mdkejsgotangco, there have been like 10 mails about it in the last week02:18
mdkekquickguide and kuserguide don't validate because of a problem they have with ccbysa.xml02:18
bhuvanmdke, atleast now, i'll check manually and see whether i can address it02:18
mdkethanks bhuvan, would be great if you can02:19
rob^mdke, I think its the way it includes them from memory02:19
rob^they need to use xinclude instead of entities02:19
mdkewell they should be working as entities too02:19
jsgotangcomdke: at least a list of all docs that won't validate will be useful i get like 200 emails a day...i have time later to look into it otheres will probably find it useful too02:19
mdkejsgotangco, those emails listed the two docs that don't validate02:19
mdkeand the error02:20
jsgotangcook only 2 docs then02:20
mdkeafaik yes02:20
jsgotangcocan i svn up now?02:20
mdkesure, i haven't committed the rename yet02:20
rob^using xinclude is a little different from entities, when you use xinclude the included page needs to have a full header whereas as an entity it is put exactly as is in the doc02:21
jsgotangcoerr just deleted learnlinux?02:21
rob^it puts it exactly as is I meant to say02:21
mdkejsgotangco, problem?02:21
jsgotangcomdke: no i thought it'll be much more than that02:21
mdkejsgotangco, i haven't finished...02:21
mdke:)02:22
mdkejust cleaning up my local tree first02:22
rob^we should be using xincludes anyway for translation02:22
jsgotangcook02:22
mdkerob^, yeah ideally02:22
jsgotangcoi should go downstairs for breakfast02:22
rob^I'll fix it after you upload your changes02:22
jsgotangcoso anything else?02:22
=== mhz_shower [n=mhz@pc-252-84-215-201.cm.vtr.net] has joined #ubuntu-meeting
mdkei think that does it02:23
jsgotangcook that was a good 3 hours at least02:23
mdke2 and a half02:23
rob^nope02:23
mdkeactually 2, we started late ;)02:23
mdkeanyway, was a heated one02:24
jsgotangcoits a nice sunny saturday morning here 02:24
mdkethanks all, glad we sorted most stuff out02:24
mdkejsgotangco, it's freezing here :)02:24
jsgotangcosucks to be there then02:24
mdkelol02:24
bhuvancool02:24
mdkemy boss was in manila last week02:24
rob^heh02:24
mdkebhuvan, where are you from by the way?02:24
mhz_shower.oO(it seems I mistaken the UTC time :((( )02:24
bhuvanindia, chennai02:24
rob^I ah just updated DocteamProjects02:24
mdkebhuvan, ah, i'm afraid I don't know where that is :)02:24
bhuvan:)02:24
bhuvanhope you may know india ?02:25
jsgotangcobhuvan: whoa what time is it there? 3am?02:25
bhuvanchennai is one of the metro in south side02:25
=== mdke looks it up
bhuvanits 6:55am now02:25
mdkeyeah i've heard of india02:25
jsgotangcomdke: sure british east india company lol02:25
mdke:)02:25
bhuvanabsolutely!02:26
mdkeanyhow i wanna keep talking, let's go back to #doc02:26
rob^sure02:26
=== jsgotangco [n=jsg@ubuntu/member/jsgotangco] has left #ubuntu-meeting ["Konversation]
=== mhz_shower [n=mhz@pc-252-84-215-201.cm.vtr.net] has left #ubuntu-meeting ["Leaving"]
=== mdke [n=matt@ubuntu/member/mdke] has left #ubuntu-meeting []
=== einheit_ [n=steve@209.104.102.193] has joined #ubuntu-meeting
=== bmonty_laptop [n=bmontgom@wsip-68-15-230-31.om.om.cox.net] has joined #ubuntu-meeting
=== mpt [n=mpt@66.103.220.241] has joined #ubuntu-meeting
=== robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== laszlok [n=laszlo@134.117.187.134] has left #ubuntu-meeting ["Konversation]
=== bhuvan [n=ubuntu@59.92.33.17] has joined #ubuntu-meeting
=== lamont [n=lamont@66.103.220.193] has joined #ubuntu-meeting
=== doko [n=doko@66.103.220.208] has joined #ubuntu-meeting
=== mpt [n=mpt@66.103.220.241] has left #ubuntu-meeting ["http://mpt.net.nz/"]
=== jeang [n=jeang@c3-dbn-76.absamail.co.za] has joined #ubuntu-meeting
=== jeang [n=jeang@c3-dbn-76.absamail.co.za] has left #ubuntu-meeting []
=== bhuvan [n=ubuntu@59.92.33.17] has joined #ubuntu-meeting
=== Mez [n=Mez@66.103.220.192] has joined #ubuntu-meeting
=== Mez [n=Mez@66.103.220.192] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487D44C.dip.t-dialin.net] has joined #ubuntu-meeting
=== goldfrap [n=anne_fra@203.131.138.10] has joined #ubuntu-meeting
=== goldfrap [n=anne_fra@203.131.138.10] has left #ubuntu-meeting []
=== ajmitch [n=ajmitch@port161-157.ubs.maxnet.co.nz] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== lamont [n=lamont@66.103.220.244] has joined #ubuntu-meeting
=== ogra_ [n=ogra@66.103.220.202] has joined #ubuntu-meeting
=== fabbione [i=fabbione@66.103.220.245] has joined #ubuntu-meeting
=== Simira [i=rpGirl@66.103.220.251] has joined #ubuntu-meeting
=== doko [n=doko@209.104.102.193] has joined #ubuntu-meeting
=== JaneW [n=JaneW@66.103.220.232] has joined #ubuntu-meeting
=== mvo [n=egon@209.104.102.193] has joined #ubuntu-meeting
=== JaneW [n=JaneW@66.103.220.232] has left #ubuntu-meeting ["Bye"]
=== einheit_ [n=steve@209.104.102.193] has joined #ubuntu-meeting
=== bhuvan [n=ubuntu@59.92.45.213] has joined #ubuntu-meeting
=== dholbach [n=daniel@ubuntu/member/dholbach] has joined #ubuntu-meeting
=== dholbach [n=daniel@ubuntu/member/dholbach] has left #ubuntu-meeting ["Ex-Chat"]
=== einheit_2 [n=steve@66.103.220.155] has joined #ubuntu-meeting
=== mvo [n=egon@66.103.220.179] has joined #ubuntu-meeting
=== tseng [n=tseng@mail.thegrebs.com] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487DA15.dip.t-dialin.net] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== ealden [n=ealden@219.90.91.2] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== bmonty_laptop [n=bmontgom@wsip-68-15-230-31.om.om.cox.net] has joined #ubuntu-meeting
=== mdz [n=mdz@66.103.220.206] has joined #ubuntu-meeting
=== mdz [n=mdz@66.103.220.206] has left #ubuntu-meeting ["Leaving"]
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== ogra_ [n=ogra@209.104.102.193] has joined #ubuntu-meeting
=== robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== Simza [n=rpGirl@209.104.102.193] has joined #ubuntu-meeting
=== JaneW [n=JaneW@66.103.220.232] has joined #ubuntu-meeting
=== boglot [i=chaas@gw.workaround.org] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487DA15.dip.t-dialin.net] has joined #ubuntu-meeting
=== Mini-NuX [n=mininux@i01v-62-35-126-136.d4.club-internet.fr] has joined #ubuntu-meeting
=== Mini-NuX [n=mininux@i01v-62-35-126-136.d4.club-internet.fr] has left #ubuntu-meeting ["http://mini-nux.info"]
=== robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== Simira [n=rpGirl@209.104.102.193] has joined #ubuntu-meeting
=== dtf [n=dtf@ppp-70-226-173-236.dsl.mdsnwi.ameritech.net] has joined #ubuntu-meeting
=== manicka [n=grant@203-158-44-44.dyn.iinet.net.au] has joined #ubuntu-meeting
=== ogra_ [n=ogra@209.104.102.193] has joined #ubuntu-meeting
=== LaserJock [n=LaserJoc@ppp-69-227-156-68.dsl.renocs.pacbell.net] has joined #ubuntu-meeting
=== manicka [n=grant@203-158-44-44.dyn.iinet.net.au] has joined #ubuntu-meeting
=== manicka [n=grant@203-158-44-44.dyn.iinet.net.au] has joined #ubuntu-meeting
=== doko [n=doko@209.104.102.193] has joined #ubuntu-meeting
=== dholbach [n=daniel@66.103.220.198] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== JaneW [n=JaneW@209.104.102.193] has joined #ubuntu-meeting
=== crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-meeting
=== hub [n=hub@209.104.102.193] has joined #ubuntu-meeting
=== magnon [n=co@photogeeks/magnon] has joined #ubuntu-meeting
=== farruinn [n=nathan@128.153.144.47] has joined #ubuntu-meeting
=== hunger [n=hunger@p54A606EA.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== KyralRetsam [n=ShadowLi@itl-lab-3.sclab.clarkson.edu] has joined #ubuntu-meeting
=== Burgundavia [n=corey@209.104.102.193] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
\shok..09:45
LaserJockwait, is it now?09:45
KyralRetsamyes09:46
\shall motus and motus wanna be yes09:46
magnonUbuntu MOTU meeting here right now09:46
\share sitting here now09:46
LaserJockcrap, stupid daylight savings ;-)09:46
=== tritium [n=michael@pcp0011975002pcs.sandia01.nm.comcast.net] has joined #ubuntu-meeting
=== zakame [n=zak@ubuntu/member/zakame] has joined #ubuntu-meeting
magnonhttps://wiki.ubuntu.com/MOTUMeeting09:48
zakamehi all09:48
dholbachhi everybody09:48
\shok...it's quite difficult now...i'll try to write up all the statements we have here in montreal09:48
slomohi everybody :)09:48
KyralRetsamyo09:48
sladenI thought people were going to be physically in the same place too09:49
bmonty_laptopsomeone needs to buy \sh a beer if he is going to type everything they say in Montreal09:49
KyralRetsamlol09:49
dholbachsladen: we are... comfy chairs09:49
sladendholbach: bar?09:49
zakamehihi09:49
dholbachsladen: yes09:49
=== koke [n=koke@209.104.102.193] has joined #ubuntu-meeting
highvoltagei'm a motu-wannabe, but i want to sign up in a few weeks time, i just want to watch for now.09:50
magnonwe09:51
magnonwe're having our meeting in montreal right now live, so we're trying to put up our main points09:51
magnonOur main problem is that version freeze and feature freeze is six and eight weeks away09:51
magnonand we have 1000+ merges09:51
KyralRetsam You guys should put up the channel on like a projector ;P09:51
zakamemagnon: gaah09:52
magnonabout 1300 I believe09:52
KyralRetsam6 weeks?! Yikes....09:52
\shwe're discussing right now, that we have only 6 weeks of open development, means, that we can only in this timeframe new packages into universe and doing all the merges of our packages which have ubuntu versions09:52
tritiumwhere's the live video feed of the meeting?  ;)09:52
magnonkeep the noise ratio down too please...09:52
KyralRetsamsorry09:52
sladen> even if we get a new upstream version we should always consier taking the debian version 09:53
sladen> we will try and merge rounds09:53
sladen> who decies on which pakcage goes into which round---keybuk's descisesion?09:53
sladen> it was a disccusion in the release process09:53
sladen> if people want to fix anything, let them09:53
bmonty_laptopwhat if debian version is broken?09:54
sladen> with the mergeing processs, we agreed that after IUVG we stop synching09:54
=== blueyed [n=daniel@pdpc/supporter/active/blueyed] has joined #ubuntu-meeting
sladen> sync if there's no new debian upstream09:54
sladen> we'd still be honouring debian upstream09:54
=== lamont [n=lamont@66.103.220.244] has joined #ubuntu-meeting
sladen> colin had this concern that there's no problem to get anything you want in a new revision09:54
sladen> even with a 60kB patch or something09:55
sladen> the propostal was made tyesterday that we have a couple of people doing the merges the ahrd way by hand09:55
sladen> I don't see why, what's difference froma normal merge to somebody in the task force09:55
sladen> we saw it in the breezy relase cycle that some people wee disappearing09:56
sladen> I know I'm going to disappear from the end of ...09:56
sladen> ...when you know that you're not going to have time, tell i09:56
sladens> so you want a list of people who claimi to be working on this09:56
sladen> ok09:56
sladen> I don't really like the idea09:56
magnongood job sladen :P09:56
sladen> because... if I want to help out osomewhere then I want to do it oluntarily, and not beuacse the team requires me to09:56
sladen> then are much more likey to be working on bugfixing whereas there asre other people on the channel doing packageing ... like stofgger olsen09:57
magnon*christoffer09:57
sladen> some people have to vring in the new people from revu---when did you do the last review ...during breezy, we have to clean that up as there's a huge list of stuff and it would help to get new people in and we should push them more attactive09:58
sladen> there are some KDE gys --- that there' s aproblme with KDE people09:58
sladen> but then apply the same process to all the packages09:59
=== manicka [n=grant@203-158-44-44.dyn.iinet.net.au] has joined #ubuntu-meeting
sladen> but renviewing takes time... loits of time09:59
sladen> especially when people are packaging stuff with strange copytigh licesnse or even wird languea   I can read Frehcn!09:59
sladen> strange stuff, not French stuff09:59
sladen> do I read the agenada correctly?09:59
dholbachwe have huge amount of crack here :)10:00
KyralRetsamlol10:00
dholbachand we're loosing track of what we say10:00
sladen> there are french people that don't speak a word of English. ... but Debian copyrigh has to be readable, as you can't expect Elmo to learn French to read licnese10:00
sladen> <elmo> a debian copyright in French whould get a single word response.. "Non!"10:00
KyralRetsamis he like putting down what people say in realtime? Or TRYING to?!10:01
sladen> what do we do if the Debian peoepl are slacking... there's enough, there' sa 15k packages that need merging10:01
sladen> ther problem is that when we first get this in, there won't be any updates10:01
sladen> you'll get an expection to UBG if you can show that the upload fixes a fix10:01
sladens/UBG/UVF/10:01
sladen> we don't want to make too much work for outsleves, tis' a samll team10:01
sladen> if you're going to be doing things, you'll going to have to be reasonaible forthat unilt relase10:02
sladenfor that until relase10:02
sladen> we have to reduce the number of Ubuntu specific packgaes and mainly because of trival changes and changes10:02
sladen> or get them upstream or Debian so that we're not maintianing them10:02
sladen> try and get a team that just work with Debian and try to push things?10:02
sladen> No!  Absotutely not!10:03
sladen> I was lazy in that reard myself, but ...10:03
sladen> the problem for breezy was that the tfor breezy we didn't have the teim, but now we have the time and should be able to push the pachates to Debian adna push it back in the futre or during the feature freeze10:03
sladenWHat's my oion on all this?10:03
slomoabout getting ubuntu changes back to debian... wasn't there this utnubu project which wanted to get ubuntu changes back into debian? or did they silently die?10:08
zakamethere is that at alioth10:08
magnonthere is such a project, but it relies on the debian maintainers for a certain package to be alive10:08
=== mgalvin [n=mgalvin@cpe-69-205-47-165.nycap.res.rr.com] has joined #ubuntu-meeting
siretartutnubu is focusin on getting NEW packages into debian from ubuntu, rather than to catch individual patches10:09
slomoif the debian maintainer isn't alive we have no way to get the changes in anyway... except when doing a NMU10:09
KyralRetsamIf the Debian devs aren't alive then the Ubuntu person who made the patch become the dev10:09
siretartthen we don't need to care anyway10:09
bmonty_laptopKyralRetsam: I think that would become unmanageable10:10
crimsunthat still creates a merge delta10:10
zakameKyralRetsam: yep, but that would require the person being sponsored by a DD, unless (s)he's a DD...10:10
magnonKyralRetsam: right now that would be somewhat impossible with the amount of work we have to do before UVF10:10
KyralRetsamah okay10:10
magnonand the fact that ubuntu doesn't have "maintainers" in that sense10:10
bmonty_laptopdid they stop talking in Montreal, or did sladen get tired :)10:12
sladen> ...talk about mathcing Debian names with things like  -v2  and if Ubuntu universe has arleady stripped that name off10:12
magnonsladen got tired :p10:12
sladenbmonty_laptop: they asked me a question and I lost track :)10:12
zakamesladen: awww10:12
bmonty_laptophaha10:13
sladen> thigns like the disk bar applet that was new and before relase and broke and not okay to have it in before realse10:13
sladenwhat we really need is saudoi streaming rather than a trasbiption10:13
slomoyes... but it's too late now :(10:13
sladen> we have to get packages reviewed then UVF.  New packages which don't requrie new packages that don't require new dependcies, do we accpept them?10:13
sladen> I think we agree on a date, after UVF that we have as our own freeze date for new packages10:14
sladen> we need a few weeks to test for bugs for thigns that are going to be in universe, does 4 weeks10:14
slomohm, about UVF for universe... i hope it will be some days after the UVF for main?10:15
ajmitchslomo: not likely10:15
dholbachwe're just discussing the freeze for NEW packages10:16
ajmitchsladen suggests: freeze for NEW packages at preview release time10:16
sladen<sladen> I don't think anything should go into universe after the Preview rlease10:16
dholbachone suggestion was 4 weeks before release10:16
dholbachanything NEW10:16
\shhttps://wiki.ubuntu.com/DapperReleaseSchedule10:16
slomoajmitch: that's bad imho... think of a new version of a package in universe which needs a new version of a package in main... this package in main gets updated in the last minute and the universe package can't be uploaded anymore without breaking UVF...10:16
\shhttps://wiki.ubuntu.com/DapperReleaseProcess10:16
slomodholbach: 4 weeks before release for NEW packages should be fine imho...10:17
crimsunI think we're going to have to be a lot more conservative10:17
siretartI'd say lets bind that to the release preview10:17
sladen> we have to decided separately between package uploads and reving the library10:17
crimsun4 weeks is the absolute minimum10:17
sladencrimsun: agree10:17
magnonslomo: exceptions can be made10:18
ajmitchslomo: we're discussing that - we can't really approve anything new that breaks UVF10:18
magnoneven in main10:18
magnonif there's a very very good reason for it10:18
ajmitchmagnon: but for NEW in universe? I don't think there'll be much chance10:18
magnonnew stuff after UVF? I don't want that10:18
magnonI don't see why it should be differenced10:18
sladen> we had stuff in universe which hasn't build for the last two versions10:19
sladen> ...there's focus between getting new stuff and fixing stuff that hasn't built10:19
siretartdholbach proposed to start a poll in launchpad about the deadline for NEW packages in universe10:20
sladen> we have 6 weeks to get new versions in after the no new software10:20
sladen> if we look at the relase scheuld, we have merging, ... UVF, and then we can't do aynthing anytmore so we need a phase where we insert those new packages10:20
ajmitch6 weeks from now, until UVF10:21
ajmitchI think it's about 8 weeks, actually10:21
ajmitchbut 8 weeks for NEW packages?10:21
hubwow10:21
hubthat is short10:21
siretarthttps://wiki.ubuntu.com/DapperReleaseSchedule10:22
crimsunI don't see why NEW packages should get an exception from FeatureFreeze at the absolute best10:22
ajmitchwe have to look at each package, until the deadline10:22
ajmitchcrimsun: yep10:22
ajmitchcrimsun: so that'd be 6 weeks post-UVF10:22
slomocrimsun: NEW packages don't break anything... and a buggy package is imho better than none10:23
crimsunslomo: I think none is better in that case, since it'll be much more difficult to push changes into -updates10:23
crimsunDapper has a mandate essentially to be as polished as possible, and we have to trade off features for stability10:24
tritiumyes10:24
farruinncrimsun: ditto, was just about to say that10:24
sladen> we're spending a lot of time talkign about this and the answer is actually ogin got be a case-by-case10:24
ajmitchalthough it will be case-bycase, we need a deadline10:25
slomoi would vote FF for NEW packages then...10:26
LaserJockWhat about at Feature Freeze10:26
crimsunas would I.10:26
crimsun6 weeks post-UVF10:26
sladen> please let us know a policof MIA (Missing in action/ AWOL)10:28
slomowhat?10:29
magnonif someone goes AWOL/MIA, -let the team know- etc.10:29
LaserJockisn't that in the Code of Conduct?10:29
zakameexit gracefully10:30
magnonyes10:30
sladenbut it probably hasn't been happening10:30
slomohm, would be a really short policy: tell someone when you're leaving forever/for some days ;)10:30
sladen> if people touch other packages and then go away and two months later the maintineaer comes back and says ''I alerady ha the patches'' ... why didn't you put them in bugzilla/upload10:31
LaserJockit might be nice to have a MOTUPolicies wiki that has all of this kind of stuff10:32
zakamehmmm, how about co-maintaining?10:32
magnonwe don't have maintainers10:32
slomosladen: who do you mean with maintainer?10:32
crimsunthe entire MOTU team can touch any package10:32
zakameoh10:33
magnonbut it's polite to let people do their thing, since you might end up with duplicate work10:33
magnonhowever, if you leave, then we need to know that you do10:33
sladenslomo: the person who last 'touched' that pacakge10:33
magnonwe're talking about a mailing list to improve communication10:36
zakameyeah, iirc dholbach raised it up during the last CC meeting10:37
sladen> ... we dont' have a channel/mailing list for social channel for MOTUs10:38
KyralRetsamyou mean #ubuntu-motu isnt social?10:39
sladen> ... suggesting a social mialing list for ''I'm jetting off to ...''10:39
magnonmore about so you can say when you're away, talk about new software you want in, planning releases, etc.10:39
magnonnon-technical development, so to say10:40
sladen> non-technical mailing list10:40
zakamemotu-proprio10:40
sladen> time is nearly up10:40
sladen> pitti mentioned universe-security10:40
hubwhy not10:40
sladen> we badly need a proper team rather than hit and run members.10:40
KyralRetsamI've been getting a lot of questions on the Ubuntu-Users ML about this topic10:40
sladen> we need peoepl to go and read debian-security-annunce and check d"did we get that in in the latest sync"10:41
sladen> and preparing deb diffs10:41
crimsunI've started doing that post-Breezy10:41
tritiumwe need some team structure10:41
crimsunso if there's motion for a team, I'm all for it10:41
KyralRetsamsecurity team?10:41
zakameagree10:41
sladen> is this a BOF or something?10:41
ajmitchcrimsun: there's always been a motion for a team10:42
magnonhaha10:42
magnon> you will all die a terrible death!10:42
sladen> we should refer brainstorming to another meeting10:42
magnon(-fabio)10:42
sladen> this was quite productive10:42
sladen> silcence!10:42
\shsladen - the living typewriter10:42
siretart'10:42
KyralRetsamlol10:42
sladen> will someone make some kind of notes from this ... wehav ean IRC log;  we can write up a spec and on the wiki10:43
sladen> talk to scott about MOTU bugs10:43
KyralRetsamNext time you should hookup some kinda voice-recognition software for this thing :P10:43
sladen> a poll for new packages 10:43
slomosladen: thanks for writing everything down :) you deserve a beer now ;)10:43
sladenKyralRetsam: yes!10:43
KyralRetsamwho is scott again?10:43
siretarthttp://people.ubuntu.com/~scott/ongoing-merge10:43
hubkeybuk10:43
sladen> MOTU-mailing list10:43
sladen> ubuntu-motu10:43
sladen> here's a "quick" list of thigns that need to be merged, rather tha sched, it's a few hundre pages long and need to be looked at manually10:44
=== KyralRetsam adds "Get Voice Recongition Software for next BOF to save sladen's hands" to MOTUTodo
sladen> some upstream ,some new debian revision10:44
sladen> so we have thto write the minutes andfrom the meeting10:44
sladen> do we have a wiki page?10:44
sladen> stick them ont he MOTU homapge10:44
sladen> thien thank you for the meeting and wI think we will have some tlaks10:45
sladen> what ware we doing tonight?10:45
sladen> MOTU meeting minutes10:45
ajmitchdrinking BOF!10:45
\shhttps://wiki.ubuntu.com/MOTUMeetingMinutes10:45
sladen> I love smoart, it haas a problem to "solve all your problems"10:45
sladenyeah!10:45
ajmitchok, meeting done, we can all go & drink now10:46
kokeajmitch: now?10:46
zakamehihi10:46
ajmitchkoke: ok, later10:46
ajmitchstill more BOFs to go10:46
=== zakame [n=zak@ubuntu/member/zakame] has left #ubuntu-meeting ["Leaving"]
=== crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has left #ubuntu-meeting []
=== magnon [n=co@photogeeks/magnon] has joined #ubuntu-meeting
=== Simza [n=rpGirl@209.104.102.193] has joined #ubuntu-meeting
=== ogra__ [n=ogra@66.103.220.209] has joined #ubuntu-meeting
=== JaneW [n=JaneW@209.104.102.193] has left #ubuntu-meeting ["Bye"]
=== Sanne [n=Sanne@p548D9B42.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Sanne [n=Sanne@p548D9B42.dip0.t-ipconnect.de] has left #ubuntu-meeting ["Bye"]
=== Simza [i=rpGirl@66.103.220.250] has joined #ubuntu-meeting

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