16:00:20 <djmitche> #startmeeting weekly
16:00:20 <bb-supy> Meeting started Tue May 30 16:00:20 2017 UTC and is due to finish in 60 minutes.  The chair is djmitche. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:20 <bb-supy> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:20 <bb-supy> The meeting name has been set to 'weekly'
16:00:25 <djmitche> #topic Introduction
16:00:30 <djmitche> so skelly can't make it :)
16:00:35 <djmitche> https://titanpad.com/buildbot-agenda
16:00:46 <djmitche> who is around?
16:00:52 <bdbaddog> here
16:01:14 <rjarry> hi all
16:01:17 <rjarry> o/
16:01:22 <tardyp> hello
16:01:41 * djmitche waves
16:01:45 <djmitche> #topic Week in Review
16:01:49 <djmitche> how's the week been?
16:02:08 <tardyp> 80% pyup
16:02:28 <djmitche> looks like 40% upgrades to requests :)
16:02:35 <tardyp> most of the week has been merging pyup PRs. and 40% requests.
16:02:38 <djmitche> #topic mostly updating dependency libraries this week
16:02:43 <tardyp> I did not realize requests released so often
16:02:49 <djmitche> oh, wow
16:02:58 <tardyp> so I configured pyup to only PR once a week
16:03:12 <djmitche> hence 3286	configure pyup to update only every week
16:03:14 <djmitche> yeah
16:03:26 <djmitche> very cool
16:03:29 <djmitche> #undo
16:03:29 <bb-supy> Removing item from minutes: <ircmeeting.items.Topic object at 0x806814b10>
16:03:46 <djmitche> #info mostly updating dependency libraries this week, especially requests
16:03:54 <tardyp> then we also got quality contributions
16:03:56 <djmitche> #info turns out requests updates very frequently, so scaling those down to once a week
16:04:20 <tardyp> once of the first non trivial contributions from Frontend developers
16:04:25 <djmitche> awesome
16:04:42 <djmitche> https://github.com/buildbot/buildbot/pull/3269 ?
16:04:52 <tardyp> kudos to Lekensteyn
16:05:31 <djmitche> #info great new frontend contribution (collapsing log viewers) from Lekensteyn
16:05:34 <djmitche> #topic Releases
16:06:44 <djmitche> I'm guessing no news :)
16:07:01 <djmitche> #topic     TitanPad shuting down
16:07:01 <djmitche> http://blog.titanpad.com/2016/11/shutting-down-titanpad_12.html
16:07:05 <djmitche> we use titanpad for the agenda
16:07:19 <djmitche> looking for ideas for an alternative...
16:07:28 <bdbaddog> Google docs?
16:08:04 <tardyp> I think we should stick to something compatible with github oauth
16:08:46 <bdbaddog> Could have a git repo for agendas and handle via permissions or pull request?
16:08:55 <djmitche> yeah
16:09:01 <djmitche> we rarely get agenda updates though
16:09:36 <bdbaddog> one upside is agenda's would be archiveable..
16:09:46 <djmitche> true
16:09:52 <tardyp> I think the wiki proposal from dustin is good enough
16:09:56 <bdbaddog> and no. infrastructure to manage
16:10:23 <tardyp> github wiki are glorified markdown git repositories
16:10:52 <djmitche> what if we had an agenda in a wiki that says agenda items can be added by bringing them up during the introduction (or at any other time)
16:11:07 <djmitche> github wikis aren't world-writable..
16:11:18 <djmitche> can you make a google doc world-writable?
16:11:36 <bdbaddog> you can make it so anyone with the link can edit.
16:11:44 <tardyp> yes
16:11:50 <djmitche> oh! https://productforums.google.com/forum/#!topic/docs/eOUilQHIKic
16:11:54 <djmitche> that seems good
16:12:15 <tardyp> ok
16:12:21 <bdbaddog> https://docs.google.com/document/d/1xI_JjjNv_m3M9EBVW7C39CDBwe88oIKvQnoJw89roto/edit?usp=sharing
16:12:59 <djmitche> then anyone can toss a topic in -- and we can even maybe see who did so (which has sort of been a mystery sometimes)
16:13:06 <djmitche> cool, I'll make a doc and we can use that
16:13:15 <djmitche> agreed
16:13:16 <djmitche> ?
16:13:22 <bdbaddog> Sounds good.
16:13:37 <djmitche> #agreed will use a publicly-writable google doc
16:13:40 <bdbaddog> Maybe worth a new doc per meeting and then disable edit after meeting?
16:13:49 <tardyp> we should create a shorten URL for that link
16:13:59 <tardyp> so that we can put in the irc topic
16:14:12 <djmitche> bdbaddog: that seems like a lot of process for something that doesn't change much
16:14:14 <djmitche> yep
16:14:26 <bdbaddog> k. just a thought. previsous revisions show in history..
16:14:32 <djmitche> yep
16:14:38 <bdbaddog> file->see revision history
16:14:45 <djmitche> #action djmitche to create google doc, plus short URL
16:14:52 <tardyp> http://bit.ly/2rQRidC
16:15:05 <djmitche> should we use that doc? I'm happy with it :)
16:15:16 <tardyp> bahh
16:15:18 <tardyp> why not?
16:15:41 <bdbaddog> is there a buildbot google account?
16:15:45 <rjarry> who's "annonymous dolphin" ? :D
16:16:06 <tardyp> people who are not connected in google get anonymous nicknames
16:16:13 <rjarry> oh there's a tiger too
16:16:24 <djmitche> ok, I'll use that one
16:16:32 <djmitche> #topic     MOSS Bounty completion?
16:16:41 <djmitche> bdbaddog: ^^ this is your topic?
16:16:48 <bdbaddog> yes.
16:17:10 <bdbaddog> wanted to know if it's reasonable to say that item is complete and if so, would the bounty just get attributed to the project itself?
16:17:39 <tardyp> I am in favor of this
16:18:18 <djmitche> me too
16:18:20 <tardyp> This would help if we have some server costs
16:18:23 <bdbaddog> Ideally (I think) we should attribute the work to whomever did it and then say they've contributed the bounty to the project?   Report that back to MOSS ?
16:18:35 <djmitche> yeah
16:18:45 <djmitche> it's tricky since this is pretty far from the documented process
16:18:59 <tardyp> this would avoid taxes
16:19:32 <bdbaddog> sure. Mozilla still get's the write off as well.
16:19:47 <djmitche> yeah
16:19:48 <bdbaddog> are we being truthful that the item is complete?
16:20:19 <djmitche> #info EC2-related bounty is still pending, but the work has largely been completed by tardyp
16:20:35 <djmitche> #info tardyp would like to "donate" that bounty to the project
16:21:00 <tardyp> I think it is. I am not sure how much we have EC2 users that could report further issues
16:21:24 <tardyp> I thought skelly was on ec2 but he is on openstack
16:21:33 <djmitche> I think Twisted used to use it
16:21:34 <bdbaddog> so the bullets on this page are handled: http://trac.buildbot.net/wiki/BountyProgram
16:21:36 <djmitche> not sure if they still do
16:21:59 <bdbaddog> https://github.com/buildbot/buildbot/issues/2961
16:22:21 <tardyp> twisted are on eight
16:25:17 <Foxboron> tardyp: the tip earlier works perfectly btw :)
16:26:20 <djmitche> ok
16:26:32 <djmitche> bdbaddog: can you talk to gerv about what he needs then?
16:27:11 <bdbaddog> sure. I think it's summarized in the email I forwarded to botherders.
16:27:19 <djmitche> ok
16:27:22 <bdbaddog> Ideally a blog post about the bounty and it's completion..
16:28:07 <djmitche> is that sometihng you can do, tardyp ^^?
16:28:21 <tardyp> ok
16:29:00 <djmitche> #info bdbaddog, tardyp to work on wrapping that up
16:29:05 <djmitche> anything else?
16:29:08 <bdbaddog> btw.. that google doc was just meant to be a sample, not a permanent home.
16:29:24 <djmitche> haha, ok, I'll make a fresh one
16:29:28 <bdbaddog> Didn't see a response if there was a builtbot google account?
16:29:41 <djmitche> there is'nt
16:29:48 <djmitche> but I can create a doc in my account
16:30:16 <bdbaddog> k.
16:30:45 <djmitche> #endmeeting