15:59:33 #startmeeting Communtiy Team meeting - 03 Feb 2020 15:59:33 Meeting started Mon Feb 3 15:59:33 2020 UTC. The chair is ggus. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:37 hello o/ 16:00:07 hi everyone 16:00:08 Here's our community team meeting pad: https://pad.riseup.net/p/tor-community-team-2020-keep 16:06:50 let's wait a little bit more, so people have time to update and read the pad with others updates 16:10:57 Hello everyone. 16:11:00 Updated the pad. 16:11:09 * ggus reading the pad 16:13:25 ok, let's start! 16:13:42 kushal: i think we will need to update the tor relay guide since we created rpm.tpo 16:14:11 the relay guide was moved to the community portal last year 16:14:31 https://community.torproject.org/relay/setup/ 16:14:55 kushal: do we have tickets for these changes? :) 16:18:20 kushal: we can discuss later, let's move to the other topic, so 16:18:27 ggus, yup 16:18:32 I mean let us move on. 16:18:35 * Next #DocsHackathon 16:19:02 a small recap: last year we did a documentation hackathon and it was very nice 16:19:36 it was the first time running this event, and we have more documentation work to do 16:20:14 i was thinking we could do this in march, since it's the same period for Outreachy applicants to contribute to Tor (if we apply again) 16:21:03 here's the blog post we did last time: https://blog.torproject.org/join-tors-docshackathon-next-week 16:21:14 what we want to improve this time? :) 16:21:21 (on the process) 16:24:26 i feel that the hackathon was great to get new people contributing, but then we didnt managd to keep them busy afterwards 16:24:38 im thinking specially on rotationmatrix 16:24:59 keep them busy/connected 16:25:30 yes, agreed 16:26:09 for the rest, we got a lot of updated content and the hackathon worked very well i think 16:26:11 I think we don't have some easy tasks for volunteers to followup 16:28:04 emmapeel: do you think we should run a localization hackathon too? 16:28:20 hmmm 16:28:33 not sure. i will ask erinm what she thinks 16:28:52 ok! 16:29:05 i can try to prepare tickets for next hackathon. 16:29:26 we will need a few programming related tickets for the hackathon in nullcon.net 16:29:34 it is on 6-7th March. 16:29:48 But, for now, we will need just some text as announcement. 16:30:03 let me add to the pad, kushal 16:30:13 programming for tor browser or can also be lektor? 16:30:47 emmapeel, anything which will help Tor. 16:30:52 i added as a topic, so we can discuss 16:31:19 we ned a lot of help with lektor :S 16:31:22 let's go over docshackathon and then we can brainstorm a little bit on hackathon in nullcon 16:32:20 emmapeel: we're going to use the same tag as the last docshackathon? 16:32:53 ggus: for me makes sense to have the same tag if we do a docs hackathon 16:33:19 yes, ^^ same tag 16:33:37 there is still some stuff there 16:33:40 +1 16:33:49 https://dip.torproject.org/groups/torproject/web/-/issues?label_name%5B%5D=DocsHackathon&scope=all&state=opened&utf8=%E2%9C%93 16:34:21 yes 16:35:14 maybe for next hackathon we need to figure out the whole gitlab-accounts stuff, also another problem we had was 2 people working on the same ticket... we should be sure to assign to the people working on the issue to prevent that 16:35:48 I already started working on several of those issues 16:37:44 c1e0: yes, some of them are waiting to be reviewed in github, we can follow up on this friday sync meeting those that are waiting my review, so we can merge 16:38:21 march looks a good month for the docshackathon? yes, no? 16:38:24 i am available to review stuff, but i dont want to step on ggus toes 16:38:37 so if you tell me i can review n merge 16:38:40 o/ 16:38:46 ey rotationmatrix ! 16:38:51 o/ 16:39:04 i like March for the docshackathon 16:39:47 do you think 1 week was ok? or should we have more time? 16:40:07 I think one week was enough 16:40:22 it was enough although we took a lot on reviewing the results 16:40:27 Because it takes over a bit from our other work :) 16:40:48 one week is cool to get peope like stephw also aware of the stuff 16:41:03 yeah 1 week was good. the weekend was definitely a plus for people who were busy during the week. 16:42:07 nice, any other ideas/insights about docshackathon, rotationmatrix? 16:42:22 yes. also now that we have the docs prepared maybe people will be able to start before 16:43:44 i am a bit afraid of the whole setup for PRs etc 16:43:59 the assigning people on issues was my other one. would be good for preventing duplicate PRs 10 minutes within each other. 16:44:27 is there a possiiblity of people being able to open their own accounts for the hackathon? 16:44:42 i mean in dip.tpo 16:45:20 hm, i think it depends if we will have migrated to gitlab until there 16:45:31 can guest account open merge requests for hackathons? 16:45:40 because there's the spam problem 16:45:43 rotationmatrix: can in github 16:46:26 but in dip atm there are some repos you cannot really open PRs, something is going on that triggers 503s when you try to create PRs 16:46:32 I would be interested to know how having a gitlab account made the process easier for people... I created a bunch that were never used... :) 16:46:34 ah okay 16:46:55 I personally think it’s easier to do a PR on GitHub 16:47:00 pili: yeah you are right. i am not sure what is the proper process, not sure if dip will be the place 16:47:04 Both to review and merge 16:47:05 ^ agreed 16:47:21 yeah, i think PR on GitHub is easier, since people have accounts there 16:47:42 yes, unless you are iranian 16:47:58 emmapeel: good point 16:48:39 true, but i think even tpo is blocked in iran, no? 16:48:56 so our own instance would be an issue too 16:49:01 own gitlab instance 16:49:15 not sure. i remember we didnt wanted to promote the use of github or something 16:49:19 as tpo 16:50:46 i think we can add something like:"if you don't like github, you can use gitlab.com or you own selfhosted git repo, just ping us on the irc channel" 16:51:29 ^^ this sounds good. 16:51:30 yeah that is perfect 16:51:34 "submitting the update by email, docx or in a pad will not be accepted" 16:52:05 hmmm that sounds bad 16:52:06 no format-patch? 16:52:55 format-patch by email will prevent reviews per-line and comments 16:53:04 better something public for the hackathon 16:53:10 yes 16:53:13 so other contributors can also evaluate 16:53:16 ah good point 16:53:35 * rotationmatrix didn't know that was a thing. lol 16:53:38 (not necessary for ALL contributions to the website, but in this case i htink format-patch is not an option= 16:53:41 ) 16:54:31 ok people, we only have more 5 minutes 16:54:39 anything else for docshackathon? :) 16:54:52 side question, does github ban iranian users due to us sanctions? 16:55:01 yep 16:55:10 okay 16:55:18 due to an overzealous interpretaaion of US law i would say 16:55:25 https://www.theverge.com/2019/7/29/8934694/github-us-trade-sanctions-developers-restricted-crimea-cuba-iran-north-korea-syria 16:56:45 also, don't worry about my absense. it was a combination of new job + trying to get an irc bouncer running. lol 16:57:14 :) rotationmatrix 16:57:19 irc bouncer: a life change! 16:57:32 nah. bouncers are MITMs! 16:58:00 ikr! was always losing history when my laptop autoslept and disconnected webchat. 16:58:05 ok folks, i'll close this meeting. kushal, i have added a task to the nullcon hackathon, but ping me during this week 16:58:21 lol! yeah, reason why i had to run my own. 16:59:00 #endmeeting