Workshop, Manuals with a gender perspective, IFF, Valencia
From Gender and Tech Resources
Revision as of 11:13, 15 July 2016 by Alex (Talk | contribs) (Created page with "{{Activities |Title of the activity=Producing guides and self-learning resources for tackling gender-tech based violence: What is there and what is needed? |Category=Gender an...")
Title | Producing guides and self-learning resources for tackling gender-tech based violence: What is there and what is needed? |
---|---|
Category | Gender and Tech |
Start | 2016/07/15 |
End | 2016/07/15 |
Hours | 2 |
Scale | |
Geolocalization | 39° 28' 11", -0° 22' 35"
Loading map...
|
Organisation | Tactical Tech and Coding rights |
Website | https://codingrights.org/ |
Target audience | People engaged in produced learning resources around privacy and security with a gender perspective |
Number of participants | 30 |
Context and motivations | Over the past two years, there has been an increasing production of guides and other self learning resources oriented at better understanding what is violence against women (online and offline) and how to document and share about the initiatives, processes and tools that are challenging it under its different forms. The workshop will address this panorama of resources departing from the participants experiences and their needs in relation to those materials. When mapping what is there and what is missing, they will draft guidelines for shared good practices when producing new materials (such as how to not reinvent the wheel and duplicating upstream work, thinking ahead the maintainability, translatability, feedback, peer review and overall sustainability of those resources) and will reflect on how to develop materials that are ethical, inclusive and accessible. This workshop should enable people engaged with the production of self learning resources around privacy and digital security to better understand how to include a gender and intersectional perspective, inasmuch as it should enable networking among people planning to produce gender-related materials in the field of privacy and digital security. |
Topics | manuals, gender, interseccionality, not reinvent the wheel, mapping needs |
Links | https://gendersec.tacticaltech.org/wiki/index.php/Manuals_with_a_gender_perspective |
Media | [[File:]] |
Agenda | Presentation and introduction should not take more than 25 mins: Coordinators of the session introduce the objectives of the session, agenda and how we will work (methodological steps) +
Quick round of introduction people in the room: Mapping knowledge and experiences in the room with production of guides (need to think about a good dynamic to do that) In order to make the most of the session, we will work in 4 or 5 small groups (between 4 or 5 persons) around different exercise and/or common guideline and will then share all together – 45 mins |
---|---|
Methodologies | > A. Mapping what is there in relation to guides on privacy and security with a gender perspective or that can be easily re-purposed with a gender perspective:
Could you review this list and let me know if there are more resources on your side we need to add? https://gendersec.tacticaltech.org/wiki/index.php/Manuals_with_a_gender_perspective Idea would also to have participants reviewing and adding their own references too Mapping also what is not there and is needed? And why is it needed and/or why is not there? Format - other learning resources (video, graphics, movements) - interactions and achievement (games) - more art Content: - explain what is feminism - content for people with disability, more readable fonts and accessible images - digital story telling - generational gap (older people) - trainers content > B. Mapping our own community, improving practices: What are good practices for developing guides stand alone and guides with a gender perspective? Can we work on those guidelines (see proposal below)? + Understanding our own challenges and what we could do for/with the others? Before producing a new manual some questions we should askː Don't reinvent the wheel Are you duplicating upstream work? If a similar manual is already available Who's behind it? Is it a long-term project or a one shot one? Can you continue or complement their work? Who's the public and what are the objectives ? What are their security & technical levels? What are their comprehension about feminism? Who will produce/develop it and for whom (generational gap, geographical location, socio-demographic dimension)? Will your manual will be more about tools and how to configure those, or will it be more about threat modelling and/or behavioral processes? Under which license will you distribute it and which rights will you grant third parties (access, use, copy, remix, etc)? Credits your reviewers and experts that have provided you with feed back!! How will you maintain it? This encompass questions about frequency of updates needs depending of the tools and processes you will detail, and about processes you will run to engage your community in updating contents with you. How will you get feedback and peer review from readers? Will you be able to include all the feed back? (Some criteria will deal with correctness, completeness, up to date). Remember to always indicate the last date the manual has been updated/released. How will you achieve or not translation & translatability of your manual? Which type of platforms will you use for achieving the translation? Will you achieve also cultural translation for instance? Accessible for disable people Will you provide further support to the readers such as a contact mail or a hotline? How will you ensure that your contents are ethical, inclusive and trans-queer-feminist "approved"? How will we monitor the impact of our self learning resources/Impact Assessment methodologies? How the distribution will be done? What is the target public? Think about potential partnerships (researchers, academia, volunteer translators etc) |
Resources | |
Gendersec |
Feelings | The session enabled to identify other persons and organisations engaged in producing resources and was useful for putting in common some good practices, inasmuch as for mapping what was already there and accordingly which resources were needed |
---|---|
Feedbacks | People like it! |
Start | |
Stop | |
Keep |