Import https://goo.gle/developer-signals.
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. |
Jeffrey Yasskin would like Thomas Steiner to review this change.
Import https://goo.gle/developer-signals.
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. |
@to...@chromium.org: Can you check that I migrated this correctly? Feel free to suggest further improvements in this CL or to have me merge this and then send your own changes.
Others: I adjusted some of the cross-links to point here. Let me know if I missed any or if you'd cross-link differently.
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?
I 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.
signal is *recommended* for [dev trials](/blink/launching-features/#dev-trials).
@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.
* Working Group call minutes that included industry participants like
[this](???).
@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?
external-facing developer outreach, DevRel has access to the official
[@ChromiumDev Twitter account](https://x.com/chromiumdev)—well noting that this
@to...@chromium.org: Does DevRel now post more widely than just Twitter? Can we mention a different social media account?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
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?
I 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.
Yeah, +1 to making this more generic, or mentioning multiple venues.
signal is *recommended* for [dev trials](/blink/launching-features/#dev-trials).
@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.
IMHO, 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.
external-facing developer outreach, DevRel has access to the official
[@ChromiumDev Twitter account](https://x.com/chromiumdev)—well noting that this
@to...@chromium.org: Does DevRel now post more widely than just Twitter? Can we mention a different social media account?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Agree with all comments and have addressed them with suggested edits. This document was written in a different time, _sigh_…
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.
Yeah, +1 to making this more generic, or mentioning multiple venues.
Agreed, and addressed in my suggested edit.
or via Google Search if you don't
Thomas SteinerSimilarly, should this include multiple potential search engines?
Agreed, and addressed in my suggested edit.
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)).
```suggestion
social media search or via web search.
```
Proceed similarly on StackOverflow, GitHub, or perform a generic Web search
```suggestion
Proceed similarly on StackOverflow, GitHub, or any other relevant platform
```
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.
IMHO, 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.
```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_.
> * <link to Twitter poll>
```suggestion
> * <link to social media post or poll>
```
* 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.
I've just removed the examples.
* 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/).
```suggestion
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?
+1.
Addressed in the suggested edit.
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
```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
```
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Preview this change at https://chromium-website--cl6173013-ps6-w7bultog.web.app
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Preview this change at https://chromium-website--cl6173013-ps7-hrmykby3.web.app
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |