📖Terminology
Understand some of the key acronyms and terms we use on the project.
Last updated
Understand some of the key acronyms and terms we use on the project.
Last updated
The following acronyms represent abbreviations of federal stakeholder groups and concepts related to the grants process.
| Term | Definition |
|---|---|
The following terms we commonly use to describe our work on the codebase and other technical aspects of the project.
| Term | Definition |
|---|---|
Major updates to the content of this page will be added here.
| Date | Update | Notes |
|---|---|---|
FACE
Financial Assistance Committee for E-Governance — various federal agencies who all do grantmaking
ECGAP
Executive Committee on Grants Administration Policy
CGMOs
Council of Grants Management Officers — various federal agencies who all do grantmaking
NOFO
Notice of Funding Opportunity — also called "grant announcements"
S2S (Grantors and Applicants)
System to System - Grants.gov provides an extensive list of web services for Applicants and Agencies to perform the Find and Apply functions using our System-to-System (S2S) interface.
Applicants and grantor agencies typically integrate the Grants.gov web services into their existing grant management systems to provide a seamless user interface to their grants staff.
FDP
ISSO
Information System Security Officer
SSP
System Security Plan – a series of documentation that describe the security controls we have or plan to implement to secure our production software system.
ATO
Authority to Operate - a status that approves an IT system for use in a particular organization.
PB
Participatory Budgeting
Code repository
A set of folders that contain all of the code needed to build, run, and host a piece of software (or other technical tools). Sometimes used interchangeably with "codebase".
Version control
A mechanism for storing current version of a codebase as well as the history of changes made to that code.
Git
The most commonly used system for version control.
GitHub
A software platform that lets users store and host code repositories that are version controlled with git. It also offers a series of other tools that help teams plan and manage work related to their codebase.
Issue
GitHub's way of tracking tasks or units of work that need to be completed within a project. Note: An "issue" doesn't necessarily represent something that is "wrong" with the codebase. It could be a new feature or piece of functionality.
Bug
Something wrong with codebase that causes unexpected behavior, and requires "debugging" to identify and fix the issue.
Pull request
Sometimes abbreviated to "PR", a pull request is a way to ask project maintainers to review and accept changes to the codebase. These changes might include new features or bug fixes.
Sprint
A specific period of time (commonly two weeks) during which a team works on a defined set of tasks and aims to deliver new functionality.
100k deliverable
Describes major product work streams at a 100,000 foot view, which aim to deliver a set of related features over a multi-year timeline, e.g. "Improved discovery".
30k deliverable
Describes major product features at a 30,00 foot view, which aim to deliver new or improved functionality to users over a multi-month timeline, e.g. "Static site public launch".
10k deliverable
Describes a group of related tasks at a 10,000 foot view, which aim to deliver functionality necessary for a given 30k deliverable over a multi-sprint period, e.g. "Static site public launch - content updates."
2/12/2024
Initial Content
Updated with Initial content
4/23/2024
Acronym change
Updated acronym from FDG to FDP