16:03:30 #startmeeting websites meeting 16:03:30 Meeting started Wed Aug 28 16:03:30 2019 UTC. The chair is pili. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:30 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:04:23 one sec 16:04:37 I've just come out of another meeting so I need to get myself situated :D 16:05:17 pad is here: https://storm.torproject.org/shared/rdmFw02OnAaIp79kvIqtGGLyo71d6VrGOzAVHHrIshr 16:06:06 hi stephw emmapeel :) 16:06:11 who else is around? 16:06:14 hiro ggus ? 16:06:23 hey 16:06:28 we're missing antonela today as she's on the road as we speak 16:06:42 maybe we can start with community portal updates? :) 16:06:51 (spoiler alert: I have none :( ) 16:07:09 not to many things, i was traveling last week. but 16:07:17 i’m sorry i don’t either, so many things happening right now 16:07:34 oh i wanted to ask stephw to check again the localization section and make sure her review changes are there 16:07:46 so i can mark the localization section as finished 16:08:10 i migrated the EFF legal faq to the community portal: https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/ 16:08:30 i still need to fix some broken links 16:09:25 i also created the bad relays page - https://community.torproject.org/relay/community-resources/bad-relays/ 16:09:48 ah, cool 16:09:59 even though it's not a consensus in bad-relays working group, it's important to have this resource translated 16:10:44 i still need help with https://community.torproject.org/relay/community-resources/good-bad-isps/ 16:11:28 maybe we need some sort of table of contents for that 16:11:29 i'm planning to implement irl1 idea of using metrics data + wiki page 16:11:41 so people can jump directly to the countries on the page? 16:11:44 pili: yes, it's a feature that i'd like to have 16:12:26 I think there is some plugin or module or something for lektor that does that already 16:12:34 I believe nusenu wanted to use that for the page in the past 16:12:41 they were talking with hiro about it 16:13:19 how do we implement this TOC feature? 16:13:55 with the lektor title markdown link it was possible 16:14:10 ggus: let me see if I can dig up the email 16:14:15 but i am not sure if we managed to install it 16:14:22 it was in use for the glossary 16:15:43 emmapeel: yeah, that rings a bell about installation 16:16:02 emmapeel: i had a shower thought to move the glossary to localization section in community portal 16:17:17 https://github.com/lektor/lektor-markdown-header-anchors 16:17:18 that's the plugin 16:17:19 I thought hiro installed it already on the community portal 16:18:24 pili: to finish the relay operations part, we still need: - GoodBad ISPs + Metrics data; - How to update your OS (it's already done, I just need to find a good place to put the instructions); - Fix broken links. 16:18:58 We need to have this section done for relay outreach in september :o 16:19:20 ops, and another item: - Tor associations around the world and their donation page 16:19:23 ggus: sounds great, for the metrics data portion... how are we going to use that data with the static site? is it going to re-build periodically with the latest data? 16:20:01 pili: i only see the i18n plugin with lektor plugins list 16:20:13 ok, maybe it never happened :) 16:20:14 in the community git 16:20:25 pili: yeah, we still need to figure out this 16:20:44 I guess one of us could try to install it locally and run lektor with it to see how it would work 16:21:33 also> that plugin allowed you to add the TOC as part of the template, not as a [tag] you can insert in the text 16:22:04 i guess it is posible to make it become a tag but somebody should code it 16:22:18 * emmapeel dont want to point any fingers :D 16:23:28 is the existing functionality not enough then? 16:23:42 could we ask the plugin writers to implement this? 16:24:48 ok, let's move on I think :) 16:25:16 if we really want to use this plugin though we need to a) test it and b) find out if someone can extend it to do what we want 16:25:22 otherwise we just do what we can, i.e not have a TOC :) 16:26:10 I just noticed that the training resources were removed from the page, I guess in preparation for the correct format? ;) 16:26:25 we should try to get some uploaded by next week at the latest 16:26:47 we're going to use the latex thing? 16:27:16 that's not going to be ready any time soon I don't think :) 16:27:22 I was playing with pandoc last week for some slides on a talk I'm giving 16:27:26 but didn't get too far 16:27:42 I think for now we should go with the original plan of just uploading to the community portal 16:28:01 and upload different localised versions in the relevant directories 16:28:17 so the right ones show up with the language dropdown 16:30:04 I think next week during the docs hackathon I will work on the community portal and try to come up with a proof of concept for having the materials in the community portal repo for now 16:30:58 maybe it is easy for hiro to provide some table like the ones for the different Tor releases 16:31:08 *thinking about localizing files 16:31:31 hmm 16:31:40 yeah, maybe, we should follow that model 16:31:46 although those files are hosted elsewhere 16:31:50 i feel i cannot convey the importance of translating through the translation platform. if people starts to simply submit random translations is not going to work well on the long term 16:32:22 it will be very hard to maintain such a text/codebase 16:32:24 emmapeel: it's more about providing the localized training slides we already have 16:32:44 e.g ggus already has his training materials localised in a number of languages 16:32:54 ok 16:33:17 my idea is to take those files and upload them to the community portal for now 16:33:18 while we get the resources localisation pipeline set up 16:33:29 grrml ok 16:33:51 we don't have enough people to do everything we need or want 16:34:04 emmapeel: I understand why you don't like that though, this is a stop gap 16:34:22 I'm sure ggus is not going to go off and translate the slides to thai himself :D 16:35:09 :D 16:35:14 yeah, my thai is not fluent.. :P 16:35:17 ok, anything else on the community portal? 16:35:34 we need everything on onion services section 16:35:37 neither will our thai translators because the slides are not on the translation platform :P ok i shut up with that 16:35:51 another thing> to prevent the loss of contributions we should disallow users to comit to https://dip.torproject.org/web/community 16:36:12 only allow torpusher 16:36:19 emmapeel: make all repositories read-only? 16:36:39 in dip 16:36:50 yup 16:36:55 not all, only the ones that are overwritten by torgit 16:37:16 i.e. https://dip.torproject.org/web/community :master :staging :develop 16:37:17 let me see, I'm going to try do that now 16:38:35 emmapeel: I guess if I make everyone reporter only on those repos that should work? 16:38:50 but I wonder what other permission that will take away 16:39:39 hiro: do you know how to do this? 16:40:50 anything else to discuss while I try to figure out how to do that? :) 16:41:19 I think this is what we want https://docs.gitlab.com/ee/user/project/protected_branches.html 16:41:40 maybe we can have protected branches 16:41:46 he exactly 16:43:43 pili: we need to review our release dates for community portal. some sections are in production mode, like, bridges 16:44:31 emmapeel: I think hiro already did this 16:44:48 I can see that master and staging are protected branches for support and community at least 16:44:53 so I think we're good 16:45:34 i can edit files in master i think 16:45:45 for which repo? 16:45:54 ah no 16:46:04 only maintainers should be able to :) 16:46:09 and the only maintainer is hiro 16:46:10 i can 'niciar una nueva solicitud de fusión con estos cambios ' 16:46:15 good :) 16:46:17 so it works 16:46:22 great 16:46:38 yay, we have a happy emmapeel ? ;) 16:46:51 back to release dates 16:46:54 yay! 16:46:57 pili: i think next week we all should focus on docs hackathon - support, tb-manual and tpo 16:47:02 there are too many issues 16:47:17 sure 16:47:18 what else do we need to prepare there? 16:48:16 we need to send an email to the participants (due this friday) and maybe open a pad to organize things? 16:48:22 maybe we have to check that the documentation for lektor and local testing is ready 16:48:31 so people can quickly communicate with others? 16:48:34 i don't know 16:48:47 emmapeel: yeah 16:49:05 pads are very useful for collective actions 16:49:15 self-organizing 16:49:26 we should have A pad 16:49:34 (A) pad 16:49:39 maybe full of links to ther pads but as a point of contact... 16:49:40 the self-organized pad 16:50:29 https://pad.riseup.net/p/tor-docs-hackathon-keep 16:50:36 there you go, that's my contribution ;) 16:51:41 yay! 16:52:27 emmapeel: I've given you the task of checking lektor docs 16:52:31 I think it's mostly ready 16:52:40 we probably just need to make sure that the wiki has these links for people 16:53:17 ok, we have just over 5 minutes left 16:53:18 I see people are updating the pad 16:53:27 any other pressing issues to discuss before the end? 16:53:38 the pad uprising is starting 16:54:05 ok with checking the docs 16:54:36 im groot 16:55:13 i'm good too 16:55:54 ok, let's move to the pad then and end the meeting :) 16:56:03 #endmeeting