**Ethics Materials**
**SSI Fellowship project (Esther Plomp) with The Turing Way.**
**January 2025**
Relevant People

- Arielle Bennett, Senior Researcher, Open Source Practices, Tools, Practices & Systems, [e-mail]
- Malvika Sharan, Senior Researcher, Open Research, Tools, Practices & Systems, [e-mail]
- Kirstie Whitaker, founder The Turing Way, Executive Director, Berkeley Institute for Data Sciences
- **SSI Fellow, Esther Plomp**, is a member of The Turing Way and will coordinate the project and is primarily responsible for all deliverables and outcomes.

These ethical materials have been based on ethical procedure followed by [JupyterHub /Organisational Mycology](https://github.com/the-turing-way/jupyterhub-orgmyc-EOSS/blob/main/research-instrumentation/ethics-materials.md), available under a CC-BY 4.0 License.

### 1. Purpose and Aims of Research

Esther Plomp has received a SSI Fellowship (2025-2026) that focusses on how contributions to The Turing Way can be facilitated, with a particular distinction made between contributions by volunteers and contributions by paid members. The project is also supported in-kind by the University of Aruba. The project wants to conduct a survey (co-created with Turing Way community members via a focus group session during a Collaboration Cafe), followed up with in-depth semi-structured interviews with members and contributors of The Turing Way. As this study involves human participants and collection of personal data, and may have an impact on The Turing Way community (by individuals donating their time and potentially their personal data) I am seeking ethical approval from The Turing Way community. The project will be conducted as openly as possible, with data collection efforts and preliminary findings shared with the community as openly and quickly as possible.

This study is intended to:

* Identify successes, challenges and opportunities that contributors face when they contribute to The Turing Way
* Identify what paid contributions look like (financial compensation, training, mentoring, visibility, time?)
* Identify if there are any (unwanted) dynamics caused by different types of contributors (volunteer or paid)
* Support both paid and volunteer contributions to the community, developing strategies to avoid differentiation between these types of contributions
* Inform the revision and improvement of the contribution processes, ensuring that contributors receive fitting compensation and acknowledgement.

A major goal of the project is to ensure The Turing Way is an inclusive community to both contributors that are contributing on a volunteer and paid basis. The project is part of a constant process of designing, learning, and refining ways of working and engaging with The Turing Way community. The resulting data may be published and reused in other projects and communities to improve contribution processes.

Esther Plomp will conduct the primary research, including focus groups, interviews with community members, a quantitative community survey and research on publicly available forum discussion data. Esther Plomp has been a (partially) paid contributor, thanks to institutional support of both the Faculty of Applied Sciences of the Delft University of Technology (the Netherlands) and the University of Aruba (Aruba). She takes an intermediate position between paid and volunteer contributions, potentially mitigating any power dynamics present that could impact data collection. *The Turing Way* has [resources on addressing feedback when there are power imbalances](https://book.the-turing-way.org/collaboration/leadership/leadership-building) which will be utilised as needed, alongside the project's [Code of Conduct](https://book.the-turing-way.org/community-handbook/coc).

## Positionality statement on biases
Bias is in many ways inevitable: Esther's identity and experience with The Turing Way community will shape the experience of the interviewees and research participants. To make the experience more comfortable participants will be reminded of their autonomy–they are free to withdraw, skip questions they find uncomfortable, challenge Esther's interpretation of particular observations or incidents, and otherwise shape their participation in ways that best reflect their true experiences.

There is also the risk that people will not feel comfortable expressing critiques about leadership, as Esther is considered to be part of leadership. Participants will be provided with the option to contact a Turing Way community member that is not involved in leadership (name??) to express their concerns via this route, allowing for these concerns to then be expressed anonymously towards Esther and to be taken into account in the project.

By continually seeking feedback on the project, the methods and results will be constantly re-evaluated and updated as needed.

## 2. Details study procedure per activity

### 2.1 Survey

It is difficult to predict what the response rate of any given survey will be. The survey will be open to all The Turing Way community members who actively view the communication spaces used by the community (such as Slack, mailing lists, and GitHub). Survey respondents will range from 50 to 100 individuals. If the response rate is unexpectedly low, input will be asked from community members on individually based communication.

The survey will be piloted with three individuals that will not participate in the final version of the survey but are invited to participate in the interviews. These three individuals will have different backgrounds, ideally a volunteer contributor, paid contributor and someone with a mixed volunteer/paid contributor.

The survey should identify:
* What proportion of the Turing Way community responding to the survey is a paid or volunteer contributor.
* How these types of contributors feel supported or what challenges they face in contributing to The Turing Way.
* The impact of funding on the contributions, also on the long-term effect on the contributor/community.

### 2.2 Community data on GitHub/Slack

In order to support survey/interview data, publicly available data from issues, pull requests and discussion posts on The Turing Way, as well as discussions on Slack, can be used in order to support statements made in survey/interviews. There is no plan to fully scrape or analyse all the content in the GitHub Repository/Slack.

### 2.3 Semi-structured Interviews
Based on survey data several contributors will be asked to elaborate on their answers in the survey in more detail. The intention is to engage with **10-20 community members in the interview stage**, 5-10 members that are a volunteer contributor, 5-10 members that are or have been paid contributors, 2-3 members that took a leadership role (contributing to a working/planning group) in the community on a volunteer basis, 2-3 members that took a leadership role on a paid basis. In addition, a balance will be strived for in terms of level of contribution experience, roles and self-reported demographics, pending on availability of community members. Participants will be asked to self-identify their role, duration and time-frame of their participation in the community.

Semi-structured interviews are intended to:
* Refine the definition of paid and volunteer contributions
* Identify in more detail what challenges contributors face and how this is related to compensation for their efforts
* Identify improvements for the contribution process.

### 2.4 Community discussion of results
The community will be involved via a discussion around this ethical procedure in the Collaboration Cafe of 19 March, as well as involved in structuring the survey questions. Furthermore, the community will be involved in other communication opportunities:

* Survey questions will be communicated again after the focus group for further input, before the survey will be conducted.
* Survey questions and further input will be invited during the Book Dash in May (Collaboration Workshop and online event 20-21 May)
* The results of the study will be discussed with community in the form of a Fireside Chat or during a Community call, before being published in the form of an article.
* Where possible, asynchronous contributions from contributors who are unable to attend events will be incorporated by sharing discussion notes and requesting responses.
* Finally, the lessons learned will be used to improve the existing processes of The Turing Way, and will be contributed to the Book in the form of a new chapter or section so that the results and recommendations are also available for other communities.

### 2.5 Article
An article will be written, which will:
* Document the challenges and opportunities in supporting contributors, as well as the various strategies that can be employed to ensure compensation for contributors
* Share lessons learned
* Describe strategies for pathways for paid/volunteer contributors

## 3. Ethical Considerations

### 3.1 Project Methods and Data

The main research questions relate to The Turing Way community, therefore data collection will be focused on members of The Turing Way (community members on Slack, GitHub contributors and newsletter subscribers) in order to investigate the support that both paid and volunteer community members experience in contributing to The Turing Way. As the research will primarily focus on The Turing Way the results will not be generalizable. The research may be relevant to other open science/scource communities, but in any dissemmination of the results it will be stressed that the results are primarily applicable to The Turing Way.

Data will derive from various sources, such as focus groups, discussions, public data from GitHub/Slack, a survey and semi-structured interviews, sketching an accurate picture of the processes and how they are experienced by Turing Way contributors.

To ensure robustness, we will engage in ongoing member-checking. Prior to releasing a report, for example, we will circulate it among participants in the research project.

### 3.1 Recruitment Strategy
Community members will be asked (passively) to participate in the study via messages in the newsletter, Slack and during Community Calls. Community members will also be actively approached by directly emailing or messaging them. If members indicate that they are not interested in participation they will no longer be actively recruited.

Challenges for representation will include: ensuring that community members from a variety of backgrounds, expertise levels, and involvement in the project are included in data collection; collecting data on those missing from the community, who might contribute but cannot/do not due to the existing barriers; and enabling potential participants to participate with as little interference to their day-to-day work as possible. To mitigate some of these challenges, Esther will proactively reach out to members of the community throughout the duration of the project, offer participation time slots that meet their preferences and accommodate their work and personal responsibilities.

There is a majority voice missing from community surveys and forum post analysis: those that might have become contributors but did not due to structural or personal barriers so never joined the community to add their voice. Where possible, these missing contributors will be approached to ensure representation in the results.

### 3.2 Diversity of Engagement

Several steps are taken to ensure engagement with a variety of people:

* Advertising the call for participation on all possible communication forums.
* Requesting that participants inform us or their peers about the opportunity to participate, particularly encouraging these participants to think about people who might have a unique or underrepresented view on the topics we cover.
* Attending The Turing Way Collaboration Café events to share intermediate findings and make attendees aware of opportunities to participate.
* Seeking feedback on preliminary findings via the GitHub repository (Issue #), which will include information on how to participate, and include discussions that will inform the study and affect the interview/survey questions.

## 4. Interviews

Semi-structured interviews will be audio recorded and transcribed. Following, qualitative coding techniques are applied to generate themes insights (see Strauss, A., & Corbin, J. M. (1990). *Basics of qualitative research: Grounded theory procedures and techniques.* Sage Publications, Inc. and Miles, M. B., & Huberman, A. M. (1994). *Qualitative data analysis: An expanded sourcebook* (2nd ed.). Sage Publications, Inc.). Qualitative data analysis involves layering interpretation onto the data by first identifying commonalities and differences in responses to the same or similar questions. After identifying these commonalities and differences, a codebook is developed to deepen the analysis, breaking themes down further into subthemes. Codes are applied to snippets of text where these themes appear. As an example, in this project, initial themes may include “contributor challenges” and “first contribution.” These themes may then be broken down into “contributor challenges - conflict with employment responsibilities; contributor challenges - time famine” and “first contribution - documentation; first contribution - code.” Final stages of analysis involves linking these codes to one another. For example, we may link the contributor challenge of time famine to difficulties making code contributions vs. documentation contributions. These themes and any relevant contextual information in our outputs.
* Representative quotes from interviews may be used to substantiate claims.
* For public sharing, notes/transcripts will be structured by interviewee via a unique participant ID. Before publishing any data, participants will have the opportunity to redact or remove data they do not wish to have included. For public sharing only quotes from participants that have consented to public sharing will be used.

## 5. Data Management Plan

### 5.1 Data provenance and procurement
The qualitative interview data and quantitative survey data used for the project will be gathered and analysed as part of SSI Fellowship of Esther Plomp, running from 2025-2026.

* Survey data will be collected between April-May.
* Interview data will be collected between June-August. For each interview, the date and time (in the interviewer’s geographic location) and location (videoconference) will be recorded.
* Archival data (such as GitHub posts, mailing lists) will be collected over the period of the project. When collecting this data, the date and time of the communication will be recorded.
* Notes and collaborative artifacts (such as photos of whiteboards, sticky notes, diagrams) will be collected from events such as collaboration cafés or Book Dash events. The date and time of the workshops will be recorded.

### 5.2 Preprocessing

* Interview recordings will be transcribed using **a local GPU using WhisperX (to be updated)** . Transcripts will be loaded into a private Proton Drive with access only available to Esther Plomp and ?. Transcripts will be loaded into qualitative data analysis software (QualCoder) on local machines. Transcript excerpts will be placed in a spreadsheet on the same Drive during the analysis phase.
* Archival data will be collected in the export format of the platform used for the communication. These data will be handled in the same way as interview transcripts, described above.
* Survey data will be collected using Google Forms. Responses will be exported as a CSV file, stored in the private Google Drive before stored for the longterm on a Proton drive, and analyzed on local machines.
* Notes and collaborative artifacts from Collaboration Cafes or Book Dash events will be preserved in their original form on the Proton Drive.

### 5.3 Data Sharing
* Excerpts from the interview, archival, survey data, and event notes and artifacts will be communicated in reports and a research article. Anonymised excerpts will also be stored and shared when approved by the research participant, as described in the research participation consent form.
* Two years after the final publication from the project, all remaining data that is not being retained due to participant choices or due to irrelevance will be destroyed.
* We will create a public GitHub repository (with a version copied to Zenodo for long term preservation, under a CC-BY license) with participant-approved excerpts from interviews and surveys. This repository will represent the experiences of the participants on topics deemed relevant to the study. Participants who agree to have excerpts shared will have the opportunity to review and/or remove content prior to publishing. We will also include the research instruments (semi-structured interview protocol, survey questions, consent form and this ethics procedure) in the project repository, an explanation of our process for developing the instruments, a methods description for data collection and analysis, and the scope of work for this project.
* Findings will be communicated in English, with an accompanying glossary for any unfamiliar terms to increase interpretability.

### 5.4 Storage & Security
* Recordings will be locally stored. Once recordings are transcribed they will be deleted.
* Transcripts are only available to Esther Plomp **and ?** . These will be stored on a private Proton Drive.
* A private Google Drive will be used for survey data storage: participants will be informed of the risks associated sharing their data with a Big Tech company.
* Demographic data is optionally provided. Questions about demographic data will be included as they are relevant for the experiences as a community member. This data will be monitored carefully to avoid identification of community members.

## 6. Governance

Community consensus will be strived for during the project duration, with Esther Plomp making any final decisions if consensus cannot be reached. Working openly on GitHub as much as practicable offers the opportunity for audit and scrutiny by community members and stakeholders.

## 7. Stakeholders

Main stakeholders in the project:

* Turing Way community members
* Turing Way leadership

Peripheral stakeholders

* Other open source community members and potential members who can benefit from more systematic analysis of where improvements can be made to the contribution pathways of open source projects

## 8. Impact

The overarching goal of this project is to enhance and enrich contributor communities with practical strategies for empowering a more diverse array of contributors. Central to the overarching aims of the project are concrete recommendations for process and pathway improvements which increase the overall diversity and vibrancy of The Turing Way community.

We do not anticipate any significant harms that will come from the outputs of our work. Findings may possibly cause distress or discomfort to members of the community or leadership. Spaces for discussion will be facilitated to mitigate these risks and ensure that the discomfort will lead to improving the inclusion of the community.

## 9. Sustainability

### 9.1 Environmental sustainability
The project is not expected to generate a comparatively large amount of data or to use computationally expensive algorithms to analyse it, so the additional environmental costs of storage and compute are relatively low.

The majority of the work will take place remotely via online collaboration, reducing carbon emissions from the need to travel to conduct the research, but not eliminating the environmental impact of utilising technology.

## 10. Transparency

### 10.1 Process
The project has been discussed with *The Turing Way* leadership and the Community prior to work commencing. A [GitHub Issue](https://github.com/the-turing-way/the-turing-way/issues/3833) has been opened to keep track of project progress, invite feedback and present interim findings.

Esther Plomp will attend community calls and collaboration cafes to discuss the project openly to enable community members to ask questions, challenge the project approaches, and discuss different aspects of the work.

Project procedures are outlined in detail in the consent form for 1:1 interviews, which clearly outline the risks and benefits of the work.

### 10.2 Outcome Transparency

* The project intends to produce an open access research article covering the findings and recommendations from the research.
* De-identified data from the 1:1 interviews and survey will also be published openly under an open License on a GitHub repository (with a version shared on Zenodo).
* Findings and recommendations will be shared with The Turing Way leadership, so that practical changes to contributor pathways can be applied where needed. Generalisable findings will also be incorporated in the Turing Way book.

## Consent Form

**Consent Form: Participation in The Turing Way Community Research Activities**

**SUMMARY OF KEY INFORMATION:**

You are being asked to participate in a research study conducted by Esther Plomp on behalf of The Turing Way for her SSI Fellowship. The Turing Way has granted permission to conduct observations and interviews with community members. This research is being conducted for the purposes of evaluating and improving the Turing Way's community-building strategies, with a focus on differentiations between volunteer and paid contributions. Participation in the research is voluntary, and the decision to participate or not will have no impact on your relationship with The Turing Way community.

**PURPOSE:**

Data collection for this study is intended to:

* Identify successes, challenges and opportunities that contributors faced when they contributed to The Turing Way
* Identify what paid contributions look like (financial compensation, training, mentoring, visibility, time?)
* Support both paid and volunteer contributions to the community, developing strategies to avoid differentiations between these types of contributions
* Inform the revision and improvement of the contribution processes, ensuring that contributors receive fitting compensation.

**PROCEDURES:**

If you decide to participate, we will schedule a time to interview you about your experiences in and opinions of the Turing Way community. We expect the interview to last between 30 to 60 minutes. This interview will be held remotely over videoconference. The conversation will be audio-recorded for transcription, after which the audio-recording will be deleted. You will be asked to review the transcript, an activity that is voluntary. Afterwards, anonymized transcripts with limited reidentification risks will be publicly published (only with consent) in a GitHub repository under an open license to facilitate reuse. You may still participate in the study even if you do not consent to public sharing of your anonymized transcript. However, we will need your consent to use your data for analysis within the study. During the interview we will follow the [Turing Way Code of Conduct](https://book.the-turing-way.org/community-handbook/coc).

**RISKS AND BENEFITS:**

There are no major risks and benefits expected when participating in this research. If the interview is making you feel uncomfortable you can decide to close the interview at any time. You will be asked about demographic data (such as country, gender) that will be optional to answer.

Your opinions may include criticism to leadership. While leadership is actively looking for feedback to improve processes within The Turing Way, we understand if you would like to avoid any type of retaliation and prefer to contact someone other than Esther about these concerns.

* I understand that if I want to express critique about The Turing Way and want to do so without revealing my identity to Esther, I may contact Yanina Bellini Saibene ([e-mail]).

Your data will be carefully managed. Specifically:

* Recordings will be stored off-cloud and with local disk encryption before deletion.  
* Recordings will be transcribed into text via Zoom, or a local GPU using WhisperX if participants are not comfortable using Zoom for these purposes. Transcripts are stored on a private Proton Drive that only Esther Plomp can access.
* There is always a potential risk of a data breach. Risks are considered minimal as the intention of the project is to share the resulting data as transparently as possible.

**CONFIDENTIALITY**

Unless you grant permission to use your name, title, and/or quote you in any publications that may result from this research, the information you share will be confidential. De-identified quotes and paraphrased responses may be used in reports and other publications of the study’s results.

* Yes, I grant permission for the use of my name, title, and/or quote, in any publications, thus revealing my identity publicly.
* No, I grant permission for the use of my anonymized quote(s) ONLY

Any information shared for future research will NOT include your name or other personal identifying information. The dataset including your responses will then be published on a public repository after you have had a chance to review and approve it.

* I consent to the use of my data for the particular study described above.
* I consent to the use of my data in a publicly-shared dataset, where my data will be anonymized.
* I understand that I can withdraw my consent for either activity at any time up until the public dataset has been published (by the latest January 2026).

**DATA USE, RETENTION, AND EU-GDPR**

The categories of personal data you are being asked to consent to are your name, email address, role in the Turing Way community, other employment information (such organization, role and career stage), audio recording, and qualitative descriptions of your experiences and insights from working in/engaging with the Turing Way community.

Your personal data will be transferred out of your home country and the European Union to Esther Plomp, located in Aruba, and stored on a Proton Drive (storage in the EU).

Transcripts will be anonymized. This work will be easier if you do not identify other individuals in your interview. If you forget and use names of other contributors the information will be redacted later.

**QUESTIONS:**

If you have any questions about this research project, wish to withdraw, or if you think you may have been injured or harmed as a result of your participation, please contact: Esther Plomp, [[e-mail]](mailto:[e-mail]) or Arielle Bennett, [[e-mail]](mailto:[e-mail])

Participation in this research is voluntary. By signing, you indicate that you have decided to participate in this study and provide consent for processing your personal data. You will be given a signed copy of this form to keep.

Name of Participant: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Signature of Participant: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date: \_\_\_\_\_\_\_\_\_

## Updated Survey Questions

**In what way do you consider yourself to be a Turing Way community member?** *(Tick all that apply)*
* I engage with discussions on Slack
* I have contributed to the Turing Way book via GitHub (for example: providing input in discussions, opening up Issues/Pull requests, adding or reviewing content)
* I have participated in events, such as Community Calls, Collaboration Cafés or a Book Dash
* I have participated in activities, such as a Working Group or mentoring community members
* I took leadership roles in a working group or in the organisation of an event
* No, I haven't engaged with The Turing Way at all before opening up this survey
* Other ....

**Do you identify as a marginalized community member? (definition)**
- Yes
- No
- Not sure

**Of these options below, which of the following career stages best describes you?**
- Junior (entry-level, often with direct guidance from seniors)
- Mid-level (more independent work on complex projects)
- Senior (focus on leadership, mentorship, and driving strategic efforts)
- Other (please describe)

**In what capacity are you normally contributing to the Turing Way?**
- On a volunteer basis: my contributions have nothing to do with my current work position and I contribute in my free time
- On a volunteer basis: my contributions are related to my work position but I do not get time allotted to contribute to The Turing Way and I contribute in my free time
- On a paid basis: my contributions are related to my work and there is (formally) dedicated work time for this
- On a paid basis: my role is predominantly paid to work on The Turing Way.
- On a paid basis: I have received financial compensation for my activities in the Turing Way (via a research proposal or fellowship - not including accessibility reinbursement)
- I’m not sure
- Other:

**Are there other non-financial ways that you were compensated for your work in The Turing Way?** Please select all that apply:
- I received feedback on my work by peers
- I was able to develop skills
- I was able to follow a training (for example, on GitHub)
- I was able to add activities to my CV
- I was able to network and received opportunities via this network
- No, I have not received any of the above mentioned compensations
- Other: ..
-

**Do you think that your contributions are adequately recognised and rewarded? Please elaborate on how your contributions are recognised (or not) by both The Turing Way Community and your employer (if this is relevant).**

**Approximately how often do you normally contribute to The Turing Way?**
*A contribution may include participation in a discussion on Slack, being active on the GitHub repository (by opening of an Issue/PR or commenting on an existing one), or attending an event (such as a Collaboration Café or Fireside chat).*
* Daily
* Weekly
* Monthly
* Annually
* Never
* Other (please describe)

**Please indicate here if you consent to being contacted in the future to discuss your answers to the survey in more detail**
* Yes - I have provided my email above
* No

**Who can you remember that isn't around anymore that would want to provide their input? Please provide their name and/or contact details.**

## Draft Survey Questions

**Section 1 - Demographics**
This section will be used in conjunction with other sections to help us to understand how attitudes and practices in The Turing Way differ across different fields, roles, and career stages.

**Of the options below, which best describes your job role?**
* Undergraduate or Masters Student
* PhD Candidate
* Postdoctoral Researcher or Fellow
* Lecturer
* (Assistant/Associate/Full) Professor
* Research Software Engineer
* Senior Team or Department Leader
* Research Infrastructure Role (Technician, Community Manager, Data Manager and so forth)
* Other (please describe in the box below)
*
Of these options below, which of the following career stages best describes you?
* Junior
* Mid-level
* Senior
* Other (please describe)

**Do you consider yourself to be a Turing Way community member?** (Tick all that apply)
* Yes, I engage with discussions on Slack
* Yes, I have contributed to the book via GitHub
* Yes, I have participated in events, such as Community Calls, Collaboration Cafés or a Book Dash
* Yes, I took leadership roles in a working group or in the organisation of an event
* No, I haven't engaged with The Turing Way at all before opening up this survey

**Do you consider yourself to be primarily a volunteer or paid contributor to The Turing Way**
* Volunteer (I contribute in my free-time)
* Paid (contributing to The Turing Way is part of my position)
* Both
* I'm not sure

**What time-period are you keeping in mind when you are answering this survey?** (If you were both a volunteer and paid contributor in different time periods, you have the option to answer the survey twice!)

**Approximately how often do you contribute to The Turing Way (Community or Book) during an average work week?**
A contribution includes a discussion on Slack, GitHub, opening of an Issue/PR, or attending an event.
* Daily
* Several times a week
* Once a week
* Several times a month
* Once a month
* Several times a year
* Annually
* Never
* Other (please describe)

*Section 2: Barriers and opportunities for contributors*

**Do you think that your contributions are adequately recognised and rewarded?**
* Yes
* No

**From your perspective, what are the main barriers to contributing to The Turing Way?** (if time is the main barrier you are experiencing, what other barriers are also there so that you cannot make the time to contribute?)

**Would receiving some sort of payment or compensation remove those barriers? What payment or compensation method would you prefer?**

**How easy is it for paid contributors to contribute to the community/book?** (1-5)

**How easy is it for paid contributors to take leadership roles in the community?** (1-5)

**How easy is it for volunteer contributors to contribute to the community/book?** (1-5)

**How easy is it for volunteer contributors to take leadership roles in the community?** (1-5)

**Do you feel like paid contributors have more say in what happens in the community?**
(1-5)

**Can you elaborate your answer on the ease of contribution to the community for volunteer and paid contributors?**

**Do you think paid contributors are a requirement for the sustainability of the Community?**
* Yes
* No
* Not sure

*Section 3 / Wrap up and possible follow up for semi-structured interview. *

**Please indicate here if you consent to being contacted in the future to discuss your answers to the survey in more detail**
Yes - I have provided my email above
No

**Please suggest any names of other Turing Way community members that could contribute to the project** (We particularly welcome suggestions for individuals that disengaged with the project)

## Draft Research Interview Questions

Optional demographic data
- Country currently based in
- Gender

Non optional data:
- Volunteer/paid contributor

* **Tell me about your involvement with the Turing Way community?**
* What got you interested in the community? What has kept you engaged?
* Why do you contribute?
* What has been difficult when trying to contribute to The Turing Way?

* **Do you feel adequately compensated/positively impacted for your efforts in The Turing Way?**
* Probes: Could you tell me more about that (when, how it happened, what it entailed - such as positive impact career/development and so forth)
* Why do you see that as a success? Why do you see it as a failure?
* What do you see as adequate compensation?

* **Do you feel like it makes a difference to be a volunteer or paid member to contribute to the Community?**
* Does it make a difference in leadership roles?

* How does paid contribution relate to the sustainability of the community?"

* **What could the Turing Way do to facilitate contributions to the community?**
* How can community development be improved?
* What does the community need more of?