Ksenia
Ksenia
To get better insight into site ranking we could add labels based on the Tranco rank of the site globally. It could be something like: `top-100` `top-500` `top-1k` `top-5k` `top-15k`...
There is an problem with certain issues not being moved to needstriage milestone and not getting any labels: https://github.com/webcompat/web-bugs/issues/106463 https://github.com/webcompat/web-bugs/issues/106459 https://github.com/webcompat/web-bugs/issues/106383 https://github.com/webcompat/web-bugs/issues/106369 https://github.com/webcompat/web-bugs/issues/106351 https://github.com/webcompat/web-bugs/issues/106317 https://github.com/webcompat/web-bugs/issues/106284
As NSFW labelling that has been added in https://github.com/webcompat/webcompat.com/pull/3704 is based on a static DB at the moment, let's add an ability to periodically fetch updates for this DB.
The current UI for github issues in https://github.com/webcompat/web-bugs-private/issues?q=is%3Aissue+milestone%3Aml-autoclosed+is%3Aclosed requires one to open an issue page in order to see the content and change milestone as needed. I think it would...
As https://github.com/webcompat/webcompat.com/issues/3656 has been deployed let's add documentation describing how to run it.
There are failing tests in the recent builds: https://app.circleci.com/pipelines/github/webcompat/webcompat.com/1893/workflows/3241893d-f701-43bd-b512-94fe64743ad0/jobs/1894 ```python if request is None: > builder = EnvironBuilder(*args, **kwargs) E TypeError: __init__() got an unexpected keyword argument 'as_tuple' env/lib/python3.9/site-packages/werkzeug/test.py:1081: TypeError...
We've enabled GA to run a few experiments to try and improve the drop-off rate of the web compact form. As this work is now done, we can turn off...
When an issue is placed to the moderation queue it has this text in the content: ``` A human will review if the message meets our current acceptable use guidelines....
Filing this issue to track findings on experimenting with models for label prediction with bugbug. I’ve collected additional data for this experiment (used issues `timeline` instead of `events`) as `timeline`...
I've tried to deploy a new milestone on staging today and after deployment, the site was showing 500 error. Worth mentioning that I've created "moved" milestone on GitHub last week....