Maintainer Transition Setup

Description

This PR sets up the infrastructure for transitioning the project to new maintainers while establishing clear community standards and expectations.

Changes Made

📋 Community Standards & Guidelines

• Added CONTRIBUTING.md with comprehensive development guidelines and community standards
  • Zero tolerance policy for toxic behavior (one strike = ban)
  • Clear behavioral expectations for contributors
  • Technical setup and development workflow
  • Maintainer responsibilities and requirements
  • Release process documentation

🎫 GitHub Issue & PR Templates

• Added .github/ISSUE_TEMPLATE/config.yml - Template chooser configuration
  • Disables blank issues to encourage structured reports
  • Links to Discord, Contributing guidelines, and Security policy
• Added .github/ISSUE_TEMPLATE/bug_report.md - Bug report template
  • Structured format requiring environment details and reproduction steps
  • Links to community standards and Discord for support
• Added .github/ISSUE_TEMPLATE/feature_request.md - Feature request template
  • Guides users to provide use cases and implementation details
  • Includes maintainer transition context
• Added .github/ISSUE_TEMPLATE/question.md - Redirects questions to Discord
  • Explains difference between GitHub issues vs Discord discussions
  • Reduces support burden on issue tracker
• Added .github/pull_request_template.md - PR template
  • Comprehensive checklist for contributors and maintainers
  • Architecture compliance requirements
  • Security considerations

📖 README Updates

• Added prominent maintainer-seeking notice at top of README
  • Links to Discord community and Contributing guidelines
  • Clear timeline for applications (Feb 15) and selection (Feb 28)
• Enhanced Support section with Discord integration
  • Prioritizes Discord for questions and community support
  • Clear guidance on when to use GitHub vs Discord
• Updated Contributing section to emphasize community standards
• Fixed Changelog reference to point to GitHub Releases instead of non-existent CHANGELOG.md

Community Management Strategy

Discord Integration

• All templates and documentation point to Discord for:
  • Questions and general help
  • Real-time community support
  • Maintainer applications and discussions
• Discord server created: https://discord.gg/q59pTrN9AA

Behavioral Expectations

• Zero tolerance policy clearly communicated across all touchpoints
• One strike rule for toxic, demanding, or rude behavior
• Volunteer work emphasis throughout all documentation
• Respectful interaction requirements before technical contribution guidelines

Maintainer Transition Process

• Repository will remain under current account for Obsidian plugin store compliance
• New maintainers will be added as collaborators with appropriate permissions
• Clear timeline and application process established
• Community standards ensure quality maintainer candidates

Quality Assurance

• All GitHub templates tested and use correct file formats (.md with YAML frontmatter)
• Links verified and functional
• Consistent messaging across all documentation
• Clear separation between GitHub (technical issues) and Discord (support/questions)

Impact

This PR transforms the project from individual maintenance to community-driven development while:

• Protecting maintainer time through clear boundaries and Discord redirection
• Attracting quality contributors through professional documentation and standards
• Filtering out problematic users through upfront behavioral expectations
• Establishing sustainable processes for long-term project health

Testing

• All GitHub links functional
• Issue templates display correctly in GitHub UI
• Discord server setup and tested
• README formatting and links verified
• Template file formats confirmed (.md vs .yml)

This PR establishes the foundation for a smooth maintainer transition while protecting the project's quality and community standards.