From e73c8496b5989a244001f068877a6b72096fd372 Mon Sep 17 00:00:00 2001 From: woksin Date: Sat, 22 Aug 2026 18:27:19 +0200 Subject: [PATCH] Add contributor discussion route --- .github/ISSUE_TEMPLATE/config.yml | 3 +++ README.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 8312ffe..4b4c288 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1,8 @@ blank_issues_enabled: false contact_links: + - name: Questions and design discussion + url: https://discord.gg/kt4AMpV8WV + about: Ask Chronicle client questions and discuss API direction before opening a broad proposal - name: Security report url: https://github.com/Cratis/Chronicle.Python/security/advisories/new about: Report suspected vulnerabilities privately diff --git a/README.md b/README.md index 71d150d..1678f22 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ Chronicle kernel. 1. Read [CONTRIBUTING.md](CONTRIBUTING.md). 2. Follow the [client development guide](Documentation/client-development-guide.md). -3. Pick an open issue with a bounded acceptance checklist. +3. Start with [connection-string parsing](https://github.com/Cratis/Chronicle.Python/issues/2), the current good-first-issue contribution. 4. Submit a pull request from a fork or branch. ## Development setup