How about thinking through how bias in algorithms should be tested, discovered, and fixed and building that in? Some types of testing might be statistical for

How about thinking through how bias in algorithms should be tested, discovered, and fixed and building that in? Some types of testing might be statistical for example, and involve trying software on a large group of people with a variety of backgrounds. The bugtracker could be designed to be integrated with those testing and discovery methods. How to fix such bugs may not be clear, and normal methods of who to assign them to might not work (perhaps some have to be assigned to teams or outside parties?) In general a bugtracker that integrates with all the tools used in development, testing, and fixing would be more efficient and useful. Automatic import of statistics and graphs, maybe built in running of test code to reproduce the bug for the developer who has to fix it, some indication of the impact of each bug in terms of audience (which customers does it affect? What is the public relations impact if it is not fixed and causes problems later? How might it affect sales?) Seems like an integrated system could explore a lot of new possibilities.