Closed
Bug 777080
Opened 12 years ago
Closed 6 years ago
Data flow diagrams for Firefox OS
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(blocking-basecamp:-)
RESOLVED
WONTFIX
blocking-basecamp | - |
People
(Reporter: me, Unassigned)
Details
(Whiteboard: [WebAPI:P0][LOE:S])
I know we've spoken about it already, but just want to document it in Bugzilla. Privacy/legal needs to know all the places that Firefox OS communicates with or connects to Mozilla & other outside service providers. Please reassign to the right person to pull these together, I didn't know who was the right person.
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
blocking-kilimanjaro: --- → ?
Updated•12 years ago
|
blocking-basecamp: ? → +
blocking-kilimanjaro: ? → ---
Updated•12 years ago
|
Whiteboard: [WebAPI:P0]
Comment 1•12 years ago
|
||
We should find the right owner here. Scoping as 'S' for now.
Whiteboard: [WebAPI:P0] → [WebAPI:P0][LOE:S]
I don't think this is a blocking issue. Lucas: Would you be able to find an owner if this is something we really need.
Assignee: clee → ladamski
blocking-basecamp: + → -
Reporter | ||
Comment 3•12 years ago
|
||
Alina, do you feel that have the info that you need to produce a complete and accurate policy? If so, we can close this bug. If not, then I think this is probably blocking.
Flags: needinfo?(ahua)
Tom - Could you take a first stab at the privacy policy draft as Alex mentioned in his email, and send me a draft by EOD Thursday? I'm traveling for work this week and won't be able to get to this until after I return on Thursday evening. Thanks, Alina
Flags: needinfo?(ahua)
Updated•11 years ago
|
Assignee: ladamski → nobody
Hi all - This is an old bug that was not resolved and I just saw that that the assingnee has been changed to nobody@. Do we have the data flows documented in another bug so we can close this one?
Comment 6•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•