feat: initialize Circle Camera Tauri application with camera access

- Added Cargo.toml for Rust dependencies and project configuration.
- Created Info.plist for macOS camera and microphone usage descriptions.
- Implemented build.rs for Tauri build process.
- Defined default and main capabilities in JSON files.
- Added various icon assets for application branding.
- Developed main Rust application logic with commands for greeting, window dragging, and closing.
- Set up Vue.js frontend with camera access and controls.
- Configured Vite for development and build processes.
- Established TypeScript support with appropriate configurations.

Author: devbyray

circle-camera/.gitignore .gitignorecircle-camera/.gitignore renamed to .gitignore

@@ -0,0 +1,49 @@
+# Accessibility Statement
+
+## Our Commitment
+
+We are committed to ensuring our project is accessible to everyone. We aim to comply with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.
+
+## Compliance Status
+
+Our project aims to be compliant with:
+
+- WCAG 2.1 Level AA
+- Section 508 requirements
+- ADA requirements
+
+## Features
+
+Accessibility features in our project include:
+
+- Keyboard navigation support
+- Screen reader compatibility
+- Sufficient color contrast
+- Text resizing without loss of functionality
+- Alternative text for images
+
+## Known Issues
+
+We are currently working to address these known accessibility issues:
+
+- [List any known issues]
+
+## Testing
+
+We regularly test our application for accessibility using:
+
+- Automated testing tools
+- Manual testing
+- Screen reader testing
+- Keyboard navigation testing
+
+## Feedback
+
+We welcome your feedback on the accessibility of this project. Please report accessibility barriers using one of these methods:
+
+- Submit an issue on our GitHub repository
+- Email us at [accessibility@example.com](mailto:accessibility@example.com)
+
+## This Statement
+
+This statement was last updated on [DATE].

circle-camera/.vscode/extensions.json .vscode/extensions.jsoncircle-camera/.vscode/extensions.json renamed to .vscode/extensions.json

@@ -0,0 +1,50 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+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 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 without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement 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.
+
+## Reporting Violations
+
+If you experience or witness unacceptable behavior, please report it by contacting
+the project team at [INSERT EMAIL ADDRESS]. All reports will be handled with
+discretion.
+
+## Enforcement
+
+Violations of the Code of Conduct may result in temporary or permanent exclusion
+from project participation, as determined by project maintainers.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

ACCESSIBILITY.md

@@ -0,0 +1,45 @@
+# Contributing to This Project
+
+Thank you for your interest in contributing to our project! This document provides guidelines and instructions for contributing.
+
+## Code of Conduct
+
+Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) before contributing.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+- Check if the bug has already been reported in the Issues section
+- Use the bug report template when creating a new issue
+- Provide detailed steps to reproduce the bug
+- Include screenshots if applicable
+
+### Suggesting Features
+
+- Check if the feature has already been suggested
+- Use the feature request template
+- Explain why the feature would be useful
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a new branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Commit with clear messages (`git commit -m 'Add some amazing feature'`)
+5. Push to your branch (`git push origin feature/amazing-feature`)
+6. Open a Pull Request
+
+## Development Process
+
+- All development should happen in feature branches
+- Pull requests require at least one review before merging
+- All tests must pass before a PR can be merged
+
+## Style Guidelines
+
+- Follow the existing code style
+- Write clear comments and documentation
+- Keep commit messages concise and descriptive
+
+Thank you for contributing!

CODE_OF_CONDUCT.md

@@ -0,0 +1,68 @@
+# Project Governance
+
+## Project Structure
+
+This project is maintained by a team of volunteers and follows a community-driven governance model.
+
+## Roles and Responsibilities
+
+### Project Maintainers
+
+- Review and merge pull requests
+- Release new versions
+- Establish project direction
+- Manage community interactions
+
+### Contributors
+
+- Submit pull requests
+- Report bugs and suggest features
+- Participate in discussions
+- Help with documentation and testing
+
+### Users
+
+- Provide feedback
+- Report bugs
+- Suggest features
+- Spread the word about the project
+
+## Decision Making Process
+
+1. **Proposals**: Anyone can propose changes via issues or discussions
+2. **Feedback**: Community feedback is gathered
+3. **Consensus**: We aim for consensus among maintainers
+4. **Implementation**: Once approved, changes are implemented
+
+## Becoming a Maintainer
+
+Contributors who show consistent, high-quality participation may be invited to become maintainers. The process includes:
+
+1. Nomination by an existing maintainer
+2. Review of contribution history
+3. Consensus among existing maintainers
+4. Formal invitation
+
+## Communication Channels
+
+- GitHub Issues and Discussions
+- Community Chat (e.g., Discord, Slack)
+- Regular community calls
+- Mailing list
+
+## Conflict Resolution
+
+When conflicts arise, we follow this process:
+
+1. Open discussion on the relevant platform
+2. Moderated debate with all stakeholders
+3. Attempt to reach consensus
+4. If consensus cannot be reached, maintainers make the final decision
+
+## Changes to Governance
+
+This governance document may evolve over time. Significant changes will be:
+
+1. Proposed via pull request
+2. Open for community feedback
+3. Implemented only after maintainer consensus