HOWTO suggest a new feature or change

Introduction

It is not uncommon to receive many feature or behaviour change requests. In order to reduce the amount of time we, the developers, spend analysing every request take a look at the next practises you should (or probably must) follow when.

Want ispCP to support new/more software?

Because ispCP supports not only one Linux distribution but many and even OpenBSD and FreeBSD we require all software to be available for all the supported (and proposed) Operating Systems.

These are some of the questions you should answer when suggesting (either in a forum post or in a ticket. The former is preferred so it is first discussed):

What feature/s does it provide?

Does ispCP has already support for a different implementation of that/those feature/s?

If so, what is the difference between both of them?

If not, why do you belive ispCP should support such software?

What ispCP's component/s would it affect? (e.g. engine, gui, daemon, setup, etc)

On what user level does this software works? (e.g. admin, reseller, customers)

What is its license?

And the link to the homepage?

Does it need an special setup or it runs out of the box?

If the former, what config files need to be modified? what needs to be changed?

Does it exist for non-Debian systems?

If so, non-Debian installations require further changes (i.e. config changes)?

Does it exist for non-Linux systems?

If so, non-Linux installations require further changes (i.e. config changes)?

Is it already packaged?

If so, what is the package name in Debian? and in other distributions/OS'?

If already packaged, is it an official package? on which distributions/OS'?

After you have answered all of those questions you may then request this software to be supported.