GenderMagRecordersAssistant

This is the repository for the GenderMag Recorders Assistant About GenderMag Recorders Assistant:

Table of Contents

1. About GenderMag Recorders Assistant
2. Goal
3. How to Contribute
4. How to Fix Bugs
5. FAQ's
6. More About GenderMag
7. How to use the Tool

About GenderMag Recorders Assistant:

Software has been facing usability problems since programs first started to be made. GenderMag Recorders Assistant looks to address problems with User Focus, Information Content, Structure, Layout, and much more.

Many of the problems found with the GenderMag Recorders Assistant show a bias towards usage patterns common in men or women.

This means that software is often biased towards a subset of the population instead of being inclusive to the population as a whole. Anyone can learn to use the GenderMag Recorders Assistant, from software engineers to management to usability experts.

Diverse ideas and opinions enhance the process for all involved and as such we welcome anyone from any background to contribute to our process of trying to make the world of software more gender inclusive.

Goal:

Due to the lack of all encompassing software, GM Recorders Assistant aims to provide a wide range of people with a way to fix the software we use everyday.

People with little to no experience can use GM Recorders Assistant and find an array of problems. People who’ve been contributing to open source for years can also use GM Recorders Assistant and find just as many problems.

How to Contribute:

Everyone is welcome to contribute to GM Recorders Assistant. If contributors have any questions on what to do or how to do something feel free to shoot us an email and we will get back to you as soon as possible. We encourage new open source contributors to start here.

• Create a personal fork of the project on Github.

• Clone the fork on your local machine. Your remote repo on Github is called origin.

• Add the original repository as a remote called upstream.

• Create a new branch to work on! Branch from develop if it exists, else from master.

• Implement/fix your feature, comment your code.

• Follow the code style of the project, including indentation.

• Add or change the documentation as needed.

• Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary.

• Push your branch to your fork on Github, the remote origin.

• From your fork open a pull request in the correct branch. Target the project's develop branch if there is one, else go for master!

• Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es).

How to fix bugs:

CM Chris**

FAQ’s:

CM Chris** How to download chrome extension What language do we use How much experience with Open Source do I need?

More about GenderMag:

At the GenderMag method’s core are five problem-solving facets that matter to software’s gender-inclusiveness. These facets are :

• a user’s motivations for using the software,

• their information processing style,

• their computer self-efficacy,

• their attitude towards risk, &

• their ways of learning new technology.

The GenderMag method brings these facets to life with 4 personas (Tim, Abby, Patrick and Patricia), and sets the personas and facets into a simple, systematic process (The GenderMag Cognitive Walkthrough). CM How we get from here to the tool

How to use the Tool:

The GenderMag Cognitive Walkthrough specializes and streamlines the traditional cognitive walkthrough, incorporating explicit references to the five facets of gender inclusiveness:

• a user’s motivations for using the software,

• their information processing style,

• their computer self-efficacy,

• their attitude towards risk, &

• their ways of learning new technology.

Through the GM Cognitive Walkthrough we can follow the process to find gender-inclusiveness issues. We can then fix the issues we find one at a time to remove barriers that may disproportionately affect one gender.