TAG/MeetCandidates2023/Peter Linss

From W3C Wiki

Peter Linss - TAG Candidate 2023

These are Peter's answers to the 2023 TAG Candidate Questions.

You can also read Peter Linss's nomination statement here.

Quotes from the minutes are not verbatim, and may not accurately reflect the candidate's statements.

What's an interesting question about how the Web’s architecture should evolve that you've come across recently?

Answer here.

What are the technical trends you notice are happening on the Web, and what implications do you see for the work of the W3C?

Answer here.

What should the TAG's role be in reviewing WG charters?

Answer here.

What do you think about adding maps to the Web Platform?

Answer here.

How do you think the appointed TAG seats should be used?

Answer here.

Has the TAG been taking the wrong approach in any of its recent activities, and if so, what would you change?

Answer here.


What can the TAG and W3C do about the environmental and social impacts of the Web?

Answer here.

How do you see the TAG filling a gap in technical leadership?

Answer here.

What is the most important problem the Web Platform faces that the TAG could reasonably address?

Answer here.

What values will you bring to the TAG that other candidates might disagree with?

From the minutes...

The TAG responsibility is to the web, not to member org or who appointed you. Not to their interests. User interests are first, above any subset of members. There's a tension there we need to bear in mind. TAG might need to be more active in addressing the things people do.

What do you see as the role of the TAG in relation to regulators?

From the minutes...

I do think the TAG should be more involved w/ regulation. We're not charterered to set policy, so it's a fine line. Sometimes regulators don't know tech, so we can advise so that regulations make sense. Then there's something in EWP which is the Web is designed for a purpose. We are stewards of architecture of the web, but also stewards for vision of what w3c can be. Regulation can be part of this. Board and AC could be more involved too. We are seeing more tech regulators speak to governments. So why isn't W3C there?

What are examples of W3C work that's not really in scope, and of work elsewhere that could be in W3C's scope?

From the minutes...

I'm sure there's been lots of examples but nothing is coming to me. I'm not sure how relevant this to TAG. Might be policy.

What specific things did you accomplish in your previous TAG term, or plan to accomplish in your first TAG term?

From the minutes...

First answer re: previous terms. If you don't know history, it was after the big TAG election, DanA and I turned the TAG into what it is today. Started design reviews, more communication w/ WG, shaping designs not just architecture astronauts and philosophy. I think we've been successful. Going forward, I think more of the same. We try to take the philosophy of being dynamic. We ask what should we do, and how can we do things differently. Allowing this to continue. There are things that haven't worked as well and not doing them. We can say we tried that and it didn't work and maybe we can do it differently. That knowledge going forward is helpful.

What is your experience/expertise on browser-based front-end and server-backed or back-end standards?

From the minutes...

I agree that that many TAG have been browser focused. To that end, I was the author of the Gecko engine. I have a pretty good handle on browser stuff. Also done server side, protocols. I have experience there as well.

What organizational or technical skills will you bring to the TAG?

From the minutes...

A well as chairing TAG, I also chaired CSS. Daniel Glazman and I took over when it was considered to close, it and made it one of the most of the productive groups. My leadership style is set the tone, set the direction then protect your team, let them go. We have a lot of bright and talented people.

Wanted to respond to Jeffrey. We've had a lot of ideas about automation. I hope you join so we can get some help building.