[01:24] <mwhudson> xnox: heh well i was leaning more towards purging but i guess fixing requires lower privileges
[01:29] <mwhudson> now, agda
[01:29] <mwhudson> needs an upstream update i think
[01:32] <mwhudson> hm present in git, why is it not uploaded
[01:55] <rbasak> waveform: o/ someone in #ubuntu-bugs is asking what package bug 1886581 should be moved to. I don't know the answer!
[01:55] <rbasak> https://ubuntu.com/download/raspberry-pi suggests that it should work
[09:17] <mwhudson> [289 of 369] Compiling Agda.TypeChecking.Errors ( src/full/Agda/TypeChecking/Errors.hs, dist-ghc/build/Agda/TypeChecking/Errors.o )
[09:17] <mwhudson> LLVM ERROR: out of memory
[09:17] <mwhudson> yay haskell
[10:24] <waveform> rbasak, should be linux-firmware-raspi2
[12:42] <GunnarHj> bluesabre: Hi Sean, can you please consider the suggestion here:
[12:42] <GunnarHj> https://discourse.ubuntu.com/t/default-im-config-configuration/17136
[12:42] <GunnarHj> and add your view. (didn't find you in discourse.u.c)
[14:06] <RikMills> The following packages have unmet dependencies:
[14:06] <RikMills>  python3-distutils : Depends: python3 (>= 3.8.3-1~) but 3.8.2-0ubuntu2 is to be installed
[14:06] <RikMills>                      Depends: python3-lib2to3 (>= 3.6.4) but it is not going to be installed
[14:06] <RikMills> E: Unable to correct problems, you have held broken packages.
[14:06] <RikMills> doko ^
[14:57] <bdmurray> Laney, jibel: Do you know if the "Reproducing tests in the cloud" instructions here are correct? https://wiki.ubuntu.com/ProposedMigration
[14:59] <Laney> bdmurray: I didn't write that, but it looks ok-ish
[14:59] <Laney> you need to find the right image of course
[15:01] <bdmurray> I'm getting a Traceback in the autopkgtest code
[15:04] <bdmurray> I also gather that the nova command is replaced by openstack so wonder if that is part of the issue.
[15:08] <Laney> let me have a go
[15:20] <jibel> bdmurray, these instructions may need a refresh
[15:23] <coreycb> RikMills: i'm hitting that as well
[15:24] <RikMills> coreycb: see #ubuntu-release
[15:24] <RikMills> hopefully a removal from proposed will help
[15:25] <coreycb> RikMills: thanks
[15:31] <Laney> bdmurray: the cloud is giving error 503 to me most of the time so I can't get a reliable test (:
[15:31] <Laney> :(*
[15:32] <Laney> SAD. NOT HAPPY.
[15:32] <bdmurray> Well yes that is sad.
[15:33] <Laney> autopkgtest --setup-commands setup-testbed -o temp/gzip gzip --apt-upgrade --shell-fail -- ssh -s nova -- --flavor m1.small --image ubuntu/ubuntu-focal-daily-s390x-server-20200706-disk1.img --keyname nightingale
[15:33] <Laney> this is the command I'm trying to use
[15:33] <bdmurray> https://pastebin.ubuntu.com/p/rXvmr3Pm4d/
[15:34] <Laney> is that after it does the dist-upgrade / reboot dance?
[15:34] <bdmurray> This was the only output I saw
[15:34] <bdmurray> No UUID given. Instance won't be deleted!
[15:34] <bdmurray> Unexpected error:
[15:34] <bdmurray> or lines 1 and 2 of my paste
[15:35] <bdmurray> which I guess I hadn't looked at closely ;-)
[15:36] <Laney> put some --debug in
[15:36] <bdmurray> in which part?
[15:36] <Laney> autopkgtest --debug <autopkgtest params> -- ssh --debug <more params>
[15:36] <bdmurray> all the parts then!
[15:37] <Laney> perhaps you're just getting what I am
[15:40] <bdmurray> I suspect this is going to take a while to timeout
[16:45] <bdmurray> Laney: some debug output https://pastebin.ubuntu.com/p/h2cn5nQ5YF/
[17:01] <Laney> bdmurray: I had to try like 5 times but it eventually worked; the other times the cloud failed to make machines
[17:01] <Laney> I suppose the output should be better in that case
[17:02] <Laney> I think that's probably what you're seeing
[17:05] <bdmurray> Laney: alright, thanks for looking I'll try a bit more
[17:05] <Laney> Maybe try it without autopkgtest and if you see flakiness it might be good to take that up with IS
[17:06] <Laney> something probably needs kicking
[17:06] <bdmurray> yeah, will do
[18:50] <amurray> ddstreet: hey I was going to prepare a backport of that possible fix that jdstrand identified for LP #1886115 - but I see you assigned it to yourself - so just wanted to sync on what the status was
[19:35] <amurray> ddstreet: I am happy to do it but if you are already looking at it then I don't want to repeat the work :)
[19:36] <ddstreet> amurray yeah, i've got a few more that i'm uploading for systemd today, so figured i'd toss it in
[19:36] <amurray> ddstreet: awesome - thanks :)
[21:08] <vorlon> xnox: why were you fixing haskell-yi-language ftbfs instead of letting it be removed? :)
[21:08] <vorlon> (it's removed now, regardless)
[21:08] <vorlon> mwhudson: ^^
[21:20] <mwhudson> vorlon: hurrah
[21:56] <mwhudson> does whoever is on +1 duty today want to cherry-pick https://github.com/gophercloud/gophercloud/commit/0183d6ad325843c27bd9497b9dca1f0259ffadb8
[21:56] <mwhudson> actually i should probably do that in debian
[22:15] <mwhudson> (i did it in debian)


[10:12] <ochosi> hi everyone
[10:13] <ochosi> do we have a testcase for the thunar crashes written down somewhere?
[10:13] <ochosi> (background: a new patch was posted to bugzilla yesterday, i haven't reviewed it but in a quick test i didn't manage to make thunar crash)
[10:14] <flocculant> ochosi: http://packages.qa.ubuntu.com/qatracker/milestones/361/builds/117794/testcases
[10:16] <ochosi> ok nice
[10:16] <ochosi> yeah, so that one doesn't pass either
[10:16] <flocculant> not using it currently though
[10:16] <ochosi> filenames don't change
[10:17] <flocculant> ochosi: yea - that is unfortunately the case - hence my 'do we really have to use thunar' pov :)
[10:19] <ochosi> thunar in yak seems to pass the testcase for me here though
[10:21] <flocculant> ochosi: mmm - well just keep trying the testcase - it will fail in the end :)
[10:21] <ochosi> "the end"? :)
[10:21] <flocculant> that's half the issue from my pov - it doesn't constantly crash :(
[10:21] <ochosi> i've been running it for a few minutes now
[10:22] <flocculant> if it 'always' crashed then fair play
[10:22] <flocculant> it crashed on me about 20 times yesterday
[10:23] <ochosi> well that's sorta the definition of a race condition...
[10:23] <flocculant> maybe so - didn't know that was the issue ;)
[10:24] <ochosi> btw i was revisiting the wording for notifyd settings dialog again yesterday
[10:24] <ochosi> how about "show or block notifications" for the applications tab?
[10:25] <ochosi> then i could reuse the "block" in the log tab and say "only log blocked applications" or something
[10:25] <flocculant> oh yuk :| ubiquity issue found that's not in ubuntu ...
[10:25] <ochosi> meh, ubiquity...
[10:25] <flocculant> ochosi: let me switch brain :)
[10:25] <ochosi> you have more than oneß
[10:25] <ochosi> ß
[10:25] <ochosi> ?
[10:25] <ochosi> (btw, the testcase for thunar is still running here, it hasn't crashed)
[10:25] <flocculant> yea - one that doesn't have ubuntu in it :D
[10:26] <flocculant> ochosi: :
[10:26] <flocculant> )
[10:26] <flocculant> ochosi: show or block sounds ok to me :)
[10:26] <ochosi> so the wording i've evaluated so far was: hide, block, mute, disable
[10:27] <ochosi> and for the opposites it would be: display, show, enable
[10:27] <flocculant> yea - I really dislike mute for it
[10:27] <ochosi> yup, i remember :)
[10:27] <flocculant> :)
[10:27] <ochosi> to be fair, in the future there may be sound support
[10:27] <ochosi> it's part of the spec at leastt
[10:28] <ochosi> (even though i personally hate sound for notifications...)
[10:28] <flocculant> I suppose from one pov mute works - eg it mutes the signal
[10:29] <flocculant> but berty up the road just running something is unlikely to think of that
[10:29]  * flocculant should reinstall your notifications
[10:34] <flocculant> oh dear - none of the a2 participants have their iso built turned on again :p
[10:34]  * flocculant can't double check this bug ...
[10:35] <flocculant> ochosi: is it still at logging_rebased?
[10:35] <ochosi> humm, thunar is still running and not crashing...
[10:35] <ochosi> yeah
[10:36] <ochosi> it still is that branch
[10:36] <ochosi> really wanna push it to msater though...
[10:36] <flocculant> ta - I think I lost all that when I managed to kill my install fiddling with light/dm/locking
[10:37] <ochosi> sur
[10:37] <ochosi> e
[10:37] <ochosi> i can also send you some screenhots though
[10:37] <flocculant> sure
[10:38] <ochosi> http://i.imgur.com/401GJaj.png
[10:38] <ochosi> http://i.imgur.com/PIYvHdC.png
[10:39] <flocculant> that's old :)
[10:39] <flocculant> I remember the supermarket delivering :D
[10:39] <ochosi> that's the state of the branch plus some changes that i've incorporated
[10:39] <flocculant> ok - I grabbed it now etc
[10:39] <ochosi> fwiw the screenshots are not the state of the branch
[10:39] <ochosi> i'm a little ahead with string changes
[10:40] <ochosi> e.g. mute vs. block
[10:40] <ochosi> i'm still very unsure about the subtitle of the window
[10:41] <flocculant> not sure what to say about 'show/hide' if it's going to get sound support in the future
[10:41] <flocculant> ochosi: tbh I'm not convinced it needs a subtitle
[10:41] <ochosi> maybe not, but then that looks odd too
[10:42] <ochosi> then you have it in the window frame and in the white title section
[10:42] <flocculant> does it - or is that because you 'expect' subtitle?
[10:43] <flocculant> ochosi: or maybe Customise notifications and logging ?
[10:43] <flocculant> as it stands 'appear' covers 66.6% of what it does now :)
[10:44] <ochosi> you mean "customize how notifications appear"?
[10:44] <ochosi> i think yeah, the subtitle is sorta my (visual) expectation
[10:44] <ochosi> )
[10:45] <flocculant> yup - appear does not work for the log tab
[10:45] <ochosi> "customize your notification settings" :p
[10:45]  * ochosi wanders off to cook
[10:45] <flocculant> that works
[12:16] <ochosi> flocculant: ok, pushed some of the string improvements
[12:22] <flocculant> ochosi: that makes more sense to me now - looks good :)
[12:23] <flocculant> one thing I wonder about now - on app tab because it says show or block - you could maybe lose the on/off words?
[12:24] <flocculant> or call them show/block instead?
[12:25] <flocculant> logic - words say show or block - buttons say on and off - is on showing or blocking ...
[12:25] <flocculant> but  I could just be being a bit picky there :)
[12:26]  * flocculant takes his turn wandering off to cook
[12:32] <ochosi> flocculant: yeah, that would indeed make sense. show/blocked maybe instead of just show/block?
[12:32] <ochosi> cause "block" sorta implies you wanna click if you wanna block...
[13:00] <flocculant> yup
[13:01] <flocculant> ochosi: oh - not sure if this is intentional or not - but if I click on an app in app tab it chnages the on/off state?
[13:02] <flocculant> almost like the whole name + button is the button
[13:09] <flocculant> https://sendvid.com/hkao24te just in case it isn't
[13:29] <ochosi> flocculant: yes, that is intentional. should help people click an app
[13:29] <ochosi> also means it's not so problematic to drop the switch
[13:29] <ochosi> (hopefully)
[13:30] <ochosi> before though i have to consider whether i change the internal wording in the code and xfconf because atm it's mute everywhere
[13:31] <flocculant> ochosi: ack - just wanted to make sure it was intentional :)
[13:32] <flocculant> by mute everywhere - do you mean everywhere in xfce that this type of thing is - it is called mute?
[13:32] <flocculant> if so then I can understand you ummming and aahing on it :)
[13:33] <flocculant> anyway - back later today
[13:38] <ochosi> no, just in xfce4-notifyd
[13:38] <ochosi> muting is older than logging
[13:38] <ochosi> initially i called it that
[13:38] <ochosi> aka in the current stable release
[13:39] <ochosi> anyway, i think i'll push the current state to master
[13:58] <bluesabre> morning all
[13:59] <flocculant> ochosi: ok - well I hope I helped some :)
[13:59] <flocculant> morning bluesabre
[13:59] <bluesabre> hey flocculant
[14:04] <ochosi> hey bluesabre
[14:04] <ochosi> how's it going?
[14:08] <flocculant> http://i.imgur.com/tHCyoEI.png
[14:08] <bluesabre> hey ochosi
[14:08] <bluesabre> going pretty well
[14:08] <flocculant> that's confusing - all from this installation - all opened slightly different ways
[14:09] <bluesabre> Releasing new sgt-launcher right now
[14:09] <flocculant> \o/
[14:10] <ochosi> bluesabre: i'm prepping a release for taskman and notifyd atm
[14:10] <bluesabre> ochosi, \o/
[14:11] <ochosi> odd that the xfcetitleddialog doesn't seem to be working for flocculant
[14:11] <flocculant> bluesabre: you likely to get to gtk3 settings today?
[14:11] <bluesabre> flocculant, that is the plan
[14:11] <ochosi> bluesabre: maybe we have to cherry-pick a commit of mine from libxfce4ui
[14:11] <ochosi> bbabl
[14:11] <bluesabre> ochosi, alright
[14:11] <flocculant> bluesabre: cool :)
[14:25] <bluesabre> noticed that the new sgt-puzzles package in zesty is using gtk3
[14:26] <bluesabre> as a result, the menu is always faded because the embedded window is always in a non-active state
[14:27] <flocculant> the 'game' menu I assume you mean
[14:27] <bluesabre> yeah
[14:27] <flocculant> I didn't take a lot of notice of that I'm afraid
[14:28] <flocculant> and what's xfcetitleddialog when it's at home?
[14:28] <bluesabre> lazy
[14:28] <flocculant> ha ha
[14:32] <bluesabre> https://launchpad.net/ubuntu/+source/sgt-launcher/0.2.2-0ubuntu1 uploaded, includes appstream data so it will show in gnome-software :)
[14:35] <flocculant> I might install it to see it showing up then :p
[14:35] <flocculant> not sgt ftr :D
[14:36] <bluesabre> :D
[15:55] <flocculant> bluesabre: it works as well :p
[15:56] <flocculant> knome: re the discussion sometime ago about oem
[15:56] <flocculant> I'd have the same discussion about whether we should test lvm/encryption
[15:57] <flocculant> akxwi-dave bluesabre ^^
[15:58] <akxwi-dave> very good point there flocculant
[15:59] <flocculant> I'd be inclined to think more people are likely to do that than oem
[16:02] <akxwi-dave> oh yes, you cannot nelieve the size of the fucisha bush she wanted me to dig out
[16:03] <flocculant> sounds like The Great Esacpe then :)
[16:44] <flocculant> \o/ os-prober lost all my other installs
[16:46] <flocculant> for one horrible minute I'd not just deleted the partition I wanted to ;)
[16:48] <akxwi-dave> ouch
[16:53] <flocculant> downgraded it - reran update-grub then updated it again :p
[16:55] <flocculant> I much prefer finding issues that aren't xubuntu
[16:58] <akxwi-dave> hehe more fun that way
[17:38] <bluesabre> flocculant, your non-xubuntu-specific bugs are the best ones, keep those coming
[17:39] <bluesabre> flocculant, and yes, we should probably test lvm/encryption, though those will almost never be xubuntu-specific bugs
[17:39] <bluesabre> (but they could be)
[17:40] <flocculant> yea agree on the specificity there
[17:40] <flocculant> bluesabre: I can easily add the tests to our stuff on tracker
[17:41] <bluesabre> Sounds reasonable to me
[17:41] <flocculant> ok
[17:51] <flocculant> bluesabre: added now
[18:36] <knome> flocculant, yeah, why not
[18:37] <knome> flocculant, though i believe there is less (think: none) xubuntu-specific components involved with that
[18:37] <flocculant> well the only why not for this is the same as the why not for oem :p
[18:37] <flocculant> yea - but probably useful to at least test it
[18:37] <knome> because some components in an OEM installation are xubuntu-specific (those in the config)
[18:37] <flocculant> currently set it for mandatory - but we can see how it goes and change that
[18:37] <knome> but yes, maybe they could all be once a cycle or so
[18:38] <knome> but i'm open for all kinds of experiments
[18:38] <flocculant> we'll keep that for -offtopic with the gardening I think
[18:38] <flocculant> :p
[18:40] <flocculant> knome: trouble with 'once a cycle or so' is when and then - bug might land post 'we checked that'
[18:41] <flocculant> we could change it to run-once - add OEM as run-once than 'forget about worrying' till milestones
[18:41] <flocculant> s/than/then
[18:51] <knome> once likely being later in the cycle
[18:51] <knome> bbl
[19:14] <flocculant> mmm
[19:35] <ochosi> evening all
[19:36] <flocculant> hi ochosi :)
[19:37] <ochosi> alrighty, i think i'll merge the logging_rebased branch to master of xfce4-notifyd now
[19:37] <ochosi> then translators can start their work
[19:37] <ochosi> which will actually be quite a bit this time around
[19:38] <ochosi> thanks for testing and input, flocculant
[19:38] <flocculant> ochosi: np :)
[19:52] <ochosi> wow, even found and fixed another small bug with the log
[20:13] <flocculant> :)
[21:34] <ochosi> bluesabre: can you take a peek at whether taskmanager from git master is packageable, i.e. just to see whether i forgot any depends or so in the build process
[23:51] <bluesabre> libxfce4ui 4.13.1 added to xfce4-gtk3 ppa, xfce4-settings uploaded to same and currently building


