Skip to content

Commit 75b97a1

Browse files
committed
Add contributing
1 parent b174270 commit 75b97a1

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

CONTRIBUTING.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Contributing to DSP APPSEC INFRASTRUCTURE CODE
2+
3+
Thank you for contributing to this repository. The project is sponsored by Broad Institute who have collectively added tremendous value over the years. This page describes how we handle external contributions to maximize the impact of your work and reduce delays in getting your PRs accepted.
4+
5+
### Run your idea by us first
6+
If you're thinking of writing a non-trivial amount of code to solve a problem, we encourage you to reach out via an issue to get feedback. It is likely we will have suggestions about how to proceed. It's also possible, though hopefully rare, that there is a hidden impediment that would prevent your solution from working. If we spot it at the idea stage, we can give you feedback much earlier than if we have to reject your pull request!
7+
8+
### Maintenance considerations
9+
The AppSec team at Broad maintains and enhances the application to serve the needs of both Broad Institute and external users. Sometimes, we may identify a feature idea or pull request that works and is a good idea, but we may be unable to commit to maintaining it indefinitely. This may be because it does not align with the strategic direction of the project, or simply due to time constraints on the maintainers. Once again, it always helps to solicit early feedback.
10+
11+
### Reviewing pull requests
12+
Because pull requests require a substantial amount of time to review carefully, we prioritize and schedule them into our sprints alongside all of our other work. We realize this may be frustrating and strive to provide timely updates about PR status.
13+
14+
### Questions
15+

0 commit comments

Comments
 (0)