Talk:SAC Meeting 2018-04-14
Jump to navigation
Jump to search
TRANSCRIPT
04:00:17 robe2: Meeting time - https://wiki.osgeo.org/wiki/SAC_Meeting_2018-04-14 04:00:18 sigabrt: Title: SAC Meeting 2018-04-14 - OSGeo (at wiki.osgeo.org) 04:01:40 robe2: wildintellect / TemptorSent want to just summarize our hardware status 04:01:59 robe2: I kind of gathered already from the list but probably good to summarize 04:02:50 robe2: ping wildintellect TemptorSent 04:02:54 wildint: I updated it 04:03:25 wildint: I have the wrong quote with the wrong specs, re-requested the correct one 04:03:34 robe2: wildint okay great 04:03:38 wildint: once it's here if TemptorSent thinks its right we'll vote 04:03:53 TemptorSent: O 04:03:57 robe2: next topic Funtoo. I've been really bad and haven't had a chance to do anything yet 04:04:38 robe2: TemptorSent any changes on your end to report for Funtoo container? 04:04:48 TemptorSent: I've been occupied with other projects like building out the pdal dep tree with full feature and format support. 04:05:10 TemptorSent: So I haven't made any changes of note. 04:05:27 robe2: okay hopefully one of us will get to do something next week 04:05:49 robe2: I had switched the weblate as a funtoo thing, I think it had been planned to be on OSGeo6, but seems better to try on funtoo 04:05:52 TemptorSent: We probably want to decide who's going to admin the actual webapps once they're setup, as that's an entirely different ball of wax :) 04:06:38 TemptorSent: I have weblate packaging thats working, but not perfect -- we'll want to backup before updates and clean things up as we go a bit. 04:06:38 robe2: TemptorSent agreed different ball of wax 04:06:46 wildint: might help to have a short list that outline's what someone would need to do 04:06:58 TemptorSent: I don't really do much from the web side myself. 04:06:59 wildint: so we can fish for a volunteer 04:07:16 robe2: yah not being too familiar with either, that would be good to know 04:07:32 TemptorSent: Like weblate -- I have absolutely no idea what we need in terms of features, support, customization, etc. 04:07:36 robe2: It could just be a matter of making sure it's backed up properly and dealing with security updates etc 04:08:05 robe2: I'd actually be willing to support weblate if we go for it, since I'm hoping PostGIS will be one of the biggest users of it 04:08:19 TemptorSent: I can get it running easily enough, but I can't RUN it since I don't really have the domain knowledge or even know what projects need what translated in what format. 04:08:23 robe2: are at least a non-trivial user so would make sense for me to watch over it 04:08:44 TemptorSent: Sounds good to me :) 04:08:56 robe2: TemptorSent well I think most projects right now are on transifex and they just have poml files 04:08:57 wildint: I think the people who requested it can jump in there klaxas would be a good person to test 04:09:00 TemptorSent: Let's get you setup with that this week then. 04:09:46 TemptorSent: Is anyone using the nextcloud install? I havent' heard anything, but I don't know if it's even completly setup at this point. 04:10:00 robe2: hmm I mean .po file or at least that's the way PostGIS is setup and our bot just pulls the updated pos from transifex currently to incorporate in doc building 04:10:09 robe2: So I'm guessing weblate work flow would be much the same 04:10:40 TemptorSent: Yeah, it has all sorts of features and formats supported. 04:10:47 robe2: cvvergara can probably speak on the pgrouting since they use transifex too as I recall 04:11:17 robe2: .po is pretty standard so I assume the hardest part would be getting translators on transifex to use weblate 04:11:25 TemptorSent: Yep. 04:11:52 robe2: and on the user-friendly ui thing not sure how it compares to transifex as I only pay attention to the .po output 04:12:11 TemptorSent: I have packages for pretty much all features of weblate built, so you can do pretty much whatever you need I think. 04:12:17 robe2: next topic FOSS4G2018 anyone on here from there? 04:13:16 robe2: okay guess no one from there on here. FWIW I did set them up with staging.2018.foss4g.org and looks like they are using it heavily so that's good 04:13:57 robe2: I setup a cronjob to pull the changes they make to gitea repo every 5 minutes. Of which I was going to eventually change to a webhook (that strk gave me gobbly gook directions to attempt) 04:14:09 jodygarnett: its looking good 04:14:26 robe2: anyway didn't seem that urgent since they aren't making changes too much to the theme and it updates every 5 minutes anyway if they do 04:14:56 robe2: jodygarnett I was thinking we could setup something similar with osgeo in case getinteractive or whoever needs to update the theme 04:15:21 robe2: maybe we should discuss that at some point or can wait till I have the webhook going 04:15:36 jodygarnett: that sounds fine to me, whatever is easier. May want to encourage pull-request workflow for large changes 04:15:52 robe2: I think right now i just have the main www.osgeo.org under git, but to do it right we'd probably want a separate branch for staging / prod 04:15:56 TemptorSent: Yeah, it would be even cooler if it went to a staging site first, with a commit option. 04:16:13 TemptorSent: :) 04:16:14 jodygarnett: still let's start simple and not over engineer 04:16:32 TemptorSent: It's actually pretty simple, and saves a lot of headaches. 04:16:58 jodygarnett: amusing - https://staging.2018.foss4g.org/blog/ has hello world and sample post 04:17:18 TemptorSent: Have the staging pick it up automatically, but require an ack to push to main site. 04:17:30 robe2: jodygarnett yah I'm really impressed how quickly they ran with that 04:18:38 robe2: TemptorSent ah that sounds better so we'd just have one repo as we do now - https://git.osgeo.org/gitea/osgeo/wordpress which right now I just manually pull/commit from the server 04:19:23 robe2: So committing would go straight to staging and some ack thing would trigger production change 04:19:26 TemptorSent: Yeah, nothing fancy needed -- just do something like put the commit number the main site should be running as the push token. 04:20:01 jodygarnett: I have not been brave enough to mess with the theme, I see later in the meeting there is a question about listing a new category of sponsors, that would I think require a theme change. 04:20:35 TemptorSent: It shouldn't need anything fancy changed. 04:20:42 robe2: yah so it would be good to do all that in staging first which we do have setup though its not pulling from git at moment 04:21:24 robe2: jodygarnett when is this theme change planned? I can try to fix up staging so it can at very least do a cronjob pull from repo 04:21:25 TemptorSent: Having the staging actually stage the git-master would be best in the long run I think. 04:21:46 robe2: TemportSent agreed 04:21:56 TemptorSent: That way we can flip branches or whatever is needed. 04:21:58 jodygarnett: I am sorry lets proceed with the adgenda, I am not quite sure how the sponsors page is implemented. 04:22:08 robe2: too bad strk isn't here to chime in with his bureacratic two cents 04:23:09 robe2: jodygarnett side thought perhaps you can get some foss4g2018 folks to help. I had started up with the theme and from what I could gather they figured out all the bits and started changing it 04:23:25 robe2: so they might actually have good grasp of how the sponsors page is set up 04:23:59 jodygarnett: good point 04:24:05 robe2: next topic LDAP wiki thing 04:24:16 TemptorSent: jodygarnett - for the sponsors page, just another line tagged 'Infrastructure Provided By' or something and the logos would do it. 04:24:50 robe2: oh hay that section we need for infrastructure 04:25:10 robe2: wildint we were going to put osuosl on the list of sponsors -- I guess we should ask them first 04:25:36 jodygarnett: I was going to recommend adding them to the partners and friends section instead: http://osgeo.org/partners/ 04:25:37 sigabrt: Title: Partners Archive - OSGeo (at osgeo.org) 04:25:45 wildint: seems in the same line as funtoo, though we actually donate money to them 04:25:53 jodygarnett: partners and friends = love, sponsors = money 04:26:21 jodygarnett: ore appropriate no? 04:26:21 TemptorSent: Where's the partners page? 04:26:25 robe2: ah okay that's one 04:26:25 jodygarnett: http://osgeo.org/partners/ 04:26:26 sigabrt: Title: Partners Archive - OSGeo (at osgeo.org) 04:26:49 jodygarnett: aside: why do all these magic content pages say "archive" in the title? just wondeirng ... 04:27:37 jodygarnett: So yeah if you can round up a logo and details for those two, it woudl be great to thank them publicly for their support 04:27:50 robe2: jodygarnett so I guess they would go under partners though technically infrastructure does translate to money 04:27:55 robe2: I'm fine with partner though 04:28:07 robe2: TemptorSent your thoughts on that? 04:28:35 TemptorSent: I think it may make more sense under the sponsors, at least for the infra stuff. 04:28:40 jodygarnett: there are two categories: partners (signed something with board), friends (organiations we collaborate with and admire) 04:29:12 jodygarnett: As you wish, although it may open me up to a world of pain 04:29:12 TemptorSent: The partners appear more to be other projects, but not necessarily any services associated. 04:29:22 jodygarnett: it is close ot being an in-kind sponsorship 04:29:28 jodygarnett: and I already get requests for that 04:30:03 TemptorSent: Yeah, it's essentially an in-kind donation + some additional support. 04:30:19 jodygarnett: and I want to avoid an OGC situation with a tension between finincial and in-kind support 04:30:21 TemptorSent: Same as OSUOSL 04:30:49 jodygarnett: OSUOSL really liks like a good candidate for a friend page 04:30:54 TemptorSent: That's why I'd term it infrastructre provided by rather thans sponsored by 04:31:47 TemptorSent: There doesn't appear to be an actual friends list, the partners and friends is one in the same. 04:32:04 robe2_: sorry my connectin died 04:32:33 jodygarnett: compromise, we make the friend page, and we add some text at the bottom saying "infrastructure support and hosting provided by OSUOSL and Funtoo. The names can link to the friend pages. 04:32:58 robe2_: if we had an in-kind sponsorship I think that would work for all these 04:33:21 robe2_: jodygarnett fine by me 04:33:29 jodygarnett: I understand, technically I think that would solve the representation/recognition 04:33:35 jodygarnett: socially I think it would cause difficulty 04:33:46 TemptorSent: I don't have a strong preference one way or the other, it just seems like a logical solution 04:34:43 robe2_: okay so we go with the friends page with infra section 04:34:52 jodygarnett: yeah, this is interacting wtih markeitng departments, clear $$$ for representation will beat out logic. It is lready tough explaining about what is or is not an osgeo event. 04:35:12 TemptorSent: Fair enough. 04:35:15 jodygarnett: and since that page is done by a theme, we will need to try out your commit hooks 04:36:16 robe2_: jodygarnett okay deal will let you know once I have commit hooks for staging and refresh staging with latest data from prod 04:36:34 jodygarnett: We can make the friend pages right away 04:36:48 jodygarnett: happy to do so if someone can provide me the details 04:36:55 TemptorSent: That works :) 04:38:16 robe2_: next topic GeoForAll cvvergara jodygarnett anything to say about that? 04:38:34 jodygarnett: I asked a few questions on email, and got some clarifications. 04:38:47 jodygarnett: I am mostly just encouraging from the sidelines, so not much to say 04:39:19 jodygarnett: I did raise https://trac.osgeo.org/osgeo/ticket/2144 as part of reviewing 04:39:21 sigabrt: Title: #2144 (redirect geoforall.org pages to osgeo.org/initiatives/geo-for-all/ pages) – OSGeo (at trac.osgeo.org) 04:39:30 robe2_: so is there idea to get rid of the geoforall site and just be part of www.osgeo.org site? 04:40:17 jodygarnett: yes 04:40:52 jodygarnett: that was the idea last year, website went live. We retired the drupal website, but not this geoforall.org website. 04:41:27 robe2_: okay so presume still the idea 04:41:43 jodygarnett: yep 04:42:15 robe2_: great wow could it be we covered all topics in the meeting in less than an hour :) 04:42:21 jodygarnett: reviewing that ticket there is one related issue, hard to redirect http://www.geoforall.org/training'>http://www.geoforall.org/training to http://www.geoforall.org/training'>http://www.geoforall.org/training 04:42:23 sigabrt: Title: OSGeo Labs - Training (at www.geoforall.org) 04:42:42 jodygarnett: because we would need a query parameter: http://www.geoforall.org/training?category=geoforall 04:42:43 sigabrt: Title: OSGeo Labs - Training (at www.geoforall.org) 04:42:45 robe2_: It appears Martin is not here and one of the reasons we switched time to weekend was for him. So I guess this time is no good for him 04:43:05 jodygarnett: (sorry sigabrt is spamming this meeting, I will stop talking in URLs) 04:43:39 TemptorSent: That rewrite shouldn't be too difficult. 04:44:01 robe2_: TemporSent yah agree shouldn't be too difficult though not sure where we should put it 04:44:52 TemptorSent: In the top-level apache config. 04:45:14 TemptorSent: Just a mod-rewrite rule for that particular url. 04:45:19 robe2_: TemptorSent I lost track if we even have control over geoforall.org yet 04:45:34 wildint: we don't yet, but it is still on the todo list 04:45:53 robe2_: so kinda moot anyway 04:46:07 robe2_: wildint what server is that running on is it one of ours? 04:46:16 wildint: nope 04:46:28 wildint: one of the labs set it up 04:46:35 robe2_: okay I'll put a note on that ticket then that we can't do anything about it until we have control 04:47:04 TemptorSent: Just ask them to put the redirect on the page it loads. 04:47:30 jodygarnett: I have been collecting notes in that ticket as your folks sort out the details. 04:47:46 robe2_: thanks jodygarnett beat me to it 04:47:51 wildint: I think the hold up is that the current admin hasn't responded to any emails 04:48:04 TemptorSent: Ahh, that does make it difficult. 04:48:18 robe2_: which means he probably won't respond to any redirect requests either :) 04:48:49 wildint: well there's probably someone else who works in person with him, or has more regular contact 04:48:55 jodygarnett: you may wish to bump this up to geoforall team? 04:49:30 wildint: mckenna was assigned the ticket can you put him in touch 04:49:38 robe2_: yes bump up would be good -- I volunteer you jodygarnett step forward :) 04:49:49 jodygarnett: ha ha, okay I will send an email. 04:50:44 robe2_: Looks like we lost rkased 04:51:04 TemptorSent: and jive 04:51:18 robe2_: but we have jive[m] 04:51:23 jodygarnett: does the sys admin have a name? the person we cannot reach ... 04:51:28 robe2_: and jodygarnett 04:51:38 wildint: its in the ticket 04:51:49 jodygarnett: rtfm 04:51:57 robe2_: rtft 04:52:17 wildint: https://trac.osgeo.org/osgeo/ticket/2061 04:52:18 sigabrt: Title: #2061 (Migrate GeoForAll DNS) – OSGeo (at trac.osgeo.org) 04:52:34 TemptorSent: Oh, todo item for me I guess -- setup a container for running bots for us :) 04:53:32 TemptorSent: Running it on my home dev box was getting a bit bouncy when I was doing a bunch of boot tests, so I disabled it locally. 04:54:04 robe2_: TemptorSent yah was meaning to study that buildbots thing strk was itching me to get going with 04:54:06 jodygarnett: Did I miss the updates on Wiki LDAP ? 04:54:28 robe2_: It seems I'm spending too much time these days learning new things only to have them change on me in 4 months time 04:54:59 robe2_: jodygarnett no I had mentioned it but being the bad sysop I am, I let you guys change the topic 04:55:14 TemptorSent: No significant updates, but I more or less verified that the strategy we outlined in the last meeting should work without major difficulty, but will require some brief planned downtime and some minor custom programming. 04:55:35 robe2_: anyway TemptorSent had outlined a plan for Wiki LDAP 04:55:41 jodygarnett: planned downtime is fine, custom programming sounds like work? Any way to avoid/reduce 04:55:46 wildint: brief downtime is acceptable 04:55:52 TemptorSent: Martin and I more or les concurred on the plan. 04:56:00 wildint: any way to test and verify 04:56:05 TemptorSent: Custom programing can not really be avoided. 04:56:20 robe2_: I think we were going to setup a new instance 04:56:22 wildint: I don't think we're worried about some programming, if it's one time thing like SQL 04:56:27 TemptorSent: Yes, we can mirror the wiki to a test machine and do the testing. 04:56:28 robe2_: might be worthwhile to do on funtoo 04:56:46 robe2_: I'd be happy contributing trying to break the thing :) 04:57:06 TemptorSent: The downtime is long enough to pull the DB down, make a complete snapshot, run the modifications, make a fresh snapshot, and reimport. 04:57:26 robe2_: as I recall it's a redirect script that maps what user types in to legacy_user or something 04:57:47 TemptorSent: Essentially, yes. 04:57:55 robe2_: TemptorSent you know off hand how big the db is? 04:58:04 TemptorSent: No. 04:58:08 robe2_: I presume it's not that big can probably be restored in under 10 minutes 04:58:10 TemptorSent: I haven't messed with it 04:58:31 TemptorSent: Agreed, I'd probably schedule a 2hr window with expected outage of 15 minutes. 04:58:56 jodygarnett: there was a volunteer earlier in the day reviewing wiki pages, and asking what can be updated or thrown out. Whole thing makes me tired. 04:58:56 TemptorSent: ...after we've tested the migration on staging system and it all works. 04:59:17 jodygarnett: speaking of which I put in a ticket asking for escalated wiki permissions so I could edit the main page 04:59:27 robe2_: which server is the database on? 04:59:33 wildint: wiki 05:00:15 wildint: jodygarnett, I'd give you the perm if I had any idea how 05:00:17 robe2_: some german guy must have set it up 05:00:33 robe2_: I get ident error notice in german (or at least I think that is german) 05:00:34 jodygarnett: I can wait till it is migrated to LDAP 05:00:49 robe2_: psql: FATAL: Ident-Authentifizierung für Benutzer »postgres« fehlgeschlagen 05:01:43 wildint: martin probably did the install 05:02:19 robe2_: okay will leave to martin then 05:02:45 robe2_: check size just to confirm won't be much downtime during move 05:02:47 jodygarnett: "Ident authentication for user »postgres« failed" 05:03:08 robe2_: jodygarnett that's what you get? 05:03:10 TemptorSent: Just grab one of the dumps from it 05:03:16 jodygarnett: that is what google translate said 05:03:32 robe2_: oh I figured it translated to that, I just wasn't expecting german 05:03:49 TemptorSent: You were expecting swahili? 05:03:58 robe2_: anyway I don't have sudo access to that server and seems to be under ident control 05:04:07 robe2_: TemporSent yoruba :) 05:04:35 robe2_: anyway anything else left to cover? 05:06:11 jodygarnett: think we may be done 05:06:21 robe2_: my dream of a meeting that is under an hour has been destroyed thanks to someone mentioning how we skipped over a topic :) 05:06:21 TemptorSent: Not that I can think of from the agenda. 05:07:00 jodygarnett: I have a couple of action items from code sprint and board meeting, mostly to do with website glitches. Will cover using the issue tracker. 05:07:35 robe2_: jodygarnett okay issue tracker sounds good since we've gone over though you can quickly mention them too 05:07:39 TemptorSent: Anything notable/pressing? 05:07:42 robe2_: another 10 minutes won't kill me 05:07:52 wildint: just got updated hardware quote https://drive.google.com/open?id=1M491x3mSl51K1o60Bksulf7KOCqkru55 05:07:53 sigabrt: Title: Silicon_Mechanics_Quote_345880.pdf - Google Drive (at drive.google.com) 05:08:02 robe2_: oh goody 05:08:18 jodygarnett: it was all high level, local chapter stuff not working, no committee looking out for local chapters so the board has to... that kind of thing. 05:08:53 jodygarnett: thanks for your time everyone 05:09:07 robe2_: jodygarnett no problem. don't be a stranger 05:09:21 jodygarnett: I am stranger every day 05:09:25 robe2_: TemporSent does that have the right Optane :) 05:09:34 robe2_: just with that hat :) 05:09:52 TemptorSent: It appears to now, which also apparently comes at a slight premium. 05:09:54 robe2_: take off the hat and you'll fit right in 05:10:25 robe2_: I lost track of what our original budget was 05:10:52 wildint: lower 05:11:10 robe2_: wildint yah I figured that :) 05:11:15 TemptorSent: Yeah, storage and memory prices have gone up 20% or better since the first quote. 05:11:22 robe2_: but how much lower. 05:11:35 robe2_: aren't those things supposed to come down in price with time? 05:11:40 wildint: well we budgeted $5000 05:11:53 wildint: maybe $6 05:12:00 TemptorSent: In theory... but not when supply is suddenly cut by 30% of world capacity. 05:12:04 robe2_: ah so we have a 50% over budget or so not bad 05:12:10 robe2_: certainly better than most projects 05:12:52 wildint: well we did request $22K for the year I think 05:12:59 robe2_: TemptorSent oh I'm behind on current events like I don't pay attention at all, what happened did china refuse to sell to us or something 05:13:36 robe2_: okay so we are still good then 05:13:53 TemptorSent: I think there was a samsung factory that had a power issue take out their production line, and a couple of others down for various reasons, in addion to some natural disasters and civil unrest. 05:15:05 TemptorSent: Both hard drive and flash supplies were severly impacted, possibly with much of the impact being intentional overplayed by the vendors to drive up pricing 05:15:37 TemptorSent: In some cases, ram prices have actually doubled from what I was paying just 6 months ago. 05:15:45 robe2_: Damn those vendors (I got to go into my stash of flash let my inflate it a bit) 05:16:55 TemptorSent: USB sticks have gone UP in prices even in some cases.