[01:31] <unikon> Any idea if Pidgin will be on  Gutsy Gibbon or will it only be al old version of GAIM?
[01:33] <Pumpernickel> It's already there.
[01:39] <unikon> well its not under pidgin?
[01:41] <Pumpernickel> http://packages.ubuntu.com/gutsy/net/pidgin
[01:44] <Hobbsee> unikon: sounds like your repos are borked.
[01:45] <unikon> well its up to date i beleive
[01:45] <unikon>  i havent had any past issues
[01:50] <Hobbsee> sarah@LongPointyStick:~$ madison pidgin
[01:50] <Hobbsee>     pidgin | 1:2.0.0+dfsg.1-3ubuntu1 | http://mirror.pacific.net.au gutsy/main Packages
[01:50] <Hobbsee>     pidgin | 1:2.0.0+dfsg.1-3ubuntu1 | http://archive.ubuntu.com gutsy/main Packages
[01:50] <Hobbsee>     pidgin | 1:2.0.0+dfsg.1-3ubuntu1 | http://mirror.pacific.net.au gutsy/main Sources
[01:50] <Hobbsee>     pidgin | 1:2.0.0+dfsg.1-3ubuntu1 | http://archive.ubuntu.com gutsy/main Sources
[01:50] <Hobbsee> it's there
[01:51] <unikon> would i still be able to dl and install even though im using Dapper Drake 6.06 Xubuntu
[01:51] <Hobbsee> well, if you're not running gutsy, then of course you're not goign to be able to find it in your repos
[01:52] <Hobbsee> and no you will not.
[01:52] <Hobbsee> the dependancies, etc, will have changed.
[01:53] <unikon> ahh
[01:53] <unikon> when will the release of Gutsy be?
[01:53] <Hobbsee> see the /topic
[01:57] <unikon> OCT 18th eh?
[01:57] <Hobbsee> sounds about right
[02:40] <DanaG> I rolled back to my Feisty backup.
[02:41] <DanaG> I'll try Gutsy once it's in a later-than-infant stage.
[02:41] <DanaG> But, I figured out something about my suspend issue:
[02:41] <DanaG> with the 72.14 BIOS, even XP freezes on resume, in almost exactly the same way.
[02:42] <Hobbsee> you got a new bios, and it's dying?
[02:42] <Hobbsee> where'd you get teh new bios from?
[02:42] <DanaG> I rolled back to an older BIOS; I'll try XP suspend later.
[02:42] <DanaG> I got it from the Gateway site.
[02:42] <DanaG> Here was the changelog -- the new was 72.14, the one I'm now on is 72.10.
[02:43] <DanaG> http://www.csc.calpoly.edu/~dgoyette/gateway_pa6_bios_7214.txt
[02:45] <Hobbsee> DanaG: then i'd suggest you'd do better calling gateway, rather than asking here
[02:46] <Hobbsee> (assuming you actually want anything done about it)
[04:36] <ajmorris_> anyone successfully got the partial upgrade tool working?
[09:27] <fuoco> i am using gutsy kernels on feisty. everything works well, but something broke in a specific kernel version - should i post a bug about it?
[09:30] <crimsun> not unless you can reproduce it in gutsy.
[09:31] <crimsun> we do not, by any stretch of any imagination, support running devel kernels on stable releases. :-)
[09:31] <crimsun> that said, it's likely you will be able to reproduce it currently, since udev hasn't changed.
[01:59] <Davo_Dinkum> Is Gutsy Gibbon aiming for FSF approval?
[02:01] <crdlb> what they said was they were going to create a gnu-approved gutsy variant like gnusense
[02:01] <crdlb> but regular gutsy won't be
[02:03] <Davo_Dinkum> Is it available for download yet?
[02:03] <crdlb> gutsy?
[02:03] <Davo_Dinkum> Yeah
[02:04] <crdlb> they're not even to the first alpha yet
[02:04] <Davo_Dinkum> Oh right
[02:04] <crdlb> which is apparently scheduled for june 7
[03:09] <okapi> hello to all
[03:09] <okapi> I just update from Kubuntu 6.10 and I am going crazy with 7.10...
[03:11] <okapi> First how you change and set the root password from the system setting? Seems to not keep or save the setting...Anyone can help?
[03:41] <feiy> somebody have readed the bug report:https://bugs.launchpad.net/bugs/115403
[03:42] <ubotu> Launchpad bug 115403 in gnome-terminal "a key focus bug of the gnome-terminal in gutsy" [Low,Unconfirmed]
[03:43] <feiy> yes,who can tell me how can i find the posit where
[03:43] <feiy> is bug generated!
[03:44] <feiy> the bug got same in xfce,so is a keyborder driver bug,but in ubuntu feisty ,everything is work good
[03:45] <feiy> ?
[04:36] <DShepherd> you know what would be nice.. if synaptic (or equivalent) would have screenshots of some of the applications.. or course where applicable.. that would be supremely useful...
[04:37] <gnomefreak> DShepherd: you mean little thumbnails when you choose or hover over a package name?
[04:37] <DShepherd> gnomefreak, right..something like that..
[04:38] <gnomefreak> and what about the people that complain its too slow now ;)
[04:38] <DShepherd> gnomefreak, dont tell me it is there already
[04:38] <DShepherd> gnomefreak, put it as an option... and turn if off by default..
[04:38] <gnomefreak> DShepherd: i thought of that during dapper
[04:38] <DShepherd> gnomefreak, some apps i just cant remember the exact name...
[04:39] <DShepherd> gnomefreak, i have an idea what it does....
[04:39] <gnomefreak> DShepherd: file a bug on it and give me bug # i will ping the devel about it
[04:39] <DShepherd> gnomefreak, super .. kool
[04:44] <gnomefreak> DShepherd: and remind me tuesday if you havent heard back from me. i will be out the better part of monday
[04:57] <DShepherd> gnomefreak, kool
[04:59] <DShepherd> gnomefreak, do you know of an app that highlights the cursor when the moving it after a long period of inactivity.. something like what Mac does...
[04:59] <DShepherd> ?
[04:59] <gnomefreak> no
[04:59] <DShepherd> gnomefreak, ok. thanks
[04:59] <gnomefreak> yw
[05:00] <joe4444> is Rhythmbox in Feisty newer than the one included with Dapper?
[05:01] <joe4444> there's a weird bug that stores invalid years in my iPod database with version 0.9.6
[05:01] <gnomefreak> !info rhythmbox dapper
[05:01] <ubotu> rhythmbox: music player and organizer for GNOME. In component main, is optional. Version <IP_ADDRESS>-0ubuntu9 (dapper), package size 1759 kB, installed size 6332 kB
[05:01] <gnomefreak> !info rhythmbox feisty
[05:01] <ubotu> rhythmbox: music player and organizer for GNOME. In component main, is optional. Version 0.10.0-0ubuntu2 (feisty), package size 3281 kB, installed size 10748 kB
[05:01] <gnomefreak> feistys is higher versio
[05:02] <gnomefreak> version*
[05:02] <joe4444> can i update it with dapper?
[05:02] <gnomefreak> joe4444: not supported
[05:03] <gnomefreak> joe4444: you would have to update your ubuntu version
[05:03] <joe4444> well how could i get the latest version available to dapper?
[05:03] <gnomefreak> or find a build that runs newest on dapper
[05:03] <gnomefreak> joe4444: you cant other than ^^
[05:03] <gnomefreak> dapper LTS is for security fixes not new packages
[05:04] <joe4444> my bad
[05:04] <joe4444> i have edgy
[05:04] <gnomefreak> than you are in same postition only with different version
[05:05] <gnomefreak> joe4444: if your on edyg why not just upgrade to feisty?
[05:05] <joe4444> so new packages are never available?
[05:05] <gnomefreak> joe4444: not unless they are backported
[05:05] <DShepherd> !info oneko
[05:05] <ubotu> oneko: a cat chases the cursor (now a mouse) around the screen. In component universe, is optional. Version 1.2.sakura.6-4 (gutsy), package size 34 kB, installed size 148 kB
[05:05] <joe4444> i'm going to get feisty soon, but right now i'm not ready to back up everything i need to keep
[05:06] <joe4444> so the version included in the livecd is the only version that will ever be available?
[05:06] <DShepherd> gnomefreak, ^^ that's the best i have found so far
[05:06] <gnomefreak> joe4444: rythmbox is a bit tricky to backport or to install a new version
[05:06] <DShepherd> gnomefreak, and i had to google to find out what it looks like before installing .. :-(
[05:06] <gnomefreak> lol
[05:06] <gnomefreak> DShepherd: we have a few users that use it all the time
[05:06] <joe4444> gnomefreak, maybe i'm not asking the right question...
[05:07] <DShepherd> k
[05:07] <gnomefreak> joe4444: to get the latest software in a ubuntu release that is not the latest you would have to find an unofficial package or ask for it to be backported
[05:07] <joe4444> if there is a new revision of 0.9.6 that fixes this bug, would that revision be available via apt?
[05:08] <gnomefreak> joe4444: not sure what bug you mean but the latest version should be what you have.
[05:08] <gnomefreak> !info rhythmbox edgy
[05:08] <ubotu> rhythmbox: music player and organizer for GNOME. In component main, is optional. Version 0.9.6-0ubuntu4 (edgy), package size 2910 kB, installed size 9420 kB
[05:08] <gnomefreak> ^^^ latest build
[05:08] <joe4444> for example, in CentOS i'd run "yum update httpd" if there is a new revision of apache with bug fixes
[05:09] <gnomefreak> does apt-cache policy rhythmbox   match that
[05:09] <joe4444> yeah
[05:09] <gnomefreak> joe4444: we use apt instead of yum. sudo apt-get upgrade will give you latest version that was built for your version of ubuntu
[05:10] <gnomefreak> joe4444: please take this to #ubuntu now since it has nothing to do with gutsy
[05:10] <joe4444> ok then i have a general question about the update manager...
[05:11] <joe4444> if a new revision of rhythmbox 0.9.6 were to be released, would the automatic update manager notify me?
[05:11] <joe4444> also, is it safe to upgrade to 7.04 using the update manager, or should i just run a clean install from a livecd?
[05:13] <DShepherd> joe4444, i did an upgrade.. and i had little issues (those issues we self inflicted) ...
[05:14] <DShepherd> joe4444, I guess a clean install is safer.... but backup is always a good thing to do in both cases... if possible
[05:16] <joe4444> thanks DShepherd
[05:17] <DShepherd> joe4444, your welcome
[05:28] <Pimp1984> Anyone ever used ndiswrapper?
[05:32] <Toma-> Pimp1984: long long ago, in ancient roman times
[05:32] <Toma-> Pimp1984: is it not working for you?
[05:35] <Pimp1984> I've followed the instructions for installing it, but when I type 'make install' I get an error message.
[05:36] <Pimp1984> 'cannot create directory /lib/modules/2.6.20-15-generic/misc: Permission denied'
[05:37] <Toma-> sounds like a feisty issue... throw it up in #ubuntu and see if anyone catches it
[05:38] <Toma-> btw, you need to put sudo infront of the command youre running
[05:50] <DShepherd> gnomefreak, i just use the water cursor beryl/compiz effect for now,..
[09:44] -ChanServ(ChanServ@services.)- You do not have channel operator access to [#ubuntu-boot]
[09:44] -ChanServ(ChanServ@services.)- [#ubuntu-server]  Ubuntu Server Discussions (development and support)
[09:45] -ChanServ(ChanServ@services.)- [#ubuntu-ops]  Welcome to #ubuntu-ops - Home of the operators for official K/X/Ed/Ubuntu channels. Questions, requests and complaints about Ubuntu related channels and their people can be filed here"
[09:45] -ChanServ(ChanServ@services.)- [#ubuntu+1]  Please read the topic. Especially if things are broken!
[10:36] <teethdood> anyone running gutsy yet?
[10:44] <borschty__> yes
[11:27] -ChanServ(ChanServ@services.)- You do not have channel operator access to [#ubuntu-boot]
[11:27] -ChanServ(ChanServ@services.)- [#ubuntu-server]  Ubuntu Server Discussions (development and support)
[11:27] -ChanServ(ChanServ@services.)- [#ubuntu-ops]  Welcome to #ubuntu-ops - Home of the operators for official K/X/Ed/Ubuntu channels. Questions, requests and complaints about Ubuntu related channels and their people can be filed here"
[11:27] -ChanServ(ChanServ@services.)- [#ubuntu+1]  Please read the topic. Especially if things are broken!
[12:20] <Sivik> how do i assign a static ip to a interface via CLI
[12:20] <Hobbsee> Sivik: in /etc/network/interfaces, i believe - man interfaces should tell you more
[12:22] <Sivik> Hobbsee: i don't want to do it permently, just for a little while
[12:22] <Hobbsee> ahh
[12:23] <Hobbsee> i would assume you use ifconfig, iwconfig, etc
[12:23] <Sivik> and i know there is a way to do it but i can't remember how to do it
[12:23] <Sivik> ifconfig
[12:23] <Hobbsee> (which have associated manpages)


[04:18] <mamarley> bambinone: https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack seems to work for me
[05:20] <bambinone> mamarley: hrrm I'm still getting "fatal: unable to write request to remote: Connection timed out"
[05:22] <bambinone> ahhh I was using git://, changing it to https:// did the trick. thank you!
[08:25] <bittin> https://nikkasystems.com/2023/11/17/podd-224-doxing-me-doxing-you/ watching todays Bli Säker Podden before i need to head to work and update Linux Mint and reinstall Windows 10


[15:01] <rbalint> o/
[15:01] <cyphermox> heya
[15:02] <philroche> \o
[15:07] <cyphermox> #startmeeting Weekly Ubuntu Foundations team
[15:07] <meetingology> Meeting started Thu May  3 15:07:00 2018 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:07] <meetingology> Available commands: action commands idea info link nick
[15:07] <cyphermox> #topic AOB
[15:07] <xnox> we released... hopefully... everywhere...
[15:07] <cyphermox> any business so far post-release while we all deal with new merges, SRUs, etc?
[15:07] <cyphermox> going once
[15:08] <cyphermox> going twice
[15:08] <cyphermox> gone!
[15:08] <cyphermox> thanks all!
[15:08] <cyphermox> #endmeeting
[15:08] <meetingology> Meeting ended Thu May  3 15:08:45 2018 UTC.
[15:08] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-05-03-15.07.moin.txt
[16:56] <elopio> wxl: Wimpress: jose: ahoneybun: marcoceppi: meeting in 5 minutes.
[17:00] <elopio> wxl: Wimpress: jose: ahoneybun: marcoceppi: ready?
[17:00] <wxl> more or less, @el
[17:00] <wxl> um
[17:00] <wxl> elopio
[17:00] <elopio> did elacheche say something about not being around?
[17:01] <elopio> hey elacheche :)
[17:01] <elacheche> Hey elopio
[17:01] <elopio> wxl: more or less means you are going to participate or not?
[17:02] <wxl> elopio: means i'm here and as ready as i can be given that i'm at work :)
[17:02] <flocculant> :D
[17:02] <elopio> on the last meeting I got very angry because we have asked many times for people to choose a better time so they can be in the meeting, but nobody has proposed anything.
[17:03] <elopio> elacheche: are you going to participate?
[17:03] <elacheche> Sure
[17:03] <elopio> do you know if any of the others notified about their absence?
[17:03] <elacheche> Nope
[17:04] <wxl> i've heard nothing
[17:04] <elopio> these meetings are becoming a waste of time for me. I could use this hour to do stuff and report async on the hub...
[17:04] <elopio> anyway, let's start.
[17:05] <elopio> #startmeeting Ubuntu Community Council 20180503
[17:05] <meetingology> Meeting started Thu May  3 17:05:05 2018 UTC.  The chair is elopio. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:05] <meetingology> Available commands: action commands idea info link nick
[17:05] <elopio> We start with elopio, elacheche and wxl present. Wimpress, jose, ahoneybun and marcoceppi absent without notification.
[17:05] <wxl> ahoneybun stepped down, did he not?
[17:06] <elacheche> wxl: When? o_O
[17:06] <elopio> I don't know, he mentioned something about an email that I didn't receive. I guess I'm not on the mailing list anymore, but marcoceppi doesn't reply.
[17:06] <wxl> it was the community team mailing list
[17:06] <wxl> let me dig it up
[17:06] <elopio> wxl: what info do you have? Is that official?
[17:06] <elacheche> I didn't get anything on the CC ML
[17:07] <wxl> https://lists.ubuntu.com/archives/ubuntu-community-team/2018-April/001572.html
[17:07] <wxl> i can only imagine he meant to include the cc or meant to email the cc list and missed
[17:08] <wxl> i recently replied to an email to the list regarding reinstating a member (genii, who wasn't paying attention to members) and replied back but failed to include him, so these things do happen
[17:08] <elopio> alright. Thanks ahoneybun for the notice. I hope to still see you around, and maybe join the next CC if you have the time.
[17:09] <elopio> so, that's an important topic. We need a replacement for ahoneybun.
[17:09] <wxl> i was just adding a note
[17:09] <wxl> i can't add it to the agenda but i replied to it at least
[17:09] <flocculant> surely you replace ahoneybun when the term is up? not mid-term
[17:10] <elopio> Also, we agreed that after not attending three meetings without notification, we would ask the person to step down.
[17:10] <elopio> since then, marcoceppi has missed the three meetings we had.
[17:10] <wxl> well, he's gone, flocculant. like didn't even finish his term.
[17:10] <flocculant> mmm - well nothing to do with me I guess
[17:10] <elopio> flocculant: why wait? We need people to help us now.
[17:11] <wxl> elopio: i don't mean to make excuses, but can we be sure he got those requirements?
[17:11] <wxl> i mean i know we put the info out there......
[17:11] <elopio> wxl: isn't that even worse?
[17:11] <wxl> quite possibly :/
[17:12] <elopio> anyway, the agreement was not to chase people as I was starting to do. And instead, expect them to work as they promised with their candidature
[17:13] <wxl> and i still think those are reasonable expectations
[17:13] <elopio> wxl: elacheche: should I send an email to marcoceppi asking him to step down?
[17:13] <flocculant> not sure this should be happening now in here
[17:14] <flocculant> are you going to run the meeting ?
[17:14] <elopio> for the record, I'm also happy if he steps up instead, and starts participating. I'm not sure if that fits into our previous agreement.
[17:14] <wxl> it's all part of it
[17:14] <elopio> flocculant: that's what the meeting is for.
[17:15] <wxl> i think that's the appropriate solution, unfortunately, elopio
[17:15]  * elacheche have no comments for the moement
[17:15] <flocculant> right well - I wanted to bring something up - but as you're all just bickering I'll do it another time when you're less likely to bicker amongst yourselves
[17:15] <elopio> ok.
[17:15] <wxl> i'm pretty clear no one here is bickering but feel free to speak up if you urgently need to get something out, flocculant
[17:16] <Wimpress> o/
[17:16] <Wimpress> Sorry I'm late, had another meeting overlap
[17:16] <elopio> hello Wimpress
[17:16] <elopio> elacheche abstains, wxl and I think we should ask marcoceppi to step down. Wimpress, your opinion?
[17:21] <elopio> Wimpress?
[17:21] <Wimpress> Caught up on the Backlog.
[17:21] <Wimpress> Shall we progress through the posted agenda.
[17:21] <wxl> do we not want to deal with this issue we're currently dealing with?
[17:22] <elopio> I think this is the only topic that requires immediate action.
[17:22] <Wimpress> It's not on the agenda. I think we should discuss it in AoB.
[17:22] <elopio> but we can leave it to the end if you prefer.
[17:22] <Wimpress> Let's belt through the agenda and circle back to this.
[17:23] <elopio> alright, let's go in order.
[17:23] <elopio> #topic Progress from last meeting
[17:23] <elopio> #subtopic Bold bug triaging - @Wimpress
[17:24] <Wimpress> No progress. Sorry.
[17:24] <elopio> Wimpress: did jose forwarded you the message?
[17:24] <elopio> what's missing is to poke wgrant?
[17:25] <Wimpress> No. But I know who to contact.
[17:25] <Wimpress> Yes.
[17:25] <Wimpress> Just didn't get round to it.
[17:25] <Wimpress> Release and UbuCon kept my attention elsewhere.
[17:26] <elopio> ok. It would be good to ask now if it's still a problem
[17:26] <elopio> we have been so slow that maybe it was resoled by itself.
[17:26] <elopio> it would be good to talk to William anyway, to know what to do next time.
[17:27] <elopio> #action @elopio to ask an updated status of the situation from the involved people
[17:27] <meetingology> ACTION: @elopio to ask an updated status of the situation from the involved people
[17:27] <elopio> #action @Wimpress to talk to wgrant
[17:27] <meetingology> ACTION: @Wimpress to talk to wgrant
[17:27] <elopio> #topic Triage CoC bug - all CC
[17:27] <Wimpress> No progress from me.
[17:28] <wxl> sadly i've done nothing with this but will do so this week
[17:28] <elopio> I've been doing this. I feel bad about closing the bugs I disagree with, but I guess I'll have to do it. I'll try to be nice.
[17:28] <ahoneybun> I'm here sorry was stuck on something.
[17:28] <wxl> you have been? why didn't i get the notifications????
[17:28] <elopio> so, there are a few important bugs. One suggests the addition of an antiharrassment sentence, and it has a merge proposal. I think this will be great, so I'll push it forward. Feel free to comment on the bug if you have opinions.
[17:29] <wxl> and shouldn't we discuss before closing?
[17:29] <elopio> There's another about the process being too hard, with a suggestion for a screencast. This would be awesome, but I don't have that skill. So maybe we can ask around on the hub for volunteers.
[17:30] <elopio> wxl: what if I comment with my intention to close, leaving the bug as incomplete so it closes itself if nobody comments?
[17:30] <wxl> yes but i'm confused as to why i got no notifications
[17:30] <wxl> the cc should be included on every bug
[17:31] <elopio> This is for things like phrasing, with suggestions that in my opinion are not improving the text.
[17:31] <elopio> or suggestions to add sentences that I don't think should be part of the CoC
[17:31] <elopio> wxl: you didn't get any notification because I just took notes on my notebook, haven't touched the state of the bugs yet.
[17:32] <wxl> OH
[17:32] <wxl> :)
[17:32] <wxl> then yes. we did say to have discussion on the bug, so let's do that.
[17:33] <elopio> There's one weird point, that the text on the page is slightly different than the one on the repo. Minor things, like periods at the end. I guess that means that the page is generated manually, so maybe we should work on automation for that.
[17:33] <wxl> a "here's my opinion and i move to close" would suffice
[17:33] <wxl> yes
[17:34] <elopio> but yes, that's the gist. Nothing super urgent, the most important one is the one about it being too hard. So we need to figure out ways to improve it. Mentoring people to get a GPG key sounds like fun to me, and good for the world :)
[17:34] <elopio> wxl: I'll start moving my comments to the bugs. I will not close them, mark them as incomplete waiting for other opinions.
[17:34] <wxl> i've got some ideas with that, so when we get to that bug we'll deal with it
[17:34] <elopio> so, #action @elopio to comment on the CoC bugs and update the status.
[17:35] <elopio> #topic Clearly define governance seats, terms, and quorum - @elacheche
[17:35] <elacheche> I had a chat with popey an hour ago about that, because he's one of the oldest contributors in boards.. The 4 members quorum is just like a logical formula to get a majority of 7 people board to be present.. Unfortunately, I coudln't get in touch with other contributors to share their thoughts about that..
[17:36] <elopio> also take into account that we have been struggling to get 4 people on this meeting.
[17:36] <elacheche> Coudln't find anything usefull in the wiki.. And multiples MLs archives are private, I can't search in there :/
[17:36] <wxl> that suggests a majority is the definition of quorum
[17:36] <wxl> which i think makes logical sense
[17:36] <elopio> I'm not sure if that means we should define quorum based on the people present on the meeting, or we must skip the meetings if there's not enough people.
[17:37] <wxl> robert's rules of order defines it as something like the largest number that can be expected to show up
[17:37] <wxl> which is to say it can be almost anything
[17:38] <elopio> elacheche: I think there's no need to dig too much. I'm happy for you to decide a new rule that makes the boards happy, and document it so the future boards have it clear.
[17:38] <elopio> what about opening it up for discussion on the hub, and make a decission on the meeting next month?
[17:39] <wxl> yeah we need something set in stone
[17:39] <elacheche> Actually I didn't define anything, I just shared the information that I thought it was documented years ago based on what I read while being present in meetings when I was just a non-ubuntu member
[17:40] <elacheche> +1 elopio
[17:40] <wxl> we should probably make a poll defining some options and just vote on it
[17:40] <wxl> http://www.dummies.com/careers/business-skills/roberts-rules-for-defining-a-quorum/
[17:40] <elopio> #action @elacheche to open a post on the hub to discuss the definition of quorum
[17:40] <meetingology> ACTION: @elacheche to open a post on the hub to discuss the definition of quorum
[17:41] <elopio> wait, wxl, so no post? Just decide ourselves?
[17:41] <wxl> no, make a poll on the hub
[17:41] <wxl> except that the poll is binding when the date has ended, not when we reach quorum XD
[17:42] <wxl> https://en.wikipedia.org/wiki/Quorum#Number_constituting_a_quorum
[17:42] <wxl> seems that majority of members is the standard
[17:42] <elopio> wxl: I think this shouldn't be an open poll. It should be a decission of the community council.
[17:43] <wxl> oh ok
[17:43] <wxl> yeah i guess that makes sense
[17:43] <wxl> i still think we should go time based
[17:43] <elacheche> If it's a private we will need to do that on the ML, otherwise the Hub
[17:44] <wxl> no reason not to do it in public, but i'm not sure you can do polls restricted to a particular membership
[17:44] <elacheche> yep
[17:44] <elopio> I was suggesting open discussion, to gather ideas or opinions. And make the decission based on that. We can vote here, or on the mailing list, or leave a comment on the hub, no preference there.
[17:44] <elacheche> We can get the boards involved in the poll too
[17:45] <wxl> +1 elacheche i think that's crucial
[17:45] <wxl> i brought this up after my pain in dealing with it in other boards
[17:45] <elacheche> We can do that on a private plateform, like the one we use to vote on members for CC, and share the link on boards MLs
[17:46] <wxl> works for me
[17:46] <elacheche> And as we are CC, I think we can send mails to any ML without being members of it :D
[17:46] <elopio> ok. So post or no post? And who takes care of preparing the poll and inviting the boards?
[17:47] <wxl> well we can but it's still up to them to accept it
[17:47] <wxl> post it, then email the boards and ask them for input
[17:48] <ahoneybun> I feel like the idea of a quorum should be public as it will effect other boards as well.
[17:49] <wxl> i think the ultimate decision should be a cc one
[17:49] <elopio> but we need an owner for this topic. Otherwise we will talk a lot here with no actions.
[17:49] <elopio> I can do it on june. Not this month. So any takers, or we leave it for the future?
[17:49] <wxl> well if elacheche isn't into it, i'll take it on
[17:51] <elacheche> I can do that, sorry was on an other screen x)
[17:51] <elacheche> We can do that together wxl ?
[17:51] <wxl> elacheche: you do the post and i'll contact boards?
[17:51] <elacheche> OK :)
[17:52] <elopio> ok, so the previous action stands. That's great, because I have no idea how to tell the bot to delete :)
[17:52] <elopio> #action wxl to contact the boards and tell them about the quorum discussion
[17:52] <meetingology> ACTION: wxl to contact the boards and tell them about the quorum discussion
[17:52] <wxl> afk for 5m
[17:53] <elopio> and I would say we leave the tasks about terms and governance seats for when we have finished the ones about quorum.
[17:53] <elopio> any other comments?
[17:53] <elacheche> Nope
[17:54] <elopio> #topic Send the emails to liri and enlightenment contacts - @Wimpress
[17:54] <Wimpress> Emails sent to the contacts I indetified a few days ago.
[17:54] <Wimpress> No replies as yet.
[17:55] <wxl> back
[17:55] <wxl> hey i met the debian maintainer for enlightenment at lfnw
[17:55] <wxl> he was super cool! i'd be happy to reach out to him if that's helpful
[17:55] <elopio> alright, so no more actions other than waiting to see if they are interested.
[17:55] <Wimpress> wxl: Please do
[17:55] <wxl> he actually became the maintainer out of necessity being a user
[17:56] <wxl> make an action for me please elopio
[17:56] <Wimpress> elopio: Looks like wxl is taking an action to contact Debian maintainer of E
[17:56] <Wimpress> :-)
[17:56] <elopio> #action contact the enlightenment debian maintainer - @wxl
[17:56] <meetingology> ACTION: contact the enlightenment debian maintainer - @wxl
[17:56] <elopio> awesome to see progress :) This topic is exciting, thanks.
[17:57] <elopio> #topic Make a post on the hub about the guerrilla marketing campaign. Share the draft. @Wimpress
[17:57] <Wimpress> Sorry, no progress,
[17:58] <elopio> Wimpress: I told you on the last meeting that now I could help here. Do you want me to start the topic and try to contact people?
[17:59] <elopio> the only problem is that I could turn you idea in something different. But if you send me short bullet points of what you wanted, I can try to keep close to your ideas.
[18:00] <Wimpress> elopio: Would be helpful, yes please.
[18:01] <Wimpress> I think you get idea. Please make a start.
[18:01] <elopio> #action @elopio to start a topic on the hub about guerrilla marketing
[18:01] <meetingology> ACTION: @elopio to start a topic on the hub about guerrilla marketing
[18:01] <elopio> damn, I mixed topics and subtopics. Sorry for the mess.
[18:01] <elopio> #subtopic Diversity and inclusion call - @elopio
[18:02] <elopio> there was a very nice panel yesterday, with people from different communities trying to figure out code of conduct stuff
[18:02] <wxl> oh where was this?
[18:02] <elopio> here is the recording: https://www.youtube.com/watch?v=fF1aWYLRwtg
[18:03] <elopio> this is the project: https://wiki.mozilla.org/Diversity_and_Inclusion_for_Communities_and_Contributors
[18:03] <elopio> there's a google group, and the next meeting is on june 6th.
[18:03] <elopio> we have a lot to learn here, and a lot to share too. So jump in if it sounds fun to you.
[18:04] <wxl> oh nice
[18:05] <elopio> #topic Update on community donations report.
[18:05] <Wimpress> No progress. popey and I need to allocate time to work on this.
[18:06] <wxl> may i make a suggestion that we have a regular schedule of these updates?
[18:06] <wxl> s/update/report/
[18:06] <elopio> Wimpress: the last ETA was this week. Can you give us a new ETA?
[18:06] <elopio> wxl: as I understood, the idea was to catch up on the missing reports to go back to the regular schedule.
[18:07] <wxl> i didn't know there was a regular schedule
[18:07] <Wimpress> I'll discuss with popey and try to get this scheduled this month.
[18:07] <elopio> Wimpress: works for me. Also, please let us know if we can help. This month I have a little more time than the previous.
[18:07] <Wimpress> OK, having never done it before we don't know what help we need yet.
[18:09] <elopio> :) sounds like the recurrent topic. It seems to me that at the very least, the next CC will have it easier after our term.
[18:09] <elopio> well, I hope.
[18:09] <elopio> #action Wimpress and popey to catch up on the community donations reports
[18:09] <meetingology> ACTION: Wimpress and popey to catch up on the community donations reports
[18:10] <elopio> #topic Replacement for @aaronhoneycutt, status of @marcoceppi.
[18:10] <elopio> we are back to where we started.
[18:11] <Wimpress> ahoneybun: You commented here earlier. Can you confirm you intend to step down?
[18:11] <Wimpress> If so, CoC describes how to stand down from a position responsibly.
[18:12] <Wimpress> What notice are you giving us?
[18:13] <elopio> Wimpress: on the
[18:13] <elopio> Wimpress: on the
[18:13] <elopio> Wimpress: on the
[18:14] <elopio> oh, sorry. We call this "la chiripiorca" here.
[18:15] <elopio> Wimpress: on the email, he says: "I will still help out where I can until a new member can fill
[18:15] <elopio> my spot.
[18:15] <elopio> "
[18:15] <elopio> https://lists.ubuntu.com/archives/ubuntu-community-team/2018-April/001572.html
[18:15] <Wimpress> elopio: Regarding marcoceppi, has the decision we took about non-showing council members been communicated to all CC members?
[18:15] <elopio> that sounds reponsible stand down to me.
[18:15] <wxl> +1 elopio
[18:15] <Wimpress> Yep, agreed.
[18:16] <wxl> Wimpress: i don't think we've chased down every member and told them, but it's all been there in the discussions of the meetings
[18:16] <elopio> Wimpress: it was notified on the mailing list and on the hub. I don't know if he received it, but I was telling wxl that if not, that sounds even worse to me.
[18:16] <Wimpress> I think we should bring this decision to his attention.
[18:16] <Wimpress> Directly.
[18:17] <Wimpress> And ask if he still wishes to participate on the CC.
[18:17] <elopio> I don't think we can just remove anybody.
[18:17] <Wimpress> Indeed.
[18:17] <wxl> i don't think there was a subject on the list specifically about that
[18:17] <elacheche> I agree
[18:17] <wxl> and perhaps a change like that warrants a more clear communication
[18:18] <Wimpress> elopio: Can you circulate the details of the decision that was taken to CC members please?
[18:18] <wxl> this is the best we had https://lists.ubuntu.com/mailman/private/community-council/2018-March/018244.html
[18:18] <wxl> but the subject doesn't suggest it
[18:18] <Wimpress> Let's have a clear communication.
[18:19] <wxl> i think a good first step would be creating a list message with something like "important change in CC term requirements"
[18:19] <elopio> if he wants to stay, I am ok giving him three more opportunities.
[18:19] <wxl> i agree
[18:19] <elopio> you mention that it was not properly communicated, so I'm also ok starting the count from this meeting.
[18:20] <wxl> let's reach out and make sure that all members of the cc know
[18:20] <ahoneybun> Wimpress, I can confirm.
[18:21] <wxl> i'm sure jose was there for the discussion but maybe he didn't see the final decision?
[18:21] <Wimpress> ahoneybun: ty
[18:21] <wxl> so let's do an email to the list and cc marco and jose directly
[18:21] <elopio> wxl: I don't think that I'm the right person to notify about this calmly and clearly. I'm very disappointed at marcoceppi and jose just not showing up, or really just not doing anything.
[18:21] <elopio> wxl: do you want to take this action?
[18:21] <wxl> elopio: sure, i can do it
[18:22] <Wimpress> I think the email should be sent to all CC members.
[18:22] <Wimpress> Not the ML.
[18:22] <Wimpress> Everyone should be `to:`
[18:22] <elopio> #decission because elopio didn't notify clearly about the requirement to attend the meetings, we will reset the counter.
[18:22] <Wimpress> Let's not finger anyone when this is sent.
[18:22] <wxl> well tbh there are only two people we're not sure about knowing about this
[18:22] <wxl> but i can send it to all of them. i'll do both :)
[18:23] <elopio> #action wxl will notify all the CC members about this
[18:23] <meetingology> ACTION: wxl will notify all the CC members about this
[18:23] <Wimpress> wxl: Thanks.
[18:25] <elopio> sorry, I lost the agenda.
[18:25] <elopio> #topic Rejoining process for membership.
[18:25] <wxl> i just wanted us to get some eyes on this
[18:25] <wxl> tsimonq2 just proposed this
[18:25] <elopio> I like it.
[18:26] <wxl> tl;dr there have occassionally been members expired for more than 1 month who have asked for reinstatement and it was kind of unclear whether or not that's reasonable
[18:26]  * elacheche will share comments about that via the ML as a UMB member :)
[18:26] <wxl> his process asks them to essentially apply for it and then the board checks back on them to make sure all is well
[18:26] <wxl> i like it :)
[18:27] <elopio> this is a decission that falls on the membership board, right?
[18:27] <elopio> I'm wondering what should be our involvement here.
[18:27] <wxl> i think ultimately, yes, but they did include the cc for input
[18:28] <wxl> certainly if you have concerns about it, i'd pipe up
[18:29] <elopio> no concerns, just +1 from me.
[18:29] <wxl> ditto here
[18:30] <wxl> so maybe when you reply elacheche you can say the cc looked it over and the general consensus is positive :)
[18:30] <elopio> well, elacheche is reserving his comment.
[18:30] <elacheche> wxl OK, I'll use my two "hats" x)
[18:30] <elopio> :) nice.
[18:30] <wxl> :)
[18:31] <elopio> I realized now that I moved to the next topic too quickly.
[18:31] <elopio> we didn't discuss about the replacement for ahoneybun.
[18:31] <elopio> I would suggest to first wait to see if we need more replacements.
[18:32] <wxl> ok
[18:32] <wxl> i'll also try to approach marcoceppi directly
[18:33] <elopio> Wimpress suggested before to bump the next candidates from the past election. Let's keep that in mind, to discuss if it's a good idea or not when the time comes.
[18:34] <wxl> ok
[18:34] <elopio> The agenda has no more topics. Anybody else has more topics?
[18:34] <elopio> I'll start the count down.
[18:34] <elopio> 10...
[18:34] <elopio> 9...
[18:34] <elopio> 8...
[18:34] <elopio> 7...
[18:34] <elopio> 6...
[18:34] <elopio> 5...
[18:34] <elopio> 4...
[18:34] <elopio> 3...
[18:34] <elopio> 2
[18:34] <elopio> 1...
[18:35] <elopio> #endmeeting
[18:35] <meetingology> Meeting ended Thu May  3 18:35:15 2018 UTC.
[18:35] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-05-03-17.05.moin.txt
[18:35] <wxl> thanks all
[18:35] <elacheche> thanks guys :)
[18:35] <elopio> thanks for attending. Sorry (not sorry) for being grumpy :) I need a beer.