-
Notifications
You must be signed in to change notification settings - Fork 109
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
Collate Data.gov mission/vision #4354
Comments
Starting a google doc at https://docs.google.com/document/d/1WVENd4xCWeGiyMn-BZ8tMD-GLIM8zU-lumqwDhsq45c/edit?usp=sharing |
@data-gov-team could use a review of https://github.com/GSA/data.gov/wiki/Data.gov-Mission-and-Strategy... Lots of information in these documents. Let me know what you would find more helpful, and happy to add into the wiki for more shorthand search! |
Thanks @jbrown-xentity for organizing it on a wiki so that the material is all in one place. I'll be working on an updated document that's more of a mission/vision doc. |
This feels weird to write, but I actually know all of the documents on the new wiki page 😱 . Looking at the page though.. it's not clear who it's for or what the content means. A more accurate title would be "Things related to data.gov mission and strategy". As it stands right now, (if I didn't know about the documents like I do), I could not piece together a meaningful idea from the list of resources. A question that may or may not influence the improvement of the page: Is the audience of the wiki: (1) new members of the data.gov team or (2) the general public? In both cases, more scope should be added to help understand where things are coming from (P.S. The opening paragraph of the wiki is very accurate 😉) We have the work that tried to explain why we exist: We have work that explains (what we do) and (how we do what we do):
We have things that describe what has happened (where we've been):
We have a few loose ideas about where we are going:
Is the intent to have all of this on that wiki? If yes, it's a bit messy right now. If not, we can probably remove what we don't want? Or make more dedicated pages for each thing that we do want? |
I think the intent was only to collect what we have, to indicate what we need to create. |
Follow-on work in |
User Story
In order for the team to feel confident in the data.gov mission, data.gov team wants the purpose and vision of data.gov laid out.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
THEN the necessary information is easily accessible and findable.
Background
This ticket is to create/find the background, but this is a recurring item in the retro times.
Security Considerations (required)
None
Sketch
Get all the stuff we've already created, create a wiki page summarizing and documenting, and link to onboarding.
Get feedback from team on missing pieces.
The text was updated successfully, but these errors were encountered: