Add collaboration proposal for active development

Proposed collaboration on a fork of the original repository to centralize efforts and avoid fragmentation.
This commit is contained in:
Jacob Kraniak 2026-03-03 18:53:36 -05:00 committed by GitHub
parent bf9ddff7db
commit 5213d1591f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 0 deletions

10
collaboration_proposal.md Normal file
View File

@ -0,0 +1,10 @@
I've recently started actively developing a fork of trimstray/the-book-of-secret-knowledge on my branch JK_Revisions<a href="https://github.com/jacob-kraniak/the-book-of-secret-knowledge/tree/JK_Revisions" target="_blank" rel="noopener noreferrer nofollow"></a>.
This original repo has been inactive since late 2024 with over 100 open PRs, and your PR shows updates reflecting an interest in ongoing maintenance. I'd love to centralize efforts to avoid fragmentation. My branch already has linting setup, GitHub Actions for PR labeling, .gitignore/CONTRIBUTING.md improvements, and markdown placeholders ready for content.
If you have changes/PRs from earlier (or ongoing work), would you consider submitting them as PRs or Issues to my fork? We can coordinate there, keep momentum going, and if trimstray returns, push a clean consolidation back upstream.
Happy to discuss direction, merge strategy, or even make you a collaborator if it aligns.
Looking forward to your thoughts!
Jacob