More visible agile guide
Closed this issue · 7 comments
The guide was meant to be light initially with contributions or issues submitted to understand what are the most pressing questions we face regarding agile in government.
The agile guide is currently linked to the 18F guides page, but not much else. There have not been much submissions so how can we promote the guide better?
Note: A good first step would be to integrate DAP so that we can see just how much traffic there is.
@porta-antiporta want to say more what this would be about?
@porta-antiporta, which guide are you referring to?
@afomi https://agile.18f.gov/ is the guide. The markdown files that power the guide are in this repo.
@suprenant I updated the description to provide more background as to what I was thinking.
@porta-antiporta, I split out the DAP task to #79
@porta-antiporta - I'm inclined to close this Issue. The title is how to make the guide more visible for the value of getting more submissions. There are now other efforts to promote the guild and content.
Using DAP data, we can continue to support the ongoing goal of engaging and growing the user base.
@afomi i'm all for closing this issue. though i noticed a Closed (this cycle) column in Zenhub with a bunch of "open" (but completed/addressed issues). So defer to @suprenant whether we close the issue or do i just drag this to that column and tag it with "wont"?
p.s. Would have tagging issues with a label (rather than Zenhub column) indicating which cycle it was addressed in be sufficient to capture the metrics that Zenhub column seems to look to do?
It would then allow you to close the issue, rather than leaving it in an open state (in Github).
Asking because if a person views the repo issues list (as they don't have Zenhub) they may take on issues that are already "complete". For example: integrating DAP shows up as open but I thought this had been completed some time ago.
(recently edited the comment to reduce the word soup)
@porta-antiporta - thanks for the note about Zenhub.
@suprenant - there are several "Done" stories in Zenhub that are not "Closed" in GitHub, which is a bit confusing.
Is there history behind this? It seems desirable to get them closed.