https://github.com/recaptime-dev/transparency-log-threads
Issue tracking GitHub repository for squad members and community maintainers on RFC voting, moderation actions and other actions that may affect the organization and its community.
https://github.com/recaptime-dev/transparency-log-threads
communication-threads transparency-log
Last synced: 2 months ago
JSON representation
Issue tracking GitHub repository for squad members and community maintainers on RFC voting, moderation actions and other actions that may affect the organization and its community.
- Host: GitHub
- URL: https://github.com/recaptime-dev/transparency-log-threads
- Owner: recaptime-dev
- License: mpl-2.0
- Created: 2024-06-24T17:49:23.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-01-10T03:39:47.000Z (2 months ago)
- Last Synced: 2026-01-11T00:59:58.089Z (2 months ago)
- Topics: communication-threads, transparency-log
- Homepage:
- Size: 36.1 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Transparency Log Threads at RecapTime.dev HQ
Issue tracking GitHub/GitLab repository for squad members and community maintainers on RFC voting, moderation actions and other
actions that may affect the organization and its community.
## Links
We're in the works of migrating them to GitLab SaaS at lately.
Previous log entries are still available at .
## How this works?
Similar to delegate communication threads in Arbitrum governance forum, you make a new thread for logging your votes in the
RTSIP/RFC process, transparently publish any moderator actions you taken and other tasks that may affect @recaptime-dev and
the community as whole. Usually a new log entry is due within a few months for minor activities and within 1-2 months for
major actions, but since most of the team are volunteers with responsibilities outside of open-source, that could be delayed
a bit longer.
In our implementation of this, we lock issues to avoid spam and unnecessary discussions but you can still reply as long as you are
direct contributor with triage access via @recaptime-dev/transparency-log-threads team on GitHub and/or Reporter role on GitLab.
## Questions? Need access to team?
Ask in the Zulip thread: