论文标题
如何调试包容性错误？通过信息体系结构进行调试过程
How to Debug Inclusivity Bugs? A Debugging Process with Information Architecture
论文作者
论文摘要
尽管以前的一些研究发现了找到包容性错误的方法（在引入不平等的软件中存在偏见），但很少关注如何解决此类错误。如果没有从发现到修复的过程，就可以在每个开发人员的技能上遵守此类发现是一项临时活动。为了解决这一差距，我们创建了原因/何处/修复，这是一个系统的包容性调试过程，其包容性故障本地化利用信息体系结构（IA） - 组织，结构化和标记的面向用户的信息的方式。然后，我们使用开源软件（OSS）项目的基础架构作为我们的设置，对为什么/where/fix的有效性进行了多阶段定性的经验评估。在我们的研究中，OSS项目团队使用了为什么/were/fix过程来查找包容性错误，将其本地化的IA故障定位，然后修复IA以删除他们发现的包容性错误。我们的结果表明，使用/wher/fix的原因减少了OSS新人参与者所经历的包容性错误的数量。
Although some previous research has found ways to find inclusivity bugs (biases in software that introduce inequities), little attention has been paid to how to go about fixing such bugs. Without a process to move from finding to fixing, acting upon such findings is an ad-hoc activity, at the mercy of the skills of each individual developer. To address this gap, we created Why/Where/Fix, a systematic inclusivity debugging process whose inclusivity fault localization harnesses Information Architecture(IA) -- the way user-facing information is organized, structured and labeled. We then conducted a multi-stage qualitative empirical evaluation of the effectiveness of Why/Where/Fix, using an Open Source Software (OSS) project's infrastructure as our setting. In our study, the OSS project team used the Why/Where/Fix process to find inclusivity bugs, localize the IA faults behind them, and then fix the IA to remove the inclusivity bugs they had found. Our results showed that using Why/Where/Fix reduced the number of inclusivity bugs that OSS newcomer participants experienced by 90%.
