Opened 3 years ago

Closed 11 days ago

#20305 closed task (fixed)

organizing new speakers-bureau list

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Community/Outreach Version:
Severity: Normal Keywords:
Cc: lunar, ahf Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In Seattle, I spoke to a bunch of people about a "Tor speakers bureau" idea -- basically a central group on the Tor side who keep track of what speaking things Tor people are doing, and learn about new speaking things (both proactively and by being the funnel where we send all the ones that invite us somewhere), and track what opportunities we're missing, and generally prioritize to make sure we're doing our conference outreach effectively.

Then I spoke to David, who said a "somebody should" sentence very close to a "Roger, you should delegate more" sentence.

So, I hereby put David in charge of moving this idea forward. :) With a supporting cast of Roger, Kate, Shari, and Alison.

Among the next steps:

  • We probably want some public address for receiving speaker requests; and we should list that public address somewhere public.
  • We may or may not want a separate internal discussion list. Maybe not yet?
  • We should probably make a simple wiki page to explain what the list is for, so people can read about it and get up to speed if they weren't in Seattle.
  • We should try to extract the list of *currently known* talks that Tor people are doing, so it is in one place.
  • We should figure out good ways to make a public list of these talks, and keep it updated regularly. The old way was "on the Tor blog calendar" but that is non-ideal.
  • We should accumulate a list of good Tor speakers, and what they're good at speaking about. These can come first from inside our community, but I think we'll all be happier if we start learning about external people who are great at speaking about Tor -- especially if we want to get good global coverage to be able to e.g. answer Campus Party invites from Brazil.
  • One of our many goals there should be to match up speaking experience with how public or high-profile the event is, so we can get more Tor people out there talking about Tor, while still getting the *right* people in the most important places.
  • Later, we should tell the world that we want to go explain Tor to them, and here's the contact address if you want one of us. We should expect to get many "I can't pay travel but I'd love to have you", and a smaller number of "I can pay travel". We should find the right balance, since sometimes the places that can't pay are the places we most need to be represented.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by lunar

Cc: lunar added

comment:2 Changed 2 years ago by ahf

Cc: ahf added

I've only done presentation about non-tor things at smaller events, but as an inexperienced talk presenter I think the following would be useful:

  • Have a set of Tor people who are up for reviewing a talk proposal for an event before it is submitted, the outline of the presentation, and the actual slide deck and come with constructive criticism to the submitter. I remember trying my luck with submitting a talk proposal for Talla for CCC and I had no clue how to make it look "shiny" and become something they might accept.
  • If we happen to be multiple Tor people at an event and some are doing a presentation it would be useful if the other Tor people in the audience would be able to come with constructive criticism after the talk. This can be everything from "stop saying 'uhm' after each sentence" to "your C code example had a buffer overflow on line 3!" and so on.

During the blue sky session in Amsterdam there was a stick-it note with "a generic slide deck on Tor with tons of notes in it". This could be worth considering as well if someone is up for maintaining it :-)

comment:3 Changed 11 days ago by gaba

Owner: dgoulet deleted
Status: newassigned

Releasing some old tickets.

comment:4 Changed 11 days ago by dgoulet

Resolution: fixed
Status: assignedclosed

This is now handled by the community team mostly...

Note: See TracTickets for help on using tickets.