Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 | 1 year ago | |
---|---|---|
.. | ||
DIR_METADATA | 1 year ago | |
OWNERS | 1 year ago | |
README.md | 1 year ago | |
crbug.js | 1 year ago | |
pinpoint.js | 1 year ago | |
user-activity.js | 1 year ago |
Developers do a lot of work to help with a bug that may not directly lead to fixing the bug. This can include triaging a bug (e.g. set the correct component on the bug, find the right owner for the bug, loop somebody else in to investigate the bug, etc.), requesting more information from the OP, investigating to help the bug owner resolve the bug, etc. We want to be able to identify and measure such activities, so that these efforts can be acknowledged and rewarded.
The user-activity.js
script helps measure the bug-activity of a developer in
various monorail projects. Example usage:
nodejs tools/crbug/user-activity.js \
-u sadrul@chromium.org,sadrul@google.com \
-p chromium,skia,v8,angleproject \
-s 2022-01-01
The following command line flags are supported:
-u
: The user-email(s) for the developers. If the user uses multiple
accounts (e.g. @google.com, @chromium.org, etc.), then specify all of them
comma-separated.
-p
: The project(s) the developer participated in. If the developer
participated in the bug-tracker for multiple projects (e.g. chromium,
angleproject, v8, etc.), then list all of them comma-separated. Default is
just chromium
.
-s
: The starting date from when the activities should be counted.
Following are some notes on how activity is measured: