Closed
Bug 1621991
Opened 5 years ago
Closed 5 years ago
What do we name things in Glean?
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: janerik, Assigned: janerik)
References
Details
Attachments
(2 files)
Split-out discussion from the multi-lang architecture proposal.
Currently it's only a survey of the current situation.
|
Assignee | |
Comment 1•5 years ago
|
||
I'm stuck here right now, as I'm not sure about naming. I split this out to make the discussion more focused, but now I need your input: What do we name the different "projects" of the Glean SDK, so that we can comfortably talk about them and also draw the lines of where to implement what and keep behavior consistent across all parts.
Attachment #9132903 -
Flags: feedback?(mdroettboom)
Attachment #9132903 -
Flags: feedback?(chutten)
Attachment #9132903 -
Flags: feedback?(alessio.placitelli)
|
||
Comment 2•5 years ago
|
||
Comment on attachment 9132903 [details]
[FOG] Naming proposal
Looks good to me. My only comment was to include the table in the docs so it's findable and we can keep it up to date with current implementation status.
Attachment #9132903 -
Flags: feedback?(mdroettboom)
|
||
Comment 3•5 years ago
|
||
Comment on attachment 9132903 [details]
[FOG] Naming proposal
I think the names in the table heading are an excellent start.
Attachment #9132903 -
Flags: feedback?(chutten) → feedback+
|
||
Updated•5 years ago
|
Attachment #9132903 -
Flags: feedback?(alessio.placitelli) → feedback+
|
|
Assignee | |
Comment 4•5 years ago
|
||
The proposal saw some feedback and we made the decision to put this with some changed wording into the Glean SDK book (see PR).
Closing this bug when the PR lands.
|
|
Assignee | |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•