We want to do a quick pass over our code and spread some logging love around. I've decided to split this into into logical parts and assign potential owners to each part. Some of these parts are huge, so take a resonable approach to it:

• If you don't think it's your responsibility, forward it to the person you think it is;
• If it's too much work, split it across more people;
• If it's not relevant to logging, mark it as completed.

I suggest to take the following strategy:

• Use the info log level for informational data, which should appear in a regular run of Code
• Use the trace log level for traceable function calls, state changes, etc
• Use the warn log level for non-blocking, non-critical, possibly expected errors

You can refer to vs/platform/update/electron-main/abstractUpdateService for an example.

Warning: Be careful with concurrent edits to this issue, as always. Refresh the page before you edit it (hopefully you won't need to) or before you check a checkbox.

Platform

• vs/platform/actions @jrieken
• vs/platform/backup @Tyriar
• vs/platform/broadcast @bpasero
• vs/platform/clipboard @rebornix
• vs/platform/commands @jrieken
• vs/platform/configuration @sandy081
• vs/platform/contextkey @alexandrudima
• vs/platform/contextview @joaomoreno
• vs/platform/environment @joaomoreno
• vs/platform/extensionManagement @sandy081
• vs/platform/extensions @sandy081
• vs/platform/history @bpasero
• vs/platform/instantiation @jrieken
• vs/platform/integrity @alexandrudima
• vs/platform/issue @RMacfarlane
• vs/platform/keybinding @alexandrudima
• vs/platform/lifecycle @bpasero
• vs/platform/list @joaomoreno
• vs/platform/markers @jrieken
• vs/platform/opener @jrieken
• vs/platform/progress @jrieken
• vs/platform/request @joaomoreno
• vs/platform/state @bpasero
• vs/platform/storage @bpasero
• vs/platform/telemetry @chrmarti
• vs/platform/theme @aeschli
• vs/platform/update @joaomoreno
• vs/platform/url @joaomoreno
• vs/platform/windows @joaomoreno
• vs/platform/workspaces @bpasero

Workbench Parts

• vs/workbench/parts/backup @Tyriar
• vs/workbench/parts/cache @jrieken
• vs/workbench/parts/cli @joaomoreno
• vs/workbench/parts/codeEditor @alexandrudima
• vs/workbench/parts/debug @isidorn
• vs/workbench/parts/emmet @ramya-rao-a
• vs/workbench/parts/execution @isidorn
• vs/workbench/parts/extensions @sandy081
• vs/workbench/parts/feedback @RMacfarlane
• vs/workbench/parts/files @isidorn
• vs/workbench/parts/html @mjbvz
• vs/workbench/parts/markers @sandy081
• vs/workbench/parts/output @sandy081
• vs/workbench/parts/performance @jrieken
• vs/workbench/parts/preferences @sandy081
• vs/workbench/parts/quickopen @bpasero
• vs/workbench/parts/relauncher @bpasero
• vs/workbench/parts/scm @joaomoreno
• vs/workbench/parts/search @sandy081
• vs/workbench/parts/snippets @jrieken
• vs/workbench/parts/stats @chrmarti
• vs/workbench/parts/surveys @joaomoreno
• vs/workbench/parts/tasks @dbaeumer
• vs/workbench/parts/terminal @Tyriar
• vs/workbench/parts/themes @aeschli
• vs/workbench/parts/trust @joaomoreno
• vs/workbench/parts/update @joaomoreno
• vs/workbench/parts/watermark @chrmarti
• vs/workbench/parts/welcome @chrmarti

Electron Main

• vs/platform/url/electron-main/urlService @joaomoreno
• vs/platform/update/electron-main/updateService.* @joaomoreno
• vs/platform/request/electron-main/requestService @joaomoreno
• vs/code/electron-main/sharedProcess @joaomoreno
• vs/code/electron-main/auth @joaomoreno
• vs/base/parts/ipc/electron-main/ipc.electron-main @joaomoreno

Misc

• vs/workbench/api @jrieken (@joaomoreno: joh, feel free to distribute work if it's too much)
• vs/editor @alexandrudima @rebornix (@joaomoreno: not sure if interesting for the editor. we'd have to come up with an editor log service)