=== doko_ is now known as doko [02:56] join #ubuntu-co-meeting,#ubuntu-co [02:56] join #ubuntu-co-meeting === Adri2000 is now known as Guest10811 === beuno_ is now known as beuno === Guest10811 is now known as Adri2000 [15:02] * slangasek waves [15:03] o/ [15:03] \o [15:03] #startmeeting [15:03] Meeting started Thu Oct 2 15:03:25 2014 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:03] Available commands: action commands idea info link nick [15:03] hi [15:03] o/ [15:03] [TOPIC] Lightning round === meetingology changed the topic of #ubuntu-meeting to: Lightning round [15:03] $ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson caribou infinity mvo bhuey sil2100 robru) [15:03] mvo infinity sil2100 slangasek robru stgraber jodh caribou bdmurray barry doko bhuey cjwatson [15:03] first! [15:04] apt: [15:04] - Diagose failure that Daniel Westervelt had with armhf/maas [15:04] (bug in Acquire::GzipIndexes code but already fixe) [15:04] - Enable all hardening options (including PIE) [15:04] - Smoe more work on acq-trans branch [15:04] click: [15:04] - Deal with libqt5gui5 -> -gles fallout (emulator releated) [15:04] - Fix gnutls error for public.apps.u.c in their deploy charm [15:04] (lp:~mvo/canonical-is-charms/ubuntuone-servers-deploy-public.apps.u.c) [15:04] - Address review comments for lp:~mvo/click/acquire [15:04] - Port acquire to use pythons new asyncio (lp:~mvo/click/acquire-asyncio) [15:04] - Port lp:~mvo/click/sso to pycurl and resolve gnutls issues (missing [15:04] ServerName in server config for TLS) [15:04] - Start discussion with SDK team about lp:~mvo/click/click-check-libs [15:04] - Work on fixing lp:~mvo/click/lp1232130-kill-on-remove-2 [15:04] (tricky because ubuntu-app-launch is on the session bus but click is root) [15:04] - Port lp:~mvo/click/repository to use pycurl and provide httplib2 like [15:04] http_request() function to make porting simpler [15:04] - Review lp:~cjwatson/click/chroot-name [15:04] - Update lp:~mvo/click/lp1319790-chroot-fstab [15:04] lp:~mvo/click/dont-crash-for-empty-db, [15:04] lp:~mvo/click/lp1232130-kill-on-remove, [15:04] lp:~mvo/click/lp1219912-build-exclude, [15:04] lp:~mvo/click/framework-info to current click [15:04] click-bin-path: [15:04] - Debug/fix crash when nothing has a bin-path [15:04] sponsoring: [15:05] - Review/upload ubuntu-core-config/initramfs-tools-ubuntu-core [15:05] system-image: [15:05] - Upload pycurl based image downloader to the foundations PPA [15:05] - Debug build failure with pycurl in system-image ppa build [15:05] - Debug/fix incorrect writes with lambda and write custom writer [15:05] - Look into unneeded core image dependencies [15:05] - Port pycurl branch to CurlMulti [15:05] - make total progress totally reliable [15:05] - add get_download_manager() factory [15:05] - update default config for ppa system-image-cli [15:05] - tweak seeds, do not include recommends in system-image seed [15:05] (done) [15:05] mvo: \o/ [15:06] no infinity at the moment [15:06] Ah, ok [15:06] sil2100: [15:06] - Landing team work, preparing landing e-mails [15:06] - CI Train maintenance and feature: [15:06] * Deployment of the build job refactoring [15:06] * Refactoring of the publish job [15:06] * Adding unit tests to the few newly ripped out publish job chunks [15:06] * Work on the dual landing scheme for ubuntu-rtm [15:06] * Start looking into the issue of not all bug numbers landing in debian/changelog [15:06] - Debugging and fixing problems in commitlog generation (google API problems) [15:06] - Sending out announcements about changes in some of our processes [15:06] - Packaging and quilt advice for some upstream projects [15:06] - Preparing script for ubuntu-rtm backlog generation [15:06] - Health problems, one day of sickness, slow recovery - less work done... [15:06] barry: get_download_manager() should actually be good now, it will check the bus for udm and use that if its available and otherwise try to fallback to pycurl [15:06] (done) [15:07] mvo: that's really great [15:07] mvo: i might still want the setting to override autodetection, but we'll see [15:07] barry: thats added as well :P [15:08] barry: via the environment right now though for easy testing [15:08] mvo: yep, makes sense [15:09] * feeling ill this morning, so not a very comprehensive report [15:09] * partner package reviews [15:09] * working on various branch reviews (upstart, apport) [15:09] (done) [15:09] robru: [15:09] barry: whats the best irc channel to ask about asyncio for "normal" files? and if its worthwhile to work on a patch? [15:10] #chair mvo [15:10] Current chairs: mvo slangasek [15:10] mvo: good question. *maybe* #python-dev? i have to see if there's a specific asyncio channel [15:10] (as I may not make it to the end of the meeting today) [15:10] looks like no robru [15:10] stgraber: [15:10] ah sorry, need a minute [15:10] robru looked alive ;) [15:11] oops, sorry [15:11] been preparing for LinuxCon and Plumbers, did the LXC 1.0.6 release, did the LXC 1.1~alpha2 release, got a FFe for that latter and uploaded to utopic [15:11] ok, robru after stgraber then [15:11] now trying to track down a very annoying kernel bug that's affecting my server [15:12] mvo: https://code.google.com/p/tulip/ (tulip being the code name for the standalone version) [15:12] I'll be gone next week except for Friday, then I'll be gone the week after at LinuxCon/Plumbers and the week after that for the device sprint. [15:12] fully back on the 27th [15:12] (DONE) [15:12] - ripped all knowledge of spreadsheets out of the CI Train jenkins backend. It is now 100% ready to have something else replace the spreadsheet (just waiting for the spreadsheet replacement itself to be ready). [15:12] - work continues on encapsulating the various bits of spaghetti that exist in the ci train code. eliminated knowledge of the json configuration format from the prepare job, check-publication-migration job, and the build job. [15:12] - made it easier to rollback production deployments in case I land something broken [15:12] - resurrect accidentally deleted copy2distro script and brought it up to current coding standards (pep8, pyflakes, etc) [15:12] - fixed all kinds of little bugs and typos and stuff [15:12] - ported most of the bash scripts to sh, except for one in which sh breaks pbuilder for some unknown reason. [15:12] - eliminated an entire class of ridiculous path-traversing code which was hunting for silos... which exist only in a single well-defined location. [15:12] - various and sundry landings. [15:12] - vacation next week! [15:12] (done) [15:12] * upstart [15:12] - bug 1198180 investigations with apw. [15:12] bug 1198180 in upstart (Ubuntu) "possible leak in upstart 1.5" [Medium,Confirmed] https://launchpad.net/bugs/1198180 [15:12] * goget-ubuntu-touch: [15:12] - Raised MP to add '--list-images' option: [15:12] https://code.launchpad.net/~jamesodhunt/goget-ubuntu-touch/add-list-images-option/+merge/236510 [15:13] * system-image [15:13] - Lots of activity. Currently investigating improvements to upgrade [15:13] logic and will then start serious package whittling. [15:13] lxc autopkg tests fail [15:13] 🀫 [15:13] doko: that's normal [15:13] jodh: nice work on the goget branch [15:13] ahh [15:14] mvo: w/e hack :) [15:14] doko: see part about the kernel panic on my server :) adt will pass again once the public images server works again [15:14] * sosreport 3.2 released [15:14] - Started to work on Debian/Ubuntu packaging [15:14] - Continue implementation of git-dpm [15:14] - Found zero-day bug in apt plugin [15:14] * Investigation on a iSCSI/LVM/DM-MPIO mount issue at boot [15:14] * Preliminary work on running kdump-tools at RunLevel S [15:14] (done) [15:15] caribou: git-dpm ftw! [15:15] barry: looking forward to your talk != [15:15] :) [15:15] modified errors charm and code to create version_info [15:15] research into volume of CORE files being reported to the Error Tracker [15:15] searched for CORE files to be removed from swift [15:15] r537: daisy/submit.py: do not ask for a CORE for packages without Ubuntu or Ubuntu RTM as we will not be able to retrace them [15:15] r538 "daisy/submit.py: add in a metric for retraced crashes missing a stacktrace" [15:15] r540: daisy/submit.py: do not ask for CORE files if the report is missing information required for retracing the crash" [15:15] reworked steve's apport changes for whoopsie-upload-all [15:15] investigation into ubuntu-touch default test whoopsie failure and discussion with plars about it [15:15] reviewed paul larson's change to whoopsie default ubuntu-touch test (approve) [15:15] submitted apport bug LP: #1374544 regarding SegvAnalysis field weirdness [15:15] reported apport bug LP: #1376374 regarding repeat processing of crash files [15:15] Launchpad bug 1374544 in apport (Ubuntu) "crash file indicates Disassembly is missing when it isn't" [Undecided,New] https://launchpad.net/bugs/1374544 [15:15] Launchpad bug 1376374 in apport (Ubuntu) "whoopsie-upload-all will run hooks on a corrupt crash file multiple times" [Undecided,New] https://launchpad.net/bugs/1376374 [15:15] SRU verification of bug LP: #1324833 [15:15] Launchpad bug 1324833 in aptdaemon (Ubuntu Trusty) "crash handler does not include package version" [High,Fix released] https://launchpad.net/bugs/1324833 [15:15] uploaded fix for update-manager LP: #1374715 regarding CVE urls [15:15] Launchpad bug 1374715 in update-manager (Ubuntu) "CVE links in the updater are invalid" [Medium,Fix released] https://launchpad.net/bugs/1374715 [15:16] uploaded trusty SRU for LP: #1354571 so we'll stop uploading crashes with bad core dumps to the error tracker [15:16] Launchpad bug 1354571 in apport (Ubuntu Trusty) "apport-retrace ignores warnings from gdb" [Medium,Fix committed] https://launchpad.net/bugs/1354571 [15:16] submitted merge proposal fixing sru-report traceback [15:16] ✔ done [15:16] system-image: LP: #1370586; LP: #1376758 (triaged); system-image 2.5-0ubuntu1 (monkeypushing rebuilds, citrain, rtm, testing). reviewed mvo branch. [15:16] Launchpad bug 1370586 in Ubuntu system image "Add synchronous method to determine if there are known updates" [High,Fix released] https://launchpad.net/bugs/1370586 [15:16] Launchpad bug 1376758 in Ubuntu system image "Ability to specify script to call at end of download rather than rebooting" [High,Triaged] https://launchpad.net/bugs/1376758 [15:16] debuntu: tox 1.8.0-1. python-concurrent.futures 2.2.0-1. tons of pycurl bug triaging, conversion to git (for better debian/ubuntu package management), 7.19.3-1-2, 7.19.5-1, 7.19.5-2, and LP: #1376736 (FFE) with 7.19.5-2ubuntu1 ready to go. debian bug #763770. debian sbuild creation (fails due to debian bug #607228) [15:16] Launchpad bug 1376736 in pycurl (Ubuntu) "[FFe] update to pycurl 7.19.5" [Undecided,New] https://launchpad.net/bugs/1376736 [15:16] Debian bug 763770 in src:pycurl "pycurl: Add DEP-8 tests" [Normal,Open] http://bugs.debian.org/763770 [15:16] Debian bug 607228 in sbuild "no way to run setup command inside a chroot" [Normal,Fixed] http://bugs.debian.org/607228 [15:16] other: reviewed branches for cgoldberg and robru. falcon upstream branch rebase and back/forth to get landed. [15:16] more git-dpm hacking [15:16] -- done -- [15:17] doko is next [15:17] - vacation last week [15:17] - catching up with email [15:17] - toolchain updates [15:17] - python update [15:17] - a bit of MIR processing [15:17] (done) [15:17] and now bhuey [15:18] and cjwatson is not here today [15:19] no bhuey? [15:19] [TOPIC] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:19] anything else? anything interessting happening last week thats worth sharing? [15:19] I have: asyncio is cool [15:21] nothing…? [15:21] mvo: continue! :) [15:21] [TOPIC] kernel crash dumps === meetingology changed the topic of #ubuntu-meeting to: kernel crash dumps [15:21] caribou: do you want to talk a little bit about this? [15:22] mvo: yes, it's *super* cool [15:22] barry: heh :) everybody want to get back to real work eh ? [15:22] mvo: maybe a brief update if someone is interested [15:22] caribou: yes! [15:23] the Debian/Ubuntu way of capturing a kernel crash dump is, once kexec triggers a reboot following a kernel panic [15:24] to run a SysV initscript called kdump-tools that will do the necessary steps to read from /proc/vmcore [15:24] use makedumpfile to process the /proc/vmcore output and to some filtering and compression and to produce a file [15:25] in /var/crash/{timestamp dir} directory. the content of the dmesg output is also captured in that directory [15:26] the system is then rebooted. On startup Apport will produce a Report file in /var/crash that contains the output of the dmesg file [15:26] that Apport report used to contain the full kernel crash dump but given the size of those files, it is now left in the timestamped directory [15:27] the kernel crash file can be later analyzed in conjunction with a kernel namelist which includes the debug symbols [15:28] I recently introduced in the latest version available in Debian (1.5.7) a functionality to allow the crashdump file to be sent to a remote server via SSH or NFS [15:29] There is also some preliminary work being done to have the kernel dump capture to be executed at run level S [15:29] caribou: is there sensitive information in the crash dump, and if so, does it get trimmed out before it leaves the local machine? [15:30] there can be, especially if all userspace memory is capture (the default is not to capture them) [15:30] but network information, in-transit data & such is bound to be present in the crash dump file [15:31] which is why many user are very cautious of what is being done with those files. Some even refuse to make them [15:31] available, so sometime the analysis has to be done remotely on their servers [15:32] For instance, the file system structure, file names, TCP/IP information & adresses, process list with arguments, all of those are easily available with the default setup [15:33] It is makedumpfile responsability to filter out unneeded/unwanted memory pages [15:34] that's about all I have if I want to remain brief [15:34] cool, interessting stuff, thanks for this! [15:34] oh, for some reason it seems much more difficult to get a crash dump on a laptop/desktop [15:34] and next week we will have cjwatson talking about (one of the things) he is working on [15:34] I have an outstanding bug on that [15:35] oh, what the issue here? [15:35] caribou: thanks! [15:35] yw [15:36] more comments/questions? if not it seems we are close to EOM :) [15:37] #endmeething [15:37] thanks everyone! [15:37] #endmeeting even === 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 [15:37] Meeting ended Thu Oct 2 15:37:55 2014 UTC. [15:37] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-02-15.03.moin.txt [15:38] mvo: thanks [15:38] thanks! [15:40] thanks! [15:42] o/ [17:13] #startmeeting Community Council [17:13] Meeting started Thu Oct 2 17:13:42 2014 UTC. The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:13] Available commands: action commands idea info link nick === 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 | Community Council Meeting | Current topic: [17:13] running a bit late, but we're here :) [17:13] hi [17:13] aloha [17:13] #chair elfy YokoZar czajkowski [17:13] Current chairs: YokoZar czajkowski elfy pleia2 [17:14] #link https://wiki.ubuntu.com/CommunityCouncilAgenda [17:15] so, anyone from the Membership board or Kubuntu around? [17:15] popey might be [17:15] * popey awakens [17:16] wassup? [17:17] hggdh, jared, marcoceppi, cyphermox_, about? [17:17] pleia2: aye [17:17] just checking in with the membership board, seeing how things are going, if there's anything we can do to help [17:18] Sorry, I wasn't prepared for this, didn't realise we were going to be called to chat. [17:18] especially I suspect - are meetings being held with another members for quorum now in general? [17:18] However I have some comments if you want them ☻ [17:18] sure that would be great thanks popey [17:18] o/ [17:19] valorie: yay :) can you stick around for a few minutes so we can chat about kubuntu after membership board? [17:19] sure [17:19] hiya [17:19] * shadeslayer passes around some blueberry icecream [17:19] shadeslayer: we're second on the agenda [17:20] yum! [17:20] cool :) [17:20] popey: comments? [17:20] So my observations being back in the membership board... [17:20] 1) Not may people are applying. [17:20] yeah, that's been the case for a couple years now :( [17:20] 2) Those that do apply aren't motivated to actually turn up to meetings [17:21] the second seems odd [17:22] yeah, I don't know why that would be [17:23] I have a theory ☻ [17:23] That there's less cache with being an ubuntu member now [17:23] it's not "special" [17:23] real life perhaps - but if it was me - I'd contact the board to at least say so [17:23] so why bother [17:23] i mean, in the past we always had no-shows. [17:23] and I don't have hard data for how many we had then vs now [17:24] I guess it's more obvious now, when you have only one person apply, and they don't turn up... [17:24] * pleia2 nods [17:24] popey: do you think more of a fan fair needs to be made or moe visability of what happens? [17:24] Not sure of the solution. [17:25] I think it's probably a symptom of a general decline in contributions [17:25] was just going to say similar [17:26] that's something that almost everyone without exception has said in these catch ups [17:26] hola [17:27] I did think at one point meeting should be less frequent and do them in larger bunches so people cna tune in and watch [17:27] so more people may become excited about the process [17:27] Riddell: ola once membership is over we'll move to Kubuntu cheers. [17:27] maybe quarterly [17:28] then you get the problem that "I applied 3 months ago..." [17:28] trouble with that is life/timezones get in the way and they miss one chance... [17:28] yeah [17:29] pleia2: nods [17:29] and its not much effort for us to turn up to irc once a month and say "Hello?" if nobody is tehre [17:29] could see about encouraging more community members to attend in general, I know I don't really attend anymore :\ [17:29] I may've asked this question before, but does it even need to be a meeting? [17:29] or we could do a monthly meeting adn once a quarter the CC joins the meeting to meet the new people and welcome them [17:29] YokoZar: transparency is nice [17:29] what about moving it to a hangout ? [17:30] or at least an option of a hangout [17:30] pleia2: I meant as opposed to something like asynchronous public emails. czajkowski's suggestion would make it more personal, which could be an interesting twist in the other direction [17:30] hangouts are not an option for younger folks or those on slower connections [17:30] and seems more intimidating to me :) [17:30] pleia2: I don;t think moving completely away from IRC would be good [17:30] 4 people judging me is bad enough, when they're looknig at me, eek! [17:31] trying to find a middle ground [17:31] I dont think its a problem with the meeting [17:31] also rough on non-native speakers who are better at typing (and we can google translate) [17:31] I think it's a problem with us having no new contributors [17:31] no "pipeline" as they say [17:31] yeah, it does seem like a broader issue [17:31] nods [17:32] newcomers who I see doing great work are going for membership, there just aren't many of them [17:32] popey: do you know if folks working on phones are going for membership? [17:32] Well, thats two areas. [17:32] that's where Canonical's team has moved focus to, but I don't see much of them [17:33] 1) people working on the phone platform [17:33] 2) people working on apps [17:33] I see them as two distinct areas [17:33] I'm thinking apps [17:33] yes, we encourage core apps contributors to go for membership [17:33] and some have already [17:33] (and got it) [17:33] that's good :) [17:33] e.g. people working on clock, email client etc have got their membership as a direct result of phone contributions [17:34] which isn't just "making apps" but providing good feedback / bugs to SDK & platform developers [17:34] we invited some along to sprints as well, which is quite a commitment for them [17:34] mmm [17:35] so no-one out in the wider community is going to know about that [17:35] about what? [17:35] popey: aye saw that in peoples blogs and on G+ [17:35] I tend to announce like a lunatic when a core app dev gets membership [17:35] popey: ones getting membership directly [17:35] and turn up and cheer [17:35] "directly?" [17:35] popey: oh ok - not seen it [17:35] they go through the same process as anyone else [17:35] yes - but do they go to meetings? [17:35] yes [17:35] same process [17:36] no different at all [17:36] aah ok - read it wrong then - sorry :) [17:36] np [17:36] but traditionally speaking a member was someonw working on the platform [17:36] not someone creating apps _for_ the platform [17:36] Maybe this decline in contribution isn't as big a problem as we think. Maybe people are shifting to upstream contribution, or we have fewer problems drawing active demand, or similar [17:36] Maybe it's good to be a functional boring piece of software. [17:36] but core apps are a bit "special" in that many ship by default on the device which is quite a big contribution [17:37] as far as I can see we have fewer people working on things like ubiquity or unity or other desktop bits [17:38] I believe many desktops / distros have this problem. [17:38] (maybe I'm wrong)? [17:38] I don't think we'll come to much of a conclusion here [17:39] indeed. [17:39] we should continue a discussion about whether contributions are a problem and how to improve things though, maybe on the new community discussion list [17:40] ubuntu-community-team@lists.ubuntu.com [17:40] happy to start that [17:40] thanks popey [17:40] popey: excellent! [17:40] shall we move on to Kubuntu Council? [17:41] #topic Kubuntu Council check-up === 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 | Community Council Meeting | Current topic: Kubuntu Council check-up [17:41] hola chicos [17:41] hey valorie, shadeslayer and Riddell! [17:41] hi [17:41] shadeslayer gone home but sgclark also here from kubuntu [17:41] ah ok, hi sgclark :) [17:42] greets [17:42] during these once-per-cycle checkins, we try to see how things are going with the team, and if you need us in any way [17:42] so, how are things? [17:43] some points I came up with.. [17:43] exciting times for us imo [17:43] We seem to be getting funds from the ubuntu community donations in acceptable time and I see the latest report has been published which is good [17:43] Our Kubuntu Plasma5 images are being produced from a PPA and being published on cdimages which is great [17:43] \o/ [17:43] the ubuntu website uses the deprecating term [17:44] "derivatives" for ubuntu flavours such as ourselves [17:44] would be good to have that fixed http://www.ubuntu.com/about/about-ubuntu/derivatives [17:44] is there an open bug for it on ubuntu-website in lp? I can chime in [17:44] nope, I can file one [17:44] (this is something I worked to fix in the latest Official Ubuntu Book, it was a lot of s/derivatives/flavors!) [17:44] this was discussed years ago [17:45] Riddell: thanks [17:45] and I thought the whole "derivitives" word was banished [17:45] yeah, I did too, totally feel your pain here [17:45] The technical problems that I feared from Canonical moving away from [17:45] community made software are coming true, KDE is recommending SDDM [17:45] having moved away from LightDM because of the need to agree to a [17:45] special licence to Canonical. I'm now having trouble making SDDM work [17:45] with our images and have nowhere in Ubuntu to turn to for help. [17:46] And you've already discussed the lack of new community members which I feel is also due to canonical moving away from community made software [17:46] I think it's a sane business decision but I do worry we'll come across a problem in future such as with wayland that we won't be able to fix [17:47] yeah [17:47] me too [17:48] this article is about a massive Kubuntu rollout https://insights.ubuntu.com/2014/07/07/ubuntu-and-open-source-help-the-city-of-munich-save-millions/ [17:48] but doesn't mention kubuntu once [17:48] :\ [17:48] canonical needs to credit the community that builds ubuntu [17:48] I didn't realize it was Kubuntu either [17:48] https://bugs.launchpad.net/ubuntu-website/+bug/1339508 "Misspelling in insights article" [17:48] Launchpad bug 1339508 in Ubuntu Website "Misspelling in insights article" [Undecided,In progress] [17:49] it's actually a really great process there, they come to akademy and we're have sprints in munich which effectively replace UDS [17:49] they didn't contact either munich or us when they wrote that article [17:49] that's unfortunate to hear [17:50] Reviewing the licence policy situation the Ubuntu liceensing page says all the right stuff http://www.ubuntu.com/about/about-ubuntu/licensing "Must allow these rights to be passed on along with the software. You should be able to have exactly the same rights to the software as we do." [17:50] which is correct. [17:50] The Canonical IP policy continues to be incorrect however http://www.canonical.com/intellectual-property-rights-policy "Any redistribution of modified versions...will need to recompile the source code to create your own binaries" [17:50] This is incorrect, as all software is free software once it is [17:50] distributed to someone that person can further distribute it all they [17:50] want under the relevant free software licence. To claim otherwise is [17:50] an insult to the copyright holders, the upstreams who write our [17:50] software, and goes against the Ubuntu policy above. It causes worry for our [17:50] supporters and is one reason why Blue Systems are looking at other [17:50] distributions. It needs to be changed and I strongly feel it is the [17:50] task of the community council to stand up to Canonical on this topic. [17:50] we don't seem to have dholbach or mhall119 here today, so I'll be sure to point them at this log to see what can be done to follow up with Canonical on this [17:51] (I'm not sure who to contact) [17:52] to your last point, this is really difficult, we've tried interacting with lawyers but it seems to be their lawyer language we can't get past [17:52] it worries me to see Canonical stop pushing freedom as a value [17:52] other CC members should chime in here, but we've spent months on this, mostly banging our heads against the wall [17:52] this could be basic as to why we're not drawing new people [17:52]