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
<!-- TODO: Who are the points of contact in your project who are responsible/accountable for the project? This can often be an engineering or design manager or leader, who may or may not be the primary maintainers of the project. List them by GitHub Username-->
4
+
5
+
6
+
- ftrotter-gov
7
+
- spopelka-dsac
8
+
9
+
10
+
## Repo Domains
11
+
12
+
<!--
13
+
The Repo Domains section of your CODEOWNERS.md file helps manage code review responsibilities efficiently. Each domain represents a different aspect of the repository, such as documentation, frontend, backend, DevOps, testing, etc. In this section, list each domain and assign the appropriate GitHub usernames or teams responsible for that domain. This ensures that pull requests (PRs) are reviewed by the right experts, maintaining high code quality and relevance.
14
+
15
+
For example:
16
+
17
+
/docs/ @doc-team @johnsmith @janedoe
18
+
19
+
/frontend/ @frontend-team @alice @bob
20
+
21
+
/backend/ @backend-team @charlie @dana
22
+
23
+
Furthermore, GitHub teams are a good feature for managing groups of contributors who need to be notified about specific domains within a repository. By creating and using GitHub teams, you can allow contributors to ping multiple relevant experts simultaneously.
24
+
25
+
To set up GitHub teams:
26
+
27
+
- Navigate to your organization's settings and select "Teams".
28
+
- Create a new team for each domain, such as @frontend-team, @backend-team, or @doc-team.
29
+
- Add the relevant members to each team. Ensure that the team includes all the individuals who should be notified about PRs in their domain.
30
+
- When filling out the Repo Domains section in your CODEOWNERS.md file, use the team handles instead of or alongside individual usernames. This way, when a contributor opens a PR affecting a specific domain, they can simply tag the team, and every member of that team will be notified.
Thank you for helping maintain accurate code.json information for this project! This data helps track open source projects across the organization and ensures compliance with federal open source policies.
12
+
13
+
### Which field would you like to update?
14
+
15
+
<!-- Please check the appropriate box(es) by changing [ ] to [x] -->
16
+
17
+
-[ ] name
18
+
-[ ] description
19
+
-[ ] longDescription
20
+
-[ ] status
21
+
-[ ] permissions
22
+
-[ ] organization
23
+
-[ ] repositoryURL
24
+
-[ ] vcs
25
+
-[ ] laborHours
26
+
-[ ] platforms
27
+
-[ ] categories
28
+
-[ ] softwareType
29
+
-[ ] languages
30
+
-[ ] maintenance
31
+
-[ ] date
32
+
-[ ] tags
33
+
-[ ] contact information
34
+
-[ ] localisation
35
+
-[ ] repositoryType
36
+
-[ ] userInput
37
+
-[ ] fismaLevel
38
+
-[ ] group
39
+
-[ ] subsetInHealthcare
40
+
-[ ] userType
41
+
-[ ] repositoryHost
42
+
-[ ] maturityModelTier
43
+
-[ ] Other (please specify below)
44
+
45
+
---
46
+
47
+
### Please describe the changes needed
48
+
49
+
<!-- Provide details about what changes are needed and why -->
50
+
51
+
### Additional Context
52
+
53
+
<!-- Any other information that might help us understand your request -->
54
+
55
+
---
56
+
57
+
### Helpful Resources
58
+
59
+
-[Generate your code.json entry](https://dsacms.github.io/codejson-generator/) - Use this form to generate a valid code.json
60
+
-[code.json Guidance](https://github.com/DSACMS/gov-codejson/tree/main/docs) - Documentation on code.json
about: Ticket for requesting outside collaborator to be added to repository
4
+
title: "[REQUEST]: "
5
+
labels: # TODO: Add labels for categorization of requests
6
+
assignees: # TODO: Add organization owner or help desk team
7
+
---
8
+
9
+
## Request an outside collaborator to be added to repository
10
+
11
+
For individuals that are not members of the DSACMS GitHub organization, these outside collaborators can request access to a repository. Fill out this issue to file the request or make a pull request to the `COMMUNITY.md` file, then a repository admin will grant access.
12
+
13
+
### Information Required
14
+
15
+
Name of individual:
16
+
GitHub username:
17
+
Role in project:
18
+
Role in repository according to COMMUNITY.md (Maintainer, Approver, Reviewer):
19
+
20
+
### Additional Notes (Optional)
21
+
22
+
<!-- Provide any additional context or requests -->
"project_name": "What is the name of the project or software?",
36
+
"project_repo_name": "What is the name of the repository?",
37
+
"project_org": "What CMS GitHub organization is it under?",
38
+
"description": "Provide a short description of the software. It should be a single line containing a single sentence. Maximum 150 characters are allowed.",
39
+
"long_description": "Provide longer description of the software, between 150 and 10000 chars. It is meant to provide an overview of the capabilities of the software for a potential user.",
40
+
"status": "What is the status of the project?",
41
+
"license": "What license is the project under?",
42
+
"usage_type": "What is the usage type for this project? For more information on each option, visit github.com/DSACMS/gov-codejson",
43
+
"repository_host": "Where is the repository hosted?",
44
+
"vcs": "What version control system is used?",
45
+
"forks": "How many forks does the repository have?",
46
+
"platforms": "What platform does the software runs on? Separate items by commas.",
47
+
"categories": "What categories best describes the project? Separate items by commas. List of categories here: https://yml.publiccode.tools/categories-list.html?highlight=categories",
48
+
"software_type": "What type of software is the project?",
49
+
"languages": "What programming language(s) is the software written in? Separate items by commas.",
50
+
"maintenance": "How is the software maintained?",
51
+
"contract_number": "What is the contractor number of the project?",
52
+
"tags": "Provide a list of tags to describe the software for search. Separate items by commas.",
53
+
"contact_name": "A point of contact is needed for the project. What is the name of the point of contact?",
54
+
"contact_email": "What is email address of the point of contact?",
55
+
"feedback_mechanisms": "What are methods a repository receives feedback from the community (e.g. URL to GitHub repository issues page, website, email)",
56
+
"localisation": "Does the software support multiple spoken languages?",
57
+
"repository_type": "What type of repository is this project?",
58
+
"user_input": "Does the project accept user input? (e.g. allows user to query a database, allows login by users, upload files, etc.)",
59
+
"fisma_level": "What FISMA level is this project classified as? Learn more: https://security.cms.gov/learn/federal-information-security-modernization-act-fisma#perform-system-risk-categorization",
60
+
"group": "Which group at CMS is the project part of?",
61
+
"projects": "What project is the repository associated with? Separate items by commas.",
62
+
"systems": "What systems does the repository use or interface with? Separate items by commas.",
63
+
"upstream": "What upstream dependencies does the repository use? Separate items by commas.",
64
+
"subset_in_healthcare": "Which subset of healthcare does the project belong to?",
print("scc (https://github.com/boyter/scc) not found on system")
46
+
47
+
#Otherwise just use previous value as a default value.
48
+
returnNone
49
+
50
+
defprompt_exemption_text(exemptionType):
51
+
print(f"ℹ️ You have selected {exemptionType} for your Usage Type.")
52
+
returninput("Please provide a one or two sentence justification for the exemption used. For more information on Usage Type, visit github.com/DSACMS/gov-codejson: ")
53
+
54
+
defformat_multi_select_fields(text):
55
+
iftext=="":
56
+
return []
57
+
58
+
new_text=text.split(",")
59
+
60
+
new_text= [text.strip() fortextinnew_text]
61
+
62
+
returnnew_text
63
+
64
+
defupdate_code_json(json_file_path):
65
+
# Read the JSON
66
+
withopen(json_file_path, 'r') asfile:
67
+
data=json.load(file)
68
+
69
+
# Add date_information and labor hours to the JSON
0 commit comments