Twitter (via Twitter's own search if you have an account
Jeffrey YasskinShould we move this to refer to social media in general, as the developer community is now splintered between twitter, mastodon and bluesky?
Mike TaylorI think we ought to replace all the Twitter links with something else, but I defer to @to...@chromium.org and other DevRel folks on what to replace them with.
Thomas SteinerYeah, +1 to making this more generic, or mentioning multiple venues.
Jeffrey YasskinAgreed, and addressed in my suggested edit.
Done
or via Google Search if you don't
Thomas SteinerSimilarly, should this include multiple potential search engines?
Jeffrey YasskinAgreed, and addressed in my suggested edit.
Done
Twitter (via Twitter's own search if you have an account
[[example]](https://x.com/search?q=%22img%22%20%22loading%3D%27lazy%27%22&src=typed_query),
or via Google Search if you don't
[[example]](https://www.google.com/search?q=%22img%22+%22loading%3D%27lazy%27%22+site%3Atwitter.com)).
Jeffrey Yasskin```suggestion
social media search or via web search.
```
Fix applied.
Proceed similarly on StackOverflow, GitHub, or perform a generic Web search
Jeffrey Yasskin```suggestion
Proceed similarly on StackOverflow, GitHub, or any other relevant platform
```
Done
signal is *recommended* for [dev trials](/blink/launching-features/#dev-trials).
Mike Taylor@to...@chromium.org: It's not actually recommended there. We just have "At this point, you should consider asking other browser vendors and the web developer community for signals on their opinion of the API." in https://www.chromium.org/blink/launching-features/#dev-trials. If DevRel thinks we _should_ recommend this before dev trials, could you send a change to that file? If you're going to do that, I think it's fine to leave this text (or similar) here in this PR.
Thomas SteinerIMHO, this doesn't make sense as a recommendation _before_ a dev trial. Instead, I would hope we would get some developer views as a result of publishing the dev trial.
Jeffrey Yasskin```suggestion
signal is *optional* for [dev trials](/blink/launching-features/#dev-trials).
```I lowered this to _optional_, since it still makes sense to document developer opinions or demand at the dev trial stage (if just to save some work once the feature ships and it becomes _required_.
Done
> * <link to Twitter poll>
Jeffrey Yasskin```suggestion
> * <link to social media post or poll>
```
Fix applied.
* Discussion boards like [WICG Discourse](https://discourse.wicg.io/).
Thomas SteinerDiscourse is no longer active, but support on the WICG prposals repo may be an alternative.
Jeffrey YasskinI've just removed the examples.
Done
* Online social networking sites like [Twitter](https://x.com/home).
* Version control sites like [GitHub](https://github.com/).
* Discussion boards like [WICG Discourse](https://discourse.wicg.io/).
Jeffrey Yasskin```suggestion
- Online social networking sites like.
- Version control sites like [GitHub](https://github.com/).
- Discussion boards.
- ```
Fix applied.
* Working Group call minutes that included industry participants.
@to...@chromium.org: This linked to https://groups.google.com/a/chromium.org/g/blink-dev/c/YMrf4l2DqtM/m/B8FB2axQAQAJ in https://goo.gle/developer-signals, but that isn't WG call minutes. I've removed the example for now, but do you know what the right link was?
* Working Group call minutes that included industry participants like
[this](???).
Jeffrey Yasskin@to...@chromium.org: This linked to https://groups.google.com/a/chromium.org/g/blink-dev/c/YMrf4l2DqtM/m/B8FB2axQAQAJ in https://goo.gle/developer-signals, but that isn't WG call minutes. Do you know what the right link was?
Comment moved to current patchset.
external-facing developer outreach, DevRel has access to the official
[@ChromiumDev Twitter account](https://x.com/chromiumdev)—well noting that this
Mike Taylor@to...@chromium.org: Does DevRel now post more widely than just Twitter? Can we mention a different social media account?
Thomas Steiner+1.
Jeffrey YasskinAddressed in the suggested edit.
Done
external-facing developer outreach, DevRel has access to the official
[@ChromiumDev Twitter account](https://x.com/chromiumdev)—well noting that this
may introduce follower bias. DevRel can signal-boost or create polls, and ask
people to chime in on conversations happening on GitHub, Discourse, and
Jeffrey Yasskin```suggestion
external-facing developer outreach, DevRel has access to the official
Chrome accounts on various social media platforms—well noting that this
may introduce follower bias. DevRel can signal-boost or create polls, and ask
people to chime in on conversations happening on GitHub and
```
Fix applied.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Preview this change at https://chromium-website--cl6173013-ps8-4ttnsnmi.web.app
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
* Working Group call minutes that included industry participants.
@to...@chromium.org: This linked to https://groups.google.com/a/chromium.org/g/blink-dev/c/YMrf4l2DqtM/m/B8FB2axQAQAJ in https://goo.gle/developer-signals, but that isn't WG call minutes. I've removed the example for now, but do you know what the right link was?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
* Working Group call minutes that included industry participants.
Mike Taylor@to...@chromium.org: This linked to https://groups.google.com/a/chromium.org/g/blink-dev/c/YMrf4l2DqtM/m/B8FB2axQAQAJ in https://goo.gle/developer-signals, but that isn't WG call minutes. I've removed the example for now, but do you know what the right link was?
It seems fine to leave this without a link, IMHO.
Yepp, that's fine with me, too. (The initial idea was to link everything with an example, but this proved hard.)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Preview this change at https://chromium-website--cl6173013-ps10-hr9y8o3h.web.app
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Commit-Queue | +2 |
@to...@chromium.org: It sounds like you're happy with the current state of the CL, and Mike has +1'ed, so I'll merge this. Let me know if you'd like any follow-up changes.
* Working Group call minutes that included industry participants.
Mike Taylor@to...@chromium.org: This linked to https://groups.google.com/a/chromium.org/g/blink-dev/c/YMrf4l2DqtM/m/B8FB2axQAQAJ in https://goo.gle/developer-signals, but that isn't WG call minutes. I've removed the example for now, but do you know what the right link was?
Thomas SteinerIt seems fine to leave this without a link, IMHO.
Yepp, that's fine with me, too. (The initial idea was to link everything with an example, but this proved hard.)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Auto-Submit | +1 |
Commit-Queue | +2 |
Code-Review | +1 |
Commit-Queue | +2 |
(maybe this will make the bots happy)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Import https://goo.gle/developer-signals, with some modernization.
That document was written by to...@google.com with contributions from
re...@igalia.com, yoav...@google.com, ny...@google.com,
chri...@google.com.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |