Infrastructure/ansible
3
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

🔧 roles(fasjson): Add my RH email to foa alias, create jwheel alias #2575

Merged
ryanlerch merged 1 commit from change/fca-alias-jwheel into main 2025-04-19 18:43:28 +00:00
Conversation 9 Commits 1 Files changed 1 +3 -2
jflory7 commented 2025-04-18 20:29:39 +00:00
Contributor
Copy link

Two changes were made here:

  • Explicitly add my Red Hat email address to all email addresses sent to
    the foa@ email alias. My FAS email is not my Red Hat email, but
    there are some communications sent to this specific alias that I need
    to always go to my Red Hat email address. They are topics specifically
    about the work that I do at Red Hat.

  • Create a new jwheel@ personal email alias. This is the username I
    intend to claim after my name change, and it also matches my Red Hat
    email address (jwheel [at] redhat [dot] com). Gradually, I am going to
    work on moving email from jww@ to jwheel@. If an option ever is
    available in the future to change FAS usernames, this is the changed
    name that I would choose.

Two changes were made here: * Explicitly add my Red Hat email address to all email addresses sent to the `foa@` email alias. My FAS email is not my Red Hat email, but there are some communications sent to this specific alias that I need to always go to my Red Hat email address. They are topics specifically about the work that I do at Red Hat. * Create a new `jwheel@` personal email alias. This is the username I intend to claim after my name change, and it also matches my Red Hat email address (jwheel [at] redhat [dot] com). Gradually, I am going to work on moving email from `jww@` to `jwheel@`. If an option ever is available in the future to change FAS usernames, this is the changed name that I would choose.
jflory7 commented 2025-04-18 20:30:41 +00:00
Author
Contributor
Copy link

rebased onto 84a8bb3a82

rebased onto 84a8bb3a8231a230df345d346e521c7e97d5e3fe
jflory7 commented 2025-04-18 20:30:42 +00:00
Author
Contributor
Copy link

rebased onto 84a8bb3a82

rebased onto 84a8bb3a8231a230df345d346e521c7e97d5e3fe
jflory7 commented 2025-04-18 20:31:03 +00:00
Author
Contributor
Copy link

Also, no account currently exists at this address: https://accounts.fedoraproject.org/user/jwheel/

Also, no account currently exists at this address: https://accounts.fedoraproject.org/user/jwheel/
zuul commented 2025-04-18 20:33:51 +00:00
First-time contributor
Copy link

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/52bb8a68de2b4061b335958f4c91b4fa

Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/52bb8a68de2b4061b335958f4c91b4fa - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/2ca15a8b75b04583b158a2ada475b3c1) : SUCCESS in 2m 57s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/a6097cf6e6e74ad78c7db668260f967e) : SUCCESS in 2m 10s
kevin commented 2025-04-19 18:35:16 +00:00
Contributor
Copy link

rebased onto fc5425c07f

rebased onto fc5425c07fffe798f20c922e20ee99f63b796b76
kevin commented 2025-04-19 18:35:23 +00:00
Contributor
Copy link

rebased onto fc5425c07f

rebased onto fc5425c07fffe798f20c922e20ee99f63b796b76
zuul commented 2025-04-19 18:38:12 +00:00
First-time contributor
Copy link

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/67f674b991d044b3b0fb57443a378266

Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/67f674b991d044b3b0fb57443a378266 - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/172ff95bbc2646b09f8f1a42bee56ed8) : SUCCESS in 2m 43s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/1cfd71fcfbef400b8de78dd55e301fc5) : SUCCESS in 2m 04s
kevin commented 2025-04-19 18:43:16 +00:00
Contributor
Copy link

+1

Note that you could just make the new account with that name and we could move group memberships over to it... but thats sadly a lot of work. ;(

Merging this now in the mean time.

+1 Note that you could just make the new account with that name and we could move group memberships over to it... but thats sadly a lot of work. ;( Merging this now in the mean time.
kevin commented 2025-04-19 18:43:28 +00:00
Contributor
Copy link

Pull-Request has been merged by kevin

Pull-Request has been merged by kevin
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
freeze-break-request

   
post-freeze
  
blocked

Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Bug

The software is not behaving as expected. It could be an error, a crash, or an incorrect result. Bugs often need to be prioritized based on their severity and business impact

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
Feature

It's something that a user would be able to see or interact with, such as a new button, a new page, or an improved workflow.

  
in-progress

This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
points:1

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points:13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
points:2

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points:3

medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points:5

a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points:8

complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
priority:high

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
priority:low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
priority:medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
ready

indicates that an issue has been fully refined, has a story point value, and is ready to be pulled into a sprint. It has all the information needed for a developer to start working on it immediately.

  
review

This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

No labels
freeze-break-request
post-freeze
blocked
Bug
Chore
Feature
in-progress
points:1
points:13
points:2
points:3
points:5
points:8
priority:high
priority:low
priority:medium
ready
review
Technical Debt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/ansible#2575
No description provided.
Delete branch "change/fca-alias-jwheel"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?