You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
It would be great if we could have a new section on the Status page which shows the "stats" of how we are going with issues. For instance, it would show the:
Total number of issues received over the last month
Would be great if if showed a difference of this vs the 1 - 3 months prior
Total number of comments received over the last month
Would be great if if showed a difference of this vs the 1 - 3 months prior
Would also be great if this could be broken down by user so we can recognize people who are actively supporting other users - maybe this would split the difference between issue raisers vs answers (taking into account if the person who raises the issue comments on their own issue)
Break these issues down by their various tags
I'm imaging that because of the data and how much there is, we won't want to live scrape it every time the app pool recycles like we do with the current stuff. So we probably need a persisted store to hold the summarised data as we go.
The text was updated successfully, but these errors were encountered:
It would be great if we were to use a common approach to all of these types of pages that do similar things
=> Persisted store that is updated in the background async at given intervals for Status Board, Dynamic Contrib, Packages and Stats pages.
Using a NoSQL / document store might work best for this type of storage? And Azure Command Queues for the backend tasks to be run?
I agree a common approach would be great. The biggest thing is trying to find the balance between something that is easy to update for config purposes (like what we did with the flat file for the current Status page) vs holding lots of data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if we could have a new section on the Status page which shows the "stats" of how we are going with issues. For instance, it would show the:
I'm imaging that because of the data and how much there is, we won't want to live scrape it every time the app pool recycles like we do with the current stuff. So we probably need a persisted store to hold the summarised data as we go.
The text was updated successfully, but these errors were encountered: