Repository navigation
Publish minutes of 2026-11-12 WEWG meeting - #1194
Merged
Merged
Conversation
xeenon
approved these changes
Nov 12, 2026
| * [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 |
Collaborator
There was a problem hiding this comment.
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] |
| * [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 |
Collaborator
There was a problem hiding this comment.
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 |
Member
Author
There was a problem hiding this comment.
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
force-pushed
the
meeting-2026-11-12-wewg
branch
from
November 19, 2026 15:47
69681b7 to
48b02e2
Compare
Member
Author
|
Merging as is without fixing the missing gaps for Simeon, to prepare for the publication of today's minutes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: