mirror of https://github.com/avivsinai/bitbucket-cli.git synced 2026-09-19 07:13:00 +08:00

Files

T

avivsinai d12c4724b8 docs: advertise WinGet install and fix stale support/governance references (#281 )

- Add the WinGet install command to the README now that
  AvivSinai.Bitbucket-CLI is available in the catalog.
- Point SUPPORT.md, GOVERNANCE.md, and CONTRIBUTING.md at GitHub Issues;
  drop the non-existent community Slack and GitHub Discussions references
  (Discussions are not enabled for this repository).
- Refresh the RELEASE.md post-release announce step to match reality.
- Remove the accidentally committed promptcode_bitbucket-cli-full.md export
  and ignore promptcode_*.md so generated dumps stay out of version control.


Claude-Session: https://claude.ai/code/session_014oAN4wP1xC2M9xypRnaX5E

Signed-off-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>

2026-08-01 19:26:16 +03:00

1.2 KiB

Raw Permalink Blame History

Project governance

Roles

Maintainers: responsible for roadmap curation, triage, and releases. Current maintainers:
- Aviv Sinai (@avivsinai)
Reviewers: contributors with merge rights on specific areas (commands, clients, docs). Reviewers can approve PRs but maintainers perform final merges.
Contributors: anyone sending PRs, docs updates, or filing issues.

Decision making

Day-to-day decisions happen in issues or PRs.
Significant changes (CLI UX, API surface, security posture) require an accepted design proposal or RFC tracked in docs/rfcs/ (future enhancement).
Maintainers aim for consensus. If consensus cannot be reached, the maintainer quorum decides.

Meetings

We operate asynchronously. Ad-hoc maintainer syncs occur as needed; notes are published in docs/notes/ when applicable.

Becoming a maintainer

Demonstrate sustained, high-quality contributions for at least two release cycles.
Show ownership over an area (e.g., pipelines, config, docs).
Request nomination by opening an issue. Existing maintainers will vote and record the outcome there.

Stepping down

Maintainers may step down at any time by notifying the team. Access will be revoked and CODEOWNERS updated accordingly.

1.2 KiB Raw Permalink Blame History