FYI: task-scheduler-dev@chromium.org

[Gabriel Charette]

FYI, introducing task-sche...@chromium.org as the new public list to discuss the new base/task_scheduler/post_task.h API, its backing implementation, and the migration of Chromium to it.

We will keep scheduler-dev@ involved in relevant discussions but will use our own public list for day-to-day discussions. Similarly please CC us on anything relevant to task scheduling :).

Cheers,

Gab

[Sami Kyostila]

Thanks Gab, will do! We might eventually want to defrag everything to a single list but let's start with this setup.

- Sami

--
You received this message because you are subscribed to the Google Groups "scheduler-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scheduler-de...@chromium.org.
To post to this group, send email to schedu...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/scheduler-dev/CAJTZ7LKXsEvRs5A34EYyOqTX4_UzOYsp5sPq8pQHx9uPkS8zhQ%40mail.gmail.com.

[Ojan Vafai]

Neither list gets very much traffic. What's the benefit of two lists?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/scheduler-dev/CAPuLczsTsXxp1UtX3edMEQ-PtH1EhNzbb2_mAXwpWVO8Wy%2BEew%40mail.gmail.com.

[Gabriel Charette]

Actually, the initial thought was that many things are very much intended for the immediate team (e.g. a new crash, a metrics spike notification in an experiment, etc.). But given all the examples I can think of that only apply to the immediate team are internal. The remainder are scheduling discussions which are relevant on scheduler-dev.

So recommendation would be:

 - Use internal list for experiments notifications (crashes, metrics, etc.)

 - Use scheduler-dev@ for any scheduling related discussion.

As such I agree that task-scheduler-dev@ might not be useful. Let's see if we can avoid it. I'll delete it in a month if it's not used in retrospect.

[Ojan Vafai]

Sgtm.