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
This task aims to encapsulates what it will require to get the dashboard up and running for the official Ubiquity orgs from how the codebase sits at 38f5c7f.
MVP:
Data Collection: real-time - this looks like a plugin that'll capture all the relevant events we need for analytics which is primarily pull_request and issue.closed for now and collecting the required info for a given issue and storing.
Data Collection: retroactive - this will look like an API/script that'll parse the org's repos and tasks and aggregates everything then storing.
UI: Replace static data with data source chosen above (likely repo JSON)
UI Design: My designs skills leaving me wanting so I'd delegate this spec to someone else
The above will get it to an "active" state that allows it to be used, from there we'd quickly iterate on expanding and improving the fetching, analysis and UI design.
Notes:
I built the types first and planned to implement all of the fetching and parsing logic incrementally and validating each step. I never intended on pushing it as-is so it's everything is still up for debate in terms of what and how we should analyze and how it gets displayed.
/plugin-or-cli - is responsible for data collection and is probs 80% ready. It's built for retroactive right now but only tested as a script not as a plugin (it'll need to be an action as it's a long execution time).
The rest of the UI is built around the static data, it can be worked on immediately by anyone so long as a vision is laid out or creative freedom is given lmao
This task aims to encapsulates what it will require to get the dashboard up and running for the official Ubiquity orgs from how the codebase sits at 38f5c7f.
MVP:
pull_request
andissue.closed
for now and collecting the required info for a given issue and storing.The above will get it to an "active" state that allows it to be used, from there we'd quickly iterate on expanding and improving the fetching, analysis and UI design.
Notes:
/plugin-or-cli
- is responsible for data collection and is probs 80% ready. It's built for retroactive right now but only tested as a script not as a plugin (it'll need to be an action as it's a long execution time).Originally posted by @rndquu in ubiquity-os-marketplace/ubiquity-os-kernel-telegram#42 (comment)
The text was updated successfully, but these errors were encountered: