=== mercurus [~mercurus@PIPP-p-144-134-201-191.prem.tmns.net.au] has joined #ubuntu-doc === enrico [~enrico@enrico.developer.debian] has joined #ubuntu-doc [08:09] Good morning people! [08:09] I imagine you are all still sleeping at this time, though [08:09] However, I wanted to send some HIs, telling you that I got to Taiwan, I got a new laptop and I'm bringing it online [08:10] Actually, with Ubuntu it installs out of the box, but I generally use Debian My Way and it takes a bit more [08:10] see you later! === jiyuu0 [~jiyuu0@218.111.210.223] has joined #ubuntu-doc === Kinnison [~dsilvers@213.151.107.243] has joined #ubuntu-doc [08:47] Morning === plovs_work [~plovs@195.13.248.82] has joined #ubuntu-doc === tdjb [~tdjb@c-67-161-150-249.client.comcast.net] has joined #ubuntu-doc === tdjb [~tdjb@c-67-161-150-249.client.comcast.net] has left #ubuntu-doc ["Leaving"] [09:13] Hey, folks... [09:14] Hi Chris [09:14] Hi, Dave... :) === Kinnison inverts ChrisH [09:15] ChrisH: try /whois [09:15] You can't do that, Dave! [09:15] I was David Bowman. === Kinnison sighs [09:16] you're a silly silly man :-) [09:16] I'm severely tired... [09:17] Just had yesterday to recover from the journey. And a friend came by to ask which Linux flavor he should talk to get an easy desktop. So much for the Sunday. :) [09:17] Heh [09:26] s/talk/take/ === ChrisH seriously needs more caffeine [09:31] hi guys [09:36] plovs_work, hello [09:37] is this disclamer ok? [09:37] Permission is granted to copy, distribute and/or modify this document for non commercial purpose, so long as all appropriate credit is provided, including author's name and original URL. The author makes no claim to the accuracy of the information provided. This information is provided in the hope that it will be useful, but WITHOUT ANY WARRANTY. Use this information at your own risk. Always make proper backups and use caution when modifying critical [09:37] system files. === lulu [~lu@213.151.107.243] has joined #ubuntu-doc === Burgundavia_ [~rasputin@213.151.107.243] has joined #ubuntu-doc [11:05] hello all [11:07] hello [11:10] Marning Burgundavia_ [11:25] hi all :o) === Kinnison [~dsilvers@213.151.107.243] has joined #ubuntu-doc [12:08] Kinnison, ?? === Kinnison_ [~dsilvers@213.151.107.243] has joined #ubuntu-doc === Burgundavia_ [~rasputin@213.151.107.243] has joined #ubuntu-doc [12:24] anybody object if I set up a baz archive, as I don't have commit access to the svn archive [12:25] Burgundavia_: Hi, Corey... can you set up that baz repo on the Canonical servers? Someone from Canonical promised to offer a sandbox. [12:26] For now, it'll be best for corey to do the archive on his machine I guess [12:26] We don't have an official place for it [12:26] is the userguide currently the quickguide? [12:26] baz is good enough that once you have an official place for it; you just branch it into the official place and everyone works from there instead [12:27] Burgundavia_: No, the user guide is the large document. The quick guide does not yet have a place afaik. [12:27] Kinnison: Sounds good. [12:27] ChrisH, does the quickguide exist yet? === ChrisH wishes he could have stayed for the baz BOF [12:27] So I should help Burgundavia_ set up an archive for working on the quick-guide stuff? [12:27] Baz is pretty simple in the basic use-case [12:27] Burgundavia_: Alex has started it already. But I think it's not committed yet. [12:28] yes, I saw alex working on it [12:28] Is alex still here? [12:29] Don't think so. He's online as plovs_work [12:29] Kinnison, Burgundavia_: Yes, would be great if you too create a baz repo. [12:29] ok can do [12:30] Is there already some basic information on a Wiki page on how to work with it? Like the 10 most frequently used commands or a simple transition guide for CVS/SVN users? I'd appreciate that. [12:30] check out the doc that can be installed with baz [12:31] ChrisH: I tell you what. I'll get Burgundavia_ to write a "quick start for baz for docteam" doc [12:31] bwuahahahaha [12:31] ahhh [12:31] :) [12:32] Isn't there a baz BOF these days that someone can take notes at? [12:32] Mako is taking notes IIRC [12:32] Good. === enrico [~enrico@enrico.developer.debian] has joined #ubuntu-doc [01:20] Hello! Who's left at the conference? === Kinnison raises his hand [01:21] Kinnison: welcome in ubuntu-doc! [01:21] all the others have left already? [01:22] enrico: Now; don't take my presence as meaning that I want to write docs :-) === Kinnison is helping Burgundavia_ with baz [01:22] Burgundavia_: welcome in ubuntu-doc! === jiyuu0 [~jiyuu0@219.95.247.189] has joined #ubuntu-doc [01:25] enrico: Hey... :) [01:29] I have set up a baz archive and have started working on the quickguide [01:29] Woohoo! [01:30] I *would* teach him how to make a mirror; but he lacks any webspace of use === Kinnison attempts to pimp Pepperfish at Burgundavia_ [01:32] ChrisH: hey! [01:33] Burgundavia_: You want Pepperfish hosting. Mmmmm Pepperfish [01:34] Kinnison: pepperfish? [01:36] that is Kinnison's hosting company [01:37] oh, cool! Does he give out free hosting? :) [01:37] No :-) [01:53] hi guys, sorry for being away, work is really work sometimes [01:54] jiyuu0, welcome to license-hell [01:54] ya [01:54] so long to read [01:54] and confusing [01:54] jiyuu0, and what you wrote is still not free enough, i'm afraid [01:55] wow [01:55] maybe i'll take it out... no license [01:55] jiyuu0, no go, you need some sort of license :-) [01:56] sigh [01:56] jiyuu0, but we can work something out [01:56] jiyuu0, now you know where all the lawyer jokes coe from [01:56] come from [01:56] it's all their fault [01:56] haha [01:57] i think i'll just put whatever i've modified today [01:57] then later wait for ppl to suggest [01:57] at least better than my previous disclaimer [01:57] plovs_work: hi! Are you back to work already? [01:57] what is the license problem? [01:57] enrico, hi! yes back at work, how is Taiwan? [01:58] enrico, jiyuu0 is trying to find a license for his work, without being beaten up [01:58] plovs_work: quite nice! Very warm, cheap laptops (I finally got a new one) [01:58] enrico, about time :-) [01:58] plovs_work: what are the requirements? GFDL? Some free version of CreativeCommons? [01:58] jiyuu0, enrico knows more about licenses then most of us [01:59] plovs_work, yes... givin but still got crusify [01:59] jiyuu0, that is license-hell for you, for fun say GFDL is not free on #debian-legal [02:00] how can free not free [02:00] some ppl just like to debate [02:00] debian-legal is generally a bit of a mess [02:00] enrico, what is a good license for docs? [02:00] enrico, and why? [02:00] however, it may be that Debian and FSF sort the mess and something will be solved [02:01] enrico, i think they will, it is really knit-picking they are doing atm [02:01] plovs_work: a good license depends on what you want to do with it [02:02] jiyuu0, so what do you want to do with it? [02:02] what are your requirements? [02:02] give it away for free... do whatever u like.. give some credit... and not use for commercial [02:03] enrico, it is about http://ubuntuguide.org/ btw [02:03] enrico, could we use material license under such a license? [02:04] enrico, i would like to use the material if all parties agree, it is really good [02:04] If it is non-commercial, can we still include that in our stuff? [02:04] Burgundavia_, still in Spain? [02:04] yep [02:05] I don't know if you caught it, but I am actively working on the quick guide on my machine [02:06] Burgundavia_, wuld non-commercial be an issue? [02:06] jiyuu0: uh, non commercial is quite a requirement. For example, GFDL allows commercial redistribution (that is, selling it) as long as when you buy it, it is still free software (that is, you can modify it, sell it, give it away and so on) [02:06] I don't know [02:07] I will go find a Canonical person and clear it [02:07] jiyuu0, for example if we would put it on the cd, we want to be able to sell the cd [02:07] enrico, so if they take it... just change the name... print it and sell... it's ok? [02:07] jiyuu0, and they give you credit also [02:08] plovs_work, but ubuntu going to be free right? [02:08] That is how about 5-10 years ago all those guides came out that that were basically just tldp stuff glued together [02:08] enrico, gfdl does not require credit does it? [02:08] jiyuu0: if they take it, change the title, print it and sell it it's ok as long as what they print and sell is still free (that is, when you buy you can then modify, print, sell, give away...) [02:08] jiyuu0: however, they can't take your name away from it (that is even illegal in many countries, no matter what the license says) [02:08] jiyuu0, it is freem you can download it, but it is ok to sell the disc as well [02:09] ic [02:09] jiyuu0, afaik the stuff we write is or will be under gfdl (right enrico?) [02:09] GPL *please* [02:09] i think i'll follow the license u guys use [02:10] less headache [02:10] jiyuu0, i am sorry for the trouble, but that is the world we live in... [02:10] plovs_work: he can decide. I think GPL would be nice. [02:10] enrico, what is the difference between GPL and GFDL? [02:11] enrico, for simple people like me? with short words? [02:11] jiyuu0: GPL says that the work should come with its source code, so if you generate the HTML from some other file, you should also distribute the sources [02:11] Burgundavia_, could i get your stuff from somewhere to check it out? [02:12] but gpl only for software right... no doc [02:12] enrico, eg the docbook file i am writing already [02:12] jiyuu0: GFDL is still a bit messy now, in that it allows some parts to be unmodifiable [02:12] and the html is the whole source code === enrico will try to summon mako, which is more expert in these things [02:13] jiyuu0, at least you get to meet lots of nteristing folk :-) === jiyuu0 hope not to meet with lawyer [02:14] jiyuu0, make is not a lawyer afaik, besides he's a funny guy [02:15] make? [02:15] jiyuu0, mako [02:16] jiyuu0: I think plovs_work scared you a bit, though [02:16] mako isn't responding now unfortunately [02:17] ok... [02:17] jiyuu0: Hiya! I'm not a license lawyer. We need to update the website with our documentation license = GFDL. We have decided on this as Canonical is a commercial company and we sponsor Ubuntu. [02:17] i just don't want to make other ppl / myself in trouble because of the guide... [02:17] I know GPL very well, something of Creative Commons, but not much of GFDL except that it's still a bit messy [02:18] We understand that there are invarient sections and we ask that as these are contentious, they are not included. However, you are entitled to license your work under any license you choose. You may have taken work from the wiki and mailing lists. Mailing list doc are copyright by their owner I understand. Wiki work is copyright by the owner and people assign copyright to Canonical so we can use work to help Ubuntu. === mako [mako@micha.hampshire.edu] has joined #ubuntu-doc [02:18] hey there [02:18] also remember that CCbyA is not compatible with GFDL [02:18] Burgundavia_: If you need it I can always set you up a space to put your bazaar archive mirror for others to work with [02:18] mako: ! [02:18] enrico: hey there [02:18] mako: welcome! [02:19] mako: plovs_work asked about the difference between GPL and GFDL [02:19] alright.. the GFDL is designe specifically for documentation and the GPL refers particularly to computer programs [02:20] but additionally, RMS believes that the two should be treated differently [02:20] lulu, but if my work is taken from elsewhere... like previous research on fedora/other distro... how does that count? [02:20] both have copyleft style parts [02:20] it's not exactly from wiki and mailing list here... [02:20] the GPL is more simple and portable but it refers to things like binaries versus, source, etc etc which don't apply cleanly to the world of documentation [02:21] the GFDL is much younger and more controversial [02:21] mako, is it possible to license and the later change it to something else? [02:21] it allows for invariant, non-removeable sections (which are limited to "off topic" primarily non-technical bits in teh text of the license but are often not described that way) [02:22] jiyuu0, The simplest thing to remember is that if you are original creator, you can relicense at will. If you are not, you can only use under the license granted [02:22] in addition to invarient non-removeable front covertexts, back-covertexts [02:22] dedications, acknolwedgements [02:22] and invarient removeable endorsements [02:22] jiyuu0: what you take from elsewhere remains under the license it was created under. [02:22] it also contains a number of issue which are more commonly described as "bugs" in the license [02:22] Burgundavia_, but u talking about some command and stuff [02:22] In addition, if there is no licence explicitly given, the work remain copyright, and you cannot use it [02:22] so it's hard to justify where it's from [02:22] it could be from friend [02:22] including one part which some people have interpreted to mean that encryption or even compression of GFDL documents might be in violation of the license [02:22] or here and there... [02:23] it's very clear that this is not the intention, and rms has said he would want to fix this [02:23] jiyuu0, A statement like "rm -rf" cannot be copyright, but "Using rm -rf while root at / is not recommonded" is [02:23] but for a number of political reason, teh FSF has been very slow to release a new draft of the license -- even to solve the "bugs".. software is (and should be) a higher priority for them [02:23] lulu, elsewhere could be own research... from ppl, books, internet [02:23] plovs_work: the copyright holder of a work can relicense a work [02:24] Burgundavia_, but if taken from different resource with diff license... how? [02:24] plovs_work: but they can't change the of texts which they have already distributed under any free software license [02:24] jiyuu0, It is better to be safe than sorry, as companies (ie Canonical) usually make better targets [02:24] plovs_work: things get complicated when you have many contributors to a single project [02:24] mako, ok, thanks [02:25] Burgundavia_, sigh... headache... really confused [02:25] plovs_work: because it would mean taht you either need to find all contributs to relicense (and get them to consent) or you need to have *signed* copyright assignements [02:25] jiyuu0, Yes, copyright sucks [02:25] plovs_work: this is what the FSF does. if you want to contribute to an fsf project.. you fax them a signed copyright assignment [02:25] mako, would you mind lookin at http://ubuntuguide.org and suggest a proper license [02:26] jiyuu0: i have seen it [02:26] mako, info there are not taken 100% from ubuntu wiki [02:26] but a mix from here and there [02:26] one problem with the GFDL is that is basically incompatible with *every* other license [02:26] I suggest you slow down the discussion a bit, before jiyuu0 gets a headache... [02:26] Too late for me already. :) [02:26] enrico, thanks... tension with these issues [02:27] plovs_work, Kinnison is going to set me up a public mirror after the meeting [02:27] jiyuu0, sorry for the trouble, and i *still* think your doc is great [02:27] jiyuu0: it depends on what you want.. if you want debian to be able to include it, something like the GPL or a public domain dedication or a BSD style license would be a good idee [02:27] Burgundavia_, who is Kinnison? do i know him? (who am i? do i really exist? ...) [02:28] mako, so meaning GPL is the standard... with less problem [02:28] compared to others [02:28] jiyuu0: i personally use CC licenses.. usually the CC version 1.0 sharealike or the new cc-attrib-sharelike.. although the new licenses are not debian compatible [02:28] plovs_work, Kinnison = Daniel Silverstone [02:28] jiyuu0: well, it's a software license.. and it doesn't require attribution, if this is something that you want [02:28] plovs_work: Haven't you been to the Marina with us? :) Kinnison was the guy besides my wife. [02:29] i was, you have a photo? [02:29] plovs_work: All his photos suck. And I didn't take one of him. [02:29] mako, so i'll go for GPL then [02:29] if that solves the problem [02:29] ChrisH, ok, got it already, sorry, old age setting in... [02:31] plovs_work: John seems to be confused about the quick guide... [02:31] jiyuu0: right.. now if you've used pieces from the wiki, those bits are copyright the author [02:31] and... [02:31] have to credit em? [02:31] ChrisH, i can do a write-up to the list [02:32] jiyuu0: technically, you have to get the permission for hte authors [02:33] that is not somthing easy... i have to do reverse engineering [02:33] jiyuu0: it's very difficult [02:33] true [02:33] jiyuu0: i mean, go ahead adn put your document under the license of your choice [02:33] plovs_work: Very good. We should coordinate work on the nutshell thingy (the "6000 words" one), too. [02:34] Burgundavia_, could you send me what you have by mail? [02:34] brb [02:35] Burgundavia_: once I've sorted you out with a mirror for your archive; I'll take you through what is needed for others to work with you and then you can write a wikipage for it [02:36] mako: what would it take to make it so that everything in the wiki is under a free license? [02:37] mako: putting notices in the edit pages? [02:37] that is what other people do [02:37] mako: could we do it as well? [02:37] that is what, for example, wikipedia does [02:37] yes, we could do it [02:38] if you forsee enforcement of the license though, i seriously doubt this will be enough [02:38] enrico: we were going to put it in the legal page with all the legal stuff. Do you think we need it on every page? [02:38] mako: I think we shuold, since we intend the wiki to be a scrapbook for bigger documentation [02:38] lulu: in the "edit page" page for sure [02:38] the FSF requires signed copyright assignements from every significant contributor to a gnu project [02:38] mako: oh, annoying [02:40] enrico: edit page = good idea. [02:41] lulu: yes [02:41] enrico: yeah, this is why people don't do it [02:41] really, the biggest problem i forsee is having lots of documents that you want merge under incompatible licenses [02:42] quite honestly, i don't see consensus forming around the GFDL for a number of reasons [02:42] but there is a lot of existing technical and free software documentation under the GFDL [02:43] but if we were to merge most of it, it would require bringing in invarient nonremoveable sections and printing things like "A GNU Manual" on the cover of any books and the address of the FSF on the back === sid77 [~sid77@151.11.187.66] has joined #ubuntu-doc === sid77 hi [03:10] Kinnison, will this mirror be svn, arch or ftp? [03:10] it'll be a bazaar mirror [03:10] over ftp [03:10] or http [03:10] Kinnison, but we might use baz as well? [03:11] Indeed. Bazaar is the right way (tm) [03:11] Kinnison, thanks, cool === lifeless [~robertc@dsl-43.6.240.220.rns01-kent-syd.dsl.comindico.com.au] has joined #ubuntu-doc [03:13] If people need bazaar help, lifeless here is the project lead [03:14] lifeless: Hey... glad to have someone who answers to stupid questions. :) [03:14] :) [03:14] lifeless, we want zsh command-line completion for baz ... please? [03:15] First we probably need some documentation on baz (Wiki Quickstart page) [03:15] ChrisH, spoilsport [03:16] so, there is a wiki, and we're starting on doco at the moment. [03:16] Very good, Sir. [03:17] for zeesh, someone could port the tla completions :) [03:17] I'm not a zeesher. [03:21] back [03:22] Burgundavia_: what were your concerns with using the GPL for commerciail publications? [03:22] Burgundavia_: the GPL does not bar commercial distributrion of software and would not bar commercial distribution of documentation either [03:22] ture [03:22] true [03:23] No, my concern was not around the GPL [03:23] Burgundavia_: what was it with? [03:23] i guess i didn't really follow it [03:23] My concern was around the current license of jiyuu0's text says non-commercial only [03:23] Burgundavia_: oh, right [03:23] i can remove it [03:24] well, it sounds like jiyuu0 is interested in fixing that [03:24] jiyuu0: lets wait a day or two and try to find the Right license [03:24] jiyuu0: i like the idea of using CC-BY-SA myself [03:24] http://creativecommons.org/licenses/by-sa/2.0/ === jiyuu0 checkin [03:25] i think it's free enough that it is in the spirit (and maybe even letter) of free software licenses but ensures that attribution is kept (which the GFDL does) and that it is copyleft (that the GFDL does) almost any of the parts people find problematic [03:25] sorry without almost any of the parts taht people find problematic [03:26] that page is not the text of the license, althought it has a link.. but is a good human readable summary [03:26] but that leaves us out in the cold as we use GFDL does it not? [03:26] Burgundavia_: define we? :) [03:26] Burgundavia_: i'm going to talk to mark shuttleworth about the canonical produce documentation [03:26] the doc team [03:27] ok [03:27] but almost everyone on the docteam can use whatever license they choose [03:27] because they don't work for canonical [03:27] and people, like jiyuu0 and many others.. are not particularly happy about the GFDL [03:27] mako: well, mark already decided on GFDL some time ago [03:28] actually i have no issues [03:28] I am not a huge fan of the GFDL either [03:28] i'm not either actually, but since i work for canonical it doesn't matter :) [03:28] only scared ppl have issue on me [03:28] jiyuu0: well, there are reasons to be concerned by the GFDL [03:28] jiyuu0: at least the current draft [03:28] enrico: lulu has asked me to talk to mark about this [03:28] enrico: because it is a topic that keeps coming up on the doc list and seems to be keeping people from doing work and moving forward [03:29] enrico: do you think moving to a non-gfdl documentation license would be an improvement? [03:29] i'm a little worried because evidently, many people in wikipedia are regretting their decisions [03:29] When WP was started CC did not exist [03:29] but because they do not track copyright holders, they can't relicense [03:30] otherwise they would probably have gone with it === lulu [~lu@213.151.107.243] has joined #ubuntu-doc [03:30] CC licenses are (a) international (b) written by lawyers (c) more tested and more used (d) more simple (to enfforce, to understand, to use) [03:31] gfdl has optional front cover texts, back cover texts, invarient sections, acknowledgements, dedications, endorsements and additional bits that come to effect when you're copying in quantity [03:31] it's complex :) [03:32] GFDL makes it almost impossible to small printed documents, as you need to print a whole crapload of hte GFDL [03:32] Burgundavia_: yes [03:32] Burgundavia_: CC licenses allow you to provide a URI [03:32] *and* CC documents are international [03:33] there are versions updated to the language and law of a dozen or so countries [03:33] while the GFDL is US only [03:33] i mean, it might o [03:33] work other places too.. but that wasn't a goal [03:33] but all this wonderful talk is just hotair unless we can get Mark to go along [03:33] Burgundavia_: i can talk to mark [03:34] but i would like to be able to say taht i'm representing teh view of more than myself :) [03:34] enrico: what do you think? [03:34] enrico: i know one of your concerns was with debian compatibilituy [03:34] I would go with CCbySA if we can [03:35] enrico: and quite honestly, i don't know a single up-to-date documentation license taht debian-legal likes [03:35] enrico: but i suspect that if someoen pushed a gr, the CC-bysa would pass [03:35] so pretty much debian compatiablity is a no go anyway [03:35] unless you want to use a sofware license for documentation.. or a public domain dedication [03:36] which is not necessarily bad [03:36] mako: I don't know much about Debian, but I think that debian's rebuttal of it made many people wary [03:36] although i prefer copyleft licenses myself [03:36] enrico: of the GFDL or of the CC-bysa [03:36] ? [03:36] mako, i would like as free as possible, but debian-compatible as well [03:36] I do prefer copyleft licenses [03:36] Of the GFDL, because it made much more noise [03:36] what was wrong with the CC-bysa? [03:36] enrico: unless you use a pre 2.0 CC (i.e, out of date), there are no copyleft documentation licenses i know of [03:37] enrico: very bizarre hair splitting things [03:37] (besides the unspellable name, and probably that they've taken it out) [03:38] the only concern about GFDL was that it can't go in Debian main (so far) [03:38] http://lists.debian.org/debian-legal/2004/07/msg01193.html [03:38] but i strongly disagree with most of that interpretation [03:39] i think that " [03:39] If this is the case, private distribution of the work would seem to be [03:39] forbidden. Along with obvious technological measures that control access, [03:39] such as a firewall on a LAN or a virtual private network (VPN), distributing [03:39] using encryption (such as Secure Sockets Layer (SSL)) would appear to be [03:39] prohibited." [03:39] that is a pretty ridiculous interpretation [03:39] it's CLEAR to me that they're not banning private distribution :) [03:39] intent matters in law and -legal doesn't seem to realize that [03:40] if you don't take intents into consideration when checking laws, no laws will ever be sane [03:41] one could add an explicit statement to please debian-legal, though, but that's a bit arrogant since debian-legal doesn't appear to be sane here [03:41] BTW, how come CC took that license out? [03:46] because 95+% of people who used CC licenses used attribution :) [03:47] they said they would add them back if there was a major outcry [03:47] i emailed them and ask them to create a pure SA license [03:47] but i guess other people did not [04:05] mako: let debian-legal do it [04:05] back again [04:05] or we can plea for CC-ification of a fixed GFDL like it happened with GPL [04:05] can I force an absolute path for loading of images in docbook format? [04:09] Burgundavia_: In theory: yes. But if someone decides to put the guide into somewhere different than / (which could easily happen on the ubuntulinux.org web site as well) then the image is broken. [04:10] ok, so the best is the distribute the image with the guide then? [04:15] We need to do that anyway. [04:28] ok [05:05] I have done a mock up of graphical style of showing how to use an application. I also think we can release it to translators as an svg, so they can just import the new screenshot and change the text, then reexport the png [05:05] what do people think? [05:34] Burgundavia_: I didn't quite get what you mean [05:34] Burgundavia_: :( [05:35] Ok, I think we should use screenshots [05:36] however, we should also have that screenshot with help messages showing what buttons do what [05:36] However, thus it makes hard to translate [05:37] my solution, keep the screenshot-with-explaination in svg format for us, and exported to png for the released document [05:37] thus, the translators can translate the svg and get a new screenshot and reexport [05:37] do you understand that? [05:50] ah, ok. But how do you make a SVG screenshot? [05:50] I'd love to be able to make SVG screenshots, actually [05:52] no svg screenshot, png screenshot [05:52] using gimp [05:53] the new license is CCbySA2.0 [05:54] hey guys, i just talked to mark [05:54] Burgundavia_: ah, screenshot-with-explanation! Now I get it [05:54] and he says that CCbysa is good to guy if there's consensus that it's a better license [05:54] good to go even === mako hugs enrico === mako highfives lulu [05:55] :) [05:55] so, it's up to the team [05:55] if there's consensus that CCbySA is a bettter choice, i can update the text and hook it up [05:55] Burgundavia_: can't it be done directly with captions inside docbook? Or it's one of those cool explanations that circle the things and tell what they are? In that case, yes, SVG would be very cool! [05:55] mako: wasnt CCbySA outdated? [05:56] yes, it circles each description [05:56] mako: I mean, not in 2.0? [05:56] enrico, yes by 2.0 [05:56] no.. CC-SA was outdated [05:56] plain old sa is only a 1.0 license [05:56] so, CC did a 2.0 free license after all? [05:56] by-sa is both a 1.0 anda 2.0 license [05:56] and is CCbySA free? [05:56]