bugbug
bugbug copied to clipboard
mozilla
Create a model to identify accessibility bugs
To get labels, we can use the presence of "access" in the keywords, or the presence of "access-s" in the whiteboard.
I'd like to work on this. I believe I'm not stepping on anyone's toes?
As far as I understood, the goal is to build a model that assigns accessibility label to the relevant issues?
You are more than welcome. If you need any help or have any questions, please join the bugbug Matrix room. I will be glad to help.
As far as I understood, the goal is to build a model that assigns accessibility label to the relevant issues?
Yes, accessibility bugs are tagged manually with access keyword or [access-s*] in the whiteboard field (e.g., [access-s2]). The goal is to automatically label such bugs as soon as they got reported.
You could start by setting up the environment and installing the dependencies as explained in the readme file.
Next, you could try training an existing model; spambug model could be a good candidate:
python3 -m scripts.trainer spambug
If you feel stuck, do not hesitate to ask in bugbug Matrix room
Hello, @suhaibmujahid I would like to work on this issue as this will provide me some insights into the main project. How do I start?
Hello, @suhaibmujahid I would like to work on this issue as this will provide me some insights into the main project.
Feel free to do that.
How do I start?
Please read the comments above.
@suhaibmujahid Can you please suggest what I have to learn or maybe some resources that can help me in making it?
Next, you could try training an existing model;
spambugmodel could be a good candidate:python3 -m scripts.trainer spambug
I did run this command but I didn't understand anything.
I did run this command but I didn't understand anything.
Have a look here: https://github.com/mozilla/bugbug#structure-of-the-project to get an idea about the project structure. Seeing how other models are implemented could be helpful.
While trying to work this issue, I thought, isn't it possible for us to extend the bugtype model to also identify and label accessibility bugs as well?
Let me know if this is okay, I can open a PR.
