Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE #2259: Update authorizing official to senior official #304

Merged
merged 5 commits into from
Jul 2, 2024

Conversation

therealslimhsiehdy
Copy link
Contributor

@therealslimhsiehdy therealslimhsiehdy commented Jun 20, 2024

Ticket

Resolves #2259

Changes

Screenshot 2024-06-20 at 12 00 15 PM

Screenshot 2024-06-20 at 12 08 42 PM

Screenshot 2024-06-20 at 12 09 22 PM

Screenshot 2024-06-20 at 12 11 39 PM

Screenshot 2024-06-20 at 12 12 24 PM

Screenshot 2024-06-20 at 12 13 15 PM

Screenshot 2024-06-20 at 12 14 31 PM Screenshot 2024-06-20 at 12 14 52 PM

Context for reviewers

Setup

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

  • Met the acceptance criteria, or will meet them in a subsequent PR
  • Created/modified automated tests
  • Added at least 2 developers as PR reviewers (only 1 will need to approve)
  • Messaged on Slack or in standup to notify the team that a PR is ready for review
  • Changes to “how we do things” are documented in READMEs and or onboarding guide
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the assoicated migrations file has been commited.

Ensured code standards are met (Original Developer)

  • All new functions and methods are commented using plain language
  • Did dependency updates in Pipfile also get changed in requirements.txt?
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
  • Checked keyboard navigability
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
  • Add at least 1 designer as PR reviewer

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

  • Pulled this branch locally and tested it
  • Reviewed this code and left comments
  • Checked that all code is adequately covered by tests
  • Made it clear which comments need to be addressed before this work is merged
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the assoicated migrations file has been commited.

Ensured code standards are met (Code reviewer)

  • All new functions and methods are commented using plain language
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values
  • (Rarely needed) Did dependency updates in Pipfile also get changed in requirements.txt?

Validated user-facing changes as a developer

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing

  • Checked keyboard navigability

  • Meets all designs and user flows provided by design/product

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers, the suggestion is to use ones that the developer didn't (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Note: Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist

As a designer reviewer, I have

Verified that the changes match the design intention

  • Checked that the design translated visually
  • Checked behavior
  • Checked different states (empty, one, some, error)
  • Checked for landmarks, page heading structure, and links
  • Tried to break the intended flow

Validated user-facing changes as a designer

  • Checked keyboard navigability

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Screenshots

Copy link
Contributor

@erinysong erinysong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified that all content changes display on the cloud pages sandbox. Requested a small spelling change but LGTM to merge after that is fixed!

@@ -2,6 +2,6 @@ Complete your request as quickly as possible by taking these actions.{.checklist

- **Eligibility**: [Make sure your organization is eligible to have a .gov domain](../../domains/eligibility/).
- **Domain name**: [Choose an available .gov domain that complies with our requirements](../../domains/choosing/).
- **Authorizing official**: [Find out who your authorizing official is](../../domains/eligibility/#you-must-have-approval-from-an-authorizing-official-within-your-organization) and make sure they approve your request.
- **Request form**: Gather [all the information you’ll need](../../domains/before/#information-you’ll-need-to-complete-the-domain-request-form) to complete your domain request.
- **Senior official**: [Find out who your senior official is](../../domains/eligibility/#you-must-have-approval-from-an-senior-official-within-your-organization) and make sure they approve your request.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit: ...-a-senior-official-...

- **Authorizing official**: [Find out who your authorizing official is](../../domains/eligibility/#you-must-have-approval-from-an-authorizing-official-within-your-organization) and make sure they approve your request.
- **Request form**: Gather [all the information you’ll need](../../domains/before/#information-you’ll-need-to-complete-the-domain-request-form) to complete your domain request.
- **Senior official**: [Find out who your senior official is](../../domains/eligibility/#you-must-have-approval-from-an-senior-official-within-your-organization) and make sure they approve your request.
- **Request form**: Gather [all the information you’ll need](../../domains/before/#information-you-will-need-to-complete-the-domain-request) to complete your domain request.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

@kristinacyin kristinacyin requested review from kristinacyin and removed request for a team June 24, 2024 15:45
Copy link
Contributor

@kristinacyin kristinacyin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! ⭐

@@ -30,9 +30,9 @@ Using a .gov domain for your online services (like your website or email) helps

### An official from your organization needs to approve your domain request

All domain requests must be approved by an authorizing official. This person must be in a role of significant, executive responsibility within the organization.
All domain requests must be approved by an senior official. This person must be in a role of significant, executive responsibility within the organization.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
All domain requests must be approved by an senior official. This person must be in a role of significant, executive responsibility within the organization.
All domain requests must be approved by a senior official. This person must be in a role of significant, executive responsibility within the organization.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated! Screenshot 2024-06-26 at 4 38 58 PM

@@ -27,12 +27,12 @@ If you’re eligible to have a .gov domain, we want you to get one. The types of
After you request a .gov domain, we'll review the information you provided about your organization. We use the [U.S. Census Bureau’s criteria for classifying governments](https://www.census.gov/programs-surveys/gus/technical-documentation/methodology/population-of-interest1.html){.usa-link--external} to help determine eligibility. In some cases, we’ll ask for more information (such as legislation, a charter, or bylaws) to verify eligibility.


## You must have approval from an authorizing official within your organization
Your authorizing official is a person within your organization who can authorize your domain request. This person must be in a role of significant, executive responsibility within the organization.
## You must have approval from an senior official within your organization
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be "a senior official" - not updating because I think that will break links in various places. Can you update here and in the links?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here are the new links to click through!

Before you request (this one has two links on this page for the senior official portion which should lead to the link below!)
The main link for approval from a senior official

@therealslimhsiehdy therealslimhsiehdy merged commit 7acb006 into main Jul 2, 2024
4 checks passed
@therealslimhsiehdy therealslimhsiehdy deleted the rh/2259-update-ao-to-so branch July 2, 2024 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Senior Official replaces Authorizing Official in get.gov
4 participants