[00:14] <valorie> oh, meeting tomorrow
[00:14] <valorie> might be possible to attend!
[19:04] <pleia2> jono: diversity meeting?
[19:05] <jono> pleia2, I am currently stuck on a call, is there any chance you could run it for now
[19:05] <jono> apologies
[19:05] <jono> I should be done son
[19:05] <jono> soon
[19:05] <pleia2> busy at work at the moment, you can start when you return
[19:06] <jono> who is here for the meeting?
[19:06] <jledbetter> o/
[19:06] <jledbetter> No worries about starting later though. Finishing up something real quick.
[19:06] <jono> maybe we can reschedule it if there is a low turnout
[19:07] <jledbetter> Works for me.
[19:08] <AlanBell> o/
[19:09] <jono> thanks, folks, I will reschedule, apologies
[19:10] <hypatia> i'm around too
[19:10] <pleia2> we have a regular team meeting in 50 minutes
[20:01]  * pleia2 waves
[20:01] <pleia2> meeting time :)
[20:01] <pleia2> #startmeeting
[20:01] <Mootbot-UK> Meeting started at 20:01. The chair is pleia2.
[20:01] <Mootbot-UK> Commands Available: [TOPIC], [PROGRESS REPORT], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[20:01] <pleia2> who all is here for the meeting?
[20:01] <jledbetter> o/
[20:01] <Pendulum> o/
[20:01] <hypatia> woot meeting
[20:02] <pleia2> http://wiki.ubuntu-women.org/Meetings/Agenda
[20:02] <Mootbot-UK> LINK received:  http://wiki.ubuntu-women.org/Meetings/Agenda
[20:03] <pleia2> [TOPIC] Natty Blueprints progress: https://blueprints.launchpad.net/ubuntu-women.org/+spec/ubuntutheproject-community-n-ubuntu-women-project-goals
[20:03] <Mootbot-UK> New Topic:  Natty Blueprints progress: https://blueprints.launchpad.net/ubuntu-women.org/+spec/ubuntutheproject-community-n-ubuntu-women-project-goals
[20:04] <pleia2> so we've made some updates to this this week
[20:05] <pleia2> since Ada Lovelace day was pushed to October our plans around that for march shifted too
[20:05] <pleia2> and with the UDS work I haven't had time to pitch in with any other competition or bloggathon ideas
[20:06] <AlanBell> o/
[20:06] <pleia2> so we deferred these items to next cycle
[20:06] <jledbetter> pleia2, Didn't the blogging about UDS experience take that?
[20:06] <pleia2> jledbetter: yeah
[20:07] <pleia2> probably :)
[20:08] <pleia2> "work to get new wiki theme approved and into the wiki" is now marked as INPROGRESS, we submitted a ticket a couple weeks back and worked with canonical sysadmins to get the theme installed (more on this later in the meeting)
[20:08] <pleia2> [TOPIC] Natty Blueprints progress: https://blueprints.launchpad.net/ubuntu-women.org/+spec/ubuntutheproject-community-n-ubuntu-women-mentor-partnerships
[20:08] <Mootbot-UK> New Topic:  Natty Blueprints progress: https://blueprints.launchpad.net/ubuntu-women.org/+spec/ubuntutheproject-community-n-ubuntu-women-mentor-partnerships
[20:09] <pleia2> also progress here! I moved all the mentoring docs we reviewed at our last meeting to live
[20:09] <pleia2> http://wiki.ubuntu-women.org/Mentoring finally reflects reality :)
[20:09] <Mootbot-UK> LINK received:  http://wiki.ubuntu-women.org/Mentoring finally reflects reality :)
[20:10] <pleia2> I still have "identify BT Mentors that would make good candidates to assist with Ubuntu Women mentoring - cprofitt / lyz" to do, I spoke briefly with cprofitt about this the other day but still need to schedule a time with him
[20:11] <jledbetter> Great. I have my ideas but look forward to hearing what you two find too.
[20:11] <pleia2> cool, we can use the help once things get rolling :)
[20:11] <pleia2> I think that's pretty much for blueprints updates, unless others have any comments
[20:13] <pleia2> [TOPIC] New Items: Wiki testing!
[20:13] <Mootbot-UK> New Topic:  New Items: Wiki testing!
[20:13] <pleia2> elky put this together this week once we got the wiki theme installed: http://wiki.ubuntu-women.org/NewWikiTheme
[20:14] <pleia2> I'm not really taking a lead here, since this is still elky and AlanBell's domain - AlanBell any comments?
[20:14] <AlanBell> ok
[20:14] <AlanBell> I think I will add some notes to that page as well
[20:14] <pleia2> great
[20:14] <AlanBell> so the way the new theme works is that the sidebar and footer are actually regular wiki pages
[20:15] <AlanBell> so we can edit them \o/
[20:15] <pleia2> \o/
[20:15] <AlanBell> however this means we need to reference them on every page where we want them
[20:15] <AlanBell> with <<Include(Header)>> at the top
[20:15] <AlanBell> and can you guess what goes at the bottom?

