Changes between Initial Version and Version 1 of org/meetings/2018MexicoCity/Notes/VolunteerOnboarding

Oct 4, 2018, 6:59:12 PM (9 months ago)



  • org/meetings/2018MexicoCity/Notes/VolunteerOnboarding

    v1 v1  
     4Kat: Difficulties in onboarding volunteers 530PM, room A
     6roles of teams
     8experiences in other organizations
     10- employee onboarding experiences... interns.  where to start.
     12We're bad at it... how do we improve?  designate someone from each team
     13for month at a time.
     15- potentially abusive, not just benefit TPO, but the volunteer: anonbib,
     16irc, mailing lists, absorb. then decide. you're not getting paid.
     18- volunteering on www: invited only days, and public acts. Oct 3 meeting
     19public on volunteering. scaling problem with mentoring volunteers.
     20status of each project
     22- documentation writer=>  determining what they should learn.
     24- voluteering experience. list of what ppl can contribute. too general?
     25not feeling welcomed in tech, mentoring/reaching out. ambassadors by team.
     27- individual engagement works, but not scalable. matter most/open source
     30- method not a static list, knowing the avail resources
     32yes, method, but www site is main entryway.  wayfinding.
     34- old www, new one soon with community portal.  using the tools we have
     35now. redo volunteer page, not exploiting volunteers. SP, br, volunteer
     36work with credit
     38- advisor role in ind studies with credit
     40allocating the actual work for an ind study
     42- if CS studies know it's possible... ppl would appreciate
     44- SP, br as pilot program
     46- bug list, 'word of the day'... 'task of the day'
     48requires coordinator with volunteers
     50- dedicated hire to coordinate...  we have a volunteer.
     52- are bugs categorized.
     54- authoritarian to be telling volunteers
     58- mailing list? here are some tasks to do...
     60requires someone from each team to contribute
     62- as an engineer "how can i help" via various channels. list of topics,
     63widely varied. coordinating party to fixing a bug. on the www to list.
     65- workflow: ask for a task from teams once a month for volunteers. as
     66with deb, which packages need help.
     68email contact, or trac tag
     70- diff paths dev v local meetups.  each team should consider and determine
     72updating the current www page.  context of the teams, requesting, dump
     73on the wiki pls
     75- bar of entry.. process by team
     77- volunteer page redirect to the wiki?
     79brief overview of teams and link to how to contribute
     81- relay ops? phoul... Core TPO at academic conferences, arma 'mobbed' at
     82mcgill. taping CS departments.  volunteering to coordinate.
     84- academic focus, pressure to publish without social change. crypto
     85contributions v academics. publishing about anonymity systems.
     87- academia. research, relays by students, etc.
     89- non-tech relays and contributing to TPO on campus
     91- determining the audience on campus, speakers 'transforming' students
     93discussing first steps listed...
     951. update volunteer page
     96@www ppl
     982. ask teams to contribute tasks to do
     1013. summarize teams and categories
     103(email draft to internal@ about contributing)
     105losing volunteers by not having a next step
     107- academia and industry unique connection via Tor
     109- PETs as a venue for that. When speaking at campuses... mention PETs
     111- money for stipends to get more ppl to PETs, sources for funding and
     112criteria for stipends
     114- Goog Summer of Code. TPO not approved. Summer of Privacy as alternate.