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

Stakeholder engagement: which API documentation UI to use? #388

Open
4 tasks
shmonks opened this issue Sep 24, 2024 · 2 comments
Open
4 tasks

Stakeholder engagement: which API documentation UI to use? #388

shmonks opened this issue Sep 24, 2024 · 2 comments
Assignees
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it feature: docs: PD team documentation documentation on PD team processes and architecture, etc. p-feature: Stakeholder documentation documentation for Users of People Depot role: product s: VRMS stakeholder: VRMS size: missing

Comments

@shmonks
Copy link
Member

shmonks commented Sep 24, 2024

Overview

We need to get feedback from stakeholders about preferred form of API documentation, following Fang's research indicating pros and cons of two main options: Swagger and Redoc

Action Items

  • Create draft of slide deck
  • Review
  • Send link to Bonnie for feedback
  • Send message to VRMS (and CTJ?) PMs, asking if we can join one of their team meetings to talk about it, with link to version of slide deck saved to local drive

Resources/Instructions

@shmonks shmonks added role: product s: VRMS stakeholder: VRMS size: missing feature: docs: PD team documentation documentation on PD team processes and architecture, etc. p-feature: Stakeholder documentation documentation for Users of People Depot complexity: small All steps are laid out in detail so that someone new to the project can work on it labels Sep 24, 2024
@shmonks shmonks added this to the 3 - Project Mgmt milestone Sep 24, 2024
@shmonks
Copy link
Member Author

shmonks commented Oct 3, 2024

Hi @vanessaavviles - please consider the following questions and add an update below:

  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 (if necessary): "Add any pictures that will help illustrate what you are working on."

@vanessaavviles
Copy link
Member

Fang could not make the meeting this past tuesday, so we will work on going through the presentation all 3 of us next tuesday's meeting and have it ready to show the team thursday of next week.

@shmonks shmonks removed their assignment Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it feature: docs: PD team documentation documentation on PD team processes and architecture, etc. p-feature: Stakeholder documentation documentation for Users of People Depot role: product s: VRMS stakeholder: VRMS size: missing
Projects
Status: 🆕New Issue Review
Development

No branches or pull requests

3 participants