[20:16] <pleia2> :)
[20:16] <AlanBell> so pages like http://wiki.ubuntu-women.org/Profiles are fully dressed with sidebar and footer
[20:16] <AlanBell> the home page is . . . that wasn't a good analogy was it?
[20:16] <AlanBell> the home page has the footer, but nothing at the top
[20:17] <pleia2> the home page will need some work as we're transforming it from our wiki to our main landing page
[20:17] <AlanBell> yup
[20:17] <pleia2> valorie helped with the wording which I put up here: http://wiki.ubuntu-women.org/Natty/Home
[20:18] <pleia2> so we'll need to take those words and integrate them with our current Home page and get formatting sorted
[20:18] <AlanBell> so pretty much all pages need the header and footer tags added, and checking that they look suitably awesome
[20:18] <AlanBell> which will mean that they have a header table that sucks a bit in the default theme
[20:19] <pleia2> AlanBell: thoughts on timing? Do we want to change the default before or after we make these changes?
[20:19] <AlanBell> however, as soon as it is looking pretty good we can make it default
[20:20] <AlanBell> not sure
[20:20] <AlanBell> the footer is OK in both really
[20:20] <pleia2> yeah
[20:21] <pleia2> I'm sort of leaning toward changing the default first
[20:21] <pleia2> since even w/o header and footer it doesn't look bad
[20:21] <AlanBell> true
[20:22] <AlanBell> it might be that on some pages we decide not to use the header (or use a different one)
[20:22]  * pleia2 nods
[20:23] <AlanBell> I think the theme is fundamentally working
[20:23] <pleia2> yeah, me too
[20:24] <AlanBell> you can still log on, get to things, edit pages, see the diffs etc
[20:24] <pleia2> ok, I'll touch base with elky and see what her thoughts are and maybe we just go from there?
[20:24] <AlanBell> I think we should probably ask more people to set their default theme
[20:25] <pleia2> ok
[20:25] <AlanBell> if there are no complaints by monday then ask for it to be turned on
[20:25] <AlanBell> by default
[20:26] <pleia2> alright, I'll round up some people in -women to help us test once you've made updates to http://wiki.ubuntu-women.org/NewWikiTheme
[20:27]  * pleia2 is on call this weekend, so should be around most of the weekend
[20:27] <AlanBell> ok
[20:27] <pleia2> thanks AlanBell :)
[20:27] <pleia2> [TOPIC] Other, Announcements, etc
[20:27] <Mootbot-UK> New Topic:  Other, Announcements, etc
[20:28] <pleia2> anyone else have anything before we wrap this meeting up?
[20:28] <pleia2> quick reminder about http://wiki.ubuntu-women.org/UDS
[20:28] <hypatia> nothing from me :/
[20:28] <hypatia> i applied!
[20:29] <pleia2> yay!
[20:29] <pleia2> me too :)
[20:29] <pleia2> sponsorship applications (http://uds.ubuntu.com/participate/sponsorship/) close on the 29th, so be sure to get yours in before that
[20:30] <pleia2> if you want someone to review your app text just ask (there are also email addresses on http://wiki.ubuntu-women.org/UDS who are volunteers to said they'd review apps)
[20:31] <hypatia> i'm kinda annoyed it didn't let you review the app after saving it
[20:31] <hypatia> :/
[20:31] <hypatia> mine was a bit short :)
[20:31] <pleia2> yeah, or send you a receipt with your text
[20:31] <pleia2> I forget what I wrote in the past
[20:33] <pleia2> ok, I think we're done then :)
[20:33] <pleia2> thanks everyone!
[20:33] <pleia2> #endmeeting
[20:33] <Mootbot-UK> Meeting finished at 20:33.
[20:46] <AlanBell> http://wiki.ubuntu-women.org/NewWikiTheme updated


 Did you find anything wwrong with the extensions, ive been trying to get someone to upload them to universe for 2/3 months. i would like to know why.
[04:37] <gnomefreak> anyway im gonna have a drink in hopes i sleep tonight.
[11:09] <armin76> asac: i was wrong...1.9 sigbuses...i think it was beta5 the one that worked fine
[11:20] <BUGabundo_work> hi
[11:20] <BUGabundo_work> http://blogs.adobe.com/penguin.swf/2008/11/now_supporting_16_exabytes.html
[11:20] <BUGabundo_work> mozzila has release an alpha version of flash 64 bits
[11:20] <BUGabundo_work> http://labs.adobe.com/technologies/flashplayer10/
[11:20] <BUGabundo_work> can we have it packaged on a PPA so we can test it on jaunty?
[11:29] <armin76> quick
[11:30] <BUGabundo_work> sorry armin76?
[11:30] <armin76> nothing *g*
[12:28]  * directhex melts
[12:28] <directhex> http://labs.adobe.com/technologies/flashplayer10/releasenotes_64bit.html
[12:29] <directhex> 64 motherloving bits!
[12:30] <BUGabundo_work> too late directhex
[12:30] <BUGabundo_work> already mention it
[12:30] <BUGabundo_work> even emailed the MLK
[12:30] <BUGabundo_work> *ML
[12:31] <directhex> poot
[12:35] <armin76> asac: hrm...and beta5 did as well...weird
[14:51] <asac> fta: did you trash i386 build for nspluginwrapper?
[14:51] <asac> 1.1.0 is available on i386 .... 1.2.0 not
[14:52] <asac> strange
[16:47] <fta2> asac, i didn't, we talked about that already, it's blocked somewhere i don't remember
[16:47] <asac> fta2: yeah. it was added to p-a-s :(
[16:48] <asac> fta2: http://cvs.debian.org/srcdep/Packages-arch-specific?rev=1.712&root=dak&view=markup
[16:48] <fta2> yes, pas
[16:48] <asac> i sent mail to the folks that can commit there
[16:48] <fta2> i asked for it to be fixed a while ago, no new since
[16:49] <asac> fta2: how did you ask?
[16:49] <fta2> irc, they directed me to a list of 3 emails
[16:50] <asac> fta2: yeah most likely the ones in the file
[16:50] <asac> i sent there too now
[16:51] <asac> infinity is in that list. but he is on holiday after the jaunty bootstrapping
[17:00] <mconnor> that sentence is so much funnier before you realize jaunty is 9.04
[17:03] <asac> mconnor: must be native speaker fun ;)
[17:04] <mconnor> asac: its just the idea of jaunty bootstrapping
[17:04] <asac> hehe
[17:04] <asac> is jaunty a rarely used word?
[17:13] <mconnor> asac: its rather uncommon these days
[17:20] <fta2> asac, kees sent me a debdiff to support the new native 64bit flash plugin
[17:20] <fta2> it's also in his ppa
[17:38] <asac> fta: yeah. cant do that until its final
[18:02] <asac> at least till beta
[18:24] <philsf> is asac's word on bug #279802 final? (i.e. nothing to be done in Ubuntu's FF3.0.3, it's a hotmail bug) will the change from 3.0.2 that causes this "regression" will not be reverted?
[19:33] <armin76> asac: hows is it possible that beta5 doesn't sigbuses when running with gdb?
[22:41] <asac> armin76: not sure ;)
[22:46] <fta> asac, not even in jaunty?
[22:51] <asac> fta: alpha flash?
[22:51] <asac> not sure. we need to discuss that
[22:51] <asac> there are a bunch of things
[23:44] <crimsun> fta: I also have a new source package for the 64-bit Flash
[23:45] <crimsun> fta: i.e., I've refactored debian/{config,postinst} to handle both 32- and 64-bit, so if installing on 32, you get the stable, and on 64 the alpha.  I've tested it for new installs and upgrades on hardy and intrepid for both i686 and amd64.
[23:46] <crimsun> asac: yes, it's one thing to consider whether to continue using nspluginwrapper for Flash
[23:49] <asac> crimsun: we want it
[23:49] <asac> have to discuss with nspluginwrapper upstream
[23:49] <asac> want it == not mandatory of course
[23:49] <asac> the idea why we brought this is to prevent crashes of ffox
[23:50] <asac> brough this to i386 i mean ;)
[23:50] <asac> crimsun: are you working on a new package?
[23:50] <asac> crimsun: we have to talk then ;)
[23:50] <asac> crimsun: will you be at UDS?
[23:54] <crimsun> asac: yes, Sunday through Wednesday
[23:55] <fta> crimsun, maybe talk with kees then. and i assume there's no point in me touching that too.
[23:57] <crimsun> fta: just figuring out a local bzr issue, thanks
[23:57] <crimsun> I'll need to add the nspluginwrapper bit back in, then


