Code of Conduct
Relevant source files
The following files were used as context for generating this wiki page:
The Code of Conduct for the MBBank project establishes a framework for community interaction and professional standards. It serves to ensure a harassment-free experience for all participants, regardless of their background, identity, or level of expertise. This policy applies to all community spaces and official public representations of the project.
Sources: CODE_OF_CONDUCT.md:3-8, CODE_OF_CONDUCT.md:33-35
Community Pledges and Standards
The project commits to maintaining a positive environment through specific behavioral standards. Contributors and leaders are expected to foster inclusivity and respect within the community.
Positive Behaviors
- Utilizing welcoming and inclusive language.
- Respecting diverse viewpoints and life experiences.
- Gracefully accepting and applying constructive criticism.
- Focusing on community-wide benefits.
- Demonstrating empathy toward other members.
Sources: CODE_OF_CONDUCT.md:12-18
Unacceptable Behaviors
The project explicitly prohibits several types of conduct to protect its members:
- Sexualized language, imagery, or unwanted advances.
- Trolling, derogatory comments, and personal/political attacks.
- Harassment in both public and private spheres.
- Unauthorized publishing of private information (doxing).
- Conduct inappropriate for a professional setting.
Sources: CODE_OF_CONDUCT.md:20-27
Enforcement and Responsibilities
Project maintainers hold the primary responsibility for clarifying and enforcing behavioral standards. They are empowered to take fair corrective actions against inappropriate, threatening, or harmful behavior.
Reporting Mechanism
Instances of abuse or harassment should be reported directly to the project maintainer.
| Contact Method | Target |
|---|---|
| duongtuan30306@gmail.com |
Sources: CODE_OF_CONDUCT.md:29-31, CODE_OF_CONDUCT.md:37-38
Incident Investigation
The following flowchart illustrates the conceptual flow of an incident report handling process based on the enforcement guidelines:
Project maintainers are obligated to maintain the privacy and security of the individual reporting the incident.
Sources: CODE_OF_CONDUCT.md:29-31, CODE_OF_CONDUCT.md:40-41
Project Integration and Safety
The principles of the Code of Conduct extend into technical contribution guidelines and security practices to protect users and the community.
Information Security
In alignment with professional conduct, contributors are strictly prohibited from including sensitive data in public issues or Pull Requests.
- Prohibited Items: Real banking credentials, account numbers, or session tokens.
- Security Reports: Vulnerabilities should be reported via the specific Security Vulnerability Report template rather than public channels.
Sources: CONTRIBUTING.md:65-66, SECURITY.md:9-11
Technical Standards
The project enforces code quality as a form of professional respect. Contributors must ensure their changes adhere to the established workflow.
Sources: CONTRIBUTING.md:27-38, CONTRIBUTING.md:54-58
Handling API Errors
The software implementation includes logic to handle "GW" (Gateway) error codes, which may arise from incorrect user interactions such as captcha failures. This ensures the system remains robust even when community members encounter errors.
- Captcha Errors (GW283): The system automatically retries authentication up to a defined limit (default 30 times).
- Session Errors (GW200): The system triggers re-authentication to maintain service continuity.
Sources: mbbank/sync/mbbank.py:126-127, mbbank/aio/mbbank.py:151-152
Summary
The MBBank project’s Code of Conduct is adapted from the Contributor Covenant v2.1. It establishes a professional baseline that prioritizes safety, privacy, and technical excellence. By participating in this project, contributors agree to uphold these standards, ensuring a collaborative environment focused on the project's goal of providing a lightweight API wrapper for banking services.