In the interest of fostering an open, welcoming, and inclusive environment, we as contributors, maintainers, and the MSIS Development Team pledge to make participation in our project and community a harassment-free experience for everyone, regardless of:
- 🌍 Age, body size, disability, ethnicity, gender identity and expression
- 🎓 Level of experience, education, socio-economic status
- 🌐 Nationality, personal appearance, race, religion
- 🏳️🌈 Sexual identity and orientation
We are committed to providing a safe, respectful, and professional environment for all participants in the MedSIS App community.
Examples of behavior that contributes to creating a positive environment include:
Professional Conduct
- ✅ Using welcoming and inclusive language
- ✅ Being respectful of differing viewpoints and experiences
- ✅ Gracefully accepting constructive criticism
- ✅ Focusing on what is best for the community and students
- ✅ Showing empathy towards other community members
Technical Excellence
- ✅ Writing clean, maintainable, and well-documented code
- ✅ Following established coding standards and guidelines
- ✅ Conducting thorough code reviews with constructive feedback
- ✅ Maintaining 100% test coverage for contributions
- ✅ Prioritizing security and data privacy in all implementations
Collaboration
- ✅ Communicating clearly and professionally
- ✅ Responding to feedback and questions in a timely manner
- ✅ Helping other contributors learn and grow
- ✅ Sharing knowledge and best practices
- ✅ Acknowledging the contributions of others
Data Privacy & Security
- ✅ Protecting student and institutional data at all times
- ✅ Complying with the Data Privacy Act of 2012 (RA 10173)
- ✅ Reporting security vulnerabilities responsibly
- ✅ Maintaining confidentiality of sensitive information
- ✅ Following secure coding practices
Examples of unacceptable behavior by participants include:
Harassment & Discrimination
- ❌ The use of sexualized language or imagery
- ❌ Unwelcome sexual attention or advances
- ❌ Trolling, insulting/derogatory comments, and personal or political attacks
- ❌ Public or private harassment
- ❌ Discriminatory jokes or language
Unprofessional Conduct
- ❌ Publishing others' private information without explicit permission
- ❌ Deliberately introducing bugs or security vulnerabilities
- ❌ Plagiarizing code or documentation
- ❌ Submitting low-quality or untested code
- ❌ Ignoring code review feedback without justification
Privacy Violations
- ❌ Unauthorized access to student or institutional data
- ❌ Sharing sensitive information outside authorized channels
- ❌ Violating the Data Privacy Act of 2012 (RA 10173)
- ❌ Misusing personal information for unauthorized purposes
- ❌ Failing to report known security vulnerabilities
Malicious Activities
- ❌ Attempting to compromise system security
- ❌ Distributing malware or malicious code
- ❌ Conducting denial-of-service attacks
- ❌ Social engineering or phishing attempts
- ❌ Any other conduct which could reasonably be considered inappropriate
Project maintainers are responsible for:
-
Clarifying Standards
- Maintaining and communicating behavior standards
- Providing clear guidelines for contributions
- Updating documentation as needed
-
Enforcement
- Taking appropriate and fair corrective action
- Removing, editing, or rejecting contributions that violate this Code of Conduct
- Temporarily or permanently banning contributors for inappropriate behavior
-
Protection
- Protecting the privacy and security of all participants
- Ensuring compliance with data protection regulations
- Maintaining a safe and inclusive environment
Contributors are responsible for:
-
Adherence
- Following this Code of Conduct in all project spaces
- Respecting the decisions of project maintainers
- Accepting feedback gracefully
-
Quality
- Submitting high-quality, tested code
- Following coding standards and guidelines
- Maintaining documentation
-
Security
- Protecting sensitive information
- Reporting security issues responsibly
- Following secure coding practices
This Code of Conduct applies to all project spaces, including:
Online Spaces
- 📧 Email communications (dev@msis.eduisync.io)
- 💬 GitHub issues, pull requests, and discussions
- 📝 Code reviews and comments
- 🌐 Project website and documentation
- 💻 Development environments and repositories
Offline Spaces
- 🏢 Project meetings and events
- 🎓 Educational institution interactions
- 🤝 Professional conferences and gatherings
- 📞 Phone and video calls related to the project
This Code of Conduct also applies when an individual is representing the project or community in public spaces.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the MSIS Development Team:
Primary Contact:
- 📧 Email: conduct@msis.eduisync.io
- 🔒 Subject: [CODE OF CONDUCT] Brief description
Alternative Contacts:
- 📧 Security Issues: security@msis.eduisync.io
- 📧 General Concerns: dev@msis.eduisync.io
What to Include in Your Report:
- Your contact information
- Names (real, nicknames, or pseudonyms) of individuals involved
- Description of the incident
- Date and time of the incident
- Location/context where it occurred
- Any supporting documentation (screenshots, logs, etc.)
- Any other relevant information
All reports will be reviewed and investigated promptly and fairly. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
Privacy Guarantees:
- ✅ Reporter identity will be kept confidential
- ✅ Information shared only with necessary parties
- ✅ No retaliation against reporters
- ✅ Updates provided to reporter on case status
┌─────────────────────────────────────────────────────────────┐
│ ENFORCEMENT WORKFLOW │
└─────────────────────────────────────────────────────────────┘
1. 📝 REPORT RECEIVED
↓
- Acknowledge receipt within 24 hours
- Assign case number
- Protect reporter confidentiality
↓
2. 🔍 INITIAL REVIEW
↓
- Assess severity and urgency
- Gather additional information
- Identify involved parties
↓
3. 🔎 INVESTIGATION
↓
- Review evidence and documentation
- Interview relevant parties (if needed)
- Consult with team members
↓
4. ⚖️ DETERMINATION
↓
- Evaluate against Code of Conduct
- Determine appropriate response
- Document findings
↓
5. 📢 ACTION
↓
- Implement enforcement decision
- Notify involved parties
- Update reporter on outcome
↓
6. 📊 FOLLOW-UP
↓
- Monitor for compliance
- Provide support if needed
- Document case closure
Project maintainers will follow these Community Impact Guidelines in determining consequences:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome.
Consequence: A private, written warning providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Duration: Immediate
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved for a specified period. This includes avoiding interactions in community spaces as well as external channels. Violating these terms may lead to a temporary or permanent ban.
Duration: 30 days
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community. No public or private interaction with the people involved is allowed during this period. Violating these terms may lead to a permanent ban.
Duration: 90 days
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment, or aggression toward individuals or classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community. All access to project resources will be revoked.
Duration: Permanent
Violations of the Data Privacy Act of 2012 (RA 10173) will result in:
⚠️ Immediate investigation- 🚫 Immediate suspension of access
- 📋 Reporting to appropriate authorities
- ⚖️ Potential legal action
Security-related violations will result in:
- 🔒 Immediate access revocation
- 🔍 Comprehensive security audit
- 📢 Notification to affected parties
- 🚨 Reporting to security team
This Code of Conduct is adapted from:
- Contributor Covenant, version 2.1
- Mozilla Community Participation Guidelines
- Data Privacy Act of 2012 (Republic Act No. 10173)
The MSIS Development Team reserves the right to update this Code of Conduct at any time. Contributors will be notified of significant changes via:
- 📧 Email notification
- 📝 GitHub announcement
- 🌐 Website update
Version History:
- v1.0 - December 5, 2025 - Initial release
If you have questions about this Code of Conduct or need clarification on any points:
Contact:
- 📧 Email: conduct@msis.eduisync.io
- 🌐 Website: https://msis.eduisync.io
- 📚 Documentation: See CONTRIBUTING.md
Response Time:
- General questions: 2-3 business days
- Urgent concerns: Within 24 hours
- Security issues: Immediate response
By participating in the MedSIS App project, you acknowledge that you have read, understood, and agree to abide by this Code of Conduct.
Thank you for helping make MedSIS App a welcoming, inclusive, and professional community! 🙏
Code of Conduct Team:
- 📧 Primary: conduct@msis.eduisync.io
- 🔒 Security: security@msis.eduisync.io
- 💬 General: dev@msis.eduisync.io
Institution:
- 🏫 Southwestern University PHINMA
- 🏥 College of Medicine
- 📍 Cebu City, Philippines
MSIS Development Team
Version 1.0.0 - December 5, 2025
Copyright © 2025 MSIS. All Rights Reserved.
"Building a respectful, inclusive, and secure community for medical education."