From 0221ffe64f4e602827bde8339eb26750b4dbda25 Mon Sep 17 00:00:00 2001 From: Andre Levesque <0sniffs_scaled@icloud.com> Date: Fri, 14 Nov 2025 15:24:43 -0500 Subject: [PATCH 1/2] docs: refresh community guidelines --- CODE_OF_CONDUCT.md | 36 +++---- CONTRIBUTING.md | 254 ++++++++------------------------------------- README.md | 10 +- SECURITY.md | 100 +++++++++--------- profile/README.md | 10 +- 5 files changed, 122 insertions(+), 288 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 25fb33e..c13e629 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -38,7 +38,6 @@ As civic technologists, we have additional responsibilities: ### Community-Centered Development * **Listen first** - Understand community needs before proposing solutions - * **Include affected voices** - Center the people your project aims to serve * **Build with, not for** - Collaborate with community members as partners * **Question assumptions** - Regularly validate your understanding with real users @@ -46,7 +45,6 @@ As civic technologists, we have additional responsibilities: ### Ethical Technology Practices * **Privacy by design** - Minimize data collection and protect user privacy - * **Accessibility first** - Ensure your solutions work for people with diverse abilities * **Open by default** - Use open source tools and share your learnings * **Security consciousness** - Protect user data and system integrity @@ -54,7 +52,6 @@ As civic technologists, we have additional responsibilities: ### Inclusive Participation * **Welcome newcomers** - Help people get started regardless of technical experience - * **Share knowledge** - Teach and mentor others in the community * **Amplify diverse voices** - Ensure all community members can contribute * **Bridge divides** - Connect technical and non-technical community members @@ -82,7 +79,7 @@ This includes: ### How to Report -If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the community leaders at [contact email]. All reports will be handled with discretion. +If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the community leaders at [civictechwr@gmail.com](mailto:civictechwr@gmail.com). You can also mention `@CivicTechWR/organizers` in a GitHub issue or direct message the organizers in Slack. All reports will be handled with discretion. For urgent safety concerns, please contact local authorities. @@ -156,35 +153,30 @@ For broader community concerns: ### Technical Support -* **Accessibility guidance** - [Link to accessibility resources] - -* **Privacy compliance** - [Link to privacy guidelines] -* **Security best practices** - [Link to security resources] +* **Accessibility guidance** - [W3C Web Accessibility Initiative](https://www.w3.org/WAI/standards-guidelines/) +* **Privacy compliance** - [Office of the Privacy Commissioner of Canada](https://www.priv.gc.ca/en/) +* **Security best practices** - [OWASP Top Ten](https://owasp.org/www-project-top-ten/) ### Community Support -* **Conflict resolution** - [Link to mediation resources] - -* **Mental health** - [Link to mental health resources] -* **Professional development** - [Link to career and skill development] +* **Conflict resolution** - [Community Justice Initiatives Waterloo Region](https://cjiwr.com/) +* **Mental health** - [Canadian Mental Health Association Waterloo Wellington](https://cmhaww.ca/) +* **Professional development** - [Communitech resources](https://www.communitech.ca/) ### Local Resources -* **Crisis support** - [Local crisis helpline numbers] - -* **Legal assistance** - [Legal aid resources for tech/privacy issues] -* **Diversity and inclusion** - [Local D&I organizations] +* **Crisis support** - [Here 24/7 crisis services](https://here247.ca/) +* **Legal assistance** - [Waterloo Region Community Legal Services](https://www.wrcls.ca/) +* **Diversity and inclusion** - [Waterloo Region District School Board Equity Resources](https://www.wrdsb.ca/our-schools/equity/) ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at . +This Code of Conduct is adapted from the [Contributor Covenant 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html). Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). The civic tech specific guidelines were developed in collaboration with the CivicTechWR community and incorporate best practices from Code for America and other civic technology organizations. -[homepage]: https://www.contributor-covenant.org - ## Updates and Feedback This Code of Conduct is a living document that evolves with our community. We welcome feedback and suggestions for improvement. Please submit suggestions through: @@ -193,9 +185,9 @@ This Code of Conduct is a living document that evolves with our community. We we * Discussion at community meetings * Direct feedback to community leaders -**Last Updated**: [Date] -**Next Review**: [Date - typically annual] +**Last Updated**: November 14, 2025 +**Next Review**: May 14, 2026 --- -Questions about this Code of Conduct? Contact us at [contact email] or discuss at our next community meeting. +Questions about this Code of Conduct? Contact us at [civictechwr@gmail.com](mailto:civictechwr@gmail.com) or discuss at our next community meeting. You can also mention `@CivicTechWR/organizers` on GitHub or reach out via Slack if you need help quickly. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6a01cb9..e00759e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,231 +1,69 @@ -# Contributing to [Project Name] +# Contributing to CivicTechWR Projects -Welcome to our CivicTechWR project! We're excited to have you contribute to strengthening Waterloo Region's civic fabric through technology. +We are excited to welcome contributors of every experience level who want to build civic technology for Waterloo Region. This guide covers how to plug into the community, find meaningful work, and collaborate effectively. -## Code of Conduct +## Community & Meetings -This project follows the [CivicTechWR Code of Conduct](CODE_OF_CONDUCT.md). By participating, you're expected to uphold this code. Please report unacceptable behavior to [contact]. +- **Weekly meetup:** Wednesdays from 6:00–8:00 p.m. Eastern. Check the [CivicTechWR Meetup](https://www.meetup.com/civictechwr/) for the latest location, session topics, and hybrid details. +- **Slack workspace:** Join the conversation in [Slack](https://join.slack.com/t/civictechwr/shared_invite/zt-2ldijjy0i-gaGvPkuafPt9Zpn7jml70w). Introduce yourself in `#introductions` and connect with project teams in their channels. +- **Project board:** Browse active initiatives and open roles via the [CivicTechWR Projects board](https://github.com/orgs/CivicTechWR/projects/10/views/6?sliceBy%5Bvalue%5D=In+progress). -## How to Contribute +## Before You Start -### For New Contributors +1. **Review the Code of Conduct:** Participation requires following the [CivicTechWR Code of Conduct](CODE_OF_CONDUCT.md). +2. **Learn about the organization:** The [organization README](README.md) outlines how default files apply across CivicTechWR repositories. +3. **Find a good first task:** Explore open issues in the current repository, especially those labeled `good first issue`, `help wanted`, or `documentation`. +4. **Claim the work:** Comment on the issue to let others know you are investigating. Maintainers will confirm and offer context. -1. **Join our community meetings** (Wednesdays at [time/location]) -2. **Read our project documentation** (especially [DVF_SCORECARD.md](./DVF_SCORECARD.md)) -3. **Check our current issues** labeled `good first issue` -4. **Introduce yourself** in our communication channels +## Contribution Workflow -### Types of Contributions We Welcome +1. **Discuss the problem:** Align on scope, acceptance criteria, and any blockers in Slack or the issue thread. +2. **Create a branch:** Use a descriptive branch name such as `feature/add-bus-routes` or `fix/accessibility-audit`. +3. **Work iteratively:** Commit early and often. Keep changes focused so they are easy to review. +4. **Run quality checks:** Execute linting, tests, and accessibility checks that apply to the repository before pushing. +5. **Open a pull request:** Complete the prompts in the [pull request template](PULL_REQUEST_TEMPLATE.md), reference related issues, and request reviewers. -- 🐛 **Bug fixes** - Help us improve the user experience -- ✨ **New features** - Add functionality that serves our community -- 📚 **Documentation** - Make the project more accessible -- 🎨 **Design improvements** - Enhance usability and accessibility -- 📊 **User research** - Help us understand community needs -- 🧪 **Testing** - Ensure our solutions work for everyone -- 🌐 **Translation** - Make our project accessible to more communities - -## Getting Started - -### 1. Set Up Your Development Environment - -```bash -# Clone the repository -git clone [your-repo-url] -cd [project-name] - -# Run the setup script -./scripts/setup.sh - -# Start development server -[project-specific commands] -``` - -### 2. Find Something to Work On - -- Check our [issues page](../../issues) for current needs -- Look for issues labeled: - - `good first issue` - Perfect for newcomers - - `help wanted` - We need community support - - `bug` - Something that needs fixing - - `enhancement` - New features or improvements - -### 3. Before You Start Coding - -- Comment on the issue to let others know you're working on it -- Ask questions if anything is unclear -- Check if the issue aligns with our [current DVF priorities](./DVF_SCORECARD.md) - -## Development Workflow - -### 1. Create a Branch - -```bash -git checkout -b feature/your-feature-name -# or -git checkout -b bugfix/issue-description -``` - -### 2. Make Your Changes - -- Write clear, commented code -- Follow our style guidelines (see below) -- Add tests for new functionality -- Update documentation as needed - -### 3. Test Your Changes - -```bash -# Run the test suite -[test command] - -# Test manually with different user scenarios -# Verify accessibility standards are met -``` - -### 4. Commit Your Changes - -```bash -git add . -git commit -m "Brief description of changes - -Longer explanation if needed, including: -- What problem this solves -- How you tested it -- Any breaking changes" -``` - -### 5. Submit a Pull Request - -- Push your branch to GitHub -- Create a pull request using our [PR template](../.github/PULL_REQUEST_TEMPLATE.md) -- Link to any related issues -- Request review from team members - -## Code Standards +## Development Guidelines ### General Principles -- **Accessibility first** - Follow WCAG 2.1 guidelines -- **Privacy by design** - No unnecessary data collection -- **Community-focused** - Consider how this serves Waterloo Region -- **Maintainable** - Write code that volunteers can understand and maintain - -### Style Guidelines - -#### JavaScript/TypeScript - -- Use meaningful variable names -- Add JSDoc comments for public functions -- Follow [Prettier](https://prettier.io/) formatting -- Use ESLint for code quality - -#### Python - -- Follow [PEP 8](https://pep8.org/) style guidelines -- Use type hints where helpful -- Add docstrings for functions and classes - -#### CSS - -- Use semantic class names -- Follow BEM methodology for complex components -- Ensure responsive design -- Test with screen readers - -#### Documentation - -- Write in clear, accessible language -- Include examples where helpful -- Keep README and docs up to date - -## Testing Guidelines - -### What to Test - -- **Functionality** - Does it work as expected? -- **Accessibility** - Can everyone use it? -- **Performance** - Does it load quickly? -- **Security** - Are there any vulnerabilities? -- **Mobile** - Does it work on different devices? - -### Testing Tools - -- [List project-specific testing tools] -- Accessibility: [WAVE](https://wave.webaim.org/), [axe](https://www.deque.com/axe/) -- Performance: [Lighthouse](https://developers.google.com/web/tools/lighthouse) - -## Civic Tech Specific Guidelines - -### Data Handling - -- **Minimize data collection** - Only collect what's necessary -- **Protect privacy** - Never expose personal information -- **Use open data** - Prefer publicly available datasets -- **Document sources** - Always cite data sources - -### Community Engagement - -- **Test with real users** - Not just team members -- **Consider diverse needs** - Different abilities, languages, tech comfort -- **Think about sustainability** - Can the community maintain this? - -### Transparency - -- **Open by default** - Make code and decisions public -- **Document decisions** - Explain why choices were made -- **Share learnings** - Help other civic tech projects - -## Communication - -### Where to Get Help - -- **Weekly meetings**: Wednesdays at [time/location] -- **Slack/Discord**: [link to communication channel] -- **Issues**: For technical questions, tag @[maintainer] -- **Email**: [contact email] for sensitive matters - -### Response Time Expectations - -This is a volunteer-driven project. Please be patient with response times: - -- **Pull requests**: We aim to review within 1 week -- **Issues**: We'll respond within 2 weeks -- **Community questions**: Usually answered same week - -## Recognition - -We value all contributions! Contributors will be: +- **Accessibility first:** Align with [WCAG 2.1](https://www.w3.org/TR/WCAG21/) standards wherever possible. +- **Privacy by design:** Collect and retain only the data a feature requires. +- **Community impact:** Prioritize features that help Waterloo Region residents. +- **Maintainability:** Write code and documentation future volunteers can understand. -- Listed in our project credits -- Invited to Demo Day presentations -- Connected with CTWR's broader network -- Given reference letters for civic tech work (upon request) +### Language- and Tool-Specific Tips -## Project Lifecycle +- **JavaScript/TypeScript:** Follow the repository’s lint configuration, format with Prettier when available, and add JSDoc or TSDoc comments for public APIs. +- **Python:** Adhere to [PEP 8](https://pep8.org/), add docstrings, and prefer type hints for new modules. +- **CSS and design:** Use semantic markup, responsive layouts, and contrast-checked color palettes. Test components with assistive technologies whenever feasible. +- **Documentation:** Default to plain language, keep examples current, and update onboarding docs when workflows change. -### Season Timeline +## Testing Expectations -- **Weeks 1-3**: Project setup and team formation -- **Weeks 4-6**: Core development and user research -- **Weeks 7-9**: Feature development and testing -- **Weeks 10-11**: Refinement and demo preparation -- **Week 12**: Demo Day presentation +- **Automated tests:** Run the commands listed in the repository README (for example, `npm test`, `pytest`, or language-specific linters). +- **Accessibility checks:** Use tools such as [WAVE](https://wave.webaim.org/), [axe DevTools](https://www.deque.com/axe/), or browser accessibility inspectors. +- **Manual validation:** Confirm key user journeys succeed on desktop and mobile devices. Document any known limitations in the pull request. -### After the Season +## Communication Channels -- The project may continue with community maintainers -- Code will remain open source for future use -- Documentation will be preserved for learning +- **Slack:** Coordinate in [Slack](https://join.slack.com/t/civictechwr/shared_invite/zt-2ldijjy0i-gaGvPkuafPt9Zpn7jml70w); project channels are the fastest way to get help. +- **GitHub issues:** Use issues for tracking work, design discussions, and decisions so knowledge stays discoverable. +- **Email:** Sensitive or non-public matters can be sent to [civictechwr@gmail.com](mailto:civictechwr@gmail.com). +- **GitHub organizers team:** Mention `@CivicTechWR/organizers` when a decision or review needs organizer attention. -## Questions? +This is a volunteer-driven community. Maintainers aim to respond to new issues within a week and review pull requests within two weeks, but availability varies. Flag time-sensitive work early so the team can coordinate support. -Don't hesitate to ask! We're here to support your contribution to civic tech in Waterloo Region. +## Recognition & Support -**New to open source?** Check out [First Timers Only](https://www.firsttimersonly.com/) for general guidance. +- Contributors are highlighted during demo nights and in community updates. +- Organizers can provide reference letters that describe your CivicTechWR impact. +- We encourage pairing and co-working sessions—ask in Slack if you would like a buddy to collaborate with. -**New to civic tech?** Read about [Code for America's principles](https://www.codeforamerica.org/values) that guide our work. +## Questions or Ideas? ---- +- Post in the project channel on [Slack](https://join.slack.com/t/civictechwr/shared_invite/zt-2ldijjy0i-gaGvPkuafPt9Zpn7jml70w). +- Open a GitHub discussion or issue to capture proposals and feedback. +- Connect with organizers at the next Wednesday meetup for real-time support. -Thank you for helping build technology that serves our community! 🚀 +Thank you for contributing your skills to CivicTechWR! Together we build technology that helps Waterloo Region thrive. diff --git a/README.md b/README.md index 8da7e19..5382e89 100644 --- a/README.md +++ b/README.md @@ -15,17 +15,17 @@ Default files that appear in all CivicTechWR repositories (unless overridden): - **CODE_OF_CONDUCT.md** - Our community standards and expectations - **CONTRIBUTING.md** - How to contribute to our projects - **SECURITY.md** - Security policy and vulnerability reporting -- **SUPPORT.md** - How to get help with our projects - **ISSUE_TEMPLATE/** - Issue templates for bugs, features, and questions - **PULL_REQUEST_TEMPLATE.md** - Pull request template ### Organization Profile -- **profile/README.md** - Organization profile shown on https://github.com/CivicTechWR +- **profile/README.md** - Organization profile shown on the [CivicTechWR GitHub page](https://github.com/CivicTechWR) ## Why This Repository? GitHub automatically uses files in `.github` as defaults across all repositories in the organization. This ensures: + - Consistent community standards across all projects - Easier onboarding for new contributors - Centralized maintenance of policies and guidelines @@ -34,9 +34,9 @@ GitHub automatically uses files in `.github` as defaults across all repositories Found an issue or want to suggest improvements to our community files? Open an issue or pull request! -- **Meetup:** https://www.meetup.com/civictechwr/ -- **Website:** https://civictechwr.org -- **Email:** civictechwr@gmail.com +- **Meetup:** [CivicTechWR Meetup](https://www.meetup.com/civictechwr/) +- **Website:** [CivicTechWR.org](https://civictechwr.org/) +- **Email:** [civictechwr@gmail.com](mailto:civictechwr@gmail.com) ## Resources diff --git a/SECURITY.md b/SECURITY.md index e6fa3f4..eb65687 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -4,10 +4,10 @@ This CivicTechWR project template is actively maintained. Security updates are provided for: -| Version | Supported | -| ------- | ------------------ | -| Latest | :white_check_mark: | -| Previous| :x: | +| Version | Supported | +| -------- | ------------------ | +| Latest | :white_check_mark: | +| Previous | :x: | ## Reporting a Vulnerability @@ -15,16 +15,17 @@ This CivicTechWR project template is actively maintained. Security updates are p If you discover a security vulnerability in this project template, please report it responsibly: -**Email:** [security@civictechwr.org] (if available) or project maintainers -**Response Time:** We aim to respond within 48 hours +**Email:** [civictechwr@gmail.com](mailto:civictechwr@gmail.com) (mention “security” in the subject line) +**GitHub escalation:** Mention `@CivicTechWR/organizers` on an issue or pull request if you need organizer attention. +**Response Time:** Volunteers aim to acknowledge reports within 48 hours. ### For Project-Specific Security Issues -If you're using this template for your CTWR project and discover a security issue: +If you are using this template for your CivicTechWR project and discover a security issue: -1. **Do NOT create a public GitHub issue** -2. **Contact the project team directly** through private channels -3. **Follow responsible disclosure** - give teams time to fix issues +1. **Do not create a public GitHub issue.** +2. **Contact the project team directly** through private channels, or email [civictechwr@gmail.com](mailto:civictechwr@gmail.com) if you are unsure who to reach. +3. **Follow responsible disclosure** by giving maintainers time to investigate and fix the issue before any public discussion. ## Security Reporting Process @@ -38,73 +39,74 @@ If you're using this template for your CTWR project and discover a security issu ### What Happens Next -1. **Acknowledgment** - We'll confirm receipt within 48 hours -2. **Assessment** - We'll evaluate the severity and impact -3. **Fix Development** - We'll work on a solution -4. **Disclosure** - We'll coordinate public disclosure with you -5. **Recognition** - We'll acknowledge your contribution (if desired) +1. **Acknowledgment** - We will confirm receipt within 48 hours. +2. **Assessment** - We will evaluate the severity and impact. +3. **Fix development** - We will work on a solution and share timelines when possible. +4. **Disclosure** - We will coordinate responsible disclosure with you. +5. **Recognition** - We will acknowledge your contribution if you would like. ## Security Best Practices for CTWR Projects ### For Project Teams -- **Review the [Security Guide](docs/SECURITY_GUIDE.md)** before starting development -- **Use secure coding practices** throughout development -- **Enable automated security scanning** in your repository -- **Follow the [Gitleaks Response Guide](.github/docs/gitleaks-response.md)** whenever the secret scanning workflow reports a finding -- **Conduct security reviews** before major releases -- **Train team members** on civic tech security considerations +- **Plan security from the start** by identifying data flows and trust boundaries in project docs or issues. +- **Use secure coding practices** throughout development and review contributions for potential risks. +- **Enable automated scanning** such as GitHub secret scanning, Dependabot alerts, and linting that focuses on security concerns. +- **Review collaborator access quarterly** and remove or reduce access for accounts that have not contributed recently to limit exposure from dormant accounts. +- **Conduct security reviews** before major releases or partner deployments. +- **Onboard volunteers** with guidance on handling sensitive community data. ### For Community Members -- **Report security issues responsibly** - Don't create public issues for vulnerabilities -- **Keep dependencies updated** - Regularly update project dependencies -- **Follow security guidelines** when contributing code -- **Respect user privacy** when testing or providing feedback +- **Report security issues responsibly** by using the private channels listed above. +- **Keep dependencies updated** in your contributions to minimize known vulnerabilities. +- **Follow security guidelines** when contributing code or documentation. +- **Respect user privacy** when testing or providing feedback. ## Civic Tech Security Considerations ### Community Data Protection -CivicTech projects often handle sensitive community data. Special considerations: +Civic tech projects often handle sensitive community data. Special considerations: -- **Privacy by design** - Minimize data collection -- **Transparency** - Be clear about data use -- **Community consent** - Get explicit permission for data collection -- **Secure storage** - Protect any collected data -- **Data retention** - Delete data when no longer needed +- **Privacy by design** - Minimize data collection. +- **Transparency** - Be clear about data use. +- **Community consent** - Get explicit permission for data collection when possible. +- **Secure storage** - Protect any collected data. +- **Data retention** - Delete data when no longer needed. ### Government Partnership Security When working with government partners: -- **Understand data classification** - Know sensitivity levels -- **Follow compliance requirements** - Meet government security standards -- **Secure communication** - Use encrypted channels for sensitive discussions -- **Access controls** - Limit who can access government data -- **Audit trails** - Log access to sensitive information +- **Understand data classification** so you know the sensitivity of information you handle. +- **Follow compliance requirements** aligned to the partner’s standards. +- **Use secure communication** channels for sensitive discussions. +- **Apply access controls** to limit who can access government data. +- **Maintain audit trails** that log access to sensitive systems or records. ## Security Resources ### For CTWR Teams -- **[Security Guide](docs/SECURITY_GUIDE.md)** - Comprehensive security documentation -- **[Technical Design](docs/TECHNICAL_DESIGN.md)** - Security architecture guidance -- **[Contributing Guidelines](docs/CONTRIBUTING.md)** - Security requirements for contributors +- **[CivicTechWR Contributing Guide](CONTRIBUTING.md)** - Collaboration and security expectations for contributors. +- **[GitHub secret scanning](https://docs.github.com/en/code-security/secret-security/about-secret-scanning)** - Overview of GitHub’s secret scanning capabilities. +- **[Dependabot alerts](https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)** - Monitoring dependency vulnerabilities. ### External Resources -- **OWASP Top 10** - Common web application security risks -- **Canadian Centre for Cyber Security** - Government security resources -- **Privacy Commissioner of Canada** - Privacy law guidance -- **PIPEDA** - Personal Information Protection and Electronic Documents Act +- **[OWASP Top Ten](https://owasp.org/www-project-top-ten/)** - Common web application security risks. +- **[Canadian Centre for Cyber Security](https://www.cyber.gc.ca/en/)** - Government security guidance. +- **[Office of the Privacy Commissioner of Canada](https://www.priv.gc.ca/en/)** - Privacy law guidance. +- **[PIPEDA overview](https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/)** - Personal Information Protection and Electronic Documents Act resources. ## Security Contacts ### How to Reach Us -- **Primary channels:** email `civictechwr@gmail.com`, post in the private organizers channel, or send a direct message in the CTWR Slack workspace -- **GitHub escalation:** mention `@CivicTechWR/organizers` on the relevant issue or pull request to notify the organizers team +- **Primary channel:** Email [civictechwr@gmail.com](mailto:civictechwr@gmail.com) (include context or repository name in the subject line). +- **Slack escalation:** Direct message the organizers or post in the private organizers channel if you already have access. +- **GitHub escalation:** Mention `@CivicTechWR/organizers` on the relevant issue or pull request to notify the organizers team. ### Response Expectations @@ -141,9 +143,9 @@ CivicTechWR projects support security research conducted in good faith: Contact us through: -- **CTWR Community Meetings** - Weekly Wednesday meetings -- **GitHub Discussions** - For general security questions -- **Direct Contact** - For sensitive security matters +- **CivicTechWR community meetings** - Weekly Wednesday sessions noted on Meetup. +- **GitHub Discussions** - For general security questions that do not contain sensitive details. +- **Direct contact** - Email [civictechwr@gmail.com](mailto:civictechwr@gmail.com) for sensitive security matters. **This policy applies to:** @@ -153,4 +155,4 @@ Contact us through: --- -*This security policy is part of our commitment to building safe, trustworthy civic technology that serves our community responsibly.* +_This security policy is part of our commitment to building safe, trustworthy civic technology that serves our community responsibly._ diff --git a/profile/README.md b/profile/README.md index 7b07bf3..6b698f1 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,8 +1,10 @@ -## Welcome to CivicTech Waterloo Region +# Welcome to CivicTech Waterloo Region -*Please standby, CTWR is coming back to life and taking over* +Please standby—CTWR is coming back to life and taking over. - Visit our website [CivicTechWR.org](https://civictechwr.org/) - Check out what projects are currently happening here: [CTWR Projects In Progress](https://github.com/orgs/CivicTechWR/projects/10/views/6?sliceBy%5Bvalue%5D=In+progress) -- Join us on Slack here: https://join.slack.com/t/civictechwr/shared_invite/zt-2hk4c93hv-DEIbxR_z1xKj8cZmayVHTw -- Schedule: https://docs.google.com/spreadsheets/d/1hAxstCyiVBdYeSQlIrlkhnSntJLJ3kNnoCuechFJN7E/edit?gid=0#gid=0 +- Join us on [Slack](https://join.slack.com/t/civictechwr/shared_invite/zt-2ldijjy0i-gaGvPkuafPt9Zpn7jml70w) +- Share your ideas on the [CTWR Feedback Portal](https://feedback.ctwr.org/) +- Collaborate with the community in [CoLab](https://discourse.ctwr.org/) +- Schedule: [Community schedule](https://docs.google.com/spreadsheets/d/1hAxstCyiVBdYeSQlIrlkhnSntJLJ3kNnoCuechFJN7E/edit?gid=0#gid=0) From c1b5fc047d7238a194530895cef9ca047aac6128 Mon Sep 17 00:00:00 2001 From: Andre Levesque <0sniffs_scaled@icloud.com> Date: Fri, 14 Nov 2025 15:42:02 -0500 Subject: [PATCH 2/2] refactor: align templates with CivicTechWR values --- ISSUE_TEMPLATE/accessibility_issue.yml | 2 +- ISSUE_TEMPLATE/bug_report.yml | 2 +- ISSUE_TEMPLATE/community_partnership.yml | 15 +++++---- ISSUE_TEMPLATE/feature_request.yml | 16 +++++---- ISSUE_TEMPLATE/general_task.yml | 16 +++++---- ISSUE_TEMPLATE/quick_task.yml | 15 +++++---- ISSUE_TEMPLATE/user_research.yml | 15 +++++---- PULL_REQUEST_TEMPLATE.md | 41 ++++++------------------ 8 files changed, 54 insertions(+), 68 deletions(-) diff --git a/ISSUE_TEMPLATE/accessibility_issue.yml b/ISSUE_TEMPLATE/accessibility_issue.yml index bf1348b..90100d7 100644 --- a/ISSUE_TEMPLATE/accessibility_issue.yml +++ b/ISSUE_TEMPLATE/accessibility_issue.yml @@ -185,7 +185,7 @@ body: - Community members affected: [estimated number/percentage] - Essential services impacted: [which civic functions] - Equity considerations: [who is excluded by this barrier] - - DVF score impact: [effect on civic exciting score] + - Community values affected: [accessibility, privacy, community impact, etc.] - type: checkboxes id: priority-factors attributes: diff --git a/ISSUE_TEMPLATE/bug_report.yml b/ISSUE_TEMPLATE/bug_report.yml index d2d1f3e..d68a389 100644 --- a/ISSUE_TEMPLATE/bug_report.yml +++ b/ISSUE_TEMPLATE/bug_report.yml @@ -146,7 +146,7 @@ body: placeholder: | - Number of users potentially affected: [estimate] - Community services impacted: [list services] - - DVF score impact: [which areas affected] + - Community values affected: [accessibility, privacy, community impact, etc.] - Urgency for community: [timeline needs] - type: checkboxes id: testing-help diff --git a/ISSUE_TEMPLATE/community_partnership.yml b/ISSUE_TEMPLATE/community_partnership.yml index 38c1db1..bc33f3d 100644 --- a/ISSUE_TEMPLATE/community_partnership.yml +++ b/ISSUE_TEMPLATE/community_partnership.yml @@ -134,15 +134,16 @@ body: - label: Impact measurement and evaluation - type: textarea - id: dvf-impact + id: community-values attributes: - label: DVF Impact - description: How does this partnership affect our DVF scorecard? + label: CivicTechWR Values Alignment + description: How does this partnership support our core principles? placeholder: | - - Community Partner score: [expected impact] - - Talent & Team: [skills/capacity gained] - - Technically Exciting: [technical validation/requirements] - - Civic Exciting: [community reach/impact enhanced] + - Accessibility first: [how the partnership reduces barriers] + - Privacy by design: [data sharing/stewardship considerations] + - Community impact: [community outcomes enabled] + - Maintainability: [support for sustainable collaboration] + - Inclusive collaboration: [ways partners/community are involved] - type: checkboxes id: partnership-stage-activities diff --git a/ISSUE_TEMPLATE/feature_request.yml b/ISSUE_TEMPLATE/feature_request.yml index 7f22df8..d96077f 100644 --- a/ISSUE_TEMPLATE/feature_request.yml +++ b/ISSUE_TEMPLATE/feature_request.yml @@ -11,15 +11,17 @@ body: Thanks for taking the time to suggest a feature! Help us understand how this will benefit our community. - type: checkboxes - id: dvf-category + id: community-values attributes: - label: DVF Impact Category - description: Which DVF areas does this feature primarily impact? + label: CivicTechWR Values Alignment + description: Which core principles does this feature support? options: - - label: Community Partner - Improves stakeholder engagement - - label: Talent & Team - Enhances team productivity or skills - - label: Technically Exciting - Introduces new technology or innovation - - label: Civic Exciting - Increases community impact or accessibility + - label: Accessibility first - reduces barriers for diverse users + - label: Privacy by design - stewards community data responsibly + - label: Community impact - addresses real civic needs + - label: Maintainability - keeps the project volunteer-friendly + - label: Inclusive collaboration - engages partners and community voices + - label: Not sure yet - needs discussion - type: textarea id: user-story diff --git a/ISSUE_TEMPLATE/general_task.yml b/ISSUE_TEMPLATE/general_task.yml index 9887331..c4e9e1c 100644 --- a/ISSUE_TEMPLATE/general_task.yml +++ b/ISSUE_TEMPLATE/general_task.yml @@ -83,15 +83,17 @@ body: required: true - type: checkboxes - id: dvf-impact + id: community-values attributes: - label: DVF Impact Areas - description: Which DVF areas does this task support? + label: CivicTechWR Values Alignment + description: Which core principles does this task support? options: - - label: Community Partner - Improves stakeholder relationships - - label: Talent & Team - Builds team capacity or engagement - - label: Technically Exciting - Advances technical innovation - - label: Civic Exciting - Increases community impact + - label: Accessibility first - reduces barriers for diverse users + - label: Privacy by design - stewards community data responsibly + - label: Community impact - addresses real civic needs + - label: Maintainability - keeps the project volunteer-friendly + - label: Inclusive collaboration - engages partners and community voices + - label: Not sure yet - needs discussion - type: dropdown id: effort-estimate diff --git a/ISSUE_TEMPLATE/quick_task.yml b/ISSUE_TEMPLATE/quick_task.yml index 7c12827..03ddb3b 100644 --- a/ISSUE_TEMPLATE/quick_task.yml +++ b/ISSUE_TEMPLATE/quick_task.yml @@ -25,15 +25,16 @@ body: description: Optional background, links to Figma/Miro/Docs. placeholder: 'Meeting notes from Sept 23' - type: dropdown - id: dvf + id: impact-focus attributes: - label: DVF Impact (pick one) + label: Impact Focus (pick one) options: - - No impact / N/A - - Community Partner - - Talent & Team - - Technically Exciting - - Civic Exciting + - Accessibility & inclusion + - Community impact + - Privacy & data stewardship + - Volunteer sustainability / maintainability + - Operational/housekeeping (no direct community impact) + - Not sure yet validations: required: false - type: checkboxes diff --git a/ISSUE_TEMPLATE/user_research.yml b/ISSUE_TEMPLATE/user_research.yml index 7c40a25..fa4cd4d 100644 --- a/ISSUE_TEMPLATE/user_research.yml +++ b/ISSUE_TEMPLATE/user_research.yml @@ -121,15 +121,16 @@ body: - label: Account for different economic situations - type: textarea - id: dvf-connection + id: community-values attributes: - label: DVF Framework Connection - description: How does this research connect to our DVF scorecard? + label: CivicTechWR Values Connection + description: How does this research connect to our community principles? placeholder: | - - Community Partner: [how this validates partner needs] - - Talent & Team: [skills needed, community involvement] - - Technically Exciting: [technical validation needed] - - Civic Exciting: [community impact validation] + - Accessibility first: [which barriers or needs are explored] + - Privacy by design: [how data is respected] + - Community impact: [community questions answered] + - Maintainability: [insights that support sustainable solutions] + - Inclusive collaboration: [community voices engaged] - type: dropdown id: timeline diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md index 65de1e3..55564d3 100644 --- a/PULL_REQUEST_TEMPLATE.md +++ b/PULL_REQUEST_TEMPLATE.md @@ -1,6 +1,6 @@ # Pull Request -> Quick change? Fill in **Summary**, the sections you touched (Testing / Accessibility / DVF), mark the rest as N/A, and hit create. The full template is here when you need it. +> Quick change? Fill in **Summary**, the sections you touched (Testing / Accessibility / Community values), mark the rest as N/A, and hit create. The full template is here when you need it. ## Summary @@ -78,37 +78,16 @@ - [ ] Change supports community self-service goals - [ ] Improves community access to services/information -## DVF Assessment Impact +## Community Values Alignment -How does this change affect our project's DVF scorecard? +How does this change support CivicTechWR's core principles? -**Community Partner** (1-5): [Current score] → [New score if changed] - -- [ ] No impact -- [ ] Improves partner engagement or value delivery -- [ ] Addresses partner feedback or requirements -- [ ] Concern: [explain any negative impact] - -**Talent & Team** (1-5): [Current score] → [New score if changed] - -- [ ] No impact -- [ ] Improves team productivity or learning -- [ ] Demonstrates new technical skills -- [ ] Concern: [explain any negative impact] - -**Technically Exciting** (1-5): [Current score] → [New score if changed] - -- [ ] No impact -- [ ] Introduces innovative technology or approach -- [ ] Improves technical architecture or quality -- [ ] Concern: [explain any negative impact] - -**Civic Exciting** (1-5): [Current score] → [New score if changed] - -- [ ] No impact -- [ ] Increases community impact or reach -- [ ] Improves user experience for community members -- [ ] Concern: [explain any negative impact] +- [ ] Accessibility first - reduces barriers for diverse users +- [ ] Privacy by design - stewards community data responsibly +- [ ] Community impact - addresses real civic needs +- [ ] Maintainability - keeps the project volunteer-friendly +- [ ] Inclusive collaboration - engages partners and community voices +- [ ] Not sure yet - needs discussion ## Demo Day Readiness @@ -218,5 +197,5 @@ How does this change affect our project's DVF scorecard? - Focus on community impact and civic tech best practices - Verify accessibility standards are maintained -- Check that change aligns with DVF framework and season goals +- Check that change aligns with CivicTechWR community values and season goals - Ensure code quality supports volunteer contributor maintenance