#60: Agenda building for the TAG f2f: 7–11 September 2026

Visit on Github

Opened Jun 23, 2026

Let's use this issue to discuss what items we'll want on the agenda for our f2f.

Topics discussed so far on various calls and in Slack include:

  • Architectural Decision Records (should we start creating those?)
  • Timeboxing design and charter reviews
<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/meetings/60

Discussions

Discussed Jun 29, 2026 (See Github)

Matthew: I have one, I want to point out since the last F2F, I notice this one and webpayment, we have to look at the use cases to check. I think wheels are invented a couple of time. There seems to be duplication of events and it is good to discuss it in F2F. Also, we talked about this last week, that we see couple of different proposals that point to .well-known and because there is not one-to-one communication between UA and server, there's some sort of routing layer on top, which is bespoke - I think we should try to harmonize or standardize this.

Marcos: I won't dive into payment detail but Matthew is correct about the cross-site relations. Some related to capabilities and some related to access control and they are related to each other. I am interested to put a TAG finding I wanted to work on long time ago.

Hadley: I have a big list for this

Marcos: should we have a repo for this?

Hadley: sounds like a good idea.

Hadley: I also see the pattern in advertising where advertiers/intermediatories want to have a trusted relationship with the top-level page so it can inherit some of the permissions (to make them special). this is alarming as it will be bad for the web.

Matthew: we should make it a pinned repo on the TAG repo as we want encourage people to give us feedback on it. It was a time ago we had something about gaps. It is worth if there is anything there we can put for agenda.

Marcos: I remember it wasn't a good experience. I remember we could not bring them over before as they were not good fit for purpose (?). The web is absolutely comptetive so it is better this is tried on other platforms. I would be motivated to ask "what would be good for the users, from the gaps", we can discuss it in the f2f.

Matthew: I agree. I have not seeing it getting compared to other platforms and this is areasonable thing. Shall we change the repo name to "wishlist"? I don't thin the intend here is to call for things missing...

Marcos: I agree with that.

Hadley: I am offering renaming it. I wonder if we go with the wishlist, whether it will include that we spot and bad for the web and we want to be removed from the web. I don't want to ??

Matthew: we could propose closing the ones that won't fix. we can keep them open forever.

Hadley: maybe. we can also have the discussion in the future and adapt based on what happens.

Heather: we need to focus on the scope of the thing.

Heather: any more topic?

Hadley: we started to talk about a document about gathering things that web pages do things that a user would not expect. I want to work on that.

Matthew: I would like to contribute to that document. For me, "people think that the data they put in a form only goes on when people press submit button". Is there any private repo as I want to put agentic finding there.

Marcos: it is private-by-default.

Hadley: do we have a repo on the draft finding.

Matthew: is there any developer meet-up in the F2F?

Hadley: yes

Marcos: I need to find space in the Vancouver office. We can ask Mozilla office as they seem to have an office there and they have developer offices usually.

Heather: this sounds like something that is traditional.

Marcos: yes it is

Hadley: the theory is that we get with developers so we can have feeling of the real challenges. we used to have hackathon and we can do those too.

Marcos: I can ask over slack but need to colect info on the people attending for sending to security office.

Hadley: put that in the document you shared with us.