feat: Update people statuses and communication context for clarity and accuracy
This commit is contained in:
@@ -30,6 +30,11 @@ When the format fits, prefer:
|
||||
- Always clarify authenticated vs non-authenticated when behavior depends on it.
|
||||
- Always separate external issues from regressions.
|
||||
- Always state reproducibility and scope.
|
||||
- Fidelity Teams consistently displays names in surname-first order.
|
||||
- Mattermost is a separate internal communication context; most people visible in Teams are not the same people David interacts with in Mattermost, with Jeff as the main exception.
|
||||
- Jeff is the main bridge into the Fidelity-side Teams context.
|
||||
- David works on the All-Win Software side and mainly helps advance the work Jeff needs to report on the Fidelity side.
|
||||
- Do not write updates as if David is directly embedded in the Fidelity Teams collaboration loop unless the context explicitly says so.
|
||||
- For standups, report the previous workday context, not blindly the prior calendar day.
|
||||
- On Mondays, use Friday's work context unless a later prior day has Mattermost activity.
|
||||
- If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
status: inactive
|
||||
updated: 2026-04-17
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
@@ -14,6 +14,8 @@ tags:
|
||||
|
||||
Historical Fidelity collaborator in project support discussions.
|
||||
|
||||
- No longer works with the current All-Win Software / Mattermost / Slack collaboration group.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
@@ -30,4 +32,5 @@ Historical Fidelity collaborator in project support discussions.
|
||||
|
||||
- Treat Derian as a relevant collaborator for historical pipeline/debugging context
|
||||
- Treat Derian as most relevant for historical CI/CD coordination and documentation support
|
||||
- Treat Derian as historical context, not a current active collaborator
|
||||
- If future context clarifies the formal role or team, update this file directly
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
status: inactive
|
||||
updated: 2026-04-17
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
@@ -14,6 +14,8 @@ tags:
|
||||
|
||||
Historical Fidelity collaborator in XFlow-related discussions.
|
||||
|
||||
- Previously worked for Fidelity but no longer does.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
@@ -31,4 +33,5 @@ Historical Fidelity collaborator in XFlow-related discussions.
|
||||
|
||||
- Treat Erik as a relevant source when historical context touches XFlow ownership boundaries or migration difficulty
|
||||
- Treat Erik as a high-signal source for framework architecture and responsibility boundaries
|
||||
- Treat Erik as historical Fidelity context, not a current active stakeholder
|
||||
- If future context clarifies the formal role or team, update this file directly
|
||||
|
||||
@@ -18,7 +18,7 @@ tags:
|
||||
Current direct manager for the active Fidelity project; repeated communication gatekeeper and scope shaper in historical XFlow work.
|
||||
|
||||
- [norman-arauz.md](./norman-arauz.md)
|
||||
Frequent XFlow collaborator in historical Slack threads; primary implementer/investigator across SwiftUI, AO/Fid4 bugs, and release work.
|
||||
Former collaborator in historical Slack threads; primary implementer/investigator across SwiftUI, AO/Fid4 bugs, and release work, but no longer works with the current All-Win Software / Mattermost / Slack group.
|
||||
|
||||
- [david-delagneau.md](./david-delagneau.md)
|
||||
Repeated historical collaborator on pipeline, CI/CD, and Sparta/SwiftUI proof-of-concept work, especially around Jenkins, reporting, and framework setup.
|
||||
@@ -33,7 +33,7 @@ tags:
|
||||
Repeated historical collaborator who surfaces architectural concerns, SwiftUI constraints, and cross-team dependency risks.
|
||||
|
||||
- [erik-reynolds.md](./erik-reynolds.md)
|
||||
Historical collaborator focused on XFlow manager behavior, integration boundaries, migration effort sizing, and framework responsibility boundaries.
|
||||
Historical collaborator focused on XFlow manager behavior, integration boundaries, migration effort sizing, and framework responsibility boundaries; previously worked for Fidelity but no longer does.
|
||||
|
||||
- [gurram-santosh.md](./gurram-santosh.md)
|
||||
AO-related contact who often validates fixes or confirms whether issues still reproduce in consumer environments.
|
||||
@@ -48,7 +48,7 @@ tags:
|
||||
FTPlanning-side contact relevant when issues crossed from XFlow into consumer-framework ownership.
|
||||
|
||||
- [derian-cordoba.md](./derian-cordoba.md)
|
||||
Historical collaborator in pipeline and documentation work, especially around CI/CD support and operational notes.
|
||||
Historical collaborator in pipeline and documentation work, especially around CI/CD support and operational notes; no longer works with the current All-Win Software / Mattermost / Slack group.
|
||||
|
||||
- [tauf.md](./tauf.md)
|
||||
Taufiqur Ashrafy, often referred to as Tauf; CI/Jenkins support contact who helps with release-pipeline troubleshooting and related publication issues.
|
||||
|
||||
@@ -3,7 +3,7 @@ type: person
|
||||
project: fidelity
|
||||
role: manager
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
updated: 2026-04-17
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
@@ -22,6 +22,7 @@ Current direct manager for the active Fidelity project.
|
||||
- Frequently rewrote PR descriptions, Jira updates, and cross-team messages before they were sent
|
||||
- Regularly redirected work based on release risk, consumer pressure, or manager/stakeholder expectations
|
||||
- Often pushed for explicit distinction between framework bugs, consumer bugs, service issues, and scope creep
|
||||
- Acts as the main communication bridge into the Fidelity-side Teams context while David works from the All-Win Software side
|
||||
|
||||
---
|
||||
|
||||
@@ -57,6 +58,7 @@ Good updates usually clarify:
|
||||
- Jeff feedback is often a signal to tighten wording before communicating externally
|
||||
- Jeff often asks for evidence, reproduction detail, and exact next action before approving external communication
|
||||
- If a draft is still ambiguous, Jeff may prefer to rewrite it directly so the external version is unambiguous and does not generate avoidable follow-up
|
||||
- Jeff is often the person who reports progress or status into the Fidelity-facing context after David advances the implementation or investigation work
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ type: role-map
|
||||
project: fidelity
|
||||
role: manager
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
updated: 2026-04-17
|
||||
tags:
|
||||
- role
|
||||
- manager
|
||||
@@ -22,6 +22,8 @@ tags:
|
||||
|
||||
Direct supervisor or primary reporting manager for the active project.
|
||||
|
||||
- In practice, Jeff is also the main bridge between David's All-Win Software work and the Fidelity-side reporting context.
|
||||
|
||||
---
|
||||
|
||||
## Usage
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
type: person
|
||||
project: fidelity
|
||||
role: collaborator
|
||||
status: active
|
||||
updated: 2026-04-16
|
||||
status: inactive
|
||||
updated: 2026-04-17
|
||||
tags:
|
||||
- person
|
||||
- fidelity
|
||||
@@ -14,6 +14,8 @@ tags:
|
||||
|
||||
Frequent Fidelity/XFlow engineer collaborator in historical Slack threads.
|
||||
|
||||
- No longer works with the current All-Win Software / Mattermost / Slack collaboration group.
|
||||
|
||||
---
|
||||
|
||||
## Known Context
|
||||
@@ -29,4 +31,5 @@ Frequent Fidelity/XFlow engineer collaborator in historical Slack threads.
|
||||
## Guidance
|
||||
|
||||
- Treat Norman as a strong source for historical implementation detail, reproduction findings, and release-process context
|
||||
- Treat Norman as historical context, not a current active collaborator
|
||||
- If later communication clarifies the formal team/title, update this file directly
|
||||
|
||||
@@ -41,3 +41,7 @@ tags:
|
||||
- Tauf was identified as a CI/Jenkins support contact who has helped with pipeline issues in the past.
|
||||
- David clarified that Tauf's full name is `Taufiqur Ashrafy`; he is often referred to informally as `Tauf`.
|
||||
- David also noted that Fidelity Teams may display people in surname-first order, which can make person matching less obvious across tools.
|
||||
- David clarified that the surname-first display in Fidelity Teams is consistent for everyone.
|
||||
- David also clarified that Teams and Mattermost represent different social contexts; outside of Jeff, people seen in Teams are generally not the same people David interacts with through Mattermost.
|
||||
- David corrected current people status: Norman Arauz and Derian Cordoba no longer work with the current All-Win Software / Mattermost / Slack group, and Erik Reynolds previously worked for Fidelity but no longer does.
|
||||
- David clarified an important working-context rule: Jeff is the only person who regularly communicates with Fidelity-side Teams stakeholders, while David works from the All-Win Software side and mainly helps advance the work Jeff needs to report on the Fidelity side.
|
||||
|
||||
Reference in New Issue
Block a user