=== freeflying_away is now known as freeflying === shuduo_afk is now known as shuduo === jono is now known as Guest52213 === funkyHat_ is now known as funkyHat === penghuan_ is now known as penghuan === ochosi_ is now known as ochsoi === ochsoi is now known as ochosi === cjwatson_ is now known as cjwatson === czajkows1i is now known as czajkowski === yofel_ is now known as yofel === shuduo is now known as shuduo_afk === ivoks_ is now known as ivoks === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away === doko_ is now known as doko === retoaded is now known as retoaded_biab === retoaded_biab is now known as retoaded [21:56] Hello docs folks! :) [21:56] Hello there [21:58] hello GunnarHj [21:59] knome: Hi, and welcome in this context. [21:59] ta ta [21:59] * pleia2 waves [22:00] ok, who wants to play chair? [22:00] #startmeeting [22:00] Meeting started Fri Dec 6 22:00:15 2013 UTC. The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [22:00] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [22:00] Hello, everyone. [22:00] #chair godbyk [22:00] Current chairs: godbyk pleia2 [22:00] Hello. [22:00] * belkinsa is here for the meeting [22:00] o/ [22:00] me to [22:01] o [22:01] #link https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda [22:01] meeting agenda :) [22:01] pleia2, pure links are #linkified without #link [22:01] dsmythies: ok to start off with your items from the blueprint? [22:01] #chair dsmythies [22:01] Current chairs: dsmythies godbyk pleia2 [22:01] knome: neat [22:02] hey all :) [22:02] hey belkinsa [22:03] #topic Inter-group collaboration / cooperation === meetingology changed the topic of #ubuntu-meeting to: Inter-group collaboration / cooperation [22:03] hey pleia2 [22:03] so if everyone wants to browse to the blueprint: https://blueprints.launchpad.net/ubuntu/+spec/community-1311-docteam-roundtable [22:03] dsmythies left a bunch of comments on this topic :) [22:03] eagles0513875: welcome to the meeting! [22:04] there was a possible solution and a work around for the translations workflow that currently leaves the server docs behind, any comments? [22:04] I am looking for help with this one: "For the DeskTop help documentation, there is a jpeg file that includes the entity of the release name. This file has not been updated since Quantal, because nobody in the doc team knows the procedure. " [22:05] is it used anywhere? [22:05] (I don't really know much about translations, so I don't really understand the workings here) [22:05] dsmythies: I can take an action item to figure that out [22:06] dsmythies: Which file is it? [22:06] O.K. thanks. [22:06] #action pleia2 to figure out where the release name jpg comes from [22:06] ACTION: pleia2 to figure out where the release name jpg comes from [22:06] I supply the file name in a moment... [22:06] thanks :) [22:07] aiui, the "workaround" mentioned in the blueprint is *the* solution [22:07] dsmythies: ./ubuntu-help/C/figures/ubuntu-quantal.jpg? [22:07] you *need* to update the package from project at doc string freeze [22:07] though the translations could be done against the product [22:07] https://help.ubuntu.com/13.10/ubuntu-help/figures/ubuntu-quantal.jpg [22:08] which would mean translators could start working on the translations as soon as the strings change in the product [22:08] then all of that would be pushed in the package (at least on the translation freeze) [22:09] ./ubuntu-help/C/figures/ubuntu-quantal.jpg? yes. thanks. [22:09] you *need* to update the package from project at doc string freeze: Yes, thanks. [22:10] (and/)or the translation string freeze, if the translations are done against the project [22:11] Could the package be updated more frequently, to make it easier for the translators, and also make it easy for everyone to follow the progress with the docs? [22:11] if the translations are done against the project, there is no reason why it couldn't be done with every push [22:12] as long as people update the .pot file(s) [22:12] I could update help.ubuntu.com more often if people want. [22:12] We don't typically update the .pot file often. [22:13] that would be the solution though [22:13] May I ask what is a .pot file is? [22:13] belkinsa, a translation template file [22:13] Thank you. [22:13] belkinsa: It's the 'translation template' file. It contains the list of text that the translations should translate. [22:14] the issue with updating the .pot file often is that people who are translating actively might translate many strings that are dropped from the final version as further fixes and additions are made [22:15] the issue with not updating the .pot file often is that a lot of new strings become translatable at the same time [22:15] and it might be a burden that the translators can't handle, especially if that happens really close to the release [22:16] knome: The sooner we do our part, the better - still applies, right? [22:16] sure [22:16] I agree, but tranlations drag on, and we want to be able to publish later trnalations without folding back in a new .pot file, if possible. [22:17] yeah, the docs evolve through the cycle so we don't want people translating *similar* strings 5 times because we keep changing wording [22:17] I believe strings that remain between releases remain translated, right? [22:17] pleia2: But, to be honest, how often does that happen? [22:17] That's the basic reason why we have a string freeze. [22:17] one of the things you can do is keep reviewing the strings before they land in the docs to make sure they are of high quality and do not need changing [22:17] pleia2, yes. [22:18] GunnarHj: historically, not often because there was one guy working on docs :) but we're reviving the team [22:18] pleia2: Ok, point taken. ;-) [22:18] documentators should take care of their wording. [22:18] if they mess it up, that's too bad, but it shouldn't happen again and again [22:18] GunnarHj: it may be a non-issue, but I just don't know yet [22:19] you probably want to talk with the translators to hear what they think [22:19] O.K., lets move on. [22:19] I agree on that. [22:19] they might either appreciate all-at-once or do not mind about having to translate certain strings multiple times [22:20] do we want to talk about upstream issues? (see the blueprint) [22:20] Upstream issues referring to gnome-docs or something else? [22:20] "During the 13.10 cycle, the docs (both the serverguide and Ubuntu DeskTop help) uncovered a number of issues where the root causes are really upstream GNOME yelp issues." [22:20] etc [22:20] so I'm thinking yes :) [22:20] pleia2: Ah! Gotcha. [22:21] Yeah, one problem we encountered early on was that some docs have conditional text in them. [22:21] Yesm gnome stuff. I think Shaune McCance [22:21] The text varies depending on if you view the docs in Unity or GNOME Shell or LXDE, etc. [22:21] Comment from Little Girl with my apologies if this is in the wrong place - feel free to delete or move it (2013-11-03): ... [22:21] see the blueprint! :) [22:21] And there was a bug where the Yelp app wouldn't detect Unity properly. [22:21] So it'd always display GNOME Shell docs instead of Unity docs. [22:22] Has anyone filed a yelp bug? [22:22] I think we got the Unity bug patched and fixed, however. Did that patch make its way into the 13.10 repositories, dsmythies? Or were there other Yelp issues, too? [22:22] knome: ah yes! good catch, LittleGirl chatted with Shaun [22:22] GunnarHj: I filed the one about Unity (along with a patch). [22:22] Yes, I filed upstream bug reports [22:22] bottom of blueprint whiteboard [22:23] One upstream bug is fixed, but the fixed has yet to propagate down. [22:24] Not much more to talk about now then, or? [22:24] Okay. Who do we pester to get it propagated down? [22:25] I do not know, and am not certain that is hasn't. I don't know what revision number to look for. [22:27] dsmythies: Ah, I found the upstream bugs you sent me in an email: [22:27] https://bugzilla.gnome.org/show_bug.cgi?id=709951 [22:27] https://bugzilla.gnome.org/show_bug.cgi?id=709943 [22:27] https://bugzilla.gnome.org/show_bug.cgi?id=709941 [22:27] Gnome bug 709951 in yelp-build "yelp build ignores conditionals when creating file copy list" [Normal,Resolved: fixed] [22:27] Gnome bug 709943 in DocBook "yelp-xsl/xslt/common/html.xsl missing a fundamental docbook tag conversion" [Normal,Unconfirmed] [22:27] Gnome bug 709941 in yelp-build "html looks for yelp-code.png which is not there" [Normal,Unconfirmed] [22:27] Robert Ancell seems to have updated yelp (ubuntu) with upstream news lately. [22:27] I'll take a look at those again. [22:28] 709943 has a workaround. [22:28] 709941 is not the end of the world. [22:29] godbyk: If you could help woth communications with Shaun? He seems to help from the gnome side sometimes. [22:30] dsmythies: Yeah, I'll get into it. [22:30] Thanks. [22:30] \o/ [22:31] ok, I think that's it for the blueprint topics, looks like we talked about the others during the vuds session [22:31] #topic What's new - should cover 12.04->14.04 (GunnarHj) === meetingology changed the topic of #ubuntu-meeting to: What's new - should cover 12.04->14.04 (GunnarHj) [22:32] GunnarHj: can you share some thoughts here? [22:32] I think that most people stick with LTS, so it would make sense that the "What's new" page covers everything since last LTS. [22:32] dsmythies: You can find a yelp-code.png file at /usr/share/yelp-xsl/icons/hicolor/watermarks/yelp-code.png provided by the yelp-xsl Ubuntu package. (Just FYI.) [22:33] GunnarHj: yeah, that makes sense [22:33] That's the whole point from my side. ;-) [22:33] We could split it into two sections, too. "Since [previous LTS]" and "Since [previous release]". [22:33] godbyk: yeah [22:34] That works. [22:34] godbyk: +1 [22:34] godbyk: I know, but we don't actually want a watermakr at all. [22:34] #topic Sync with gnome-user-docs early === meetingology changed the topic of #ubuntu-meeting to: Sync with gnome-user-docs early [22:34] dsmythies, add an empty png [22:34] dsmythies: Ah, okay. I see what you're saying then. [22:34] I did, last cycle. [22:35] Me again... I think we should do that sync as early as possible, so we then have sufficient time to review the result and finalize ubuntu-docs. [22:35] GunnarHj: +1 [22:35] +1 [22:35] Last cycle we didn't even finish syncing. :-( [22:35] There is no reason to fear very much late GNOME changes anyway. [22:36] GunnerHj: +1 [22:36] hooray, consensus :) [22:36] GunnarHj: Especially since I think we may be lagging behind a GNOME release for 14.04. [22:36] godbyk: Precisely [22:36] no, Trustily [22:36] do we want to decide upon a date (or month) for this? [22:37] knome :P [22:37] ASAP = now? [22:37] knome: +1 [22:37] Do you know which version of GNOME we're using for 14.04? [22:37] (Not that I expect it'll change things too much for us anyway...) [22:38] Mostly 3.8, but as regards gnome-control-center, which heavily affects the docs, 3.6. [22:38] GunnarHj: Okay, thanks. [22:38] End of January target? [22:38] dsmythies: Seems reasonable. [22:39] Then we can start modifying everything that's Ubuntu-specific. [22:39] ok great [22:39] #topic Community Help Wiki (knome) === meetingology changed the topic of #ubuntu-meeting to: Community Help Wiki (knome) [22:39] https://help.ubuntu.com/community/FrontPageRefresh [22:39] ooh pretty :) [22:40] yep, i've worked on that for a replacement for the community help wiki [22:40] It's cleaner for sure. [22:40] Indeed great work so far. :) [22:40] in addition, i've created https://help.ubuntu.com/community/OtherResources (WIP) for the purposes of replacing the signpost [22:40] all feedback is welcome. [22:41] I think the Other Resources page is a better choice then that signpost, since it lists the links that people may be looking form [22:41] for*. [22:41] it doesn't need to be an exhaustive list of all URLs in the internet [22:42] just some of the most used/useful ones [22:42] I agree. [22:42] the people can find the useless ones without our help, believe me [22:42] Enough for people to get started. [22:42] lol [22:42] and that's basically it [22:42] ok, thanks knome :) [22:43] this is not the agenda, but... [22:43] i'd like to become an admin in the community help wiki [22:43] Possibly we should try to find a *short* list of other resources that we recommend. [22:44] +1 [22:44] GunnarHj, yep, also https://help.ubuntu.com/community/ExternalGuides is linked from that page [22:44] so there is plenty of links [22:44] #link https://wiki.ubuntu.com/DocumentationTeam [22:44] and tbh, how much else do we need than; [22:44] knome: right, I'll send a +1 to the list on that (I'm not a wiki admin, but there are precious few of them, so anything will help I think) [22:44] knome: Possibly too many of them... [22:44] askubuntu, ubuntu forums, mailing list, irc, manpages, guides [22:44] and flavor support links [22:45] GunnarHj, sure, i agree, but that's a content problem, and not the main area of my interest :) [22:45] Those is enough, I think. [22:45] (don't get me wrong...) [22:45] are* [22:45] I'm fairly ignorant of how the Ubuntu wiki is set up. What superpowers do wiki admins have? [22:45] GunnarHj, delete/move pages/attachments [22:45] godbyk, ^ [22:45] Renaming too [22:46] well doesn't that equal to move? :) [22:46] knome: To make a difference, we should point at resources with good quality. People know how to google anyway. [22:46] Somewhat [22:46] GunnarHj, yep. [22:46] GunnarHj, same problem around the help wiki though; some of the content in there is not quality content either [22:47] knome: Ah, okay. Thanks. [22:47] knome: True. [22:47] from my pov, once we get https://help.ubuntu.com/community/OtherResources finished, we can drop https://help.ubuntu.com/community/FrontPageRefresh as the front page [22:47] Yeah, developers just don't doc, they just develop. [22:47] and then we can keep on reviewing and enhancing it [22:48] slickymaster expressed his concerns of the topic list gettting too long [22:48] but i don't think i know the wiki enough to judge if there is something we could drop or not. [22:49] Most of us don't have that skill. [22:49] Technical skill, I mean. [22:49] i guess the right way to go forward is to keep on digging deeper in the wiki and clean up page by page. [22:49] * pleia2 nods [22:49] I think we should encourage knome to keep on his work with front page and other resources. It will be a step in the right direction IMO. [22:49] what will ultimately tell us what's useful and what not [22:50] * belkinsa nods [22:50] Can we get any statistics as to how many visits each wiki page gets? [22:50] +1 on that idea [22:50] That'd help us focus our efforts there, I think. [22:50] we can ask IS [22:50] #action knome to finish OtherResources and then send an email to the -doc list to propose the new frontpage layout [22:50] ACTION: knome to finish OtherResources and then send an email to the -doc list to propose the new frontpage layout [22:51] Also it could tell us how many are using the wiki also [22:51] I suppose I can submit a ticket to see about that (they LOVE me, I bug them all day long!) [22:51] same here [22:51] hey littlegirl [22:51] #action pleia2 to ask Canonical IS about getting help wiki stats [22:51] ACTION: pleia2 to ask Canonical IS about getting help wiki stats [22:52] #topic Redundancy of Community Wiki and Other Forms of Support (belkinsa) === meetingology changed the topic of #ubuntu-meeting to: Redundancy of Community Wiki and Other Forms of Support (belkinsa) [22:52] is there more to discuss here? [22:52] Or have we already covered this sufficiently on the mailing list? [22:52] I think we may of covered it well on the mailing list. [22:53] ok, cool [22:53] #topic Any other business === meetingology changed the topic of #ubuntu-meeting to: Any other business [22:53] * belkinsa raises my hand [22:53] anything else to chat about at this time? [22:53] I have one [22:53] belkinsa: go for it [22:54] Do we think we need some form of blog posting to tell others in the community what the Doc Team is doing? To get more folks in. [22:54] historically we've just done it via personal blogs that go to planet [22:54] Even maybe getting developers to have some form of docs for the programs. [22:54] belkinsa: We could, but before we do, we should probably have a list of tasks that are ready for people to work on. [22:55] Right. [22:55] I'm inclined to keep it that way now, the idea of adding another resource to update because we have too many resources to update ourselves makes me worried though [22:55] Oh, right. That issue. [22:55] hehe [22:55] :) [22:55] Never mind then. [22:55] Any effort to make the developers at least think of the docs aspect is welcome. [22:55] oh, so we could send task announcements to our ubuntu-doc list and them submit them to the ubuntu-weekly-newsletter for inclusion [22:55] there is an "Other Community News" section they would fit nicely into :) [22:56] Sure, that works. [22:56] yay [22:56] I guess I was really looking for that. [22:56] perfect, thanks for the idea [22:56] Not a problem. [22:56] the real question is [22:57] does anyone read UWN? ;P [22:57] who would write an article to be sent to the newsletter and/or the planet [22:57] hah right, that [22:57] I do. [22:57] * godbyk nominates knome! [22:57] w00t [22:57] godbyk, no thanks at this point, but i might do that later. thanks for the nomination ;) [22:57] But stats would be nice for UWN. [22:57] knome: It was worth a shot! ;-) [22:58] always. [22:58] i'll keep it in mind though [22:58] it's been a while since i've posted [22:58] And the article idea is a good one too. [22:58] ok, anything else? [22:59] thanks everyone :) [22:59] Should we set up a poll for another meeting in January? [22:59] godbyk: yeah [23:00] Not a problem and yes. [23:00] no, nothing else from me. bye. [23:00] #action pleia2 to set up poll for january meeting [23:00] ACTION: pleia2 to set up poll for january meeting [23:00] happy holidays, all :) [23:00] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [23:00] Meeting ended Fri Dec 6 23:00:22 2013 UTC. [23:00] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-06-22.00.moin.txt [23:00] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-12-06-22.00.html [23:00] Thank you. [23:01] Thanks for chairing, pleia2! === freeflying_away is now known as freeflying