Re: Collating browser and spec issues

I'd prefer to keep it in one place if possible – I see it mainly as a
categorised list of links to browser's bug trackers, spec issues etc.

I have a local doc I use for this purpose ATM but suspect it would be more
use if we had something that was shared and visible so other can contribute
if they want.

On Tue, Feb 4, 2025 at 6:45 PM Cliff Crocker <cliff.crocker@gmail.com>
wrote:

> Sounds like a good idea, Michal. I can't see the project, but the idea
> makes sense to me. We discussed keeping a backlog of agenda items as well,
> which might make sense to track there as well.
>
> On Tue, Feb 4, 2025 at 11:14 AM Michal Mocny <mmocny@google.com> wrote:
>
>> Could you use a tag on the issues directly in the spec repo's?  And/or I
>> think you could create a "RUMCG github project" like we do for the Perf
>> WG triage <https://github.com/orgs/w3c/projects/7>?  Just to keep all
>> the metadata in one place, if you want.
>>
>> On Tue, Feb 4, 2025 at 12:13 PM Andy Davies <andy.davies@speedcurve.com>
>> wrote:
>>
>>> Is there a repo somewhere where we can start collating browser and spec
>>> issues that are relevant to us as a group?
>>>
>>> For example I know of a few webkit bugs related to Time Origin, and
>>> Navigation Timing
>>>
>>> Thanks
>>>
>>> Andy
>>>
>>> --
>>>
>>> Andy Davies
>>> Web Performance Consultant, SpeedCurve
>>>
>>>
>>>