5.1 KiB
Wanderson FY23Q3 QDD Report
- Quarterly Development Discussion Template
- Wanderson Code [15]
Quarterly Development Discussion Template
Performance reflections and feedback
Team member result perceptions
What have you done?
- short JWT
- lot of reviews of RBAC
- doesn't know if registration page work is included
How do you feel about it?
I think it was ok. I don't know.
I am comparing myself before being a father having 100% time reading code. Now 20% time to read what I want and need to do. True for almost everything that I've been doing. Put all of energy in everything.
Is there room for improvement?
From you?
From me?
From the rest of the team?
Good structure, the work, the visibility. no unexecpted work to be done urgently. Great. We just keep doing what we are doing.
From Cisco
Lead perception on Performance & Feedback
- Show the quarter report
- Add non code accomplishments
- How I (the lead) feel about it
-
Room for improvement?
- for the team member
- for the lead
- for the rest of the team
- for Cisco
Wanderson
Difficult not to introduce new bugs. Difficult to find focus time.
Meetings / process
Monthly team meeting, weekly team meeting. Now you are involved with many people. Small meeting before the weekly. Re-add weekly meeting. 1h talking about other projects.
Short-term goal setting and development priorities
Next quarter:
- P1. Help RBAC testing/debugging
- P2. Contribute on provisioning PIAM
- P3. Finish work on short tokens
- P4. optionally contribute for provisioning Free Tier/0-Trust
- P4. Entitlements follow up (beyond PIAM work)
Expectations
- Finish revocation for RBAC
- Finish short tokens and give a help on the rest.-
Long-term career and development priorities
How do you see yourself next year? In three years? Would you like to change anything, or are you happy as you are right now?
Do you want to be promoted to G11, take more responsibilities? Or are you happy just working as we do now, and have a discussion about progression later?
Wanderson
- overlay emacs on top of webex!
I would like long term to understand the relationship for our team and others. Understand the environment. Interacting with other Cisco teams. Looking at a broader picture.
Meeting talk about high level technical. How much progress, etc… A little bit more clear about what we are chasing for everybody. They wanted to introduce kafka, but this was already enough info to help people start learning kafka. Nice technical structure to create new products. Difficult to see this other part, especially for hidden webex rooms.
Actions?
- Force people to use centralized public channel for architectural discussions, etc…
- Try to make architectural meetings
- Understanding outside IROH what is happening, like what is DI, how are they working, etc…
Agreed upon outcomes
- Short term (next quarter): Create weekly IROH-AUth.
-
Longer term (> 6 months):
@Yann:
- Ask Leads to force people to use centralized public channel for architectural discussions, etc…
-
Try to make architectural meetings, high level changes discussion
- Understanding outside IROH what is happening, like what is DI, how are they working, etc…
- Save these reflections in the long-term priorities field in Team Space.
Wanderson Code [15]
iroh [13 (9 / 4)]
- [IROH Auth] introducing
TimeService
inAuthService
#7806 - [IROH Auth] allow only
iroh-core.time
in oauth2.core ns #7793 - [IROH Auth] - Update IROH Web middleware to build short JWTs with profile data #7671
- [IROH Auth] - update
check-refresh-token
function #7669 - [IROH Auth] - Update Design docs for Short JWT Epic #7670
- [IROH Auth]
/profile/permissions
endpoint #7562 - Patch
compojure-api
to allow endpoints with string-keys (without keywordize the request:body
) #7574 - [IROH Auth] Include route
/profile/scopes
#7553 - [IROH Auth] - Store Short JWTs #7476
between 3 and 4 months ago
tenzin [1 (0 / 1)]
between 3 and 4 months ago
- Update GPG Wanderson Ferreira #2648
tenzin-config [1 (1 / 0)]
- add postgres and redis-cache store for IROH Auth JWTs #839