Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues I've noted when completing the 2018 survey from a SA RSE perspective #226

Open
pvanheus opened this issue Sep 5, 2018 · 6 comments
Labels

Comments

@pvanheus
Copy link
Collaborator

pvanheus commented Sep 5, 2018

Unfortunately Anelda and I could not complete South African proposed changes to 2018 survey due to time pressure, so I'll note these in an issue for next year.

  1. Qualifications: We have a 4 year qualification called Honours that is the first year post-graduate. We should include this as an option.

  2. Contract: Some people are on multiple contracts from different sources - e.g. some uni funding, some additional external funding. Need to include space for this kind of answer.

  3. Decision to accept current position is missing some options. A few I can think of:

    • Job security
    • Interest in "contributing to the greater good" (not sure how to word this)
  4. Need to include questions to address "research systems engineers" / devops people.

  5. Race/Ethnicity needs to be included in demographic questions.

  6. Sexuality needs to be included in demographic questions.

  7. Family responsibilities needs to be included in demographics questions (are RSEs able to support a family? ;) )

@pvanheus
Copy link
Collaborator Author

pvanheus commented Sep 5, 2018

Incentives: can there or should there be incentives for participation?

@Oliph
Copy link
Contributor

Oliph commented Sep 6, 2018

      1. it is easy fix and should not raise any problem
  1. It is a good point, addressing other roles than just developing software. Maybe in the questions about the time spend on activities
  2. Race and ethnicity are put at the end because they are sensitive questions and often lead participants to drop the survey. However, putting the demographic section at the end should be better
  3. We will not add sexual orientation, there is no reason for that. (or I did not understand that point and it was about the gender?)
  4. Family responsability: also outside our scope. The salary, the contract should provide that information (about ability to support a family).
  5. Incentives: I would be happy to offer some incentives but we need a budget for that, which I do not have. But we can think about that possibility next year (like amazon voucher or something more techie and specific to dev, but it will need to be virtual).

@Oliph Oliph added the 2019 label Sep 6, 2018
@pvanheus
Copy link
Collaborator Author

pvanheus commented Sep 6, 2018

As to 4. sexual orientation is an unrepresented minority in STEM (see e.g. http://www.bu.edu/research/articles/lgbt-issues-stem-diversity/ and an attempt to address this http://colorcode.org.za/#about), thus my suggestion for its inclusion.

Perhaps 5. gets captured by a combination of age + salary - the key question I'm aiming at is whether there is a drop out of RSEs as they acquire additional family responsibilities as salary / job stability in industry becomes a more important factor.

As to 6. - does this raise ethical issues?

@Oliph
Copy link
Contributor

Oliph commented Sep 11, 2018

  1. Ok I see the purpose. If we include that one we will have to carefully state the purpose for participants. Otherwise it will see invasive without reason (I, for instance, will not expect questions about my sexual orientation when I fill a survey about job/work).

  2. The problem with the drop out is the bias. People that have dropped out will probably not answer the survey anyway. But that could be added, again with a careful description of the purpose of the question.

  3. The incentive is not that problematic regarding the ethics. It just need to b mentioned in the application, but it is a common practice.

@pvanheus
Copy link
Collaborator Author

Thanks for the reply. I know we need to tread carefully (I live on a continent where 4. can expose you to criminal prosecution). Thanks for all your work. I will continue to promote the survey and look forward to working together in the future.

@Oliph
Copy link
Contributor

Oliph commented Sep 12, 2018

Thank you for your feedback. I leave the issue open for discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants