[DOCS] Data privacy

未关闭
#29 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
38/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
领域
documentation

调研方向

The issue asks for security documentation based on the Slack Q&A, but names no documentation file or test. First, inspect the repository’s existing documentation structure and identify where security and privacy information belongs. Document the described data handling and browser side disclosures accurately, and consider the work done when those points are clearly covered in the relevant docs.

由索引模型根据 Issue 内容生成。

描述

docs

Document q/a from Slack:

Good questions, and I'm going to file a ticket to add to our security docs :slightly_smiling_face:
Our design is:
-- Self-managed (Docker): Graphistry sees nothing except ~annual billing information. For legal & ethical reasons, we either need to know who you are, or work through a trusted reseller.
-- Cloud Marketplaces (AWS/Az): AWS/Az send us billing reports such as account and utilization.
-- Graphistry Hub: We're built so contractors etc. cannot access production systems (e.g., cannot log into production servers + log into cloud admin panels), but devs can. We are actively hiring 2 people to help launch individual & team tiers, and ~half that work is about putting in privacy/sharing controls. If you care about tenant isolation etc, would actually welcome a conv on that, as we're planning the features for those 2 people!
An important issue for especially privacy sensitive users is the current browserside leaks usage information in 2 places. First, some of our JS dependencies loaded additional JS via CDNs, so we've worked with upstream maintainers to fix those, and the next release already removes all but one of those. Second, we had a leftover Google Analytics include (essentially just IP/URL), which we already removed for the next release as well -- it may already be gone on Hub, and I'm not sure if it ever went to Marketplace or Docker distros (requires a GA ID parameter). (edited) 
主要语言
Shell
星标
31
派生
6
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

graphistry/graphistry-cli 的其他 Issue

查看 graphistry/graphistry-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。