Open harlantwood opened 6 years ago
As I said on https://github.com/ipfs/project-repos/issues/118#issuecomment-372737024, I'm sorry for dropping the ball on this repo, @harlantwood.
It is only using Orbit repos because I was being hit repeatedly by API limits that were incredibly annoying. Limiting it to Orbit was a good way of keeping those down, as it is a small, JavaScript-heavy org.
I don't think anything went wrong with the code itself. However, I had a change in priorities and moved away from working full time on IPFS. I ended up forking this dashboard and iterating on it a ton for @mntnr, which included a design overhaul that I like a lot. But I haven't had time to work those back in here.
I don't think anyone would look at this but an OSS community manager, and I'm not sure that's something that IPFS currently has (am I wrong?).
Thanks for the update Richard. https://github.com/mntnr/dashboard looks good! Glad to see this project live on in some form.
Makes sense about API limits. Has the mntnr version solved that problem?
Yes, there's been significant improvements. I was hoping to work in more GraphQL stuff, but as it is, it is a more lean version.
For a while this was building all IPFS and mutiformats etc repos. Now it's mostly just building Orbit repos. Why?
This changed in 0ee5df8ff611f86183a6be0d93a3176ac51450fa. @richardlitt was this intentional to cut out most repos? The comment doesn't seem to reflect that intention.
@richardlitt in #117 you said "I'm not sure that anyone is currently interested in maintaining it."
I'm curious where this went wrong. Especially because I'm considering building something similar for another project... I'd love to learn from the experience here.
We had a lot of enthusiasm for a unified dashboard at the beginning... eg @jbenet in https://github.com/ipfs/infrastructure/issues/25
Mostly I'd like to know if we executed poorly (and what went wrong specifically) or if we were simply wrong that this was a useful thing to do in the first place -- that actually nobody wants to look at such a dashboard beyond the initial "wow" moment.
@flyingzumwalt