Google docs permissions

Open
#3,365 6 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet

Research direction

Start by reviewing the OTel Specification Google doc and the issue's discussion of recurring vandalism, version history, and anonymous-user permissions. The issue does not name repository files, tests, or an implementation entry point. Done would require an agreed approach to document permissions and a confirmed resolution to the vandalism concern.

Written by the indexing model from the issue text.

Description

Recently someone vandalized the OTel Specification Google doc. This is not a new problem, as we've seen this from time to time in the project. We can revert changes via the version control in google docs, but another option may be to prevent changes from anonymous users.

Opening this issue to have a discussion about it.

Dominant language
Python
Stars
1.2k
Forks
326
Avg merge
1d 12h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/community

All issues in open-telemetry/community

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.