Bootstrap community infrastructure for open data format advocacy

[Copilot]

Establishes foundational community infrastructure for Tabulky organization focused on open data format processing and interoperability (JSON, CSV, XML, YAML).

Community Health Files

• CODE_OF_CONDUCT.md - Contributor Covenant adapted with open format principles
• CONTRIBUTING.md - Contribution guidelines emphasizing open standards, format preferences, and code quality expectations
• SECURITY.md - Vulnerability reporting process with data validation/sanitization best practices
• SUPPORT.md - Help resources and open format documentation links

GitHub Templates

• Issue templates - Bug reports, feature requests, documentation improvements with data format context fields (bilingual: Czech and English)
• PR template - Includes format impact assessment and open standard compliance checklist (bilingual: Czech and English)
• Discussion templates - Q&A, ideas, show-and-tell structured for format-specific conversations (bilingual: Czech and English)

Documentation

• README.md - Mission statement, supported formats reference table (with RFC/W3C standard links), community engagement paths
• FUNDING.yml - Sponsorship configuration placeholder

Bilingual Support

All templates are provided in both Czech and English with clear naming conventions (*_cs.md/*_cs.yml for Czech, *_en.md/*_en.yml for English). Users can select their preferred language when creating issues, discussions, or pull requests. The config.yml includes bilingual contact links for better accessibility.

Templates include format-specific fields to maintain focus on interoperability and standardization goals.

Original prompt

Začínáme, nejprve je potřeba pracovat na komunitě, která bude souznět se zpracováním a podporou otevřených formátů pro výměnu dat.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[langpavel]

@copilot vysvětli, proč jsou soubory v adresáři DISCUSSION_TEMPLATE jako yaml a zbytek je markdown?

[Copilot]

@copilot vysvětli, proč jsou soubory v adresáři DISCUSSION_TEMPLATE jako yaml a zbytek je markdown?

GitHub vyžaduje různé formáty pro různé typy šablon:

• Discussion templates (v DISCUSSION_TEMPLATE/) musí být ve formátu YAML (.yml) - to je požadavek GitHub API pro kategorie diskuzí
• Issue templates (v ISSUE_TEMPLATE/) používají Markdown (.md) s YAML frontmatter - to je tradiční formát pro issue šablony

Jedná se o standard GitHub platformy, ne o naši volbu. Diskuze byly přidány později než issues, a GitHub pro ně zavědl čistě YAML formát pro konzistentnější strukturu.

[langpavel]

@copilot Is there posibility to keep template bilingual or multimingual?
I'm targeting to Czech and English.

[Copilot]

@copilot Is there posibility to keep template bilingual or multimingual?
I'm targeting to Czech and English.

GitHub doesn't natively support multilingual templates, but there are several approaches:

1. Separate template files (recommended):

   • Create duplicate templates with language suffix: bug_report_cs.md, bug_report_en.md
   • Users see both options when creating an issue
   • Easier to maintain and update

2. Single template with both languages:

   • Include Czech and English sections side-by-side in one file
   • Can be cluttered, but keeps everything in one place
   • Example: "## 🐛 Bug Report / Nahlášení chyby"

3. config.yml with language selection:

   • Use config.yml to add links to language-specific blank issues
   • Guide users to external documentation in their language

Would you like me to implement option #1 (separate files for Czech and English)? This is the cleanest approach and follows GitHub best practices.

[langpavel]

@copilot Implement 'Separate template files' option, please

[Copilot]

@copilot Implement 'Separate template files' option, please

Implemented in commit 5fb9b93. All templates now have separate Czech (_cs) and English (_en) versions:

Structure:

• Issue templates: 3 types × 2 languages = 6 templates
• Discussion templates: 3 types × 2 languages = 6 templates
• PR templates: 2 templates (Czech + English)

Users will see both language options when creating issues, discussions, or pull requests. The config.yml was also updated with bilingual links.

📁 ISSUE_TEMPLATE/
├── 🇨🇿 bug_report_cs.md
├── 🇬🇧 bug_report_en.md
├── 🇨🇿 feature_request_cs.md
├── 🇬🇧 feature_request_en.md
├── 🇨🇿 documentation_cs.md
└── 🇬🇧 documentation_en.md