13:59:36 #startmeeting community-portal 05/23 13:59:36 Meeting started Thu May 23 13:59:36 2019 UTC. The chair is pili. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:44 hi ggus emmapeel 13:59:56 jelou! 14:00:02 who else is around hiro antonela Alon_Braier 14:00:06 ola 14:00:10 isabela and stephw will not make it today 14:00:15 sstevenson are you around? 14:00:22 Hi everyone 14:00:27 i am here :-) 14:00:28 o/ 14:00:31 flexlibris!? :) 14:00:34 * antonela in another meeting too :/ 14:00:43 multitasking... :) 14:00:58 (I feel like I'm forgetting someone... :/) 14:02:13 is clash around? :) 14:02:16 I think that's everyone 14:02:38 here's the pad as usual: https://storm.torproject.org/shared/Vdky1wu-DWbg8_VPQR0WhTlmeNKmbpTBQm5rTQPgzXC 14:02:55 I am here 14:03:04 who wants to start with some updates? 14:04:14 ok, I'll pick on people then ;) 14:04:39 I'll start with relay operations 14:04:48 i am just finishing a 2 hour tails frontdesk meeting too... a it braindead 14:04:57 yikes 14:05:03 but hey! we did the localization stuff! 14:05:29 yup! 14:05:54 emmapeel: did you make that PR in the end? I've not been keeping track of the community portal since then 14:06:14 not yet, still on the workz. i got the mailing list on it too 14:06:39 about relay operations: we should include 'how to setup a bridge' manual that phw reviewed in the last week. 14:07:23 yay for the mailing list! 14:07:36 ggus: yup! I knew there was something missing that I was forgetting about :D 14:08:21 other than that, I reached out to nusenu last week I think to let them know that they can move on with their content was the templates are pretty much finalised 14:08:26 but I haven't heard anything back yet 14:08:38 we may at some point need to move forward with it ourselves 14:08:49 but they have done a lot of content already so it should be easy enough 14:09:04 any other comments on relay operations section? 14:09:08 i don't like so much these "specific guides" 14:09:16 i would prefer a choose your own adventure approach 14:09:18 https://people.torproject.org/~irl/relays.html 14:09:21 (we'll do user testing next) 14:09:38 i feel the specific ones that are less used will end up unmaintained 14:09:57 irl: hmmm, that's interesting :) 14:10:46 this is what we have atm: https://lektor-staging.torproject.org/community/staging/relay-operations/ 14:10:58 there's more content behind each section 14:11:33 that list of technical setup guides is going to get very large 14:11:36 I was thinking that the bridges section would be linked out from the main page 14:11:39 irl: i was thinking to merge this content https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy into the new website 14:12:07 irl: yeah, maybe we do subpages... or subsubpages 14:12:26 there are more guides here https://support.torproject.org/#operators 14:12:35 "How to run an {obfs2,obfs3,obfs4,fte,meek,snowflake,ssh,tls,websocket,relay,exit relay} on {Debian,Fedora,Arch Linux,Alpine..} on a {VPS,Docker,...} 14:12:49 we should replace them with a link to a properly maintained one if they are not being maintained 14:12:52 emmapeel: they aren't guides, they are just 'snippets'. 14:13:07 well, but they go unmaintained too 14:13:29 the whole support.tpo is unmaintained but that's another thing 14:14:05 the tool i used to make what i linked above is called Twine, and it is used for interactive fiction to have choose your own adventure stories, where decisions you make can take you to any other point in the story graph 14:14:11 /o\ ;) 14:14:23 ggus: what i mean is that is better to replace unmaintained content with a link to a maintained content, than upgrading updating it, because we should try to make things easier to maintain. if we have several copies then some go outdated 14:14:26 i think we should have relays {non-exit,exit} documentation in the community.tpo 14:14:38 i think having a hierachy makes it difficult, you might get a little through the relay guide and find you don't have the network bandwidth for a relay, and you want to jump to configuring a bridge instead 14:14:55 but maybe you've already decided you want to run on debian on a vps, so you shouldn't have to go through all that again 14:14:56 there is the first section on types of relays though 14:15:27 irl: I see your point though 14:15:59 we need something to get started with that we can iterate on though 14:16:11 because right now we need this live by the end of June 14:16:17 yeah, and the text that is in the thing i linked is from those starting points 14:16:23 so it is still useful to produce this text 14:16:28 and it's been hard enough to get the content created as it is :) 14:16:39 emmapeel: but first the guide should exist somewhere that i believe it shouldn't be trac. 14:16:50 +1 for not trac 14:17:12 yes, not trac cause it cannot be localized. i also agree 14:17:22 with my l10n hat 14:17:23 yup, also I don't think we should have multiple copies 14:18:12 ok, so to summarise, we have some basic content and layout and we should think about how we iterate on that to make it more intuitive and easier to maintain 14:18:49 shall we move on to user testing section? antonela any movement on that? 14:18:50 (this sounds good to me) 14:18:55 irl: i like this wizard thing like "choose your onion adventure", but having a whole document explaning relays is really needed. this adventure could be build on top of it. 14:19:46 not really :( wanted to work on that this week + ui review of community. Let's hope for tomorrow 14:21:04 ok, no worries 14:21:19 let's move on to training section 14:21:26 ggus: how's that going? 14:21:53 also I would like to say that it's ok if the content is not perfect 14:22:06 we will likely end up publishing what there is and then iterate on it 14:22:28 we need to think about how we do this in a way that it's compatible with localization 14:22:41 because we don't want to annoy the translators by changing the text constantly... 14:22:48 yes 14:23:21 well, by now i have the community portal hooked to the andbox in transifex, so we dont really alow translations. but i need to move it for the translations to start 14:23:43 we should get rid of all the placeholders before that and only put real stuff there, even if is not all 14:23:46 but reviewed content 14:24:19 so, by now feel free to chagne the phrases etc, but once it is translated plesae take that into account 14:24:34 pili: we have done so far about tor browser, tor browser for mobiles, onion share; about the tor network (how to setup relays); about onion services; how to be volunteer(almost done) 14:26:01 is that all of it then? :) 14:26:19 or are there some more subsections to be written? 14:26:49 I need to check the document that Alison was writing about good practices 14:27:29 emmapeel: ideas on how to translate the .odp files? 14:28:04 ggus: please not 14:30:02 pili: i'll share all the files with you today. Beside the files that I already shared last week with clash and you. 14:30:02 great, thanks :) 14:30:02 ggus: i think you can generate an .odp from the website pages but we dont have the possiblity of adding an odp to a translation platform i think 14:30:02 i need to go to another meeting, talk to you soon. 14:30:02 thanks ggus ! 14:30:02 emmapeel: yeah, i know. so maybe we should extract the strings? 14:30:03 flexlibris: are you around? any updates on the outreach section? 14:30:03 I guess that's how to be a volunteer though 14:30:08 ggus: yes, and put them in lektor 14:30:21 then you can make an odp with the translations if you really need one 14:32:17 ok 14:32:22 I'm moving on 14:32:35 localization we spoke about already 14:32:40 onion services... 14:32:47 I need to poke asn about this ^ 14:33:05 or start ripping off content from rise up and alec muffett and do it myself :P 14:33:51 Shall we talk about the illustrations next? 14:33:54 hehehehe well if it says something bad maybe people will react and make it better 14:34:05 emmapeel: that's my strategy ;) 14:34:13 pili i sent you an email alon sent to me 1h ago about the illos 14:34:19 I got the language\translations illustration ready for review if you want to have a look 14:34:20 yup! I just saw 14:34:27 ahh Alon_Braier is here o/ 14:34:30 oh i wanna look 14:34:31 I like it, let me share with the rest :) 14:34:52 I got a link 14:34:53 https://drive.google.com/file/d/1JLmOP0pjOH_aMZMV8-QWGFX0INV-aCSs/view?usp=sharing 14:35:28 even better ;) 14:36:42 aaagh ggogle again 14:37:01 https://share.riseup.net/#zBjs0YS5oaT80yNPyFwL2g 14:37:04 there you go ;) 14:37:05 thanks! 14:37:36 is me!!!! 14:37:36 any feedback for Alon_Braier ? 14:37:43 i love it 14:38:02 +1! 14:38:25 is a lot about translation... not sure how to show 'localization' tho.. 14:38:33 like something about local but anyway i have no idea 14:40:43 btw, you can see the progression of the illustrations here: https://dip.torproject.org/web/community/issues/30 14:40:43 at least for localization 14:40:43 if people are interested in the iterations :) 14:41:16 any changes anyone would make? 14:41:17 lovely that we can use dip for this 14:41:24 I love the third iteration 14:42:03 ggus: that reminds me, I'm nearly done with both the presentations, just need to update with the new TBA designs 14:43:16 thanks clash ! 14:43:48 ok, I think we're happy with that, thanks Alon_Braier :) I'll also send to the list so those who are not here can comment on it if necessary 14:43:54 but I think we can move ahead with this one 14:43:58 yep 14:44:19 Great! thanks everyone 14:44:54 there's 2 more illustrations to do? 14:44:59 training? 14:45:04 or just training? 14:45:07 I think this is the last one 14:45:09 sorry, I've lost track a bit 14:45:10 aaah 14:45:19 I've completely lost track then :P 14:45:48 I'm just updating gitlab with the rest now 14:46:17 is there one unified place where all design content is? 14:46:42 clash: hmm, depends what you mean by all design content, but the answer is no regardless... :) 14:46:47 there's the styleguide 14:46:56 and we've recently moved this project to gitlab 14:47:06 but there's probably content all over the place 14:49:05 i'd like to have everything in gitlab, im working for it 14:49:31 ok, one last thing i had for today was that isabela had the idea to add these illustrations on the community portal landing page 14:49:58 I started playing around with what this might look like here: https://dip.torproject.org/web/community/merge_requests/3 14:50:21 but I couldn't quite get it to work, so I would appreciate a review when someone has time 14:50:48 the illustrations are not the latest ones anyway but it was just to get a feel for how to write the template, etc... 14:51:13 are people happy with that 14:51:18 yes, i talked with isabela about it 14:51:25 i can review your pr 14:51:29 so we will have the illustrations both on the community portal landing page and the specific section pages 14:51:48 thanks antonela 14:51:49 yeah nicer 14:51:58 more illos better 14:52:01 I haven't added any classes to the images div so it would look horrible even if the images loaded properly :P 14:52:41 ok 14:52:46 anything else from anyone? 14:52:52 on community portal or others? 14:53:04 otherwise we should wrap things up as there is another meeting in here after :) 14:53:46 kill da bot 14:54:05 on other 14:54:10 i have a proposal 14:54:26 go 14:54:38 pili: I meant as in all org media, in one place, categorized maybe :) 14:54:45 to add a little button or something at the bottom of the pages with 'submit corrections to this page'that links straight to the repo contents.lr file 14:54:52 clash: not really :( 14:55:03 ah, yes, good one 14:55:08 hiro: what do you think? 14:55:21 because some people has been trying to find a way to send corrections and it is not very easy to find the repo form the website 14:55:28 from 14:55:43 i was thinking on adding a link straight to github's 'edit' link for a page 14:55:52 +100 14:56:07 well, it's never too late :P 14:56:19 or sometimes where the content is if you're not familiar with lektor 14:56:26 we can probably add it to the template 14:56:27 I think we discussed this w isabela a long time ago and she said people should be assigned to content and take care of the content 14:56:42 hiro: yup, but that can just mean reviewing the PRs 14:56:58 ie. for https://support.torproject.org/operators/operators-1/ we add a link to https://github.com/torproject/support/edit/master/content/operators/operators-1/contents.lr 14:57:25 I think this is a UX issue 14:57:47 we could have it yes, but we need to set up a flow to review those prs 14:58:01 also it might be easier to say that if someone wants to contribute that's how you can do it with links and tutorials 14:58:08 I think it might be nicer than just a link 14:58:15 i have been dealing with the input from translators and is a lot of work to find the page etc. i rather review PRs 14:58:48 ok, let's close the meeting and move to #tor-www 14:58:51 #endmeeting