Hi, here are our meeting notes:
http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-09-02-15.59.html
And here is our meeting pad:
Community team work meeting pad -------------------------------
Next meeting: Monday September 09 16:00 UTC
Weekly meetings, every Monday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress).
Meeting 2019-09-02
Presents: * Gus * pili * Cy * emmapeel
== Updates ==
FORMAT!
Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to community team work). Help with: - Something you may need help with.
Gus: This week: - community.tpo: submitted more content to relay operations section - RT: - RT backlog: answered +700 RT tickets. There are still ~170 new tickets. - Cleaned all the spam from help-es queue. - Suggestion to remove frontdesk email from bridges.tpo: https://trac.torproject.org/projects/tor/ticket/28533#comment:7 - Bridges Campaign: started to reach out some organizations and partners to run Tor Bridges (cc: phw, steph) - DocsHackathon: sent onboarding email to participants. - Contacted UX volunteer (cc: nah) - Sponsor9 phase 3 meeting - partners kick-off - wwww: sync meeting this wednesday. - Write blog post about global south trainings (due sept 10th)
Next week: - Community Team monthly report to Tor Project mailing list - More community.tpo work - DocsHackathon next steps - Work on DRL proposal
Help with: - RT: bridges for users in censored networks
Pili: This week: - help out with docs Hackathon - DRL Proposal - Website Maintenance plans - Sponsor 9 meeting Next week: - AFK - API Days Barcelona
emmapeel: This week: - docshackathon, tails reviewed translations - devised a process to publish code of conduct translations Next week: - reviewing, new langs for lektorz
Cy: This week: - Code of Conduct translation review - *RT (depending my time this week)
== Discussion ==
* DocsHackathon: - First day overview, let's check how things are going (how many participants, how many PRs, issues). - So far: 2 pull requests merged, one in process - tickets closed: - Daily reports to community-team mailing list with hackathon status. - edit button is working but we are getting a lot of feedback and we should answer eventually: https://github.com/torproject/support/issues - #Action: "Suggest feedback" button in support portal to wiki/doc/community/HowToReportBugFeedback instead of GitHub issues