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
GitHub Open issues does not really measure growth, it's more of a project/development metrics that is tracked by the Insight team. I suggest to remove it in in favour of GitHub stars across the org
There are two cards below:
Nothing happens when I click on those, I'd expect the related page to open.
Community metrics page
Question: If a new repo is created in GitHub, does the dashboard automatically pull it for the "organization wide" stats?
I think the page could have a better organization, I suggest we split per client:
js-waku (js-waku first because this is expected to be the most used client)
@waku/core NPM downloads
js-waku GitHub stars
nwaku
nwaku GitHub stars
nwaku Docker dowloads
(@waku-org/nwaku-developers I assume someone using nwaku as a lib would clone the repo? there are no common nim repository like npmjs, right?)
go-waku
go-waku GitHub Stars
(can we measure the number of clones for a repo?)
go-waku docker download
waku-rust-bindings
GitHub Stars
crates.io download
waku-react-native
GitHub Stars
npmjs downloads
I also suggest to remove the fork count, as contributor adoption is not one of our current goals.
Same for open issues.
Any time related stats should contain the time. E,g, docker pulls or npm js downloads. is it per day? all time?
Ref: waku-org/pm#35 (comment)
The text was updated successfully, but these errors were encountered: