Training Knowledge Share

From DevSummit
Revision as of 22:12, 22 November 2016 by Jucsanch (talk | contribs) (Created page with "Session to synthesize providing support for digital security training efforts * Removing conversation from white male dominated space * Interested in building training capacit...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Session to synthesize providing support for digital security training efforts

  • Removing conversation from white male dominated space
  • Interested in building training capacity
  • Responsibility around providing security guidance
  • Sharing better resources in newsroom context, figuring out where solidarity fits into this conversation and around threat modeling
  • Roundup post of existing tool kits, tool kits that are going out of date
  • Digital security training and community building in a domestic context
  • Encountering lots of people who want to train, but do not have an audience
  • Education backgrounds, issues with the way that trainings are done
  • Not just what resources are out there, but think about ways to build training approaches that are less “colonial”

BRAIN DUMP!

  1. Add to wiki list of resources: [TBD]
  2. Organizations, forums, networks to be aware of for those looking for resources for training
  3. Events and meet ups – both local and global level, large and small


EVENTS

How folks who don’t feel like experts engage with events – how can they?

  • Internet Freedom Festival 2017 (Valencia)

Diversity & Inclusion Fund – provides travel support for those with sessions in the final approved program

  • RightsCon 2017 (Brussels)

Not entirely positive on travel support, but large scale gathering of useful and involved folks

  • Allied Media Conference (Detroit)

Collaborative support for attendance, tend to be proactive in outreach to get engaged folks to come

  • NICAR (TBD)

Journalists only, closed network, but can get in if you pitch a session that is accepted


TAKEAWAYS

What are the key takeaways from this conversation over the past few days

  • Realization of the shelf life of digisec tools and resources
  • Need to break tool based training models, parachute models
  • We need to make resources and materials more remixable
  • Have help desk resources, trainer help desk for assistance
  • Coming up with language that reflects and fits our movement models
  • Accessibility of information to non-native tech users
  • Language, cultural relevancy, who is actually benefitting from these trainings?
  • How much of a barrier is the localization question and language skills problem
  • New thing! Potential risk of longevity related to tools that we’re recommending? Ex. Signal
  • Keeping software dev projects mission centered and supported
  • Alternative training models?
  • Disentangle “accessibility” and reactionary aspect of Opening Something That Is Closed
  • Become a trainer from within the culture of a movement or community itself
  • Not about delivering a training, its about building a relationship