Call for modification standards

[egarnel]

Cacti is really awesome and there are some great addons, etc out there.
Unfortunately, it is not always possible to make use of some of them due to resource limitations, additional requirements, and other stuff


I came up with a template that may help users determine if an addon will work in their environment before they go thru the effort of trying to incorporate an addon into Cacti.

[TheWitness]

Hillarious, and Anarchist asking for order

TheWitness

[rony]

I can't read it, can you put it in open document format?

[Howie]

Cacti is really awesome and there are some great addons, etc out there.
Unfortunately, it is not always possible to make use of some of them due to resource limitations, additional requirements, and other stuff

I came up with a template that may help users determine if an addon will work in their environment before they go thru the effort of trying to incorporate an addon into Cacti.

Wouldn't this be much better as something that everyone can read, like a text file? I don't see what having it in a complicated format gains... It would make the possiblity of some kind of search, or even automated installer still possible, too. Something like e-mail headers maybe? Or even XML...

[TheWitness]

Howie,

Do you want me to patch Weathermap to be compatible with Boost?

Larry

[Howie]

Howie,

Do you want me to patch Weathermap to be compatible with Boost?

Larry

It's OK. I'll figure it out. The thing is to get it so that it doesn't then depend on Cacti. The best way to do it that I could see was to start using a different datasource where you pass the local_data_id rather than a filename.

As soon as I have all the other changes for 0.9 taken care of, I'll take a look at it. Nearly there now.

[egarnel]

Cacti is really awesome and there are some great addons, etc out there.
Unfortunately, it is not always possible to make use of some of them due to resource limitations, additional requirements, and other stuff

I came up with a template that may help users determine if an addon will work in their environment before they go thru the effort of trying to incorporate an addon into Cacti.

Wouldn't this be much better as something that everyone can read, like a text file? I don't see what having it in a complicated format gains... It would make the possiblity of some kind of search, or even automated installer still possible, too. Something like e-mail headers maybe? Or even XML...

I will convert it when I get to the office tomorrow

[egarnel]

Cacti is really awesome and there are some great addons, etc out there.
Unfortunately, it is not always possible to make use of some of them due to resource limitations, additional requirements, and other stuff

I came up with a template that may help users determine if an addon will work in their environment before they go thru the effort of trying to incorporate an addon into Cacti.

Wouldn't this be much better as something that everyone can read, like a text file? I don't see what having it in a complicated format gains... It would make the possiblity of some kind of search, or even automated installer still possible, too. Something like e-mail headers maybe? Or even XML...

I will convert it when I get to the office tomorrow

text format attached.

I meant this as more of a guideline to help Cacti users determine if an addon/plugin/change would be of use and/or work for them in their environments