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
Top performers (via USD earned, tasks completed, reviews performed, etc)
Tasks Complete (per repo, per contributor, etc)
Task Rewards (per repo, per contributor, etc)
Each should have it's own view separate from the rest. The UI currently has everything squashed together via legends and stuffed into the chart bar details etc.
Once the aggregates are configured and are being updated in real-time then we'll need an API to serve the org' data (I expect repo JSON to be the storage layer, so the endpoint should fetch and read from repo and then serve) which will require it's own task to cover specifics of the complete API of the platform not just this one aspect.
We'll then setup a cron job or two that'll ping kernel-telegram and once this is implemented to support UI requests too or perhaps a separate task for accepting UI requests would be needed actually
Keeping it simple for now:
Each should have it's own view separate from the rest. The UI currently has everything squashed together via
legends
and stuffed into the chart bar details etc.API:
have dashboard ping kernel-telegram endpoint and it posts what is sent
kernel-telegram
and once this is implemented to support UI requests too or perhaps a separate task for accepting UI requests would be needed actuallyOriginally posted by @rndquu in ubiquity-os-marketplace/ubiquity-os-kernel-telegram#42 (comment)
The text was updated successfully, but these errors were encountered: