Docs: Complete README overhaul, add LICENSE, CONTRIBUTING, CODE_OF_CONDUCT

Author: root

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,155 @@
+# Contributing to iCAD Dispatch
+
+Thank you for your interest in contributing to iCAD Dispatch!
+
+---
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please be respectful and constructive.
+
+---
+
+## How to Contribute
+
+### Reporting Bugs
+
+1. **Search existing issues** - Check if the bug has already been reported
+2. **Create a new issue** - Use the Bug Report template
+3. **Include**:
+   - Clear description of the problem
+   - Steps to reproduce
+   - Expected vs actual behavior
+   - iCAD Dispatch version
+   - Browser/OS information
+   - Relevant logs (if applicable)
+
+### Suggesting Features
+
+1. **Search existing feature requests** - Avoid duplicates
+2. **Create a new issue** - Use the Feature Request template
+3. **Describe**:
+   - The problem you're trying to solve
+   - Proposed solution
+   - Alternative solutions considered
+   - Use case (who benefits?)
+
+### Pull Requests
+
+1. **Fork the repository**
+2. **Create a feature branch**: `git checkout -b feature/my-feature`
+3. **Make your changes** - Follow the coding standards
+4. **Add tests** - If applicable
+5. **Update documentation** - If needed
+6. **Commit with clear messages**: `git commit -m "Add feature: ..."`
+7. **Push to your fork**: `git push origin feature/my-feature`
+8. **Submit a Pull Request** - Fill out the template
+
+---
+
+## Development Setup
+
+### Prerequisites
+
+- Docker and Docker Compose
+- Python 3.12+ (for local development without Docker)
+- SQLite
+
+### Local Development
+
+```bash
+# Clone the repository
+git clone https://github.com/renfrewcountyscanner/icad_dispatch_v2.git
+cd icad_dispatch_v2
+
+# Copy environment file
+cp .env_example .env
+
+# Edit .env with your settings
+nano .env
+
+# Start with local build (development)
+docker compose -f docker-compose.production.yml up -d
+
+# View logs
+docker logs -f icad_dispatch
+
+# Run migrations (if needed)
+# The app runs migrations automatically on startup
+```
+
+### Running Tests
+
+```bash
+# Run the container in development mode
+docker compose -f docker-compose.production.yml up -d --build
+
+# Check logs for errors
+docker logs icad_dispatch
+```
+
+---
+
+## Coding Standards
+
+### Python
+
+- Follow [PEP 8](https://www.python.org/dev/peps/pep-0008/)
+- Use type hints where appropriate
+- Add docstrings for new functions
+- Keep functions focused and modular
+
+### JavaScript
+
+- Use ES6+ features
+- Add JSDoc comments for functions
+- Keep code consistent with existing style
+
+### Templates (Jinja2)
+
+- Indent with 4 spaces
+- Keep templates clean and readable
+- Use appropriate Bootstrap classes
+
+### Git Commit Messages
+
+- Use present tense: "Add feature" not "Added feature"
+- Keep first line under 72 characters
+- Reference issues where applicable
+
+**Example**:
+```
+Add user system permissions
+
+- Add is_admin and is_active columns to users table
+- Create user_systems table for per-system permissions
+- Add admin_required and permission_required decorators
+- Update session handling to store user permissions
+```
+
+---
+
+## Pull Request Checklist
+
+- [ ] Tests pass (if applicable)
+- [ ] Code follows coding standards
+- [ ] Documentation updated (if needed)
+- [ ] Commit messages are clear
+- [ ] PR description explains the changes
+
+---
+
+## Getting Help
+
+- **GitHub Issues**: For bug reports and feature requests
+- **Discussions**: For questions and general help
+
+---
+
+## Recognition
+
+Contributors will be listed in the README and/or CHANGELOG.
+
+---
+
+Thank you for contributing!