[12:03] Let's roll, guys. === ..[topic/#ubuntu-meeting:Burgundavia] : Logs at http://people.ubuntu.com/~fabbione/irclogs || Thu 16 June 22:00 UTC Documentation Team -- http://wiki.ubuntu.com/DocteamNextIRCMeeting || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || Find out UTC time with [12:03] gah === ..[topic/#ubuntu-meeting:Burgundavia] : Logs at http://people.ubuntu.com/~fabbione/irclogs || Thu 16 June 22:00 UTC Documentation Team -- http://wiki.ubuntu.com/DocteamNextIRCMeeting || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || UTC time with "date --u [12:03] length [12:03] cut the log thing if you like === ..[topic/#ubuntu-meeting:Burgundavia] : Logs at http://people.ubuntu.com/~fabbione/irclogs || Thu 16 June 22:00 UTC Documentation Team -- http://wiki.ubuntu.com/DocteamNextIRCMeeting || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, or #ubuntu-devel || UTC time with "date --ut === ..[topic/#ubuntu-meeting:Burgundavia] : Logs - http://people.ubuntu.com/~fabbione/irclogs || Thu 16 June 22:00 UTC Documentation Team -- http://wiki.ubuntu.com/DocteamNextIRCMeeting || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, or #ubuntu-devel || UTC time with "date --utc [12:04] there [12:04] phew [12:04] right === ..[topic/#ubuntu-meeting:Burgundavia] : Logs - http://people.ubuntu.com/~fabbione/irclogs || Thu 16 June 22:00 UTC Documentation Team -- http://wiki.ubuntu.com/DocteamNextIRCMeeting || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, or #ubuntu-devel || UTC time --> "date --utc" [12:04] ok [12:04] are we gonna wait for jerome? === mpt [~mpt@203-167-186-66.dsl.clear.net.nz] has joined #ubuntu-meeting [12:04] that is the last changed [12:04] sorry for the flood === mdke hands Burgundavia some paracetomol [12:04] the agenda is very long [12:04] perhaps we should start [12:05] do we have a chair? mdke? jerome? [12:05] maybe jerome wants to do it [12:05] ok [12:06] in any case, for those that want to take a look right now, the agenda is at https://wiki.ubuntu.com/DocteamNextIRCMeeting === coffee [~alucard@ACCE6DC9.ipt.aol.com] has joined #ubuntu-meeting === jeffsch [~jeffsch@fatwire-201-201.uniserve.ca] has joined #ubuntu-meeting [12:07] evening jeffsch [12:07] howdy [12:07] we've just been introducing ourselves === mako [~mako@bork.hampshire.edu] has joined #ubuntu-meeting [12:07] I'm new to the project as I noted in #ubuntu-doc [12:07] And again, I'm Sean. [12:08] Howdy all :) [12:08] <- Jeff Schering [12:08] The more Seans, the merrier [12:08] I am Dennis [12:08] I'm not trying to steal the limelight, and I'll shut up after this -- I'm just saying this for benefit of those not in #ubuntu-doc [12:08] mpt, :) [12:08] Same for Jeffs and Matthews === mdke nods === elmo [~james@83-216-141-215.jamest298.adsl.metronet.co.uk] has joined #ubuntu-meeting [12:08] I'm also new, as I posted to ubuntu-doc list. === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-meeting [12:08] There can only be one Mako, though [12:08] hehe :) [12:08] JonA, squinn, you're both very welcome [12:08] perhaps we should crack on [12:09] First item: https://wiki.ubuntu.com//DocteamProjects [12:10] mdke: please go ahead [12:10] i'm going to idle here.. since only part of the agenda concerns cc related stuff, i'm going to keep working on other stuff and reading the traffic [12:10] ok [12:10] yes let's deal with the first item [12:10] please mention my name when it gets to cc stuff so i can become more active :) [12:10] mako, will do, thanks [12:10] thank you :) [12:11] ok we have a number of projects on the page that Seveas posted [12:11] who thinks we can have them all ready? === BeerDump [~jgotangco@202.57.71.236] has joined #ubuntu-meeting [12:11] ok === BeerDump is now known as jsgotangco [12:11] how about taking this direction [12:11] hi bjs [12:11] +1 [12:11] If no one did it yet: I was planning to port ubuntuguide to a wikipage in July [12:11] we need somebody to take the lead for each project [12:11] sorry [12:12] Seveas, already in SVN [12:12] ok [12:12] Burgundavia, I think that is a nice idea [12:12] so someone did it :) [12:12] Seveas, froud did it, but it is not maintained there right now [12:12] is mako online [12:12] anything that doesn't have a lead doesn't get considered [12:12] so can people express opinions about Burgundavia's idea? === Seveas agrees === jeffsch agrees [12:13] +1 [12:13] but is not an official docteam member.. === hno73 agrees [12:13] Seveas, not necessary [12:13] ok [12:13] theres no such thing as official in docteam at the moment :) [12:13] jsgotangco, what are your thoughts on Burgundavia's idea? [12:14] all projects needs leads [12:14] or else it won't go anywhere [12:14] +1 [12:14] so there is general agreement [12:14] A person or a group should stay in regular contact with those "project owners" to monitor how things are going [12:15] hno73, ++ [12:15] mdke: in the interests of making sure everything's top quality, i'd recommend dodging the administrator's guides for this release [12:15] Group leaders should post updates on the DocteamProjects page regularly as to the status of their project(s). [12:15] So that we don't fall behind by surprise [12:15] that's the way the techboard is doing things too and since Ubuntu rocks, this seems to work :) [12:15] hold on let me switch to my laptop [12:15] hno73, i think that the "status" should be more regularly updated, that would help [12:15] gtaylor, + [12:15] jdub: +1 [12:15] jdub, i tend to agree [12:15] jdub: agree [12:15] jdub: agree also [12:15] ++jdub [12:15] gtaylor: agree. === jsgotangco is now known as BeerDump [12:16] shall we deal with the matter of who is prepared to take responsibility for projects this evening? [12:16] mdke, I see no reason not to... [12:16] i would also like to discuss the question of other projects === jsgotangco [~jsg@202.57.71.235] has joined #ubuntu-meeting === BeerDump [~jgotangco@202.57.71.236] has left #ubuntu-meeting ["Leaving"] [12:16] mdke: (please ping me when you get to other projects) :) [12:16] an obvious one is the HelpfulHelp page [12:16] jdub, will do [12:17] ok before moving on to that, let's deal with the question of who can take responsibility for various projects [12:17] volunteers? [12:17] let's start with kde, it will be easy ;) === gtaylor Will take something KDE :) === froud too [12:17] kde quickguide is already managed by jerome, i suggest that continues? [12:17] quickguide is nearing completion too [12:18] mdke, its almost done gtaylor and troy can finish them :) [12:18] About Kubuntu, Kubuntu User Guide, Kubuntu Release Notes, Kynaptic User Manual ?? [12:18] most of the text atm are from them now [12:18] volunteers [12:18] I will take a KDE project as well [12:18] jsgotangco, excellent :D [12:18] I'd be willing to take on Kynaptic but I heard something about it not moving upstream? [12:18] there is also install guide [12:18] kynpatic was quick hack [12:19] froud, good point === Seveas is willing to take on install guide [12:19] I think that the stuff at FindingPackages will take over [12:19] good [12:19] install PDF needs to get done [12:19] Burgundavio: Then is it necessary to maintain the kynaptic docs under ubuntu-docs? [12:19] judax, making formats is very easy when the document is there [12:19] gtaylor, for now, we need something [12:19] in any case, we have plenty of volunteers for the kde docs, perhaps they can be divvied up later [12:19] mdke, install guide is not mentioned at that page... [12:20] Burgundavia: I wrote a pretty thorough guide for it in quickguide [12:20] Seveas, thanks for pointing that out [12:20] Seveas, I will be happy to write up minutes of the meeting, that way it won't get forgotten [12:20] nice [12:20] install guide is gubuntu and kubuntuin one file [12:21] froud, we will come to that issue I'm sure [12:21] who is interested in helping out on the Gnome projects on that page [12:21] Lemme get this straight. Is the install guide = ubuntu guide[.org] ? [12:21] install guide just covers the basics of partitioning, installing and pointers to starter docs imho [12:21] squinn, not at all [12:21] squinn, no [12:21] mdke: I'm willing to help on the GNOME side. [12:22] ubuntuguide is a page filled with misinformation... [12:22] JonA, great! [12:22] Then what are we talking about when we say ubuntu guide? [12:22] Seveas, we can come to that later too [12:22] I'm at DocTeamProjects, yet still confused. [12:22] Seveas: yu can see it in FAQ Guide [12:22] JonA, do you have a particular document you are interested in from that page? [12:22] discount the administration guide [12:23] The User Guide or the About Ubuntu doc are fine by me.# [12:23] great [12:23] I am also prepared to contribute on the Gnome side [12:23] Considering it's my first contribution, the About Ubuntu doc might be better, it's shorter :-( [12:23] mdke: how will installer guide relate to existing installer documentation? user-centric vs. advanced? [12:23] jdub, i am not familiar with it, but froud can help you [12:24] mdke, I envision a step-by-step document that explains a lot [12:24] jdub: basic install is the default [12:24] jdub, its pretty basic [12:24] mdke: note that this is not listed on that page [12:24] branches in doc to more advanced [12:24] I'll be back later..I'll catch a log. [12:24] jdub, yes noted [12:24] anymore volunteers for those Gnome projects? === Seveas if I have some time left :) [12:25] In a pinch I can help [12:25] don't forget the importance of gnome to Ubuntu :D [12:25] I'll attempt anything if needed... [12:25] I can help too, where needed [12:25] I will help but not take lead on anything === Seveas dislikes KDE, so I see the importance of gnome [12:25] ok thanks for your interest all, i suggest we pursue this matter at a later stage [12:25] so the install guide you're talking about is like a 5 page "DON'T PANIC" thing? [12:25] as in, who is gonna take lead for what [12:26] who takes lead on gubuntu user guide [12:26] let's post a list of orphaned projects in the meeting summary [12:26] hno73, + [12:26] mdke, project leads can be discussed later [12:26] jdub, well, plus some background info in appendices [12:26] jsgotangco, i agree [12:26] we'll clean up the wiki page for now [12:26] jsgotangco: agree [12:26] s/some/a lot where needed/ [12:26] jdub: first aim at 10 pages but can be expanded [12:26] let's move onto the next topic [12:26] froud: that's longer than basic coverage, and starts getting into existing documentation territory [12:27] StyleGuide [12:27] I would like to postpone discussion of the Styleguide until after the third issue, given that hno73 has to leave soon [12:27] objections? [12:27] mdke: thanks [12:27] ok [12:27] ok [12:27] great [12:27] jdub: graphic installer mostly pictures [12:27] ISSUE: Create roadmap for future docteam - developer - community relations in future projects with the help of the Community Council [12:27] mako, jdub ping [12:28] mdke: you going to do 'other projects' later too? [12:28] jdub, yes [12:28] froud: i guess it might be better to state it as 'ubuntu express documentation' [12:28] jdub, straight after this then [12:28] jdub, my fault [12:29] mark brought this issue up at the CC after the recent problems on the list [12:29] mdke: only if that's what it's intended to be :-) [12:29] at ubuntu-fr, we got plenty of people just expecting someone to tell them want to translate. We would love someone from the english team to do that [12:29] -want +what [12:29] yann_, I am happy to do that [12:29] yann_, if you are around we can talk afterwards [12:30] We should have a set location to post WIP and set some dates where we invite devels to have a look [12:30] sorry [12:30] (or other editors/proofreaders) [12:31] mark suggested at the council meeting that the docteam be encouraged to attend meetings and discuss issues there [12:31] hno73: we would like docteam.u.c [12:31] froud: in what format? HTML pages? [12:31] yes [12:31] ok these are two separate issues [12:31] froud: i think that's reasonable [12:31] ok, generated from SVN [12:31] does anyone have anything to say on the Community Council front? [12:32] yes [12:32] in some human readable format, whatever it is [12:32] hno73: yes html pages building from svn co [12:33] froud: please go ahead === Nafallo [nafallo@nafallo.user] has joined #ubuntu-meeting [12:33] mako: do other teams report to CC at regular intervals? [12:34] how does that work? Is there a system we could model the interaction on? [12:34] hno73: not normally. but they usually coordinate frequently with folks from the TB [12:34] right [12:34] most teams are basically distro subprojects [12:34] so they work closely with matt or others to track progress, etc [12:34] perhaps in this case we need a schedule [12:34] sure [12:35] since the links are week ATM [12:35] weak [12:35] perhaps the CC has been lacking in this regard and relationships to it's groups [12:35] locos, docteam, forums, etc [12:35] could be, yes [12:35] so, mark has said "come to the meetings" which is a pretty easy things to say [12:36] communicate with me/elmo/mark/kamion.. maybe write up a few paragarphs of report for the wiki and try to have someone at the docteam [12:36] sorry [12:36] the CC meeting === _froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-meeting [12:37] if people think that's useful, i'd be happy to ping a representative 2-3 days before meetings to remind folks [12:37] i don't think teams really need to rely on the CC that much, just some direction i guess [12:37] i believe that it might be useful if there are disputes [12:38] is that what mark had in mind? [12:38] mdke: i'm not sure [12:38] but sure [12:38] well disputes definitely can be directed towards the CC for sure [12:38] if there are any disputes, the CC is a good place to elevate to [12:38] that's what it's there for [12:39] :) [12:39] anyway, going back, to the topic, the relations between teams like docteam are more technical oriented === Seveas thinks: reputation system === froud got split, missed [12:39] Seveas, yes indeed [12:39] I'm just thinking that it would be good to have a schedule to work against, working backwards from the Breezy release date [12:40] hno73, i agree, to some extent we work within breezy's roadmap [12:40] but we could be more specific [12:40] and that giving some reports to CC or TB might be a good way to measure progress [12:40] hno73: once the docteam gets into a rhythm, scheduling stuff can be reported back to go in the release schedule [12:40] Project leader should make up their timeline [12:40] i think all release coordination stuff should really go through the distro TB, eh jdub? [12:40] and should release something together with Breezy [12:40] or through jdub i guess [12:41] mako: TB === methu [~Methu@a81-197-216-196.elisa-laajakaista.fi] has left #ubuntu-meeting ["Leaving"] [12:41] so, in so far as something is a feature goal, it's a TB issue [12:41] yes [12:41] yes [12:41] in so far as it's a structual, advocacy, or intra or inter-team conflict, it's CC [12:41] right [12:41] with the team so small, it may be difficult to structure roadmaps for each doc === lamont__ [~lamont@15.238.5.130] has joined #ubuntu-meeting [12:41] of course, i'm happy to help bat for you guys in other situation as well [12:41] but we can try maybe? [12:42] mdke: it can be one larger roadmap that takes the different docs into account, no? [12:42] mdke, well, if every doc has a leader (leaders might have more docs), all docs can have a roadmap too [12:42] mako, possibly [12:42] most of these roadmap can be pretty similar though [12:42] mako, we certainly work within the breezy timeline === hno73 regrets he has to go now. Looks like a nice meeting :) [12:42] hno73, night [12:42] g'bye hno73 [12:42] goodnight all === hno73 [~hno73@henrik.gotadsl.co.uk] has left #ubuntu-meeting [] [12:42] hno73, much appreciated you coming here [12:43] ack [12:43] :] [12:43] mark's on his way, FWIW [12:43] great [12:43] before he gets here, shall we deal with the two issues we missed out? [12:43] k [12:43] yes [12:43] styleguide [12:43] jsgotangco, sorry we missed something before that too [12:43] mdke: so, i'd suggest you not worry about a more detailed schedule than the distro one until you start seeing the requirements [12:44] http://wiki.ubuntu.com/StyleGuide I presume? [12:44] ISSUE: other projects not mentioned on the project page (ping jdub, mpt) === sabdfl [~mark@sabdfl.silver.supporter.pdpc] has joined #ubuntu-meeting [12:44] evening all [12:44] mdke: go for style guide first [12:44] sabdfl, hi [12:44] sorry for being very late [12:44] evening sabdfl [12:44] hi sabdfl [12:44] welcome sabdfl [12:44] jsgotangco: could you summarise the current position for me please? [12:45] possibly we can finish off the Community Council discussion now [12:45] as per this meeting, i've read DocteamNextIRCMeeting [12:45] mdke, can you summarise? i came in late as well *blushes* [12:45] sabdfl, we were just saying that we would be happy to interact with the CC [12:45] (sorry about that) [12:46] sabdfl, what is it precisely that you had in mind? [12:46] (we're on the third bullet point from the top btw) [12:46] (Create roadmap for future docteam - developer - community relations in future projects with the help of the Community Council) [12:46] as the community grows, some stresses and strains are inevitable [12:47] i'd like to establish the idea that those are resolved as amicably as possible between groups, if necessary with the help of the CC [12:47] yes [12:47] the yelp business and the forum friction are examples [12:47] in this case, it seemed to me that we need to work harder to bring the doc team into the mainstream of the activities of the project [12:47] it's my mistake that i've missed this point till now, and i apologise [12:47] +1 [12:48] +2 [12:48] ++ [12:48] + [12:48] we've seen excellent work being done [12:48] +1 [12:48] i can speak for all when i say that we are happy to hear that [12:48] we've also seen some unnecessary frustration [12:48] there are a couple of principles i'd like to propose: [12:48] - volunteers should feel they have the freedom to pursue whatever technical and substantial interests they have [12:49] if we can accomodate those with core infrastructure, we will, if not, we'll orgnaise Linode virtual servers so guys can get root somewhere and play to their hearts content [12:49] that said, we should have regular meetings, so we at least have a mutual idea of what our current interests are [12:49] from the CC side, we can lay out a roadmap of the project, and what issues will likely be important at different times [12:50] IMO it is important to keep a core methodology that is consistent with what -devel is doing [12:50] and from the teams, lay out the status and the skills on board, and their itches to be scratched [12:50] mdke: we can never guarantee consistency, but a lack of communication will certainly guarantee a lack of it :-) [12:50] sabdfl, communication is the big thing [12:50] i'm happy for someone to go off at a tangent [12:50] for all i know, that tangent is more interesting and more important than my own master plan [12:51] so good luck to you if that's where you're headed! [12:51] to what degree are these issues CC jurisdiction and TB jurisdiction? [12:51] but it's still useful to have at least an idea of what's going on [12:51] well, rather than thinking of "jurisdiction" think of areas of interest [12:51] sorry [12:51] habit [12:52] for example, from a CC point of view, i can tell you that Breezy is all about community, whereas Breezy+1 will be all about certification and support and training [12:52] i mean in terms of ensuring that the docteam working methodology works for -devel and vice versa [12:52] if that helps you set targets, excellent [12:52] by methodology do you mean tools? [12:52] i mean, what format of documents we are making, where it is to be published et [12:52] et/etc [12:53] mdke: TB is likely to have the strongest interest in that [12:53] the main thing is to see that even the -devel guys will have different opinions === Seveaz [~seveas@seveas.demon.nl] has joined #ubuntu-meeting [12:53] mdke, how we create our docs would be our own business but the formats needed in release would definitely be TB [12:54] so rather than getting into a frustrating yes! no! yes! no! dialog with one or two, this stuff should be framed as a formal proposition and brought to the whole TB [12:54] jsgotangco, yeah, but if we write profiled or qanda docs that are not viewable in yelp, we're gonna have a problem [12:54] i sensed there was a huge amount of frustration, and yet it had never been brought to the TB or CC [12:54] sabdfl, ++ [12:54] that surprised me [12:54] mdke: kubuntu is just as important [12:54] sure [12:54] and yelp is not available everywhere [12:55] just an example [12:55] sabdfl: the main break down happens when devel are not really listening to problems, docteam finds its own solution and the much later, after much effort, devels come back and want to digard the direction [12:55] i don't want to settle that debate here and now - that's the sort of thing that should be brought to the TB [12:55] ok [12:55] froud: i can appreciate that would piss people off in a significant way [12:55] so if that's happened i apologise [12:55] we just need to ensure it doesn't happen for the future, by building communication [12:55] i'm sure we can work out anything that needs working out for Breezy, if you put that on TB or CC agenda [12:56] we need to resolve this issue tough [12:56] jdub and I are not eye to eye at present [12:56] froud, specific issues can be discussed with the TB [12:56] i've said my piece on yelp, which is that AFAIK it is gnome-specific, and that doesn't sort out the needs of the broader ubuntu community [12:56] beyond that i'm not qualified, and even that is possibly and over simplification [12:56] so let's leave that to a proper discussion of the TB [12:56] fair enough [12:57] yep [12:57] I would like the docteam guys to have someone present for TB and CC meetings [12:57] i would also like to ask them to ENSURE that we have something "big picture" on EVERY TB or CC meeting agenda [12:57] cool [12:57] by that, i mean that for each meeting we have something that relates to where we are going, why, what the big picture is [12:57] because that long range vision will mean we worry less about the times we stub our toe on a minor disagreement [12:58] because we know what's minor and what's major [12:58] ok we're making great progress [12:58] so hold us to that standard [12:58] +1 [12:58] true enough [12:58] rather than just doing admin, appointing members and maintainers, we should be using those meetings to build more of a shared vision of what the project is about [12:58] +1 [12:59] a lot of that has happened in the regular face-to-face developer summits [12:59] at UDU we tried to capture more of that in a public media so we could all have it there to discuss [12:59] yeah [12:59] i hope that's helped [12:59] can we consider this issue resolved? everything on the agenda under the title "Issues to be discussed with Community Council and Developers" can be brought up at either TB or CC? [12:59] i think that creating a process by which people interact more with folks like the TB and CC often will provide an avenue by which people won't be suprrised as much as will have a better way to deal with when they do [12:59] but we cna do even better [12:59] ok === mako nods [12:59] so let's say that the doc team becomes a formal project team === ostaquet [~ols@86.28-136-217.adsl.skynet.be] has left #ubuntu-meeting [] [12:59] we ask you to have regular meetings [12:59] we ask you to have someone from TB or CC present when you do [01:00] and to post a summary of those to -devel and -traffic (mako?) [01:00] and to attend the TB and CC meetings [01:00] that is an exciting prospect [01:00] summaries of all meetings can go directly to -news in their own article [01:00] they will be included in -traffic [01:00] a meeting summary is news [01:00] and make sure we talk about real project vision and direction [01:00] we should address the issue of who is to do these summaries and administrative tasks? [01:00] we are not large in number [01:01] yet... [01:01] i'm happy to provide funding for a secretarial position, as enrico did [01:01] ping me when you send something to news the first time and i'll moderate your message and whitelist you [01:01] mdke, im happy to do it [01:01] mdke, as i've been doing it for now [01:01] sabdfl, there you go :) [01:01] it was enrico that first alerted me to the current rash of issues, so i'd like to thank him for keeping an eye on what's going on [01:01] bravo enrico [01:01] jsgotangco: if there's a nice way we can support you, appropriately, let me know [01:01] yes enrico is very much avisibly active [01:02] sabdfl, will do, thanks. [01:02] i've asked hno73 (henrik omma) to be a regular point of contact [01:02] but remember, you are a real team that has real authority in the project, and you actually report to the CC not to any individual [01:02] in time i'd like you to choose a team lead, but i think it's too soon for that now [01:03] one thing about that authority [01:03] a team secretary is great [01:03] like enrico [01:03] sometimes you'll find new guys come along and want to do things differnetly [01:03] don't put them down === mdke nods [01:03] +1 [01:03] yes, i've already encountered that in edubuntu :) [01:03] i've noticed a little bit of "we're the bosses round here" [01:03] live and let live [01:03] i agree [01:04] by being bestorganised and most focused you'll effectively lead all doc efforts, but don't try to block other efforts [01:04] in the same way you bristled when someone with an @ubuntu.com email said "crapola", the new guys might feel the same way [01:04] and speaking of which, how many of you are members now? === mdke puts half a hand up [01:05] ? [01:05] we currently have 4 active svn committers === JonA is in the process of becoming one :-) === Burgundavia is [01:05] mdke: ? [01:05] sabdfl, my key is not in the strong set [01:05] 6 [01:05] key is not needed for membership, only maintainership [01:05] hopefully someday [01:05] sabdfl, a signed CoC is needed [01:05] if you are a member, you can get an @ubuntu.com email [01:05] mdke: you can sign on paper and fax it === Seveas is a member [01:06] mdke: quite a few people do [01:06] i will do that [01:06] although I'd like to get the key signed too :D [01:06] sabdfl: what is the purpose of this? [01:06] it's not a canonical ltd thing, email@ubuntu.com is the project [01:06] froud: of opening up the email addresses? [01:06] yes [01:06] mdke, if you happen to live near Amsterdam, I can sign it :) [01:06] ubuntu is much bigger than canonical, i believe [01:06] Seveas, i'm in london [01:07] Seveas, but its an excuse for a holiday... [01:07] lol :) [01:07] sabdfl: why do I need another adress [01:07] i hope soon to nominate someone outside of canonical to the CC, and those of you who are members will be voting to conrim or veto that nomination [01:07] froud: you can ask for it to forward to your existing one, or just not activate it [01:07] it's simply there for those who want it [01:07] ok we're going OT a little [01:07] ok ok, i think we're going way out of topic [01:07] Hmmmm, so this is a token tick thing? [01:07] can we close this issue now [01:08] lots more on the agenda [01:08] yes mv on [01:08] happy with item 3? [01:08] i am [01:08] +1 [01:08] +1 [01:08] ok [01:08] jdub, other projects now? [01:08] w.r.t. svn access rights, how many of you have played with Baz? [01:08] i did [01:08] not I but I know some svn [01:09] me [01:09] sucks [01:09] is it tla or baz [01:09] froud: i use it every day, and it's made a huge difference to team workflow on LP [01:09] cant decide [01:09] we barely use 10% of what svn can do [01:09] is either jdub or mpt around? [01:09] or jeffsch ? [01:09] yup [01:09] mdke: i am [01:10] ah ok [01:10] NEXT ISSUE: projects that are not on the official projects page. An obvious one is to be found here http://udu.wiki.ubuntu.com/HelpfulHelp [01:10] baz is the butterfly emerging from the caterpillar that was tla :-) [01:10] yep [01:10] wait hold on, there's a reason i brought it up [01:10] k [01:10] it seems the problem you are having is a social one, not a tech one [01:10] about permissions [01:10] yes [01:10] mdke: HelpfulHelp needs approving by sabdfl or someone, it might be complete crack as it is currently :-) [01:10] distributed revision control greatly reduces that [01:10] anybody who wants to start making changes can just create a branch, then other people can merge from them and commit [01:11] mpt, indeed, I see some serious wrongnesses in that page [01:11] mpt, but you intend it to be a docteam project right? [01:11] sabdfl, the current process is that we ask enrico to ask froud for svn access to someone we recommend [01:11] mdke: for sure [01:11] sabdfl: you want us to move to baz [01:11] it takes a little getting used to, but it's seriously worthwhile [01:11] i mean ask elmo [01:11] mpt, lets put this on hold for a minute until the baz question is over [01:11] froud: yes, i'd like you to evaluate it [01:11] long term, it will be hard to avoid baz [01:11] sabdfl: most ppl found it hard using svn :_0 [01:11] it means that there's much less of a blockage around svn commit permissions [01:11] it will be the best way for doc people to work with upstream documentation [01:12] froud: good point, ad baz is conceptually harder [01:12] sabdfl: I like the mirrors from tla [01:12] Well, then the docteam sould make baz docs :) [01:12] and technically it is better solution [01:12] sabdfl: svn is definitely challenging for some of the more non-technical writers, if Baz is moderately more complex even conceptually, I'd recommend against it. But then again, I've never used Baz. [01:12] froud, we can probably evaluate baz for now and target the use for it in the future release post-breezy [01:12] gtaylor: it is more difficult, but then, it's a sure-fire candidate for some doc-team love [01:12] jsgotangco, ++ [01:12] gtaylor: you are right [01:13] Some people take being able to commit and change things easily for granted. There are people who want to help but are scared away by technicalities. [01:13] i thin you could setup a workflow which says: [01:13] - ANYBODY can contribute. just (a) baz get http://docs.ubuntu.com/docs@ubuntu.com/docs--current--0 [01:13] (b) edit [01:14] the possibility of a change in methods can be evaluated, but the project of getting docs together should not be slowed down as that is the short term breezygoal [01:14] (c) baz commit -s "my changes" [01:14] then ask for a merge [01:14] ok [01:14] sabdfl: it introduces new social problems too :) [01:14] That's similar to the way things are now, we email patches in whereas we'd be requesting a merge. [01:14] don't let baz get in the way, but please make a note of it as the recommended way to break revision control blockages [01:14] Would it be worthwhile me nailing together a couple of simple shell scripts to make using Baz simpler for those less technical writers? [01:14] we will move the ENTIRE distro into baz over the coming months [01:14] gtaylor, but emailing patches is way more overhead [01:14] so ANYBODY can fork and merge an ubuntu package [01:15] sabdfl, wow! [01:15] That's interesting [01:15] that's, well...., awesome! [01:15] we will provide a tool called HCT, currently in alpha testing, that makes this possible [01:15] yo dudes [01:15] that is indeed interesting [01:15] OT [01:15] ok can somebody open a thread about this on the list? [01:15] slow down [01:15] stop a sec [01:15] the bottleneck [01:15] its not svn [01:15] its elmo [01:16] it is not a technical problem [01:16] err? [01:16] hello elmo [01:16] heh [01:16] it is simply a matter of getting people commit access [01:16] I've had 3 requests recently, the first of which was on Tuesday [01:16] elmo: Not in a bad way, you're a busy guy :0 [01:16] (he means) [01:16] froud: any system that is designed to filter all requests through one person is broken by design [01:16] thanks mdke [01:16] the second of which (for two accounts) was sent 4 hours ago [01:16] hy must it be one person [01:17] elmo, its not your fault!! we are just thinking about the system [01:17] because elmo is our sysadmin, and carries it solo (heriically) at the moment [01:17] elmo, froud phrased that slightly wrong [01:17] heroically, i meant [01:17] elmo rocks! :-= [01:17] :-) [01:17] with baz, any one can manage mainstream, and merge from everyone else [01:18] ok requesting commit access to elmo is a trivial issue, i think what's more important is choosing people to actually have commit access to our current svn [01:18] to be honest, i don't see a problem with obtaining approval for people getting commit access [01:18] you won't have any bottleneck at the center [01:18] ok [01:18] it won't scale to have to ask elmo all the time [01:18] postpone to the list please [01:18] i can just email elmo about people we can sponsor for commit [01:18] we have lots of issues left on the agenda [01:18] i would rather you setup an svn server on a linode box and administered it yourselves [01:18] good point [01:18] sabdfl++ [01:18] sabdfl: That would be nice [01:18] i'll put that in consideration [01:19] ok [01:19] ok close the svn issue for now === mdke wipes brow [01:19] agree [01:19] this is workable [01:19] elmo's in my kitchen, and says he will hanle any request within 72 hours [01:19] if that doesn't happen, let me know [01:19] we have no problem with elmo, he is fast, and reachable in irc [01:19] but a better system will be either for you to admin it, or to use a distributed RCS like baz [01:20] lets get back to the issue of mpt's spec on udu [01:20] ok [01:20] mpt, you were saying? [01:20] url? [01:20] http://udu.wiki.ubuntu.com/HelpfulHelp [01:20] I was saying that no-one's approved it yet, so it might need huge changes, I don't know === _froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-meeting [01:20] sabdfl, the issue to be addressed is the adequacy of the docteam projects currently on https://wiki.ubuntu.com//DocteamProjects, and what other projects the docteam can do [01:21] (ping jdub) === _froud curses the network [01:21] (here) [01:21] jdub, you were saying a while ago that you had some ideas about projects for the team, and that you would email them [01:21] you have the floor [01:22] ok, ok [01:22] oh, ok rather [01:22] hah [01:23] so i've spent a bit of time over the last couple of weeks researching the team, speaking to some of you, and looking for ways to help get docteam and developers more acquainted, and finding rad goals for docteam [01:24] most of this i'll leave to email, but i wanted to raise one project idea which i think will have a big impact on breezy [01:24] everything listed on the projects page is about *writing* documentation [01:24] which is incredibly hard stuff [01:25] and doesn't go all the way towards giving our users the best documentation experience in ubuntu [01:25] meanwhile, we have enormous amounts of existing documentation available [01:25] we just need to understand it, organise it, integrate it [01:25] we made the first steps on this before warty was released [01:26] by ensuring that documentation registered with the debian doc system was registered with scrollkeeper (thus the html docs like mutt in your yelp) [01:26] but that was an easy, first step fix [01:26] and we can do more to get all of our docs integrated into yelp and khelpcenter [01:27] the first step, on that, is analysis of what we've got [01:28] what sort of docs are we talking about here? stuff on forums/wiki, or upstream? [01:28] both maybe? [01:28] mdke: everything in packages [01:28] ah ok the latter [01:28] the in-distro user experience [01:29] now the great thing about focusing on this is that it naturally tends toward working with the rest of the devel community :) [01:29] yes [01:29] mpt: big picture, that's a great spec [01:29] jdub: i think you've hit the nail on the head - there's a tremendous amount of low hanging fruit out there. perhaps the hardest part is the stuff which requires integration with the distro, because that requires both doc skills and packagin skills, and lord knows how rarely those overlap :-) [01:29] sabdfl, thanks [01:29] technical skills are required definitely [01:30] mdke: not too much, you know - it's pretty easy stuff [01:30] cool [01:30] jdub the main question is a technical one what format to ship === jgotangco [~jsg@202.57.71.235] has joined #ubuntu-meeting [01:30] we already register to scrollkeeper [01:30] (sorry bad dsl) [01:30] mdke: and there are different kinds of docs for people to focus on [01:31] jsgotangco, will paste you some stuff [01:31] froud: nono, totally unrelated to understanding what we have [01:31] yes [01:31] and no [01:31] later [01:31] what we have will impact it [01:31] discuss with you later jdub [01:32] or you want it now [01:32] no [01:32] ok [01:32] would you be prepared to head up a group of docteam members prepared to investigate this idea? [01:32] jdub ^ [01:32] mdke: hopefully hno can help out [01:33] mdke: i can definitely provide help, but won't be able to spend time dedicated to it [01:33] we can ask him [01:33] sorry [01:33] understood [01:33] have you discussed the idea with henrik? [01:33] dedicated to leading it [01:33] not in detail, but he has a pretty good idea of what i've been thinking about [01:34] cool [01:34] ok so shall we follow this issue up on the list? [01:34] i think it will be more clear with email [01:34] jdub: I think email of the idea will be a good start [01:34] snap :-) [01:34] great minds think alike [01:35] so in german, they say 'two fools, same thought' [01:35] ok now onto mpt's spec [01:36] is everyone aware of it? [01:36] Burgundavia, you around? [01:36] yes [01:36] :) [01:37] the issue is, can this spec become a docteam project, and how can it be worked on [01:37] mdke: can i delve into a couple of technical points? [01:37] (about this) [01:37] shoot [01:37] thanks [01:38] (now, where to start...) === froud is lost [01:38] froud, http://udu.wiki.ubuntu.com/HelpfulHelp [01:38] hmm [01:38] at the start [01:38] ok, so this will be the first-entry page of yelp [01:38] (this or something very similar to it) [01:39] so rather than having a funny indexish thing [01:39] you'll actually have a document as the front page [01:39] yelp will come with one [01:39] that is mpt's idea, although my view is that this would exclude the other docs unnecessarily [01:39] but we can branch it and do whatever we like with it [01:39] if anyone's seen apple's one, think very similar to it [01:40] we can manage the implementation of it and keep whomever does develop it on the straight and narrow [01:40] jdub: we can't limit ourselves to yelp in this discussion [01:40] essentially, this document is the user guide, which can focus on topics of interest rather than applications [01:40] sabdfl: getting to it [01:41] i think our focus now should be on things people can view in a web browser and print out [01:41] so can include lots of useful ubuntu-specific and topic-oriented stuff [01:41] mdke: Researching this was very depressing ... It turns out that if people can't find what they're looking for straight away, they just *give up*. So the user docs need to look like *one* set of docs, even if they're linking off to the Web or whatever. We can't expect people to look in doc X and then doc Y and then doc Z. [01:41] sabdfl: that's getting into a much deeper discussion [01:41] mpt: we really need a docs-google [01:41] but can also provide navigation for other documentation [01:41] navigation will always let us down, unless we have real context (as in the widget in the app that the guy is using) [01:41] sabdfl: Yes, one that also works offline :-) [01:42] mpt, yeah i see your point [01:42] mpt: local app, of course [01:42] sabdfl: that's getting way off track [01:42] google on the desktop [01:42] beagle? [01:42] yes it is, but starting to talk about yelp futurisms is equally off base now [01:42] jsgotangco! [01:42] sabdfl: google api wsdl [01:42] I also discovered that people usually don't bother with tables of contents, so https://wiki.ubuntu.com/LocalHelp will need simplifying [01:42] jsgotangco, on topic pls [01:42] sabdfl: i'm sorry, but we're not [01:42] (of course, currently with yelp they have no choice) [01:42] froud: it needs to be an app on the desktop, like beagle [01:43] b [01:43] (00:39:31) jdub: you'll actually have a document as the front page [01:43] (00:39:40) jdub: yelp will come with one [01:43] looks like a yelp futurism to me :-) [01:43] so sabdfl needs more context [01:43] yelp in GNOME 2.12 will use a document instead of an index as its front page [01:44] rock [01:44] mpt is thinking in very similar terms to shaunm [01:44] also, but less likely, is beagle integration in yelp [01:44] ok [01:44] the issue is, is this spec doable [01:45] and if so, where to put the other documentation [01:45] mdke: if the user guide is written with this in mind, yes. [01:45] mdke: ie. it's both a topic-oriented document (the actual content) *and* a way of navigating to other documents [01:45] I think this needs greater considration [01:46] jdub: nothing in lin docs gnome or kde is topic help like described by mpt [01:46] mdke: also, it could be done independently of the user guide [01:46] mpt has the right idea [01:46] froud: the content in user guide generally is [01:46] i don't think this spec is doable for breezy [01:46] the infrastructure for it is not [01:46] but no lin docs are written that way at presnet [01:46] no user guide is manual [01:46] sabdfl: You mean the "Suggested Breezy goals" section by itself is too ambitious? [01:46] a bool [01:46] book [01:47] i think we need to focus on the first thing jdub raised, which is organising and presenting and coordinating the bulk of docs which are already available [01:47] yes [01:47] yes! i've rasied that before! [01:47] raised [01:47] how to get all the stuff in wiki to docbook [01:47] no the breezy goals part is ok, i guess [01:47] how to maintain it [01:47] once sorted [01:47] froud: +1 [01:47] froud: that's a separate issue [01:47] froud, that is changing the subject wholly [01:48] I think you are biting more than you can chew now [01:48] this needs more consideration and discussion [01:48] i tend to agree as far as the HelpfulHelp is concerned [01:48] thi sforum wont ball it an dbag it [01:48] the idea is good, but it will require some work [01:48] guys, lots of conflation here [01:49] 1. project to analyse and collate existing in-distro documentation [01:49] jdub: as you said, "where to begin"? [01:49] ^ we've already talked about it, i'll follow up with email [01:49] this is a huge topic, we are all tired [01:49] sabdfl: +1 [01:49] i think we need to start with the tiny part of HelpfulHelp that is currently BreezyGoals [01:49] mpt's proposal is harder to discuss because we'll have something reasonably similar to it in breezy anyway [01:49] and flesh that out into a real plan [01:49] a lot of that plan should involve the low-hanging fruit jdub identified [01:50] inasmuch as yelp's front document will change, we need to see that and start to massage it as needed [01:50] we need to address froud's question about the framework for writing docs ina collaborative web driven way [01:50] but publishing to book or web [01:50] that's more than enough for breezy [01:50] ok so the general consensus seems to be to work within the current projects for now, am I wrong? [01:51] wiki [01:51] there is tons of stuff there [01:51] focus [01:51] current projects [01:51] aim at these goals [01:52] yes these are very doable for now [01:52] our core role is to make the content [01:52] discuss yelp etc in mail [01:52] good [01:52] moving on [01:52] ok anything more [01:52] quick interim issue before moving on to the styleguide. [01:52] whoa, whoa [01:52] docbook and be repurposed to make fit [01:52] core role is not to *make* the content [01:53] jdub, he is referring to the projects on https://wiki.ubuntu.com//DocteamProjects [01:53] maybe i should just address this in email [01:53] ok jdub what is our core role then [01:53] n/m [01:53] jdub: you have a good idea I also like what mpt is saying [01:54] but we cant ball it and bag it here [01:54] no, those are unrelated [01:54] was answering that particular phrase [01:54] will leave it to mail [01:54] one of the tasks henrik had was to move docs from wiki in to docbook and svn [01:54] we are awaiting a list of these docs [01:54] froud, 1. that is not his task, and 2. that is not on the agenda [01:55] is there an update [01:55] we will work on it now that the new wiki is up [01:55] Port wiki docs - we would like to port a number of stable docs from wiki to docbook. Need a list of such docs and process for managing the port and subsequent update of such documents. See here: ./doc [01:55] from the agenda [01:55] ok, guys, we are losing the thread here. let's ajourn, we've made good progress [01:55] froud, we agreed that that section of the agenda was to be postponed [01:56] froud, yes but we'll talk to henrik about it as well [01:56] i'm beginning to lose steam here [01:56] next step, a plan from jdub, a plan from froud, and we'll put those together at a CC level with the doc team [01:56] ok [01:56] moving on [01:56] sabdfl, any closing before we adjourn [01:56] we haven't dealt with the styleguide [01:56] sabdfl: a plan on what [01:56] mdke, styleguide is a docteam issue for now [01:56] this is a docteam meeting === mdke hangs on to his patience [01:57] yes but its quite specific and other people are here [01:57] ok i give up [01:57] ill prioritize it next meeting [01:57] froud: a plan on the specific things i highlighted above, plus whatever you think is important [01:57] sorry for jeffsch tho [01:57] mdke: sorry, i've lost my brains for the night ssomewhere [01:57] me too ;) [01:57] thanks for your time, sabdfl [01:58] if you guys want to continue on docteam formats and tools and plans, please go ahead [01:58] i'll second that [01:58] i've got to pack it in [01:58] getting old [01:58] thanks sabdfl [01:58] ok [01:58] much appreciated [01:58] night all [01:58] see you later [01:58] sabdfl: take care === sabdfl [~mark@sabdfl.silver.supporter.pdpc] has left #ubuntu-meeting [] [01:58] anything else [01:59] mdke: style what about it [01:59] if you wanna deal with the agenda items, i'm here [01:59] no time for me. I must go to school now [01:59] otherwise, tell me and i will go to bed [01:59] mdke: shoot dude [01:59] let's finish the agenda [01:59] style [01:59] or what ever [01:59] ok [01:59] we need jeffsch for that [02:00] remember for next meeting [02:00] styleguide is basically out for contribs [02:00] ok > [02:00] sorry jeffsch :( [02:00] yes i'll arrange for that [02:00] jeffsch, really sorry about this [02:00] i'll live! [02:00] :-( [02:00] i'll look into styleguide tonite [02:00] mdke, have you seen the styleguide [02:01] no [02:01] whats left === froud pinches mdke [02:01] ok. see you all later === jeffsch [~jeffsch@fatwire-201-201.uniserve.ca] has left #ubuntu-meeting ["gotta] [02:01] bye [02:01] ok [02:01] anything else [02:01] i think the process for new member access should also be discussed, bullet point 4 [02:01] do we still go through enrico? [02:02] mdke: may I === mpt rofls at the "Draft" watermark on wiki.ubuntu.com === crepitus [~alucard@ACBADDD5.ipt.aol.com] has joined #ubuntu-meeting [02:02] mpt, yeah i cringed [02:02] froud, course [02:02] the way we accept committers [02:02] That Seventies Wiki [02:02] mpt, mental note to rib hno73 about it [02:02] is that we wait to get a few patches [02:02] naturally [02:02] see what the person is about [02:03] get to know them [02:03] then any of us who [02:03] but in order to get them access, enrico must confirm, at the present time [02:03] are we gonna stick with that? [02:03] feels that the person shoul dbe a committer [02:03] yes [02:03] is enrico still gonna be available? [02:04] person sends public pgp to nominator [02:04] we can ask him [02:04] who fwd to enrico [02:04] enrico collects them and send to elmo [02:04] yep ok [02:04] so basically, we can ask him if he is still happy to play this role [02:05] he does that and our debian [02:05] (packaging) [02:05] yes [02:05] the question of who is to package will also need to be raised later on [02:05] but we can leave it for now IMO [02:05] bless his cotton socks [02:06] enrico does it but anyone who knows the packaing system can do it [02:06] would it be ok to ask him what he can do/what he can't? [02:06] yeah [02:06] if he is not aorund then mdz [02:06] my guess is the packaging issue can be sorted by the TB [02:06] mdz then delegates [02:06] ok [02:06] there's also the issue in bugzilla [02:06] jsgotangco, good point [02:07] ppl seem not to like bz [02:07] froud, yes, but that is not the point [02:07] sorry [02:07] what is the point [02:07] that bugs are reported [02:07] and need to be assigned [02:07] where? [02:07] in bugzilla [02:07] where? [02:07] hmmm ppl dont like bz [02:07] some want malone [02:08] well for now the reality is that there is a documentation section [02:08] that is why they dont use it [02:08] yes [02:08] unused [02:08] bleh [02:08] so we need to decide [02:08] bz or malone [02:08] hmm [02:08] I dont care which === \sh [~shermann@server3.servereyes.de] has left #ubuntu-meeting ["And] [02:09] we don't need to decide right now [02:09] that is also a TB issue IMO [02:09] fine [02:09] do we still get bug reports in bz through enrico? [02:09] no [02:09] afaik he is the default assignee still yes [02:09] you open a bz account and monitor [02:10] yes [02:10] I'm reasonably sure I'm not giving away any secrets when saying that Ubuntu as a whole is migrating to Malone after Breezy [02:10] I would prefer a mailing list === froud winks at mpt [02:11] ok have we had enough on this issue? [02:11] we'll consider that then [02:11] investigate with enrico for now [02:11] sure [02:11] we'll have an overhaul of our structure [02:11] cool [02:11] next > [02:11] i have an issue :p [02:12] sure [02:12] is froud back on the team? [02:12] shoot [02:12] just visiting [02:12] yeah? [02:12] I must get things sorted between me an jdub [02:12] an aweful lots of "we" and "our" flying around froud ;) [02:12] until I see that I am mot going to be ful gas in neutral I an just visiting [02:12] you are back [02:13] he can call you up if you want to [02:13] heh [02:13] right, re: the wiki->svn thing, I'll follow up in email over the next few days [02:13] let's get the docteam list buzzing again [02:13] ok anything more [02:14] sorry for being late btw === mdke sits on his hands [02:14] i'll make up with this by creating the summary (uh oh) since i called the meeting in the first place [02:14] mdke, thanks for pitching in [02:14] I want the team focused on svn [02:14] froud, ? [02:15] [01:11:57] froud: just visiting [02:15] heh [02:15] on the targets and to leave the noise [02:15] wiki > svn very important [02:15] and svn > wiki [02:15] but I think this is TB [02:15] thanks [02:15] is that it? [02:15] ok before that [02:15] wait [02:15] froud, do you suggest we just stay in svn [02:15] because if we do, we'll have to manage our own svn in the future [02:16] jsgotangco, not now... [02:16] you mean baz vs svn story [02:16] mdke: keep in mind that everything will eventually be in baz, whether you guys use svn now or not [02:16] just a yes or no :) [02:16] jdub, everything, as in everything? [02:16] everything [02:16] gentoo-doc use cvs [02:16] mdke: but it doesn't really matter now, we're not doing a lot of upstream doc work [02:17] mdke: ok, so, imagine this [02:17] gnome-panel comes with documentation, but we make a few changes to the default configuration that conflict with those docs [02:17] jdub, btw by "not now..." I meant, "let's not get into this now", rather than, "let's not move to baz yet" [02:18] so a member of the docteam creates a branch of gnome-panel, and changes the documentation appropriately [02:18] yeah i follow ya [02:18] they make sure the ubuntu maintainer knows about the branch, and can include it in the list of branches that make up the ubuntu package [02:18] jsgotangco: not a yes or no answerable question. baz has some really great features we can use technically [02:18] but it presents a barrier for newbie users [02:18] needs gui [02:18] mark can give us some basic shell scripts [02:18] abstract the command line complexity [02:18] just that we agreed to discuss it later [02:18] because it's in that list, one of the spanish translators picks it up automagically in rosetta [02:18] but the concepts are big [02:19] and translates the ubuntu modificatiosn [02:19] froud, HCT, but that's another story :) [02:19] mdke: jdub is right [02:19] baz is as easy as svn if it's not explained in a revision control system geek kind of way [02:20] <- not afraid of baz *flex* [02:20] mdke: rock -> just letting you know where we're headed :) [02:20] ok [02:20] jsgotangco: jdub is describing another way to do vendor drops [02:20] an easier way [02:20] froud, i never disagreed [02:20] jdub: the problem is we need a revision control with baz book [02:20] just tired [02:20] froud: yes [02:21] let's switch to #ubuntu-doc for this discussion [02:21] ANY OTHER BUSINESS? [02:21] mdke, you rest i'll wrap this up [02:21] cool, jdub we need to talk [02:21] you want to msg [02:21] ok MEETING ADJOURNED [02:21] ok you two kiss and make up [02:21] froud: i'll call at some stage, i haven't got to everyone yet [02:22] if you're going to stay in the documentation team, that is [02:22] OK [02:22] dpends on our chat === ..[topic/#ubuntu-meeting:mdke] : Logs - http://people.ubuntu.com/~fabbione/irclogs || Tue 21 June 12:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || Tue 28 June 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, or #ubuntu-devel || UTC time --> "date --utc" [02:22] bye guys was fun, go to ubuntu-doc === judax [~judax@ppp-69-148-18-161.dsl.austtx.swbell.net] has left #ubuntu-meeting ["Konversation] [02:23] thanks mdke and jsgotangco and jdub and froud and everybody [02:23] thanks all === mpt [~mpt@203-167-186-66.dsl.clear.net.nz] has left #ubuntu-meeting [] [02:23] ok thanks all, that was great [02:23] jdub: sooner we chat the better [02:23] jdub: we need to understand each other otheriwse we will bump heads [02:24] jdub: I dont want to be in that situation and I dont think you do either === oneiron [~user@pool-70-18-199-47.ny325.east.verizon.net] has left #ubuntu-meeting ["ERC] [02:26] i have a thick skull :) [02:27] oh yeah === jdub [~jdub@home.waugh.id.au] has left #ubuntu-meeting [] === jsgotangco [~jsg@202.57.71.235] has left #ubuntu-meeting ["Leaving"] === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has left #ubuntu-meeting ["Konversation] === mdke [~mdke@mdke.user] has left #ubuntu-meeting ["Leaving"] === SloMo_ [~slomo@p5487F53A.dip.t-dialin.net] has joined #ubuntu-meeting === robitaille [~robitaill@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting === FLeiXiuS [~FLeiXiuS@pcp0011790326pcs.essex01.md.comcast.net] has joined #ubuntu-meeting [06:12] morning [06:13] Good evening for I ;-) === mbeattie [~mbeattie@ool-4355f1f7.dyn.optonline.net] has joined #ubuntu-meeting === yann_ [~Yann2@p54A5D963.dip.t-dialin.net] has left #ubuntu-meeting ["Leaving"] === Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has left #ubuntu-meeting ["Leaving"] === FLeiXiuS [~FLeiXiuS@pcp0011790326pcs.essex01.md.comcast.net] has joined #ubuntu-meeting === mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting === JaneW [~JaneW@tpr-ip-nas-1-p278.telkom-ipnet.co.za] has joined #ubuntu-meeting === doko [~doko___@dsl-084-059-075-240.arcor-ip.net] has joined #ubuntu-meeting === JaneW [~JaneW@tpr-ip-nas-1-p278.telkom-ipnet.co.za] has left #ubuntu-meeting ["Leaving"] === Simira [~Simira@140.80-202-212.nextgentel.com] has joined #ubuntu-meeting === Ju [~Ju@gob75-2-81-56-64-109.fbx.proxad.net] has left #ubuntu-meeting [] === ozamosi [~ozamosi@80.252.185.147] has joined #ubuntu-meeting === Lathiat [~lathiat@gasp.bur.st] has left #ubuntu-meeting [] === boglot [chaas@gw.workaround.org] has joined #ubuntu-meeting === titus`work [~titus`@prot2.rpbs.jussieu.fr] has left #ubuntu-meeting ["Back] === doko [~doko___@dsl-084-059-081-250.arcor-ip.net] has joined #ubuntu-meeting === lamont [~lamont@15.238.5.145] has joined #ubuntu-meeting === terrex [~terrex@84-122-69-8.onocable.ono.com] has joined #ubuntu-meeting === elmo_ [~james@83-216-141-215.jamest298.adsl.metronet.co.uk] has joined #ubuntu-meeting === terrex [~terrex@84-122-69-8.onocable.ono.com] has joined #ubuntu-meeting === \S2 [~s2@host25-47.pool8256.interbusiness.it] has joined #ubuntu-meeting === jdodson [~jdodson@70-59-134-199.ptld.qwest.net] has joined #ubuntu-meeting === Ubuntu-geek [~Ryan@64.141.138.3] has joined #ubuntu-meeting === terrex [~terrex@84-122-69-8.onocable.ono.com] has joined #ubuntu-meeting === bored2k [~rafael@235samana87.codetel.net.do] has joined #ubuntu-meeting === bored2k [~rafael@235samana87.codetel.net.do] has left #ubuntu-meeting ["Leaving"] === bored2k [~rafael@235samana87.codetel.net.do] has joined #ubuntu-meeting === jdong [~jdong@d149-67-171-99.try.wideopenwest.com] has joined #ubuntu-meeting === kassetra [~kassetra@c-67-171-201-213.hsd1.or.comcast.net] has joined #ubuntu-meeting [08:58] hello all [08:58] sup geek. [08:58] wonder if this is everyone for the meeting. [08:59] ok, UbuntuForum staff role call.... === ubuntu_demon [~ubuntu_de@82-217-148-193.cable.quicknet.nl] has joined #ubuntu-meeting [09:00] hi [09:00] I'm a moderator of ubuntuforums (demon666_nl) [09:01] k [09:02] hello [09:02] hello. [09:02] Mako...the whole other party...? [09:02] maybe they went to #ubuntu-meeting-that-other-secret-room-HA-suckers [09:05] maybe they meant June 17th as in next year 2006. [09:05] ? [09:05] lol [09:05] *crickets* === sabdfl [~mark@host217-37-231-22.in-addr.btopenworld.com] has joined #ubuntu-meeting [09:06] right, i bet the meeting was supposed to be next year. [09:06] well, we just had a big guy enter :) [09:06] who's in town? [09:06] santa claus. === sabdfl checks calendar [09:06] well at least, thats why my grandmother keeps telling me. [09:06] all of the forum's staff is accounted for [09:07] old fucker is early this year [09:07] har, seriously, old people like the june weather, i think he is changing the holiday. [09:07] do we have anyone from the doc team, who was expressing frustration with the reputation system? [09:07] Gtaylor said he was coming.. [09:08] hey [09:08] i'm here [09:08] sweet, as i am i. [09:08] ok, while we have the forums team here, let me say i think you guys do a fantastic job [09:08] hey mako and mark [09:08] hiya mako [09:09] ok, folks, http://ubuntuforums.org/meeting-agenda.txt is a list of the suggestions our forum team came up with after quite a bit of thought and discussion [09:09] i believe the "old fucker" likes our suggestions.:) [09:10] sabdfl: thnx :) [09:10] jdodson: you and i are getting NO pressies this year, that's for sure [09:10] sabdfl: eh, well if he can see me when i am sleeping, no way. [09:10] wait.. we're still missing a few people that really should be here i think [09:10] i agree, like squishywaffle [09:10] correct [09:11] but I really don't think that dispute is still the concern [09:11] We at the forums believes that the problem has been resolved. The concern now is how to avoid a similar escalation in the future [09:11] wow, grammar really ISN't my strong suit today [09:12] reading that, the forums board looks like a place to raise issues on a regular basis, right? [09:12] it's about streamlining policies and politics now right :P [09:12] jdong: yes [09:12] correct; it's gonna be our version of the Council [09:12] ok [09:12] i think it's a great idea [09:12] we have had this idea for sometime, i think its a good time to bring it out to the light at it were. [09:12] Another concern is appropriate administratrive action for what already happened [09:12] i don't think we need someone from the TB present at all of those meetings [09:13] a fellow colleague is still pretty upset over the situation [09:13] well, it seems like it would be useful to work out how to prevent pass problems by having both sides of the disagreement here [09:13] the CC is a closer call [09:13] mako: i agree. [09:13] sabdfl: good point. Perhaps trade off depending the nature of the issue at hand? [09:13] i would do it the other way [09:14] if you have a technical issue, put it on the TB Agenda [09:14] and participate in the next TB meeting [09:14] to discuss that item === mako nods [09:14] they will be happy to have items put on their agenda [09:14] particularly w.r.t. infrastructure issues [09:15] sabdfl: yeah, that can be done for tech issues. but for regular conflicts that happen on the forums, we'd like our own board to resolve these issues [09:15] (btw, i'm really glad we will have a single-sign-on for wiki and forums soon) [09:15] jdong: agreed === squinn [~squinn@68.205.198.0] has joined #ubuntu-meeting [09:15] the Forums Board would handle issues between people [09:15] there's no reason for half of the locked threads to escalate to the CC agenda [09:15] jdong: agreed [09:15] jdong: right. [09:15] yeah [09:15] i think we should make it clear that if a user is not happy, they can escalate it to the CC [09:15] sabdfl: i think that is fair. [09:15] in the same way: add it to the CC agenda, and participate in the CC meeting [09:15] my yeah was a "jdong:yeah" :P === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has joined #ubuntu-meeting [09:16] [Sorry for walking in, what meeting's this? Seems like uf-mods, I'll get out. <3 the forums by the way, guys] === philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has joined #ubuntu-meeting [09:16] sabdfl: well, perhaps with a bit of reserve. As I've said before, I don't want every issue to have an appeal at the CC [09:16] squinn: we are meeting over whether or not to add microsoft products to ubuntu, goodbye. [09:16] jdong: if you guys can handle it, then it's not an issue anymore [09:16] mako: good point. [09:17] mako: Unless users think we have the authority to handle it, they WON'T rest with our decision [09:17] ah, okay, i apologize..goodbye === squinn [~squinn@68.205.198.0] has left #ubuntu-meeting ["Leaving"] [09:17] mako: good point.. we need to make that known then.. [09:17] jdong: if someone is very unhappy with a decision of the Forum Board, they will make a mess and a noise anyway [09:18] . [09:18] sabdfl: how do you suggest silencing that? I don't want to wear out my mouse clicking the ban/delete buttons.... :( [09:19] sabdfl: true. But there's still the issue of some users thinking we are dictators [09:19] In a forum of about 50 posts per minute, even if 0.5% of posts are complaints, that would still overflow the CC agenda. We don't want that to happen, and we don't want to have to sit through a 2-hour meeting to settle a thread and a disgruntled user [09:20] ubuntu_demon: that's why they can appeal to a democratically body (the CC) [09:20] sabdfl: not much users though [09:20] jdong: i think that if you guys are doing a good job, as i know you are, the number of complaints should be very very small [09:20] mako: to my knowledge they are. === squinn [~squinn@68.205.198.0] has joined #ubuntu-meeting [09:21] mako: small that is. [09:21] mako: how does this CC work ? Is there a wiki about this ? [09:21] mako: that's not the case. There are certain types of members that if we edit one profanity, they'll appeal to the CC [09:21] lets not wear ourselves out NOW trying to solve a problem that doesn't exist [09:21] so, what i'm suggesting, is let folks go on to the CC if they really want to [09:21] that way they won't feel like you are dictators [09:21] jdong: that's their problem and our problem, not your problem [09:21] sabdfl: i think that is fair, personally. [09:21] they will think I am. appropriately ;-) [09:22] ok [09:22] jdong: publish rules and run them by us, then enforce them [09:22] sabdfl: that's fine, but I personally refuse to be forced into attending a 2-hour meeting at an inconvenient time every week [09:22] if you guys can handle the CC meeting without forum staff intervention, I'd be pleased [09:22] jdong: if there is a big team of forums admins, then it should be easy to rotate [09:22] jdong: it will make our job *very* easy and the vast majority of people won't complain if they realize they have violatd a published rule [09:22] i guess it just needs one admin at a meeting like that [09:22] sabdfl: i dont have a problem attending those meetings, personally. [09:23] so let's talk about the rules [09:23] i think we can rotate internally with few problems. [09:23] jdong: there has been at least one admin at every CC meeting in the last few months [09:23] OK lets do rules.. === gtaylor [~gtaylor@130-127-67-44.lehotsky.clemson.edu] has joined #ubuntu-meeting [09:23] when we started this, the Code of Conduct was a new and untested idea [09:23] gtaylor: hey. [09:23] i think it's worked reasonably well [09:23] jdodson: Greetings [09:23] hi gtaylor === gtaylor waves [09:23] gtaylor: greetings [09:23] it might be useful to publish some guidelines and clarifications [09:24] at the moment, it's very much "be excellent to each other" [09:24] hi gtaylor [09:24] sabdfl: right. it seems at the moment the CoC can be interpreted in different ways. [09:24] sabdfl: strengthening clauses about "being respectful" is very much in need! [09:24] jdong: agreed [09:24] sabdfl: i loved that movie. [09:24] i think we could back that up with some guidelines on, for example, how to disagree without flaming, how to use the CC and TB to resolve real disputes [09:25] how to avoid becoming personal [09:25] sabdfl: right, i want to be careful to not dictate process in the CC [09:25] jdong: true. We have to make the rules more specific [09:25] sabdfl: sorry, CoC [09:25] sabdfl: in terms of conflict resolution and such.. that should be more flexible. we should be able to easily and frequently change that. the coc should be the rules [09:25] mako: sure, the CC escalation suggestion would be in guidelines and suggestions, not in the CoC itself [09:25] mako: then we need stricter rules for the forums that you guys woudl be willing to enforce [09:25] sort a CoC FAQ === mako nods === philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has left #ubuntu-meeting [] [09:26] jdong: well, you'd be the ones enforcing it [09:26] ok sec guys.. [09:26] jdong: we'd just handle any disputes arrising as a result [09:26] mako: every time we make an enforcement, they'd come crying to the CC... [09:26] mako: rules we all agree to that the forums enforce then. [09:26] reading the meeting-agenda.txt i was struck by the idea that people might publish deliberately misleading or harmful suggestions [09:26] so we are talking about set rules on the forums and then those will be enforced by the CC? [09:26] mako: We're very lenient mods... we don't act unless there's something totally out of line... in which case the offender isn't gonna be ready to shut up just because we said so [09:26] that definitely deserves attention in the CoC [09:27] jdong: that has not been our experience so far in other areas.. if there are published reasonable rules, people realize it's not worth their trouble. if the rules say "don't call someone a nazi" and someone calls some a nazi, they're not going to waste their time [09:27] sabdfl: users on the forums often get out of control, this is the nature of the beast.. :) [09:27] sabdfl: illegitimate advice doesn't happen too often intentially [09:28] Ubuntu-geek: no, we're talking about rules for the forums that will continue to be enforced by the forum admins and moderators but that group will be accountable to the CC [09:28] Coming from a user's perspective on the forum, yet being only one whose more of a lurker with only 30 posts yet been around here since Warty, I've not seen many moderator's judgements. Not that they haven't been doing their job, but I rarely see any out-of-control user. [09:28] sabdfl: but accidental "chmod 777 this" and "delete this" and "post the content of that" happens quite often [09:28] ok [09:28] sabdfl: it has been brought up to our attention about bad advice that is unintentional, i have heard no good advice to this point to curb that yet. [09:28] jdong: all we're suggesting is that you guys be accountable to an indepdendent and more democratic body.. i think that's reasonable and i think we can fin a way to make it work [09:29] mako: i agree. [09:29] mako, agreed as well [09:29] so let's talk about the reputation system [09:29] mako: I'm fine with that :) [09:29] ok [09:29] hold :) [09:29] hold :) [09:29] wait.. DID we talk about the rules [09:29] or did we just sort of breeze through that point [09:29] Ok so we have established we are fine with a set of of rules.. Now what should those rules be. [09:30] I agree. a democratic council is a good thing. [09:30] do you guys have published rules now? [09:30] i agree with mark that "obey the CoC" doesn't cut in this case === mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting [09:30] mako: we've been telling guys to follow the CoC... and that's not working. We'll need stricter rules [09:30] http://ubuntuforums.org/faq.php?faq=new_faq_item [09:31] mako: we've been slowly ammending rules when we see problems [09:31] jdong: stricter is not how i would describe it. more descriptive perhaps [09:31] more specific [09:31] agreed, "respect" is being used a lot and is not very well defined in the forum context. [09:31] which is, in turn, stricter than a loose interpretation of the CoC [09:31] this is the sort of stuff i would like to fold into a set of general guidelines around the CoC [09:31] so, mark was talking about guidesline for following the CoC [09:32] right.. i think this an ideal place to help work on this [09:32] some of that stuff is forums-specific [09:32] i suspect that there may be a number of forums specific guidelines [09:32] like "go easy on the images" [09:32] sabdfl: man.. we're just like thinking on the same wavelength now [09:32] avoid all caps posts. [09:32] but some of it would be useful in the general case [09:32] so again, do you guys have published rules beyond "follow the coc"? [09:32] mako: in that case, can i head off and let you channel me? ;-) [09:33] mako: http://ubuntuforums.org/faq.php?faq=new_faq_item [09:33] nice [09:33] mako: privmsg [09:33] mako: that is what we have at this point.. until the other day things worked.. [09:34] Ubuntu-geek: ok.. so it's stopped working so well.. that's fine [09:35] ok guys, i'm headed out, thanks for this and thanks again for your great work on the forums [09:35] there are still going to be disagreements and people will still be hurt.. but we should try to eliminate as much of the amibiguity as we can [09:35] mako: are you registered at the forums? (just curious) [09:35] sabdlf: later. [09:35] ubuntu_demon: umm... maybe === sabdfl [~mark@host217-37-231-22.in-addr.btopenworld.com] has left #ubuntu-meeting [] [09:35] **queries database for IP lookup [09:35] j/k [09:36] mako: i think he is registered as "windows-xp-forever" [09:36] errr that was to jdong. [09:36] sabdlf: bye! === mako ok, i do now [09:36] i'm "mako" [09:36] wow.. who would've guessed [09:36] on the forum [09:37] yeah, y'know [09:37] so anyway.. [09:37] so, i'm going to work on building a coc revision and to try to build some companion guidelines for it [09:37] mako: ok. [09:37] i'd appreciate your help on this [09:38] because i think we'll (a) be able to take a lot of your guidlines as general guidelines and (b) i think you'll have your own document with some forum specific stuff [09:38] stuff like colors, images, etc [09:38] y'know better than i do [09:39] mako: correct.. and one clarification, if we propose a set of descriptive rules on the forums and an issue is raised to the CC and the rules were clearly violated the CC will follow these rules correct? [09:39] i think that if you have very visible and clear rules, it will make your job easier [09:39] yeah [09:39] Ubuntu-geek: when rules are clearly violated, you guys should act [09:39] mako: i agree. [09:39] mako: ok thanks for that clarification [09:39] if someone decides to appeal to the CC and they ahve clearly violated the rules, it will be a quick agenda item :) [09:40] mako: ok thanks :) [09:40] mako: good to know. [09:40] To this point we have discussed mainly keeping the users under control. Unfortunately, you can't keep the users under control without publishing clear guidelines for moderators that are publicly posted for all users to see. This should be done to keep balance. [09:40] mako: do you see "No harassing mods" as a reasonable rule? [09:40] Guidelines for moderator behavior, that is. [09:40] jdong: define harassing [09:41] there is *always* going to be a line between criticsm done in a way that is valid and criticism that breaks the rule and it's not always going to be clear [09:41] mako: repeatedly bringing up arguments, insisting on objecting AFTER a ruling has been made by forum staff, using other channels to express their disagreements by defaming specific moderators === philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has joined #ubuntu-meeting [09:41] we can try to be as specific as possible [09:41] mako: which is, what happened in the last incident [09:42] calm down dude, we'll get there [09:42] we've already said we'll have a published process on what to do [09:42] it will go something like: [09:42] user does X [09:43] moderators think X violates the rules. takes whatever action was published [09:43] user disagrees, goes the CC [09:43] then probably either: [09:43] CC agrees that X was clearly in violation of the rules, affirms [09:43] or [09:43] CC brings everyone body together to talk it out [09:44] ok. I'm happy with the procedure [09:44] mako: that works. [09:44] the specifics, I'll decide later whether I'm in line with [09:44] so, i think that avoids the problems you were describing above [09:44] mako: sounds good to me [09:44] any other mods ok/not with this? [09:44] ok, let's move on [09:45] so i think that defaming is always be against the rules [09:45] undoubtedly [09:45] ok I am happy with that as well.. [09:46] and there needs to be an *extra* burdon on moderators to be fair, transparent, and understanding [09:46] the way the previous situation was handled should also be against the rules... [09:46] mako: a person or entity? [09:46] jdodson: dude, we'll get there [09:46] jdodson: umm.. well i hope both [09:46] How do people get in the council ? I found this wiki : http://www.ubuntulinux.org/community/processes/council/view?searchterm=council ... i scan read it .. didn't see anything on how people get elected [09:46] mako: when were we not fair, transparent, or understanding in the past? [09:46] jdodson: ummm. i thought my question was relavent. [09:46] errr [09:47] mako: ummm. i thought my question was relavent. [09:47] jdodson: that was meant for jdong [09:47] nick completisions :) [09:47] as was my post to myself for you. [09:47] HA! [09:47] jdong: i'm not implying that. there's no need to be defensive [09:47] I'm not; I'm just time-rushed. Got a doctor's appointment in 30 min === mako nods [09:48] sorry if I sound too agressive [09:48] ok.. let me take a look at your agenda [09:48] so, i should work with someobody or a group of folks about these guildelines [09:49] i think we've accomplished the biggest goal which was to come up with a procedure [09:49] or at least the outline for one [09:49] i'm going to need to work with someone here though to sort of distill it and get it usable [09:49] mako: agreed.. [09:49] well, hands :) [09:49] anyone from the forums team besides myself what to help on this? [09:49] i will help. [09:50] I will give my input [09:50] ok great thanks guys.. [09:50] Ok, i guess. [09:50] I will help in this channel for the following 2 hours if needed [09:50] cool [09:50] so, gtaylor you around? [09:50] I have access to a paper shredder. [09:50] mako: you need help [09:51] froud: is that a statement or a question :) [09:51] mako: yes [09:51] froud: :) [09:51] ? quest [09:51] offering help [09:51] froud: yeah, i'm sure you'd have good input [09:51] that would be great [09:51] this is a wiki project [09:51] ok [09:51] hello jdodson [09:52] https://wiki.ubuntu.com/CodeOfConductGuidelines [09:52] how about there [09:52] froud: hello. [09:52] mako: sure. [09:52] mako yes I know them ;-) [09:53] mako I came in late so I will need more context from you [09:53] I can work with jdodson [09:53] private chat me your email address and i will email you a IRC log. [09:54] froud: cool.. we'll talk afterwards [09:54] i just created that page [09:54] mako: lets address the rep system before we do rules. [09:54] SO ANYWAY [09:54] i was going to suggest that [09:54] Ubuntu-geek: umm.. ok.. [09:54] lets be careful here.. i DO NOT want to have this argument again right now [09:54] i'd like to know what you guys think needs to be addressed here? [09:55] Actually, I think the forum-docteam tensions that Ubuntu-geek pointed out in our IRC room need to be addressed. [09:55] as in, what do you think needs to be improved or clarified to keep this from happening again [09:55] sure, but jdong has to leave very soon [09:55] and there aren't really enough docteam people here now [09:55] I want to use the rep system as an example of what kind of rules need to be in place, if the court pleases :) [09:56] Ok.. I would like to see the reputation system enabled for everyone, users can then decide to opt out of it if they wish via the user cp. Its a way for quality control. [09:56] You may see the counter opinion at: https://wiki.ubuntu.com/ForumRepSystem?highlight=%28RepSystem%29 [09:56] jdong: that's totally fine.. if you think we can avoid the whole thing again :) [09:56] sure [09:56] Ubuntu-geek, opt-out is a good solution if someone doesn't like it [09:56] +1 [09:57] the actual rep system yes/no issue, I think, is currently irrelevant. I'm more concerned with the way the situation was handled, and how it should be improved in the future [09:57] gtaylor: we can get to that I also want to address the situation between you and kassetra. [09:57] Ubuntu-geek: That would be a good idea [09:57] so long as such a system aims to harness positive energy I think it will be good [09:57] jdong: agreed, absolutely [09:57] i think everybody agrees with that [09:57] So in favor of the rep system as long as users can opt out.. [09:57] yes [09:57] +1 [09:58] I'd still have to say no, I was concerned about the picture this paints for the users. [09:58] mako: I don't want to spark an argument, but I personally believe the way the situation escalated should be against the "rules" and guidelines [09:58] Ubuntu-geek: i like where jdong is going for the moment, lets do that [09:58] Ubuntu-geek: we can talk about the specifics of the system soon [09:58] mako: ok i like were he is going as well. [09:58] gtaylor, in what way do you think a rep system is bad if opt-out is possible ? [09:58] enough about the opt-out [09:59] ubuntu_demon: please, lets try to have one conversation right now [09:59] jdong: lets here gtaylor [09:59] regarding which of the many topics we have opened now? [09:59] s/here/hear [09:59] mako, do you have a comment about the conduct of certain members of the community during this situation? [09:59] ok.. so i read the whole thread [10:00] mako, ok [10:00] [21:51] gtaylor, in what way do you think a rep system is bad if opt-out is possible ? [10:00] mako: the original rep thread on the forums? [10:00] yes [10:00] and i think that gtaylor's ideas were pretty sane [10:00] +1 [10:00] and i think that, initally, they were presented pretty level-headedly too [10:00] mako: i agree. [10:00] +1 [10:00] mako: what about the conduct of the doc team IRC chat? [10:01] mako: and the claims of 'moderator oppression' on the Wiki? [10:01] i think that things went downhill from there and i think it was a two ways street [10:01] gtaylor: i think that in the future, you should be careful how you push on issues.. certain terms and ideas were leveled well before i think they were appopriate [10:01] jdong: I think there were problems on both sides [10:01] we should all be careful about when we say the other person is violating the coc [10:01] froud: would you like to elaborate on the conduct of forum staff? [10:01] but I would like to not make this a docteam - forums problem [10:01] and, within a couple dozen messages, BOTH sides were doing so [10:02] mako: I'm afraid I can only halfway agree, I haven't released the private messages that caused the issue. [10:02] froud: agred. [10:02] mako: Those claims were made based on a private conversation that I kept private ot prevent further problems, I figured this was more of a CC issue rather than something that needed to be quoted publicly. [10:02] jdodson: I think this is an individual - forum thing [10:02] on the other hand, the moderators need to realize that criticism, sometimes harsh criticism, comes with the territory [10:02] gtaylor: if it's based off private message, it needs to stay in private messages [10:02] mako: agreed. we are flamebait at times. [10:03] jdodson: the docteam should / cannot be held accountable for its member actions on the forum [10:03] mako: Correct. But when harsh criticism escalates to singling out individual staff members? [10:03] froud: fair enough. [10:03] gtaylor: you can't go about making accusations that nobody can confirm or deny [10:03] mako: understood but gtaylor was out of line on the way this was handled i believe even you acknowlegded this. [10:03] jdong: it is *going* to happen [10:03] mako: The CC can confirm/deny it quite easily as what was going to be done before the issues was dropped. [10:03] jdong: i have been personally accused of violating the coc and of being oppressive several times [10:03] jdong: i've been called a racist, for gods sake [10:03] Ubuntu-geek: I think we are looking for a scape goat [10:04] mako: and what should be done about it? Nothing? We're doormats? I sympathesize with you, but I think something needs to be addressed here [10:04] Ubuntu-geek: is this the best way forward [10:04] mako: Typically when it escalates to this point, individuals are asked to leave the forums [10:04] jdong: part of being a leader is taking more flac than others [10:04] jdong: People should be civil, however at times, the only person you can control, is yourself. [10:05] jdodson: Then it turns into a doormat situation [10:05] mako: I agree [10:05] you guys can't ignore the power situation [10:05] you have power the rest of your users don't [10:05] you also have visibility [10:05] mako: Part of being a leader is to make sure that your colleagues don't get hurt personally during the system [10:05] jdong: no. it turns into a public leadership situation. is the president of the usa a doormat because he gets called names all the time? [10:05] mako: I agree on the part "being a leader..." [10:05] mako: true.. [10:05] jdodson: If I said that I want to kill the president, I'd be in jail [10:06] jdong: you *will* get criticized and sometimes it will hurt [10:06] ok guys.. lets keep on track.. :) [10:06] jdong: apples to oranges, no one said anything about killing anyone. [10:06] jdodson: If gtaylor said he wants to revoke Kass's privs, he's not having any punishment [10:06] jdong: people can say anything they want, doesnt mean it is going to happen. [10:06] Who said anything about revoking Kass' privs? [10:06] jdong: personally i want the presidents privs taken, is that going to happen, nope. [10:07] :) [10:07] gtaylor: Doc team had a field day researching how to appeal to the CC about membership, etc [10:07] jdong: And what is wrong with this? Did the forum staff not discuss what was happening for advice? [10:07] gtaylor: #ubuntu-doc had a discussion that hinted they were going to try to take away Kass's membership [10:07] jdong: pls this is not a docteam thing === JanC [JanC@JanC.member.lugwv] has joined #ubuntu-meeting [10:07] froud: it happened in #ubuntu-doc. That's why I think it's a docteam thing [10:08] We need to communicate to the users in a clear way ... they can go to the council in case of a dispute (and should only do so whenever they think rules are being broken) [10:08] jdong: I had people who agreed with me, but yes it just happened in #ubuntu-doc, it was NOT a docteam issue. [10:08] jdong: no you come to the chanlle [10:08] jdong: nobody has filed any sort of CC motion to remove Kass's privs [10:08] jdong: people have suggested i get botted off the CC [10:08] jdong: it was a place to discuss [10:08] seems it did not work [10:08] when you're in a leadership situation, this is the type of strong criticism you will sometimes get [10:08] that is not a docteam problem [10:08] froud: i think that's clear [10:08] froud: ok understood.. [10:08] froud: ok. [10:09] froud: i agree. [10:09] thank you [10:09] nobody is claiming teh docteam is out to get anybody.. just that one relevant converation happened in teh channel [10:09] ok, let's wrap this up: so Mako, you're basically saying it's in the leader's responsibility to accept harsh criticism at times? [10:09] I can agree with that [10:09] jdong: yes [10:09] jdong: like i said, people can try to do whatever they want, doesnt mean it will happen. [10:09] absolutely [10:09] and sometimes it will be bruising [10:09] i have one more piece of advice i think :) [10:09] mako: listens. [10:09] * * [10:09] when you are pissed off or hurt, it's *really* hard to make a level headed decision [10:09] mako: I can take personal hits. But when the situation's ready to escalate into a forum riot, something needs to be done [10:10] it's easier to say "let stuff roll off your back" than to actually not get upset [10:10] jdong: agreed. [10:10] mako: true.. [10:10] jdong: i really don't think most of our users knew what was going on. [10:10] jdong: agreed [10:10] jdong: i think that's probably a bit of an exaggeration [10:10] jdong: i bet 95% of people had no idea. [10:10] mako: No, it really isn't. In past experience, this is how mass disagreement arises [10:11] i have some experience as well [10:11] and i think that listening to people and having the problem dealt with transparently and openning can have things work out [10:11] jdong: ppl skills are hard [10:11] when something similar happens [10:11] mako: When a user posts an outcry in a well-visited forum that moderators are abusing their power... That can cause massive public unrest [10:11] and i say WHEN, not if [10:11] mako: transparancy is good [10:11] jdong: that's part of being a leader [10:11] mako: I want to settle these issues PRIVATELY with the complainer [10:11] jdong: it's going to happen publicly sometimes [10:12] that's life.. i'm trying to help you find out ways to make it work [10:12] jdong: I can address this issue in detail when the time in this meeting comes, it isn't fair to keep referring to my claim without hearing all sides. [10:12] mako: Then we'll be the Slashdot forums... :( [10:12] ok guys, I'll be back in like 30 minutes [10:12] jdong: but equally the mods should look at the statement without personal involvement and question themselves [10:12] jdong: visibility will give these issues more creedence. as in, the right side will be shown. [10:12] jdong: see you in 30 :) [10:12] jdong, enjoy the Dr. [10:13] lol [10:13] have fun with the less heated debates, and I hope I gain that "level head" in the meantime [10:13] :) [10:13] jdong: no needles [10:13] Hmm, was this meeting scheduled/announced..? [10:13] Seveas: yes. 19:00 [10:13] ah, too short notice :) [10:13] seveas: sorry :) [10:14] ah well, I'm not a forum guy anyway... [10:14] ok lets move forward then. [10:15] Seveas: neither am i, i am there for the doughnuts. [10:15] Just wanted to give you some thumbs up for the great work you're doing. I hope all problems are/will be settled [10:15] seveas: I am sure they will.... Thanks we try.. [10:15] Seveas, I'm sure they will :) [10:16] Ubuntu-geek: without offending anyone, I must say that I did find ppl not listening, or reading, and skimming was a problem. I dont get involved in the forums, but as an outsider this was my impression. [10:16] froud: more details if you would.. [10:16] i'm not entirely sure what to do right now.. since jdong just left [10:16] Ubuntu-geek: at the same time i canot condone degrogitory language [10:16] froud: skimming is a valuble thing to be able to do. [10:17] froud: got me though university. [10:17] mako: continue with the discussion. [10:17] mako: he is a visibile mod, there are many others here who can speak. [10:17] errr type rather. [10:17] right, but he's the only one who has really disagreed with any of my suggestions :) [10:17] mako: HA! [10:18] mako: i can do that....:) [10:18] or at least disagreed out in the open. [10:18] disagreeing quietly in irc doesn't count for me [10:18] right, so is anyone not ok with what we have talked about? [10:18] kassetra? [10:18] i've repeatedly asked for feedback [10:19] mako: I will be providing you with a detailed list of my feedback. [10:19] i don't have a monopoly on good ideas [10:19] kassetra: this meeting would probably be the right place to do it [10:19] mako: No, not in this case. [10:20] mako: I prefer writing this out completely instead of hacking at it piecemeal. [10:20] mako: your sugestions are sound [10:21] kassetra: it's a little unfair to have a meeting and get everyone together and then criticism until after the fact when we all have to go back to the drawing board together [10:21] kassetra: i value the input you've given in the past.. if you disagree with anything, i'd like to know [10:21] kassetra, perhaps you can write up your feedback and post a link to it before the meeting is over [10:21] jdodson: I am with you [10:21] forums team are you ok with the details mentioned before? We will create a set of rules for the forums, if a user violates the rules we act. If the situation is taken with the CC and the user is in violation forum rules superceed and we move on?.. [10:22] philipacamaniac, good suggestion [10:22] i am ok with details mentioned before. [10:22] me to [10:22] philipcam: they are not ready yet. [10:22] froud: with me on what? [10:22] jdodson: your ideas [10:22] mako: you ok with that still? [10:22] Ubuntu-geek, I agree [10:23] mako: I disagree strongly with many points here, but I do not like not having all of my facts completely 100% perfect before disputing. [10:23] I think makos if then else mthod works [10:23] Ubuntu-geek: yeah, absolutely [10:23] Ubuntu-geek, I agree with the details mentioned before I mean :) [10:23] kassetra: that's fine.. nobody here has their facts/arguments 100% perfect [10:23] kassetra: we dont expect perfection [10:23] it's the nature of realtime discussion [10:23] froud: except from you sean :) [10:24] mako: that may be the case, but I deal in facts as a researcher, and that is how I present all discussions. === froud passed the joint to mako [10:24] I have to agree with mako on this one. Please kassetra join in or provide an url or something [10:25] kassetra: you are like totally empowered to say whatever you lik ehere [10:25] ubuntu_demon: simply because I am not choosing to jump in blindly does not mean I am NOT joining in. [10:25] froud: hey, i want some...:) [10:25] :-) [10:25] gentlemen, if she's not comfortable revealing her objections yet, the issue should not be pressed further [10:25] kassetra: i dont think anyone is jumping in blindly here. [10:26] kassetra: ok fair enough you hav eth eright [10:26] ubuntu_demon: agreed.. lets move on to the next item. which is, user opt out rep system.. (yes) or leave it disabled (no) I want to nix this off the list. [10:26] for the record (again) i'm not interested in talking about the rep situation again [10:26] philipacamaniac: right. [10:26] what happened etc. [10:26] +1 for opt out [10:26] +1 for opt out [10:26] Ubuntu-geek: that may be best at this point [10:26] +50 for opt out === mako doesn't have strong feelings either way === froud takes the j awy from jdodson [10:26] mako: vote vote.. [10:27] lol [10:27] Ubuntu-geek, agreed let's move on. [10:27] I vote for opt out [10:27] ok so calling once.. [10:27] make never has feelings [10:27] calling it twice.. [10:27] How can we make a ruling and still be democratic if only the staff are here to vote (along with a few docteam members). [10:27] I'm not staff... +1 opt out [10:27] gtaylor: its the meeting snooze you loose.. [10:27] gtaylor: members are allowed to vote, if anyone else is here they can. [10:28] Ubuntu-geek: i don't have strong feelings either way [10:28] gtaylor: its the way FOSS works [10:28] i dn't actually really care :) [10:28] Why not put a poll up with both sides on a visible board and see what happens? [10:28] i think any of the proposals are fixed [10:28] mako: funny. i don't either, i just want everyone to stop dissing each other. [10:28] ok the system will be enabled and users can choose to opt out if they wish.. an announcement will be sent to each user within the next few days telling them how they can do so. === mako nods at jdodson [10:28] gtaylor: polls can be stuffed easily enough. [10:28] fair enough? [10:29] Ubuntu-geek: fair enough [10:29] gtaylor: it gives users the choice [10:29] i believe that can satisfy both sides here. [10:29] U-G: perhaps we should mention that to the users in someway, to opt out. [10:29] gtaylor: you happy? [10:29] jdodson: (16:28:38) Ubuntu-geek: ok the system will be enabled and users can choose to opt out if they wish.. an announcement will be sent to each user within the next few days telling them how they can do so. [10:29] :) [10:30] Ubuntu-geek: I dig. [10:30] mako: I would be happy if negative rep was disabled and rep was in effect for everyone. I'm worried about the labeling that may be associated with people having a "black sheep" title because they drop below 0 rep due to a discussion in Community Chat or whatnot. [10:30] And it should be clearly visible when they register as a new user [10:30] gtaylor: then they can disable it [10:30] philipacamaniac: well if they dont notice it, why would it matter? if they then noticed, then they could "opt-out." [10:31] gtaylor: but at the same time a person like me would opt out just because I dont want a rep [10:31] gtaylor: its as simple as 123.. [10:31] gtaylor: well, in that case, you can opt-out [10:31] gtaylor: this is functionally equivalent [10:31] should the forum default be rep off? [10:31] mako: agreed [10:31] jdodson: I was about to say... [10:32] jdodson, that would be opt-in and not opt-out :) [10:32] jdodson: no [10:32] gtaylor: I think you will find that those who opt out are actually th eguru's ;-) [10:32] for the record, i am not sure on that on. [10:32] i'm not sure it really matters [10:32] SEveas: HA! [10:32] you've built in the chose [10:32] jdodson, no .. opt-out is fine IMO [10:32] mako: ok, just wondering.... i am slow, remember that.:) [10:33] perhaps there is a way to disable rep in the community chat? [10:33] So I'm wondering, what do the staff hope to achieve by this rep system? This isn't a heated question, i really want to know. [10:33] philipacamaniac: yes, to opt-out. [10:33] If people can opt out and a percentage can't even see what others have been rated as [10:33] jdodson: it should be on unless the user switches off and at any time a user can do so [10:33] gtaylor: honestly, i dont put stock into it at all, either way, i dont care it is around. [10:33] You effectively only have people with positive rep and the whole purpose of negative rep is null. [10:34] jdodson: agreed [10:34] froud: right, i was trying to say that. [10:34] Why not only allow positive rep (so you reinforce good behavior) and let everyone partake? [10:34] +1 [10:34] We're not here to discourage people from trying to help, giving positive feedback to those that attempt to seems nuturing and encouraging for the community. [10:34] gtaylor: it must be a poistive energy thing [10:34] gtaylor: it seems to me that only positive feedback is overtly simplistic. i mean disagreements are in the CoC. [10:35] How so? If you neg rep me I'll just opt out, defeating the purpose of the system. [10:35] gtaylor: like i mentioned it will be opt out.. users will be clearly giving information on how todo this when they register on the forums and current users will as well [10:35] Your rating therefore becomes moot. [10:35] gtaylor: thats fine. [10:35] Ubuntu-geek: Discuss things with us here a minute. [10:36] Ubuntu-geek, will users have the possibility to switch it on and off all the time? And do ratings get lost when opting-out? [10:36] ubuntu-geek: Keep it democratic like you guys wanted to earlier. Tell me what you disagree with in my suggestion. [10:36] gtaylor: personally my rating is worthless(to me that is). [10:36] seveas: yes its enable/disable in their control panel [10:36] jdodson: I realize that, and allowing people to opt out of negativity makes it more worthless. [10:36] gtaylor: I think its a positive thing [10:37] froud: agreed [10:37] gtaylor: not really [10:37] Ubuntu-geek: What is your goal in allowing opt outs if the people you wish to regulate just opt out? [10:37] gtaylor: but others find it useful, just cause i dont care, doesnt meant we should not care, if it is the will of this body. [10:37] gtaylor: see it as a safety valve [10:37] gtaylor: it's functionally equivalent to a postive-only system in most cases [10:37] is gtaylor the only person who wants the non-negative rep only? [10:37] but less useful since many people who will opt out could have earned a lot of positive points [10:38] for the record that is. [10:38] gtaylor: i can see why you think it is not the most efficient solution if that is the end it goes toward but i see the two solutions and equivalent in practice [10:38] mako: agreed. === Seveas favors a non-neg-rep system too [10:38] i think they're the same thing :) [10:38] Seveas: thanks. [10:38] I still haven't heard any discussion from ubuntu-geek here... [10:38] so thats 2 then? [10:38] gtaylor: I think you will find the power is in the community [10:38] gtaylor: i thought he has been saying much, or at least my logs say so:) [10:38] Ok here are the options we have. [10:39] please guys for a sec let me tell you [10:40] 1. We can allow a opt in/out rep system. [10:40] 2. We allow only positive rep system without opt in/out (this defeats the purpose) [10:40] 3. We disable it. (not an option) [10:40] the forum software isn't to flexable in this area [10:40] if 3 is not an option, it should not be presented, no offense, just a technical thing. [10:40] Ubuntu-geek, I choose 1 with opt-out [10:40] +1 opt-out [10:40] Ubuntu-geek: How is positive only defeating the purpose when #1 is too? [10:41] I choose 1. [10:41] why does 2 defeat the purpose? [10:41] i don't understand [10:41] exactly, answer the question so we can discuss this fairly. [10:41] gtaylor: whoa.. relax [10:41] this may be beyond the forum capability, but what about Slashdot-style metamoderation? [10:41] Ubuntu-geek: question? [10:42] typing a sec [10:42] hold [10:43] what if ppl give rep + what if not giving rep is equiv to neg rep? [10:43] I think this is what gtaylor is saying [10:43] as user I have two opts [10:43] froud: ok I can see it on that level [10:43] 1. I can rep this is me saying great guy [10:44] 2. I can abstain this is me saying bad gyuy [10:44] Ubuntu-geek: this is the karma system [10:44] but It does not hurt th eguy [10:44] That's what I mean, no feelings get hurt [10:44] sort of [10:44] Nobody has to spam threads asking how to opt out to avoid negative comments, etc. === froud is shocked that mako knows about karma [10:45] froud: i know all about karma :) [10:45] Ok i can respect that.. guys.. [10:45] Ubuntu-geek: you can see it at this level, do you think it could work [10:45] snap [10:45] froud: yes.. [10:46] cool then can we +1 for #2 [10:46] or did I get it wrong [10:46] We will have a positive system without opt/in/out [10:46] Ubuntu-geek: yeah [10:46] +1 [10:46] in favor? [10:46] +1 === mako will abstain from all [10:47] +1 [10:47] -1 dont think it matters. [10:47] But maybe we should rename it to "appreciation" or something :) [10:47] opt-out is fine. [10:47] gtaylor: i'll see what i can do [10:47] gtaylor: the semantics don't matter [10:47] yeah, that's a nitpicky point [10:47] ok so everyone is happy? [10:47] anyone disagree [10:48] i think we should opt-out, either way, i will be ok with. [10:48] Happy here [10:48] I'm ok [10:48] cool [10:48] jdodson: you may be outvoted. but i agree that it doesn't mater :) [10:48] you guys rock! [10:48] mako: :) whatever, i think we should all vote on to stop dissing each other. [10:48] I agree that it doesn't matter much :) [10:48] +1 no more dissing. [10:48] mako: 1 or 2 is good for me.. but majority is fine.. [10:48] +1 [10:49] ok so next.. [10:49] Ubuntu-geek, yeah [10:49] The forums team and myself can hammer out forum rules and run these past mako.. Possibly schedule a meeting to discuss them next week? [10:49] in favor? [10:49] +1 [10:49] +1 [10:50] +1 [10:50] +1 [10:50] +1, just make sure to publicly announce the date/time of the meeting as you did with this one. [10:50] gtaylor: no problem [10:50] Ubuntu-geek, just put them on the CC agenda [10:50] CC meeting is tuesday right? [10:51] see /topic [10:51] lol oh yeah :) [10:51] tue 21 12:00 UTC [10:51] that'll be fine we'll discuss there then [10:51] ah and +1 [10:51] mako: cool with you? [10:51] I will be there tuesday [10:53] anymore left to discuss at this moment ? [10:53] k, I'm back === froud gives everybody a big hug and sloppy wet kiss [10:53] jdong: wb [10:53] jdong: sweet, we solved everyrthing [10:53] jdodson, hi :) [10:53] jdong, hi :-P [10:54] jdong: j/k === Seveas thinks froud needs some neg-rep :) === froud passes the j to jdong [10:54] Seveas: I am going to opt out of that:) === ubuntu_demon hugs everybody [10:54] Seveas: I alrwady have that [10:55] thanks everyone for hammering this out.. [10:55] np [10:55] trust the community [10:55] Now! One last request for the parties involved.. lets say sorry and move on to new stuff.. :) [10:55] froud: community is why i am here. [10:55] Ubuntu-geek: uh, yes :) [10:55] jdodson: rock [10:55] Gtaylor: I apologize for not understanding your points.. [10:55] jdodson: and roll. === mako apologizes for not having a forum account until today [10:56] Ubuntu-geek: No problem, no hard feelings, and I will try to express my points without causing this much trouble in the future. [10:56] mako: *ha* its ok. [10:56] gtaylor: sweet. [10:56] next time please feel free to email me direct.. ryan@emailblue.com [10:56] mako: yeah get on the train here dude.. [10:56] mako, I'm looking forward to meeting you on the forums [10:56] and next time.. take it to the CC instead of into the forums [10:56] because things will just escalate [10:56] and they did [10:56] correct [10:57] and people will say lto of things they will need to apologize for at the end of a very long meeting [10:57] mako: lol :) [10:57] yeah [10:57] i am i th eonly one to said i was sorry [10:57] geesh i thought others would follow suit.. [10:57] ;) [10:57] Ubuntu-geek: sorry :0 [10:57] kassetra: your list near completion? [10:57] jdodson: no, as I said before. [10:58] I didn't spell it out but I'm sorry for those I offended, not just ubuntu-geek. [10:58] kassetra: thats cool, just wondering. no offense intended. [10:58] thanks everyone.. thanks mako for being here.. [10:58] c ya [10:58] i personally want to thank myself. [10:59] And it is nice that we were able to discuss this and ease the frustrations of everyone. [10:59] A victory for Ubuntu [10:59] and mako [10:59] gtaylor: rock on ubuntu. [10:59] a big hand to you dude [10:59] your gonna get old before your time if you keep this up [10:59] yes, mako, a neutral third party with a level head always helps :) [11:00] yeah [11:00] And it's good to see the leaders of Ubuntu take an interest in community matters [11:00] When you could be doing other things [11:00] (like eating) [11:00] HA! [11:00] speaking of. [11:00] or working :) [11:00] along that lines, I hope to see more Ubuntu folks at the forums :) [11:00] or that [11:00] gtaylor, agreed === froud sends everyone back to work [11:00] see ya guys [11:00] go on scat now! [11:01] shoo, shoo [11:01] my email address was posted any feel free to email me direct with forum issues [11:01] Ubuntu-geek, keep up the good work. [11:01] everybody keep up the good work :) [11:02] agreed.. [11:02] true === philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has left #ubuntu-meeting [] [11:03] So see you guys on tuesday ... bye! === Ubuntu-geek [~Ryan@64.141.138.3] has left #ubuntu-meeting [] [11:03] What's tuesday, ubuntu_demon ? [11:03] squinn: CC meeting === mako [~mako@bork.hampshire.edu] has left #ubuntu-meeting [] [11:03] Oh, CC Meeting [11:03] right. [11:03] :) [11:04] I was thinking that. [11:04] bye! [11:04] Bye. === gtaylor [~gtaylor@130-127-67-44.lehotsky.clemson.edu] has left #ubuntu-meeting ["Kopete] === froud [~sean@ndn-165-146-74.telkomadsl.co.za] has left #ubuntu-meeting ["Konversation] === dataw0lf|w [~dataw0lf@66.219.227.114] has joined #ubuntu-meeting