Skip to content

Commit f6d3911

Browse files
rthanga1rthanga1
committed
add maintainer, security, codeowner files
1 parent 39cdb08 commit f6d3911

4 files changed

Lines changed: 157 additions & 0 deletions

File tree

‎.github/CODEOWNERS‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# Global Owners
2+
# These owners will be the default owners for everything in the repo
3+
# Unless a later match takes precedence, these users will be requested for
4+
# review when someone opens a pull request.
5+
# rthanga1 has admin privileges
6+
7+
* @rthanga1 @Sofiya-kumar @amosekr
8+
9+
# Documentation
10+
*.md @rthanga1 @Sofiya-kumar @amosekr
11+
docs/ @rthanga1 @Sofiya-kumar @amosekr
12+
13+
# GitHub configuration
14+
/.github/ @rthanga1
15+
16+
# Build and CI/CD
17+
*.yml @rthanga1 @Sofiya-kumar @amosekr
18+
*.yaml @rthanga1 @Sofiya-kumar @amosekr
19+
*.csproj @rthanga1 @Sofiya-kumar @amosekr
20+
*.sln @rthanga1 @Sofiya-kumar @amosekr
21+
22+
# Core Components
23+
/Trimble.Modus.Components/ @rthanga1 @Sofiya-kumar @amosekr
24+
25+
# Demo Application
26+
/DemoApp/ @rthanga1 @Sofiya-kumar @amosekr
27+
28+
# Security-related files
29+
SECURITY.md @rthanga1
30+
CODEOWNERS @rthanga1

‎.github/workflows/codeql.yml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
name: "CodeQL"
22

33
on:
4+
push:
5+
branches: [ "develop", "main" ]
6+
pull_request:
7+
branches: [ "develop", "main" ]
48
schedule:
59
- cron: "0 0 1 * *"
610
workflow_dispatch:

‎MAINTAINERS.md‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# Maintainers
2+
3+
This document lists the maintainers of the Trimble Modus Mobile MAUI Components project.
4+
5+
## Project Maintainers
6+
7+
The project is maintained by the following individuals:
8+
9+
| Name | Username | Role |
10+
|------|----------|------|
11+
| Ramaraj Thangapandi | [@rthanga1](https://github.com/rthanga1) | Lead Maintainer (Admin) |
12+
| Sofiya Kumar | [@Sofiya-kumar](https://github.com/Sofiya-kumar) | Maintainer |
13+
| Amose Sekar | [@amosekr](https://github.com/amosekr) | Maintainer |
14+
15+
- **Team Email**: [modus-mobile-contributors-ug@trimble.com](mailto:modus-mobile-contributors-ug@trimble.com)
16+
17+
## Responsibilities
18+
19+
Project maintainers are responsible for:
20+
21+
- **Code Review**: Reviewing and approving pull requests
22+
- **Release Management**: Creating releases and managing versioning
23+
- **Issue Triage**: Triaging issues and feature requests
24+
- **Security**: Responding to security vulnerabilities and maintaining security policies
25+
- **Community**: Supporting the developer community and maintaining project documentation
26+
- **Architecture**: Making architectural decisions and maintaining project roadmap
27+
28+
## Becoming a Maintainer
29+
30+
We welcome contributions from the community! To become a maintainer:
31+
32+
1. **Contribute Consistently**: Make regular, quality contributions to the project
33+
2. **Show Expertise**: Demonstrate deep understanding of the codebase and design system
34+
3. **Community Involvement**: Help with issues, code reviews, and community support
35+
4. **Contact Us**: Reach out to the current maintainers at [modus-mobile-contributors-ug@trimble.com](mailto:modus-mobile-contributors-ug@trimble.com)
36+
37+
## Maintainer Duties
38+
39+
All maintainers are expected to:
40+
41+
- Follow the [Code of Conduct](https://github.com/trimble-oss/.github/blob/main/CODE_OF_CONDUCT.md) (if available)
42+
- Review pull requests in a timely manner
43+
- Respond to issues and community questions
44+
- Participate in release planning and roadmap discussions
45+
- Maintain project documentation
46+
- Keep dependencies up to date
47+
- Monitor security vulnerabilities
48+
49+
## Decision Making Process
50+
51+
- **Major Changes**: Require consensus among maintainers
52+
- **Minor Changes**: Can be approved by any maintainer
53+
- **Emergency Security Updates**: Can be fast-tracked by any maintainer
54+
55+
## Contact
56+
57+
For maintainer-related questions or to express interest in becoming a maintainer, please contact:
58+
59+
- **Email**: [modus-mobile-contributors-ug@trimble.com](mailto:modus-mobile-contributors-ug@trimble.com)
60+
- **GitHub Issues**: [Create an issue](https://github.com/trimble-oss/modus-mobile-maui-components/issues) with the `maintainer` label
61+
62+
---
63+
64+
*This file is maintained by the project maintainers and updated as needed.*

‎SECURITY.md‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
We release patches for security vulnerabilities in the following versions:
6+
7+
| Version | Supported |
8+
| ------- | ------------------ |
9+
| Latest | :white_check_mark: |
10+
| < Latest| :x: |
11+
12+
## Reporting a Vulnerability
13+
14+
**Please do not report security vulnerabilities through public GitHub issues.**
15+
16+
Instead, please report security vulnerabilities to the Trimble security team:
17+
18+
- **Email**: [trimble-oss-contrib-admins-ug@trimble.com](mailto:trimble-oss-contrib-admins-ug@trimble.com)
19+
- **Subject Line**: [SECURITY] Trimble Modus Mobile MAUI Components - [Brief description]
20+
21+
Please include the following information in your report:
22+
23+
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
24+
- Full paths of source file(s) related to the manifestation of the issue
25+
- The location of the affected source code (tag/branch/commit or direct URL)
26+
- Any special configuration required to reproduce the issue
27+
- Step-by-step instructions to reproduce the issue
28+
- Proof-of-concept or exploit code (if possible)
29+
- Impact of the issue, including how an attacker might exploit the issue
30+
31+
## Response Process
32+
33+
1. **Acknowledgment**: We will acknowledge receipt of your vulnerability report within 48 hours
34+
2. **Investigation**: We will investigate and validate the vulnerability
35+
3. **Resolution**: We will work on a fix and coordinate disclosure timing with you
36+
4. **Disclosure**: We will publicly disclose the vulnerability after a fix is available
37+
38+
## Security Best Practices
39+
40+
When using Trimble Modus Mobile MAUI Components:
41+
42+
- Always use the latest version of the library
43+
- Keep your .NET MAUI framework updated
44+
- Follow secure coding practices in your applications
45+
- Regularly update your dependencies
46+
- Monitor security advisories for related packages
47+
48+
## Security Features
49+
50+
This library includes the following security measures:
51+
52+
- Regular dependency updates through Dependabot
53+
- Automated security scanning via CodeQL
54+
- Code review requirements for all changes
55+
- Vulnerability assessments on releases
56+
57+
## Contact
58+
59+
For questions about this security policy, please contact [modus-mobile-contributors-ug@trimble.com](mailto:modus-mobile-contributors-ug@trimble.com).

0 commit comments

Comments
 (0)