-
Notifications
You must be signed in to change notification settings - Fork 117
Gdash promoted to an organisation proposal #110
Comments
👍 |
@ripienaar @keymon @hamann @falkenbt any view on this ? |
I am not against the idea, but I am not sure there really is the momentum from a maintainers perspective to carry it. I'm mid changing jobs and might have more time to pay this time again in the near future - can't speak for the other maintainers though. As it is though, gdash is a tool to do one thing well so I'd be against chasing features forever - but I do like the contribution ecosystem you propose. |
Same here. I think the ecosystem approach is generally a great idea. Personally, I currently don't have a lot of time to contribute and in general I'm thinking if gdash is the right platform or if we (you?) should focus on different approaches, like improving the existing graphite-web dashboard (e.g. I found evernotes modification interesting: http://blog.evernote.com/tech/2013/07/29/graphite-at-evernote/) or contribute to a client-rendering solution like https://github.com/kenhub/giraffe, which is capable of adding interactivity to the graphs (which was requested for gdash as well). Maybe it is time to step back and think about requirements for a more general dashboarding solution and then check where and how it could and should be implemented. What do you think? |
I personally would love to see more features to this. I have been adding our own features at work that seemed to only pertain to our company needs but perhaps would be nice as a feature. For instance at the time breakdown i added another page that i kinda stole from https://github.com/obfuscurity/dusk?source=c so that it breaks down per machine in a aggregated graph. excellent for eyeballing issues in a group of servers. |
@ripienaar updates on this? thanks! |
Is anyone even still using it? There's a whole lot of really good and actively maintained tools out there. Be happy to get a org setup but only if I know there's both users and people keen to maintain it. So if people are pipe up and lets see if we can come up with a proposal |
I personally use it at my work and thought it was the best fit for us at On Tue, May 12, 2015 at 6:56 AM, R.I.Pienaar [email protected]
..::Jarrett::.. |
wikimedia foundation has a public installation at https://gdash.wikimedia.org (full disclosure: I work there) and I was looking to update it to latest upstream |
Nice! I have added several things such as pagination for the frontpage, typeahead On Tue, May 12, 2015 at 9:28 AM, Filippo Giunchedi <[email protected]
..::Jarrett::.. |
I would be keen to see gdash as an organisation.
Something like https://github.com/gdash/gdash for the actual code.
Maybe that will help to get the project moving a little bit more than it is now, although it is not my point here.
My main argument is more to do with template management and contribution.
With gdash as an organisation, we can create a gdash template repository(s).
It could be a repository per template type (as in collectd, munin, diamond), or simply branch on the same repo, or a mix of both
Something like gdash/collectd-templates and gdash/munin-templates with a branch per target (RHEL5, RHEL6,arista switch, etc.).
Also looking forward, it allows for infrastructure bits to be stored, like gh-page, rpm spec file, packer config etc. in the same realm, but under different repo.
One of the benefit would be easier access and better visibility on dashboard (more example to look at).
That should lead to more contribution, as people realise that there is a place to contribute them back to the community.
The text was updated successfully, but these errors were encountered: