Closed
Bug 1497919
Opened 6 years ago
Closed 6 years ago
Find a name for the "mobile telemetry sdk"
Categories
(Toolkit :: Telemetry, enhancement, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: Dexter, Assigned: Dexter)
References
Details
(Whiteboard: [telemetry:mobilesdk:m1])
The mobile SDK will live in the android-components repo. However, the "telemetry" name was already taken by the "telemetry-android" legacy library and it can't be renamed. [1] This is because we're publishing the library on Maven, and the directory name is the package name.
We should find a name for the mobile SDK directory, so that Sebastian can create a template library for us to start developing there. Bikeshedding is needed!
Current proposals:
- telemetry2
- telemetry_sdk
- mobile_telemetry
- mobile_telemetry_sdk
[1] - https://github.com/mozilla-mobile/android-components/tree/master/components/service/
Assignee | ||
Comment 1•6 years ago
|
||
Hey folks, any suggestion?
Blocks: 1491345
Flags: needinfo?(jrediger)
Flags: needinfo?(gfritzsche)
Flags: needinfo?(chutten)
Priority: -- → P1
Whiteboard: [telemetry:mobilesdk:m1]
Comment 2•6 years ago
|
||
I think the bikeshed should be ochre[1].
`telemetry_sdk` is fine by me. Bland, but descriptive. Are they supposed to be snake_case or css-case?
[1]: http://ochre.colorcode.is/
Flags: needinfo?(chutten)
Comment 3•6 years ago
|
||
Is a gdoc or similar maybe better for suggestions/comments/+1s?
I'll throw in moztelemetry / moz_telemetry. (no strong favor on it though)
-1 to suffixing with a "2". (that gives us baggage in the future when we transition)
+1 to anything that is bland but descriptive.
"mobile" prefixes might be redundant in the context (mobile repositories etc.)
Flags: needinfo?(gfritzsche)
Comment 5•6 years ago
|
||
(In reply to Alessio Placitelli [:Dexter] from comment #0)
> The mobile SDK will live in the android-components repo. However, the
> "telemetry" name was already taken by the "telemetry-android" legacy library
> and it can't be renamed. [1] This is because we're publishing the library on
> Maven, and the directory name is the package name.
If it's published there, should we have a some mozilla/moz/... prefix to differentiate it?
Updated•6 years ago
|
Assignee: nobody → alessio.placitelli
Comment 6•6 years ago
|
||
For documentation purposes one thing that was discussed: Glean
glean: to gather information or material bit by bit (via https://www.merriam-webster.com/dictionary/glean)
moztelemetry is already in use by other project (e.g. https://github.com/mozilla/python_moztelemetry)
Flags: needinfo?(jrediger)
Assignee | ||
Comment 7•6 years ago
|
||
(In reply to Jan-Erik Rediger [:janerik] from comment #6)
> For documentation purposes one thing that was discussed: Glean
>
> glean: to gather information or material bit by bit (via
> https://www.merriam-webster.com/dictionary/glean)
By looking at Slack as well, looks like there is consensus around "glean". I like it too! From a quick search on the Internet, it looks like I can't find any other telemetry product called like that. I'm closing this as fixed!
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mdroettboom)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•