Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
150 lines (109 loc) · 3.29 KB

CONTRIBUTING.md

File metadata and controls

150 lines (109 loc) · 3.29 KB

Contributing to Kasapro

Terima kasih atas minat Anda untuk berkontribusi ke Kasapro! Kami menyambut semua bentuk kontribusi dari komunitas.

Code of Conduct

Kami berkomitmen untuk menyediakan lingkungan yang welcoming dan inclusive. Harap baca dan ikuti Code of Conduct kami.

How to Contribute

Reporting Bugs

Before reporting:

  1. Check existing issues
  2. Search untuk bug yang sama
  3. Jika sudah ada, add comment atau reaction

Bug report should include:

  • Clear description
  • Steps to reproduce
  • Expected vs actual behavior
  • Environment (OS, Docker version, browser)
  • Screenshots (jika ada)
  • Error messages atau logs

Submit via:

Suggesting Features

Feature request should include:

  • Clear description
  • Use case / benefit
  • Example workflow (jika ada)
  • Priority (optional)

Submit via:

Improving Documentation

Apa yang bisa dikontribusikan:

  • Fix typos dan grammar errors
  • Improve clarity dan readability
  • Add examples dan use cases
  • Translate documentation
  • Add screenshots atau diagrams

How to contribute:

  1. Fork repository
  2. Create branch: docs/your-improvement
  3. Make changes
  4. Submit pull request

Lihat Contribution Guidelines untuk detail.

Development Setup

For Documentation

  1. Fork repository
  2. Clone: 
    git clone https://github.com/your-username/kasapro-docs.git
cd kasapro-docs
  3. Create branch: 
    git checkout -b docs/your-improvement
  4. Make changes
  5. Commit: 
    git add .
git commit -m "docs: improve installation guide"
  6. Push: 
    git push origin docs/your-improvement
  7. Create pull request via GitHub

Pull Request Process

  1. Update documentation jika perlu
  2. Follow style guidelines (lihat di bawah)
  3. Test changes (jika applicable)
  4. Add clear description di PR
  5. Reference related issues (jika ada)
  6. Wait for review - maintainer akan review
  7. Address feedback - respond to comments
  8. Get merged - PR akan di-merge setelah approved

Style Guidelines

Documentation

  • Language: Bahasa Indonesia (user docs), English (tech docs)
  • Format: Markdown (.md)
  • Tone: Friendly, clear, concise
  • Structure: Clear headings, organized sections

Git Commit Messages

Format: <type>: <description>

Types:

  • docs: Documentation changes
  • fix: Bug fixes
  • feat: New features
  • refactor: Code refactoring
  • style: Formatting changes

Example:

docs: improve installation guide
fix: correct typo in troubleshooting

Recognition

Kontributor akan di-recognize di:

  • README.md (Contributors section)
  • Release notes (jika applicable)

Questions?

Terima kasih atas kontribusi Anda! 🙏