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

Analyse existing users and determine duplicate user accounts Decision record #63

Open
3 of 10 tasks
Tracked by #24
sudhara opened this issue Aug 28, 2024 · 8 comments
Open
3 of 10 tasks
Tracked by #24

Comments

@sudhara
Copy link
Member

sudhara commented Aug 28, 2024

Overview

We need to review the existing users that have not logged in, in a while and come up with a recommendation on what to do currently and ongoing.

Action Items

  • Pull a list of all the existing users that have not logged in 180 days
  • Review the list
  • Identify exceptions

Review and Document

  • Write up Decision Record on what we should do with
    • current users
    • on an ongoing basis
  • Review with Team
  • Let product know what you are recommending
  • Get sign off
  • Create issues

Resources

#### Issue 
#### Problem Statement
#### Potential Solution
#### Feasibility Determination
@ale210
Copy link
Contributor

ale210 commented Sep 19, 2024

here is a list of accounts that have not had logins more than 180 days ago:

bonnie_ops -
charles_maduka -
jbubar -
npang4 -
testiamuser -
CivicTechJobs 486 days ago
VRMS 482 days ago
user-manger 287 days ago
bonnie_hfla 280 days ago
ethan_strominger 280 days ago
Judson 270 days ago
Jason.ebueng@gmail.com 237 days ago
shikhayadav 232 days ago
sidharth20 223 days ago
abdulraheem_hfla_ops 211 days ago
awlFCCamp 210 days ago
shinjonathan 205 days ago
abbyz123 202 days ago
samuelusc 202 days ago
Davon_W 202 days ago
chelseyb 202 days ago
Tyson_Miller 195 days ago
robin_glover 195 days ago
shikha0428 192 days ago
kazushi_hfla_ops 181 days ago

@sudhara
Copy link
Member Author

sudhara commented Sep 19, 2024

@ale210 to complete the Issue, problem statement, Recommendation documentation above

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 19, 2024

Exceptions

Please do not delete any logins with my username (bonnie). I will log in again to the accounts I have access to (during a meeting) and identify what I use the account for. Just because I have not logged in, in a while, doesn't mean I should not be doing so. My logins are meant to be an administrative override.

@ExperimentsInHonesty
Copy link
Member

@chelseybeck do you need this account? chelseyb 202 days ago

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 19, 2024

Exceptions to investigate

The following accounts might be needed to get projects off non IaC deployments of incubator or even in unique instances (e.g. Home Unite Us)

  • jbubar - (VRMS)
  • CivicTechJobs 486 days ago (Civic Tech Jobs)
  • VRMS 482 days ago (VRMS)
  • ethan_strominger 280 days ago (Knowledgebase)
  • Judson 270 days ago (Access the Data)
  • Tyson_Miller 195 days ago (Home Unite Us)

@ExperimentsInHonesty
Copy link
Member

@ale210 I made updates to the template (top part) of the issue, and left some comments for you.

@ExperimentsInHonesty ExperimentsInHonesty moved this from Questions/Review to In progress (actively working) in CoP: DevOps: Project Board Sep 19, 2024
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 19, 2024

@ale210 Please check to see if any of the users use this email address aws-huu@hackforla.org and add a link to your comment with the results to the next agenda. I will need that info for a spreadsheet I am working on. I am adding the link here so I can find it again when I have your answer spreadsheet

The email is in this 1password vault which only Ernie and I have access to
AWS- Recovery vault
Recovery for Projects AWS accounts

@ExperimentsInHonesty
Copy link
Member

@ale210
Please provide update (did you add it to the agenda?)

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
  • remember to add links to the top of the issue if they are going to be needed again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress (actively working)
Development

No branches or pull requests

3 participants