- Srushtika presented an Intro To VR talk
- It was recorded and will be shared!
- https://twitter.com/AnjanaVakil/status/880494234100350977
- https://twitter.com/ioana_cis/status/880490769915576320
- TS content brainstorming
- future Masterclasses topics?
- future Tech Briefings topics?
- TS GitHub
- https://github.com/techspeakers
- Wiki
- Short term:
- Update the wiki at https://wiki.mozilla.org/TechSpeakers
- Mid to long term:
- Transition some of the information to a TS GitHub Wiki
- Keep the Moz Wiki as a "landing page"
- TS toplevel info & links to relevant wiki topics in GitHub (e.g. FAQs)
- Short term:
- Repo
- Searchable list for TechSpeakers presentations
- To be used by fellow TechSpeakers for their own betterment
- Content should be submitted via pull requests
- TS infrastructure (API)
- Improve TS processes by automating whatever could be automated
- Bring the various data sources and processes together under a well-defined API & process
- Do this so we have minimal impact on already existing processes (e.g. event calendar, reporting, etc.)
- Misc Topics
- TS rebranding
- new TS brand/logo/etc compatible with the new Mozilla design language
- TS name bike-shedding
- Is it, should it be "Tech Speakers" or TechSpeakers
- Social media (discoverability) argument:
- https://www.google.com.sg/search?q=tech+speakers vs https://www.google.com.sg/search?q=techspeakers
- Try in private browsing mode
- ...other pro-s and contra-s?
- Dev Outreach - Participation brainstorm
- ...
- TS rebranding
Planning pad https://public.etherpad-mozilla.org/p/TSWikiupdates
Mockup http://imgur.com/a/j2U7W
Mockup http://imgur.com/a/HU4Yi
Similar efforts https://public.etherpad-mozilla.org/p/devrel-talks-2016
The TS program has grown from 8 to 100+ people in the last two years, but a big part of the infrastructural underpinnings are still handled manually, as the methods for the infrastructure were mostly devised ad-hoc as we went on.
For a 100-strong group this needs to change for the program to remain scalable, so we are looking to improve the process in the following areas:
Tracking TechSpeaker activities is important for keeping the program going, while trip reports make it possible to try and gauge the impact some of the TechSpeaker presence to Mozilla's goals and provides useful data to report towards the Mozilla leadership to justify the the spend for funding the program.
Event reports are also provide very handy data for both staff developer evangelists, sponsorship & event support managers and TechSpeakers themselves to decide on future speaking, representation and sponsorship options for an event (Mozilla wants to support great, well-organized and impactful events, and speakers speaking at such events).
-
Current status
- Hundreds of events tracked already in the TS Activity Calendar
- Hundreds of data points from event Trip Reports submitted
- Initial processing of these data completed and automatically imported into the TS API
- Events and trip reports are automatically cross-referenced and linked to the TS(s)
-
Potential future improvements
- Further improvement of the data processing
- Automatic linking of TS Activities to talk topics (using event & reporting data)
This would allow for TechSpeakers' expertise in certain topics to automatically show up in their "profile page" and be searchable. - "TechSpeakers Dashboard" weekly/monthly etc. data visualization of TS activities
- Mozillians.org public data (using the TechSpeakers group)
- Format: JSON API (
json
)
- Format: JSON API (
- 2015, 2016 and 2017- trip report responses
- Format: Google Spreadsheets (
csv
)
- Format: Google Spreadsheets (
- TechSpeaker activities calendar
- Format: Google Calendar (
ical
)
- Format: Google Calendar (
- CFP calendar
- Format: Google Calendar (
ical
)
- Format: Google Calendar (
- Mozillians.org
- GitHub
- Internal list
- Telegram?