community
community copied to clipboard
open-telemetry
Create fine-grained token for opentelemetrybot, allowing write access to opentelemetry-specification repo issues
Affected Repository
https://github.com/open-telemetry/opentelemetry-specification
Requested changes
Create a fine-grained token for opentelemetrybot, allowing write access to opentelemetry-specification repo issues.
Please share this token with @austinlparker.
Purpose
To run script in #2219 as part of old spec issue bankruptcy.
Expected Duration
Temporary until after the script is run.
Repository Maintainers
- @open-telemetry/technical-committee
Is "spec issue bankruptcy" something that has been agreed upon? I've heard rumblings about it, but don't remember seeing an issue / PR where it was discussed and agreed on.
For the record, I'm in favor, but want to make sure we're not getting ahead of ourselves and running a script we end up regretting.
It's been discussed by the GC, although it looks like it didn't get written down anywhere. Perhaps we can create an issue on community as an announcement that also documents the new staleness rules for spec? IIRC we were discussing having staleness be a year for things that are in needs feedback/community discussion but have had no updates within a year? We can do that before we actually run the bankruptcy. Staleness doesn't necessarily have to be automated, but we do need to automate the bankruptcy because it touches about 400 issues.
cc @tedsuo @trask on language/timing. Would be good to get an issue created/pinned in here so that we can socialize this to maintainers meeting and SIGs