Skip to content

Publish minutes of 2026-11-12 WEWG meeting - #1194

Merged
Rob--W merged 1 commit into
mainfrom
meeting-2026-11-12-wewg
Nov 19, 2026
Merged

Rob--W merged 1 commit into
mainfrom
meeting-2026-11-12-wewg

Conversation

@Rob--W

@Rob--W Rob--W commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Generated from https://docs.google.com/document/d/1ezXs4uJzbfi8nyncUQcFLDyS9Tn_trs9j_RQgM54GBE/edit using the tool and process from #105 (adapted for the WebExtensions Working Group (WEWG)).

During this meeting we discussed or mentioned issues #1169, #563 and PRs #1152, #1134, #1186, #1123, #1171, #1154, #1173, #1188.

Action items:

  • [simeon] Schedule the next batch of meetings.
  • [simeon] Create guidelines for becoming an editor.

@Rob--W
Rob--W requested a review from xeenon November 12, 2026 17:20
@Rob--W Rob--W added the wewg Topics under the umbrella of the WEWG (WebExtensions Working Group) label Nov 12, 2026
Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Resolved
* [patrick] I'll update the PR momentarily.
* [timothy] Simeon raised a question about whether it was the right structure to have multiple spec docs. I think that for changes impacting other web specs, separate docs make it easier to reference.
* https://github.com/w3c/webextensions/pull/1173/changes#r4481754582
* [simeon] I think that makes sense. There is also a broader conversation about whether individual namespaces should have its own. I think this is useful to have separate from the main spec because there's broader utility in having

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is cut off. @dotproto, can you finish it?

* [sideshowbarker] I have opinions about many things. When I see a doc with a large number of editors, I tend to be worried because that often indicates an anti-pattern in the process. Some folks hunt for an opportunity to get their name on a spec for resume purposes. Being an editor is not just editing; also involves discussing and triaging topics, mediating differences in opinions. In practice you don't have a large number of people doing that work. Like any other project, if you have someone showing up and making contributions that improve things, you might want to consider bringing them on board to formalize and recognize their contributions.
* [timothy] I foresee a large number of changes from some of the people on the call, enough to be considered an editor. A large amount of work is writing down what is already a de facto spec. I think that someone doing that work should be eligible for becoming an editor.
* [rob] I also think that the bar should be whether we're comfortable with the person doing reviews and approvals for spec considerations. A LLM can produce a lot of content, but I'm not sure if letting the same LLM generate reviews and approve is something we want.
* [simeon]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dotproto do you remember what you said here?

Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Resolved
Comment thread _minutes/2026-11-12-wewg.md Outdated
* [simeon] Rough rule is “when you add a period, insert a new line.”
* [timothy] Feels weird.
* [simeon] Agreed.
* [sideshowbarker] Not sure I know anyone that likes semantic line breaks besides Tab. We've discussed in WHATWG. Two concerns. One that Oliver mentioned, overhead on reviews and adding more work to contributors. The bigger concern is what do editors want? IMO they should have veto power over what others want

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [sideshowbarker] Not sure I know anyone that likes semantic line breaks besides Tab. We've discussed in WHATWG. Two concerns. One that Oliver mentioned, overhead on reviews and adding more work to contributors. The bigger concern is what do editors want? IMO they should have veto power over what others want
* [sideshowbarker] Not sure I know anyone that likes semantic line breaks besides Tab Atkins. We've discussed in WHATWG. Two concerns. One that Oliver mentioned, overhead on reviews and adding more work to contributors. The bigger concern is what do editors want? IMO they should have veto power over what others want

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I knew who was being referred to, but in the context I can also totally see someone reading this and thinking about Tabs vs spaces 😄

I have accepted the suggested edit (in the PR and in the original doc).

@Rob--W
Rob--W force-pushed the meeting-2026-11-12-wewg branch from 69681b7 to 48b02e2 Compare November 19, 2026 15:47
@Rob--W

Rob--W commented Nov 19, 2026

Copy link
Copy Markdown
Member Author

Merging as is without fixing the missing gaps for Simeon, to prepare for the publication of today's minutes.

@Rob--W
Rob--W merged commit e1a76f5 into main Nov 19, 2026
1 check passed
@Rob--W
Rob--W deleted the meeting-2026-11-12-wewg branch November 19, 2026 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wewg Topics under the umbrella of the WEWG (WebExtensions Working Group)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants