On 01/03/14 22:54, Ben Hartshorne wrote: > I've changed my mind about reorganizing the repo. The correct way to > summarize different approaches to the same problem is through documentation > (aka the wiki) not repository organization. It makes sense to keep self > contained projects (like ganglia-nagios-bridge) as its own repo for ease of > forks and PRs and so on. > > I've made changes to both wiki pages Daniel mentions in the hope of making > it easier for folks that are looking to solve this problem. All they need > now is a little google juice; these pages are impossible to find via > google. There are many other pages talking about nagios and ganglia that > rank higher. > > Any suggestions?
There are still trac wikis about too It is a real hassle In Github, we can actually disable the wiki feature and refer everybody back to track if that is easier to manage On the other hand, github wikis have the github ACLs If we are going to keep the github wikis, we need to modify the menu links on ganglia.info to link into the right places, etc ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
