15:00:45 #startmeeting S27 01/07 15:00:45 Meeting started Tue Jan 7 15:00:45 2020 UTC. The chair is pili. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:15 who is around today? :) 15:01:24 hello 15:01:35 hi 15:01:53 hola! 15:02:02 hi everyone 15:02:11 is asn around today? :) 15:02:16 and acat ? 15:02:18 happy 2020 15:02:33 hi! i am :) 15:02:42 happy 2020 15:03:00 no asn 15:03:08 still recovering 15:03:22 ok :) 15:03:27 here's the pad: https://pad.riseup.net/p/s27-meeting-keep 15:03:54 please add any updates you have 15:04:29 actually, do we have sysrqb around also? might be useful to have him for planning sponsor work also 15:09:17 might be early for matt i think 15:09:47 ok, we may need to change the meeting time in future to accommodate him also 15:09:55 anyway, let's get started 15:10:06 I think everyone's updated the pad 15:10:14 "early for Matt" ... it is 10:10am, come on :P :P 15:10:58 haha im not sure about his current location, is just about the usual first ping :) 15:11:15 :D 15:11:16 anyway 15:11:19 we have 3 months left of the project now 15:11:25 ! 15:11:30 yup... 15:12:15 most activities have already been started other than O2A5 - httpseverywhere for long onion addresses 15:12:41 we really need to get O2A5 going in January 15:13:15 and start assigning some devs to some of the other O2 activities 15:14:59 I think O2A2 and O2A4 go together, or at least they will hopefully use the same custom error page 15:15:15 mcs: yup 15:15:16 and I think antonela has made some good progress there 15:15:28 yep 15:15:31 maybe O2A2 should be next for brade and me 15:15:34 and i should back to them soonish 15:15:39 antonela: are you ready to work on this with devs now? 15:15:46 yes sure 15:15:56 as in, is there anything else that you need to finish off first? 15:16:01 (we are still finishing up O2A1 but are getting close I think) 15:16:08 i'd like for brade and mcs to review my proposal and let me know what do you think 15:16:26 antonela: what bug #? 15:16:29 #19251 15:16:55 if we are somewhat ok, i can work with comms on having a good wording for those errors 15:17:04 we will do that (review the proposal) 15:17:10 we have looked at it :) 15:17:26 awesome, thank you mcs 15:17:28 nice :) 15:17:43 like you know if you think we should go with one way or another, im fine iterating it 15:17:57 ok, so once O2A1 is over mcs and brade can start on O2A2 and O2A4 15:18:24 for O2A1, can i have a build? i dont think i have the latest one 15:18:37 or maybe you want to push it to some nightly for UI review 15:19:09 The code has not been merged yet but we could give you a build soon. Platform? macOS or other? 15:19:37 We can also check with sysrqb about merging so it shows up in nightlies 15:20:11 macOS if is not too complicated :) 15:20:15 thank you, appreciate it! 15:21:16 ok, then for O2A3 I think acat has made some progress 15:21:27 let me check where we are (sorry, I needed to do my homework) 15:22:03 at least #21952 is in a good state 15:22:18 yes it is, i hope we can reach some nightly for it 15:22:26 s/for/with 15:23:12 is use of Onion-Location vs. Location still an open issue? 15:23:15 I think that's the main ticket for O2A3, the others probably need some discussion to decide which we want to do 15:23:53 yes, i guess #21952 should be revised to address mcs/brade comments, although it's not in revision_needed, is it because there's still a pending review by pospeselr? 15:24:29 acat: I think so; maybe we should ping pospeselr (or maybe we just did) 15:24:38 am I supposed to be doing something and dropping the ball here? 15:25:13 pospeselr: a second review for #21952 would be great to have 15:26:33 thank you pospeselr :) 15:26:43 ok i'll get to that asap today 15:27:15 there was no rush since acat was away… but back now :) 15:27:59 so for the outstanding O2A3 tickets, let's either discuss at the end of this meeting or next week, depending on how much time we have once we finish going through the other objectives 15:29:16 so for O2A4 we have the error page on one hand and on the other hand we have tickets about onion cert indicators in the url bar 15:29:55 the error page part I think will be worked on at the same time as the O2A2 typo errors work? 15:30:15 brade / mcs is that how you plan to do it 15:30:24 pili: that’s what I was thinking. the URL bar stuff is quite different, as you correctly point out 15:30:49 ok, so, for the url bar work, antonela has come up with some proposals 15:31:01 yes and pospeselr made comments 15:31:16 and I think it's also ready to be picked up on the dev side? 15:31:17 ok 15:31:27 is pospeselr going to be working on this from the dev side? :) (I forget if we had decided already) 15:31:36 i'll back to it because we need to organize the UI a little bit, and you know indicators at the url bar are hot topic 15:31:56 i think so, given that he worked on the previous iteration, i dont know 15:32:15 (we should check with sysrqb) 15:34:03 ok, so antonela, do you want to iterate on it some more before we get a dev working on it or will it be a collaboration? :) 15:34:41 will be in collab i think, but i still need map some escenarios 15:34:47 ok, sounds good 15:35:16 which brings us to O2A5 15:36:15 does anyone remember whether this had been assigned to anyone yet? 15:37:03 I do not remember it being assigned to anyone (but my memory is far from perfect) 15:37:10 i dont think so - we need to run some meetings about it, check httpse situation and map a real path to reach some prototype 15:37:34 on that problem space we also have namecoin implementation, which can be a path for it as well 15:38:08 right, I think the namecoin implementation was pretty much ready to go iirc 15:38:24 I think we need to pursue the httpse solution though 15:38:36 i hope, yes 15:39:15 from my last conversation with eff people they're happy to help with minor things if we get stuck 15:39:16 and we need to do the bulk of the code ourselves 15:39:25 so they're on hand, but they're not going to be actively involved 15:39:51 as such, we need to find a developer to make any changes to httpse and tor browser and connect the 2 15:40:00 yep, so we need an updated plan for it 15:40:03 from my very limited understanding of it :) 15:40:24 not sure asn's ideas are about it, i hope he has ideas :) 15:40:44 ok, so that's another objective that needs some follow up discussion 15:41:10 yep 15:42:17 related with this sponsor, steph applied for the comms otf lab to work on the communication for this project (thanks stephw!) 15:42:18 * sysrqb appears late, and reads backlog 15:42:34 At some point we will need some devs eyes to review/help with the technical details of those writings 15:42:42 yup! I haven't heard anything back from that yet :) 15:43:15 back to the objectives and activities though, I would also like to get some estimates on how much work remains (in terms of points or days) for each of the activities 15:43:16 possibly by the time we have our next meeting, next week 15:43:43 sounds good 15:44:13 so if everyone can keep that in mind for next meeting to evaluate what they are working on and/or what they have assigned to them so we can evaluate whether we are going to be finished by the end of March 15:45:37 that is all I had to discuss today :) 15:46:18 happy to open discussion on any of these points 15:46:18 or anything else related to this project I may have forgotten 15:47:26 i need to coordinate a meeting for this month with fiona, will cc you if you want to join pili 15:47:37 * antonela 's calendar said that 15:47:39 antonela: sounds good :) 15:48:19 i want to demo the things that are in shape to be shown and share the other stuffs that we have in the making 15:52:20 hopefully O2A1 and O2A3 :D 15:52:27 for demos 15:52:33 at least on a nightly :) 15:53:28 yes yes 15:54:35 ok, anything else from anyone? 15:54:46 sysrqb: any insights/comments from reading the backlog? :D 15:55:25 pili: many distractions :) 15:55:38 ok, we'll talk at some other time then ;) 15:55:49 i think i was going to talk with acat about the https-e work 15:56:02 ok 15:56:15 but the onion-location/location work seemed more time-bound, so we started that first 15:56:16 sounds reasonable 15:56:28 but i'll review these and we can create a plan 15:56:59 i don't have any useful comments at this point, though :) :/ 15:57:15 sure, next week during this meeting I want to concentrate on making a plan for O2A3 and O2A5 15:57:16 no worries 15:57:22 and with that last comment, a reminder that we'll be moving to a weekly schedule for this meeting until the end of the project 15:57:33 hopefully that means shorter meetings, but we'll see ;) 15:59:34 ok 15:59:36 if there's nothing else, let's end the meeting here :) 16:00:35 thank you! 16:00:48 thanks everyone! 16:00:50 o/ 16:00:55 cheers 16:01:15 #endmeeting