[04:40] <jam> morning all
[06:34] <MarkMaglana> o/
[08:32] <Chipaca> mo'in
[08:35] <Chipaca> jam: https://r.chipaca.com/land_shallow_topo.jpg (to be fair it might have bitrot at this point, without me noticing :) )
[08:36] <jam> Chipaca, it doesn't render very well here.
[08:37] <Chipaca> yeah, here either, and imagemagick now has limits in place that block it from touching the image even (without further tweaking)
[08:37] <Chipaca> which was precisely the point the image was trying to make, so i won i guess?
[08:40] <jam> Chipaca, "I Win" :)
[08:40] <Chipaca> quite
[08:41] <Chipaca> jam: an interesting thing came up in the call yesterday, with narinder
[08:41] <Chipaca> jam: he's going to file a bug about it, but i don't think he has yet
[08:42] <Chipaca> jam: but if you look at https://github.com/narindergupta/charm-k8s-kafka/blob/master/src/charm.py
[08:42] <Chipaca> jam: at expose_relation_data
[08:43] <Chipaca> jam: ISTM that having to do that getnameinfo thing is not particularly friendly
[08:46] <jam> Chipaca, indeed. I know that there has been discussions on the Juju side of how to present a hostname when you have one
[08:46] <jam> It certainly is never guaranteed that there *is* a hostname for a unit
[08:47] <jam> And if there is one (in say, MAAS) it may not be accessible because the DNS server is local
[08:47] <jam> I also know of bugs like https://bugs.launchpad.net/juju/+bug/1867168
[08:50] <Chipaca> jam: yeah, that sounds like exactly the issue
[08:54] <Chipaca> facubatista: this Friday we scheduled a meeting with people writing a postgres charm (i'm assuming for k8s). Neither jam nor I work this Friday :) should we reschedule, or are you happy to carry it alone?
[08:54] <jam> is he in yet?
[08:54] <jam> I would recommend rescheduling, as that is one that I'd like to be at
[09:00] <Chipaca> jam: I'll ask sohini to transfer these to me so we can move them around
[09:00] <jam> Chipaca, given that the bug is about the charm-k8s-mongodb it sounds very much like that bug
[09:21] <Chipaca> jam: btw, are https://github.com/narindergupta/charm-k8s-kafka/ and https://github.com/narindergupta/charm-k8s-zookeeper/ on the list? (i don't see them)
[09:22] <jam> Chipaca, they are now :)
[09:22] <Chipaca> jam: taw
[09:25] <jam> Chipaca, is there a notes doc about Kafka meeting?
[09:26] <Chipaca> jam: i need to transfer my notes onto a doc
[09:26] <Chipaca> jam: and, in future ones, start with a shared doc so we edit it as we go
[09:32] <jam> Chipaca, so I mentioned I was investigating creating symlinks earlier (before instantiating the charm)
[09:32] <jam> it is certainly 'doable' but it changes a bit
[09:33] <jam> namely, Events currently get their name from being assigned as an attribute to a class
[09:33] <jam> (install = EventSource(InstallEvent) is how we know the hook is 'install')
[09:33] <jam> I could change it so that the name of the associated hook is part of the base event, but it felt like a pretty significant departure
[09:33] <jam> so I wanted to check before I proceeded
[09:34] <Chipaca> it does feel a bit nastier
[09:35] <Chipaca> OTOH the know-thy-name magic might prove to be too magic at some point
[09:47] <jam> Chipaca, so in my head I was going to a registry of hook events so that we can easily iterate them. right now that "registry" is CharmEvents and iterating the attrs of it
[09:48] <jam> Chipaca, ObjectEvents.events() uses inspect.getmembers(type(self))
[09:48] <jam> which seems an odd way to do a registry to *me*
[09:49] <Chipaca> jam: oh so it _doesn't_ use set_name-like magic
[09:50] <Chipaca> my bad :)
[09:50] <jam> Chipaca, oh, it does
[09:50] <jam> it does both :0
[09:51] <jam> Chipaca, event_kind is used as the name, which is populated during __init__ because of calling getattr()
[09:51] <jam> AFAICT
[09:51] <jam> _create_event_link looks at 'bound_event' which has an 'event_kind' which is the name of the attribute
[09:52] <jam> (it could have just as easily used the 'key' portion of the key:bound_event map, but chose to just call values() and then iterate those)
[10:53] <facubatista> Muy buenos días a todos!
[10:54] <Chipaca> facubatista: buen día!
[10:55] <Chipaca> facubatista: could you review #258?
[10:56] <facubatista> Chipaca, sure
[10:58] <facubatista> Chipaca, regarding friday meeting, I can take it, but if jam wants to be there, we can reschedule it, yes
[10:59] <jam> morning facubatista
[10:59] <facubatista> hola jam
[11:01] <facubatista> meeting is in standup room?
[11:02] <jam> I added a room, but I'll happily move to standup since I added it late
[11:02] <facubatista> ah, no
[11:02] <facubatista> I'm in the other one
[11:02] <jam> Chipaca, coming? https://meet.google.com/pmg-hccz-tqd
[11:04] <facubatista> niemeyer, hello! any chance you leave a mup with us?
[11:05] <niemeyer> facubatista: Sorry, machine crashed yesterday and I forgot to bring it back up.. still haven't managed to put it in a stable place
[11:24] <facubatista> niemeyer, no worries! thanks!
[12:05] <facubatista> jam, Chipaca, ...?
[12:10] <facubatista> jam, we lost you
[12:10] <jam> brb
[12:40] <jam> https://paste.ubuntu.com/p/GFFXXrwKCW/
[13:51] <Chipaca> jam, facubatista, wrt ops.lib.use, in practice it'll be lib.use(), no? because 'from ops import <>' is the pattern we're encouraging
[13:51] <Chipaca> or maybe even use()
[13:52] <facubatista> I like lib.use()
[13:52] <Chipaca> from ops.lib import use as frameworkify
[13:52]  * Chipaca hides
[13:53] <jam> mysql = frameworkify('mysql')
[13:53] <jam> nice
[14:07] <Chipaca> jam: also, binding.ports[1000:1024].open()
[14:57] <facubatista> binding.ports[1000:1024].open(name='foo')
[14:58] <facubatista> binding.ports.close('foo')
[14:58] <facubatista> binding.ports[1000:1024].close()
[15:42] <Chipaca> facubatista: where are we planning on saving 'foo'?
[15:58] <facubatista> Chipaca, some StoredState?
[15:59] <Chipaca> facubatista: AIUI this means the ports depends on saving state in the controller
[16:00] <facubatista> Chipaca, we can not depend on that?
[16:01] <facubatista> Chipaca, we're saving the events already, right?
[16:01] <Chipaca> facubatista: not in the controller yet
[16:01] <Chipaca> it's saved in a local db
[16:15] <facubatista> Chipaca, why the ports storage would be different?
[16:16] <Chipaca> facubatista: i might be getting this wrong but i think the pod can be replaced at any time at which time we lose? but maybe not, the local db
[16:16] <Chipaca> ah no the db is not in the pod
[16:16] <Chipaca> that's the problem with actions
[16:17] <Chipaca> facubatista: ignore me, brain wongled
[16:17] <Chipaca> facubatista: but don't ignore me _too_ much :-p
[16:18]  * facubatista ignores odd chars in Chipaca sentences
[16:19] <Chipaca> facubatista: any char < 2019 is rubbish anyway
[16:19] <Chipaca> facubatista: 🧉🧉🧉
[16:20] <facubatista> ja
[16:31] <Chipaca> facubatista: plz don't forget to review the docs one
[16:41] <facubatista> extensions = [
[16:41] <facubatista>     'sphinx.ext.autodoc',
[16:41] <facubatista> ops.lib.use('autodoc')
[16:45] <facubatista> Chipaca, some questions inline
[16:46] <facubatista> also, I don't remember why we still don't have a proper requirements-dev.txt file with flake8, autopep8, etc
[16:47] <Chipaca> facubatista: I don't remember what happened to your PR with that
[16:48] <facubatista> Chipaca, it's a good moment to add it
[16:49] <Chipaca> facubatista: what happened to that PR?
[17:04] <facubatista> Chipaca, we end up not automatizing the virtualenv creation, so the dependencies ended up in the README
[17:05] <facubatista> (I landed that improvement over "you find out by trial and mistake what you need" as a middle ground)
[17:10] <Chipaca> facubatista: you _don't_ need sphinx for dev though, rtd will build them for us
[17:13] <facubatista> Chipaca, unless you want something to be fixed, for when you want to check how it looked before and after
[17:13] <facubatista> but yes, that will not happen always
[17:14] <facubatista> Chipaca, maybe a docs/requirements.txt ?
[17:14] <facubatista> docs/requirements-build.txt ?
[17:14]  * Chipaca adds a facubatista/requirements.txt
[17:14]  * facubatista is very requiremented
[17:14]  * Chipaca also adds a .snapcraft/you-might-be-lost.md