You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CODE_OF_CONDUCT.md
+12-15Lines changed: 12 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,19 +8,19 @@ In the interest of fostering an open and welcoming environment, we as contributo
8
8
9
9
Examples of behavior that contributes to creating a positive environment include:
10
10
11
-
* Using welcoming and inclusive language
12
-
* Being respectful of differing viewpoints and experiences
13
-
* Gracefully accepting constructive criticism
14
-
* Focusing on what is best for the community
15
-
* Showing empathy towards other community members
11
+
- Using welcoming and inclusive language
12
+
- Being respectful of differing viewpoints and experiences
13
+
- Gracefully accepting constructive criticism
14
+
- Focusing on what is best for the community
15
+
- Showing empathy towards other community members
16
16
17
17
Examples of unacceptable behavior by participants include:
18
18
19
-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20
-
* Trolling, insulting/derogatory comments, and personal or political attacks
21
-
* Public or private harassment
22
-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23
-
* Other conduct which could reasonably be considered inappropriate in a professional setting
19
+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+
- Trolling, insulting/derogatory comments, and personal or political attacks
21
+
- Public or private harassment
22
+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
24
24
25
25
## Our Responsibilities
26
26
@@ -34,13 +34,10 @@ This Code of Conduct applies both within project spaces and in public spaces whe
34
34
35
35
## Enforcement
36
36
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at mohammed.irfanulla.s1@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
37
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening a GitHub issue or contacting the maintainers listed in [CODEOWNERS](CODEOWNERS). 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.
38
38
39
39
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.
40
40
41
41
## Attribution
42
42
43
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/).
Thank you for your interest in contributing to Mustang! We welcome contributions in all forms — bug reports, feature requests, documentation improvements, and code changes.
4
+
5
+
---
6
+
7
+
## Code of Conduct
8
+
9
+
By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).
10
+
11
+
---
12
+
13
+
## How to Contribute
14
+
15
+
### Reporting Bugs
16
+
17
+
Before opening a bug report, please:
18
+
1. Search [existing issues](https://github.com/PhonePe/mustang/issues) to avoid duplicates.
19
+
2. Use the latest released version if possible.
20
+
21
+
When filing a bug, include:
22
+
- A clear description of the problem and expected behaviour.
23
+
- The version of Mustang you are using.
24
+
- A minimal reproducible example (code snippet or unit test).
25
+
- Stack traces or error logs, if relevant.
26
+
27
+
### Suggesting Features
28
+
29
+
Open a [GitHub issue](https://github.com/PhonePe/mustang/issues) with the label `enhancement`. Describe:
30
+
- The problem you are trying to solve.
31
+
- The proposed solution and any alternatives you considered.
32
+
33
+
---
34
+
35
+
## Development Setup
36
+
37
+
### Prerequisites
38
+
39
+
-**Java 17+** (OpenJDK or Temurin recommended)
40
+
-**Maven 3.9+**
41
+
- Git
42
+
43
+
### Build
44
+
45
+
```bash
46
+
git clone https://github.com/PhonePe/mustang.git
47
+
cd mustang
48
+
mvn clean verify
49
+
```
50
+
51
+
This compiles all modules (`mustang-models`, `mustang-core`, `mustang-dw-bundle`) and runs the full test suite.
52
+
53
+
### Running Tests
54
+
55
+
```bash
56
+
mvn test
57
+
```
58
+
59
+
To run tests for a specific module:
60
+
61
+
```bash
62
+
mvn test -pl mustang-core
63
+
```
64
+
65
+
### Code Style
66
+
67
+
- This project uses standard Java conventions with [Lombok](https://projectlombok.org/) for boilerplate reduction.
68
+
- Indentation: **tabs** (see `lombok.config` and `.editorconfig`).
69
+
- Line length: **120 characters** maximum.
70
+
- All public types and methods should have Javadoc.
71
+
72
+
---
73
+
74
+
## Pull Request Process
75
+
76
+
1.**Fork** the repository and create your branch from `main`.
77
+
2.**Write tests** for any new functionality or bug fixes.
78
+
3.**Ensure all tests pass**: `mvn clean verify`
79
+
4.**Update documentation** — update the relevant docs in `docs/` and `README.md` if you change behaviour.
80
+
5.**Open a Pull Request** against `main` with:
81
+
- A clear title and description.
82
+
- References to any related issues (`Fixes #123`).
83
+
84
+
### PR Requirements
85
+
86
+
- All CI checks must pass.
87
+
- At least one approval from a [CODEOWNER](CODEOWNERS).
88
+
- No unresolved review comments.
89
+
90
+
---
91
+
92
+
## Release Process
93
+
94
+
Releases are performed by maintainers:
95
+
96
+
1. Bump the version in all `pom.xml` files.
97
+
2. Tag the release on `main`.
98
+
3. The [`maven-central-publish.yml`](.github/workflows/maven-central-publish.yml) workflow deploys to Maven Central.
99
+
100
+
---
101
+
102
+
## Questions?
103
+
104
+
Open a [GitHub Discussion](https://github.com/PhonePe/mustang/discussions) or file an issue.
0 commit comments