Compatibility/Meetings/Sync w Karl
December 15 2020
List of Issues with no milestone (SV)
I tried to check the issues on Github that have no milestone and I kept getting an error.
URL: https://github.com/webcompat/web-bugs/issues?q=is%3Aissue+is%3Aopen+no%3Amilestone
I saw the correct page only once (10 issues shown) and luckily I made a screenshot and now those issues were verified.
I've created a ticket on Github (https://support.github.com/ticket/personal/0/935694) and the problem is being investigated.
I've got a reply:
- Thanks for contacting GitHub Support! - I believe the issue here is the large size of this repository causing the timeout, as I can see there are over 63k issues in that repo. - Loading the issues page without the milestone filter loads, however, so I'm going to reach out internally to see what is happening here. - An alternative approach while we look into this would be to pull a list of issues with no milestone using the API. You can see our API docs about issues here: - https://docs.github.com/en/free-pro-team@latest/rest/reference/issues#list-repository-issues - As soon as I have an update I'll let you know.
I tried to compose the link, in order to get the issues which have no milestone, but without luck (`no milestone` has no ID, like the rest of the milestones).
Could you provide us the link so we could investigate the remaining issues, if any?
Karl: https://api.github.com/repos/webcompat/web-bugs/issues?milestone=none = Working most of the times (sometimes it gives Server error).
This is failing too https://github.com/webcompat/web-bugs/issues?q=is%3Aissue+milestone%3Aneedsdiagnosis+label%3Aengine-gecko+sort%3Acomments-asc except if you remove label.
Re-test Bugzilla issue with patch (Oana)
I was requested to re-test an issue where a patch was provided.
https://bugzilla.mozilla.org/show_bug.cgi?id=1675578
Do I need to apply the patch (and if yes, how can I do that, since it is not an .xpi file).
If the patch is already in the latest Nightly I will re-test it asap.
Karl: Ask dennis to provide a build.
November 17 2020
Issues reported by users with screenshot (SV)
We received an issue from an user, having a screenshot containing explicit content. https://github.com/webcompat/web-bugs/issues/61752
We removed the screenshot, but we were wondering if the user should be banned or at least give him a warning about not posting this kind of content?
karl: user was banned (had 2 inappropriate issues)
Issues still displayed as "In the moderation queue" even though they have been moderated (SV):
- https://github.com/webcompat/web-bugs/issues/61829 - https://github.com/webcompat/web-bugs/issues/61827 - https://github.com/webcompat/web-bugs/issues/61823
November 3 2020
Wiki pages editing without authorization issues (SV)
Some user were able to edit Wiki pages without authorization. What should we do with these issues?
karl: Report them in Bugzilla https://bugzilla.mozilla.org/form.web.bounty
https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites
- product: websites - component: wiki.mozilla.org
Link them to the webcompat issues (for more details).
(FYI) Increase number of issues (SV)
The number of issues increased but there is no need to worry, we can handle them
October 20 2020
Old certificate issues (SV)
For site that have old certificates, Mike asked us to lable them with "type-unsupported-tls", move them to Needscontact and to ping him. That is the reason we ping you now.
Do you consider we can close them as non-compat if the problem occurs on any browser and only ping you in case it is only reproducible on Firefox?
karl - move issues to Needcontact only if they are reproducible on Firefox, otherwise move them to Non-compat (reproducible on all browsers)
2020Q4 - needstriage on Webcompat Bugzilla (SV)
We were wondering what is the action item in case we find a reproducible issue from the list https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=needs-triage&sharer_id=473918
Action items:
Issue is reproducible:
- add corresponding Keyword (Details): webcompat:need-diagnosis / webcompat:need-contact / webcompat:need-contact-ready / webcompat:need-site-wait, similar to webcompat issues - (Tracking) add status "affected" to Firefox version (Optional) - add steps to reproduce if not available (for easy diagnosis)
Issue is not reproducible:
- change Status (Tracking) from "Unconfirmed" to "Resolved" -> Invalid / Worksforme - need info Karl or the reporter for extra details on the issue, or when we don't understand it
Notes: skip [Meta] bugs
October 06 2020
OKRs proposal (SV)
All the cards are in place both reserved and planned https://github.com/mozilla/webcompat-team-okrs/projects/11.
Should we discuss each?
Are there any tasks for us from upper management?
karl: task cards are all good
karl: will check the name of the educational platform used in Japan
karl: ETP shim talk directly with Tom, an come up wit a plan (maybe also help with confirmation of fixed issues)
karl: new task from upper management - not yet, work in progress, will be news during the quarter
oana: reserve: manual testing on social media TikTok (video playback)
Tasks that require testing (SV)
If there are issues that require testing (see also issues, mozregression) feel free to loop us in, and we will gladly help out.
karl: will do so
1:2 meeting proposal (SV)
We could have this meeting every other week when there is no Team meeting in the week.
karl: sure
September 29 2020
OKRs tasks planning for Q4 (SV)
We have a list of tasks that we want to propose for Q4, should we directly create cards for them here
https://github.com/mozilla/webcompat-team-okrs/projects/11 ? or discuss and make a plan what to keep and what to skip.
Karl: Yes, add all the proposed items as cards.
Finish every week with 0 untriage and 0 unmoderated bugs (SV)
This was proposed last quarter by Mike, in order to see if we can handle all issues by the end of the week. Since the number of issues was not high, we successfully managed to triage and moderate all of them.
Should we continue monitoring this progress?
Karl: we can continue monitoring and ask for help when needed.