18:00:52 #startmeeting 18:00:52 Meeting started Wed Jun 28 18:00:52 2017 UTC. The chair is flexlibris. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:52 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:26 who is here for the meeting? 18:01:31 o/ 18:01:36 hi 18:02:45 sukhe and kat5 too I presume? 18:02:49 is ChillyPhoul here? 18:02:57 hi flexlibris. yes here for the meeting 18:03:02 Yep. 18:03:22 okay let's get started 18:03:28 who has a status update and would like to go first? 18:04:09 okay I can go first 18:04:32 I've been doing a lot of planning for the upcoming October Tor Meeting in Montreal 18:04:36 we'll send the save the dates out pretty soon 18:04:58 ChillyPhoul and I have been working on an issue that has affected a lot of Windows 10 users 18:05:29 this software called Trusteer Rapport, when installed in Windows 10, makes Tor Browser fail to open 18:05:50 what kind of software is this? 18:05:58 and Trusteer Rapport is very popular because many banks require it. so we've ChillyPhoul and I have been working with the communications team on dealing with this. 18:06:09 Samdney: it advertises itself as "anti-fraud" 18:06:16 so that is ongoing 18:06:56 atagar and I, with feedback from many people, finally got the contributor guidelines in a place to send them out to tor-internal for the proposal period 18:07:20 and arma2 is helpfully spearheading that proposal 18:08:03 ChillyPhoul and I and the comms team are also looking into a grant that would allow us to hire someone to do support and communications work 18:08:42 ChillyPhoul also set up a wiki to serve as an interim support portal until we get the funding to make that a reality. I'm gonna do some edits of it and then we'll push it out via social media and the blog. 18:08:59 and then lastly I've drafted a little bit for the community team roadmap, which I'd like to talk about after updates 18:09:05 and that is it for me 18:09:26 flexlibris: Is the idea to continue adding to the wiki? Will there be a process for how to do that? 18:09:55 kat5: yes, in the same way that we've been adding content to the git repo that we wanted to eventually put on the support portal 18:10:10 So through ChillyPhoul, then? 18:10:18 the process for how to do that is to tell ChillyPhoul that you want to do that 18:10:19 yes 18:10:25 Cool. Thanks. 18:10:33 we won't leave the wiki open for edits for obvious reasons 18:10:38 I hope we have an update soon about the funding 18:10:54 cause we don't want to put too much effort into a stopgap! but at least the content will all be useful down the line. 18:11:06 any other questions/comments? 18:11:48 * ChillyPhoul is here now 18:11:50 Sorry for being late 18:12:01 no worries 18:12:09 I just gave my update. do you want to give one? 18:12:28 (sorry to immediately put you on the spot. someone else could also go.) 18:12:38 I can go next just to give ChillyPhoul some time 18:12:47 go for it sukhe :) i'll start writing mine up while you go 18:12:52 thanks 18:13:24 there are two Tor talks in Toronto in August: https://lists.torproject.org/pipermail/tor-community-team/2017-June/000048.html 18:13:52 other than that, flexlibris put me in touch with some people at SFLC India (http://sflc.in/) 18:13:58 sukhe: yay! did you put them on the events calendar? 18:14:09 we are planning talks for journalists and NGOs in September but that's not finalized yet 18:14:42 flexlibris: I will add them today; I was waiting for one of the events to update their website but they said they will do it in July so I will just go ahead and add the event 18:15:18 the SFLC India thing is particularly interesting because they have done talks in the past but in their own words, their talks were "limited" 18:15:35 sukhe: great 18:15:36 so let's hope that works out... that's all from my side 18:15:51 really hope that this one works out! 18:15:56 yup! 18:16:28 thanks sukhe. anyone have questions or comments for him> 18:16:29 ? 18:16:57 okay then -- anyone else have an update? 18:17:21 Last week Roger, myself, Tom, Alison and others did an AMA for LocalizationLab, most of the questions were about Tor Browser and blocking. We are also looking into creating more Tor Browser's for languages we do not yet support, but have complete translation coverage(#20628). This week was also the first GSoC evaluation period, which went smoothly and is now complete. Like Alison mentioned, we've 18:17:27 also been looking into this Trusteer issue, and ive been attempting to recreate the issue in a test environment, however have so far been unsuccessful. I also finished adding the content from our git to the wiki. kat5, I will also be adding your edits to the operator portion of the portal, sorry that hasn't been done yet, somehow your edits email completely got away from me. 18:20:16 We also came to the conclusion during the AMA that having a nightly transltor build of the Tor Browser would be helpful for translators to do proper review of their strings, so that is also in the works. 18:20:24 translation* 18:20:33 heck yeah 18:21:10 Thats all from me 18:21:43 questions/comments for ChillyPhoul? 18:22:08 kat5: just saw your message on Twitter (Sorry, was asleep until 15 minutes ago) 18:22:12 np 18:22:49 I will get your edits added today, and then yes, please feel free to go through and make edits :) 18:22:50 anyone else with an update? 18:22:59 I've just been continuing to manage t-shirts. 18:23:59 (i am here reading backlog; don't wait up :) 18:25:02 arma2: :) 18:25:30 thanks for yr diligence kat5 18:25:47 sukhe: be sure to put tor related talks on the events calendar on the blog! 18:25:58 arma2: read a little further! 18:26:12 oh good 18:26:24 any more updates? if not, I will move on to talking about the Community Team Roadmap 18:26:44 i am wanting us to make a community -> tor network trac component 18:27:29 we periodically want to do things to make the tor network operators happy, and those tickets have no home 18:27:35 let me know if that is a terrible idea :) 18:27:42 arma2: I like this idea 18:27:42 arma2: sounds good to me 18:27:47 * ChillyPhoul likes this idea too 18:28:07 While speaking of Trac, I'm also planning to turn our "translation" component into a keyword, like ux-team. 18:28:15 maybe one of these days we can make the community team owner of the community component! 18:28:31 i can fix owners right here 18:28:38 yahooo 18:28:44 speaking of which, community -> outreach still defaults to nima and kate 18:28:54 nima might still be a reasonable choice, but kate probably isn't 18:29:01 what shall i change it to 18:29:15 can it be tor-community-team@lists.tpo? 18:29:16 or rather, what shall i change each subcomponent to, if any 18:29:32 if it can't be that, then I guess it should be alison@tpo 18:30:02 i think it needs to be a trac user. but there is one called "metrics-team" so we should find out how that works. 18:31:54 maybe we should move this to after-meeting 18:31:58 Creating a user with the community list as its email address would likely work. Metrics might have a less messy way to do it. 18:32:15 ChillyPhoul: good idea 18:33:13 arma2: do you have any other updates? 18:33:28 please continue 18:33:33 (i am still booting) 18:33:38 for sure 18:33:45 okay great, let's talk about the roadmap some 18:34:20 here is the draft on Storm: https://storm.torproject.org/shared/5SXgWWnyQtkp8sOUFrdyOvi0WaPVoTgbmhMIGEr-QkV 18:34:27 I shared it on the mailing list a week or so ago 18:34:33 along with some other team's roadmaps 18:35:13 we're pretty late in the year to be doing this, but I would like to finish out the rest of the year so that we can get into the habit of making a year-long plan, and then ideally get to work on 2018 at the October meeting 18:36:09 * ChillyPhoul likes this plan 18:36:13 what I'd like everyone to do is look over the todo items and add anything that's missing. any team priorities, any projects that you think we should be getting to before the end of the year 18:36:42 good idea 18:36:46 and think about your own tasks within that...when you will have things done, what dependencies you have with other team members or other teams 18:37:06 the goal of these roadmaps are not just to organize our own work, but create better teamwork among teams 18:37:08 One question: Some tasks like RT tickets and translation have no "end". Should these just be added to the top list, but not the monthly breakdowns? Technically they are just every month. 18:37:18 ChillyPhoul: good question 18:37:38 I think that we should put them in every month at least 18:37:52 because let's say another team looks at our roadmap...they might see some dependencies there 18:38:00 for example, getting feedback about common user issues 18:38:04 That makes sense. :) 18:38:13 and actually we could even put that into the roadmap as like an every two-months kind of task 18:38:51 or bonus, line it up with new tor browser releases 18:38:57 yeah! 18:39:04 since those are in theory scheduled 18:39:16 yup 18:39:33 I think right now the main things are identifying the priorities. they don't NEED to be organized in the schedule just yet. 18:39:54 we can spend some time looking at the other roadmaps and talking to other teams about things like what arma2 just identified 18:40:25 this week though -- please list your projects, tasks, regular work, whatever you think belongs in here 18:41:31 anyone have questions or comments about building the roadmap? 18:42:58 okay, the only other thing I wanted to chat about was the new potential support position, but I actually think I want to table that until we know whether or not it's going to happen. 18:43:27 anyone have anything else to discuss? 18:43:42 roadmap question: is there currently no schedule for the code of conduct? 18:44:11 catalyst: not yet. I think we could sort that out relatively easily, given how many months other proposals have taken. 18:44:49 is there a draft anywhere? or, six contradictory drafts? 18:44:50 This is really early, however I am discussing with flexlibris, arma2 and Shari about modifications to my role as support. I'm looking at handling blog comments / #Tor support, likely blog comments first. Will have more of an update on that next meeting. 18:45:47 arma2 and catalyst: yes, I have a draft that Lunar and I put some work into last year. I don't know of any additional, contradictory drafts. 18:45:48 arma2: i kind of like the approach isis took with one github repo, which was "oh, no Tor CoC yet? let's use Rust's for the time being" 18:46:13 catalyst: I personally love the Rust CoC and the draft I have currently has heavily borrowed from it 18:46:18 flexlibris: cool! 18:46:21 another idea for the roadmap, not urgent since the team is small: we have long wanted a 'volunteer coordinator' person. somebody who knows what the interesting projects are that need help and that are suited for random folks who come in off the street (twitter, irc, etc). one next step there would be to coordinate with the various other projects to get them to identify 'easy' tasks. and then publicize the easy tasks and try to follow up. 18:46:26 ChillyPhoul: I'm so excited that you're doing this 18:46:41 catalyst: yes, but, yawning did the same thing where he applied a coc of his own. that way lies... unclarity. 18:47:02 codes of conduct are for groups of people, not software codebases. i think. 18:47:17 arma2: I would really like to have someone in this role, ideally funded 18:47:22 open source codebases ideally have communities surrounding them 18:47:45 I could use that person rn. :-) 18:47:47 flexlibris: me too. something to write down to remember for the future. 18:47:50 * Samdney still thinks code is mostly written by people ;) 18:48:08 arma2: I have a meeting with Tommy very soon to talk about outreach ideas and getting money for them 18:48:16 kat5: rn ? 18:48:19 a volunteer coordinator is on my list of what to discuss 18:48:41 right now. Well, not *right* now. 18:49:13 (I’m here and watching, but don’t mind me =).) 18:49:29 t0mmy: hey! 18:49:51 * Samdney is thinking if she can help somewhere ... 18:49:58 flexlibris: sounds good. i think we have wanted this position for a long time, and it's been unachievable the whole time. i think that means we should think about redefining it. 18:50:08 arma2: indeed 18:50:26 we should do that soon 18:50:37 like, before the October meeting soon 18:51:00 I will put it on my todo list and follow up with you 18:51:18 btw, are you 'alison' or 'flexlibris' on trac? 18:51:27 arma2: alison 18:51:28 btw, I already hang around a lot also on the meetings of the other teams, is this helpful for something? ;) 18:51:40 not sure why I went and made that confusing 18:51:56 Samdney: you can tell us things that happen in those meetings that you think are relevant to this meeting 18:52:00 samdney: keep an eye out for tasks that look bite-sized and good introductions? 18:52:26 will do :P 18:52:28 i.e. encourage them to use the 'easy' tag or the like on their tickets 18:52:49 or "intro" for things that are good introductions but aren't so easy :) 18:52:59 yes. each time will have their own convention. 18:53:05 s/time/team/ 18:53:16 flexlibris: i moved the owner of community -> training from kelley to you. i haven't seen kelley in a long time. 18:53:35 flexlibris: i guess more generally, maybe we should shrink the set of subcomponents, if some are being totally ignored 18:54:03 I dont think the training one has been used since Kelley and I worked on the old curriculum 18:54:10 arma2: I'll look through them 18:54:28 chillyphoul: does that mean i should set you as the subcomponent owner? ;) 18:54:41 flexlibris would make more sense, I dont give nearly as many trainings. 18:55:13 ok 18:55:27 flexlibris: i guess put "trac triage" somewhere on the roadmap? 18:56:12 (added) 18:57:34 yeah I don't think I've ever used the training one 18:57:37 okay, anything else for this meeting? 18:57:42 great. I'm calling it. 18:57:43 #endmeeting