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: COMMUNITY.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# COMMUNITY.md
2
2
3
-
bluebutton-sample-client-nodejs-react is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
3
+
The Blue Button Node Sample Client is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
4
4
5
5
## Project Members
6
6
@@ -11,13 +11,9 @@ bluebutton-sample-client-nodejs-react is supported by a dedicated team of indivi
11
11
| Maintainer | Brandon Wang | ICF |
12
12
| Maintainer | Connor Lewellyn | Nava PBC |
13
13
14
-
See [CODEOWNERS.md](.github/CODEOWNERS.md) for a list of those responsible for the code and documentation in this repository.
15
-
16
-
See [Community Guidelines](#bluebutton-sample-client-nodejs-react-open-source-community-guidelines) on principles and guidelines for participating in this open source project.
17
-
18
14
## Roles & Responsibilities
19
15
20
-
The members of bluebutton-sample-client-nodejs-react community are responsible for guiding its development, ensuring quality standards, and fostering a collaborative environment. They play a vital role in making decisions about code contributions, handling releases, and ensuring the project meets its goals and objectives. Below is a list of the key members and their specific roles and responsibilities. We are eagerly seeking individuals who are interested in joining the community and helping shape and support these roles.
16
+
The members of Blue Button community are responsible for guiding its development, ensuring quality standards, and fostering a collaborative environment. They play a vital role in making decisions about code contributions, handling releases, and ensuring the project meets its goals and objectives. Below is a list of the key members and their specific roles and responsibilities. We are eagerly seeking individuals who are interested in joining the community and helping shape and support these roles.
21
17
22
18
### Maintainers:
23
19
@@ -28,8 +24,18 @@ The members of bluebutton-sample-client-nodejs-react community are responsible f
28
24
29
25
### Approvers:
30
26
27
+
-@jimmyfagan
28
+
-@clewellyn-nava
29
+
-@bwang-icf
30
+
-@stiwarisemanticbits
31
+
31
32
### Reviewers:
32
33
34
+
-@jimmyfagan
35
+
-@clewellyn-nava
36
+
-@bwang-icf
37
+
-@stiwarisemanticbits
38
+
33
39
| Roles | Responsibilities | Requirements | Defined by |
| member | active contributor in the community | multiple contributions to the project. | PROJECT GitHub org Committer Team |
@@ -52,9 +58,9 @@ Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COU
52
58
We'd like to acknowledge the following individuals for their past contributions of this project:
53
59
54
60
55
-
## bluebutton-sample-client-nodejs-react Open Source Community Guidelines
61
+
## Blue Button Open Source Community Guidelines
56
62
57
-
This document contains principles and guidelines for participating in the bluebutton-sample-client-nodejs-react open source community.
63
+
This document contains principles and guidelines for participating in the Blue Button open source community.
58
64
59
65
### Principles
60
66
@@ -74,7 +80,7 @@ All community members are expected to adhere to our [Code of Conduct](CODE_OF_CO
74
80
75
81
Information on contributing to this repository is available in our [Contributing file](CONTRIBUTING.md).
76
82
77
-
When participating in bluebutton-sample-client-nodejs-react open source community conversations and spaces, we ask individuals to follow the following guidelines:
83
+
When participating in Blue Button open source community conversations and spaces, we ask individuals to follow the following guidelines:
78
84
79
85
- When joining a conversation for the first time, please introduce yourself by providing a brief intro that includes:
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ We welcome improvements to the project documentation. This includes:
78
78
- Developer tutorials
79
79
- Code comments and inline documentation
80
80
81
-
Please file an [issue](https://github.com/CMSGov/ms-bb2-node-sdk/issues) for documentation improvements or submit a pull request with your changes.
81
+
Please file an [issue](https://github.com/CMSGov/bluebutton-sample-client-nodejs-react/issues) for documentation improvements or submit a pull request with your changes.
Copy file name to clipboardExpand all lines: README.md
+26-3Lines changed: 26 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,17 +134,40 @@ This project follows standard GitHub flow practices:
134
134
* Tests should be written for changes introduced
135
135
* Each change should be deployable to production
136
136
137
-
<!-- # Community
137
+
# Community
138
+
The Blue Button Web Server team is taking a community-first and open source approach to the product development of this tool. We believe government software should be made in the open and be built and licensed such that anyone can download the code, run it themselves without paying money to third parties or using proprietary software, and use it as they will.
138
139
139
-
# Community Guidelines -->
140
+
We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
141
+
142
+
We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets.
143
+
144
+
# Community Guidelines
145
+
Principles and guidelines for participating in our open source community are can be found in [COMMUNITY.md](COMMUNITY.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events.
140
146
141
147
# Governance
142
148
For more information about our governance, see [GOVERNANCE.md](GOVERNANCE.md).
143
149
144
150
# Feedback
145
151
Got questions? Need help troubleshooting? Want to propose a new feature? Contact the Blue Button 2.0 team and connect with the community in our [Google Group](https://groups.google.com/forum/#!forum/Developer-group-for-cms-blue-button-api).
146
152
147
-
# Policites
153
+
# Policies
154
+
### Open Source Policy
155
+
156
+
We adhere to the [CMS Open Source Policy](https://github.com/CMSGov/cms-open-source-policy). If you have any questions, just [shoot us an email](mailto:[email protected]).
157
+
158
+
### Security and Responsible Disclosure Policy
159
+
160
+
_Submit a vulnerability:_ Vulnerability reports can be submitted through [Bugcrowd](https://bugcrowd.com/cms-vdp). Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
161
+
162
+
For more information about our Security, Vulnerability, and Responsible Disclosure Policies, see [SECURITY.md](SECURITY.md).
163
+
164
+
### Software Bill of Materials (SBOM)
165
+
166
+
A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
167
+
168
+
In the spirit of [Executive Order 14028 - Improving the Nation's Cyber Security](https://www.gsa.gov/technology/it-contract-vehicles-and-purchasing-programs/information-technology-category/it-security/executive-order-14028), a SBOM for this repository is provided here: https://github.com/CMSGov/bluebutton-web-server/network/dependencies.
169
+
170
+
For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.
148
171
149
172
# Public Domain
150
173
This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/) as indicated in [LICENSE](LICENSE).
0 commit comments