Tommahawk
12th June 2007, 04:44
I want to share 2 possible improvements.
I propose that ISPConfig be not distributed with third party packages instead use wget at client side to download and check upgrade to latest ISPConfig verified stable.
Pros: Bug fixes & updates of third party packages become seperate from ISPConfig version allowing bugfixed third party packages to be incorperated while ISPConfig version remains unchanged
Plugins: ISPConfig should adopt a plugin model that allows people to create supported/unsuppoted plugins as they desire.
Pros: Keep ISPConfig are streamlined and core as possible moving everything not absolutely compulsary into plugins which is a choice.
Pros: Keep ISPConfig small and managable
I propose that ISPConfig be not distributed with third party packages instead use wget at client side to download and check upgrade to latest ISPConfig verified stable.
Pros: Bug fixes & updates of third party packages become seperate from ISPConfig version allowing bugfixed third party packages to be incorperated while ISPConfig version remains unchanged
Plugins: ISPConfig should adopt a plugin model that allows people to create supported/unsuppoted plugins as they desire.
Pros: Keep ISPConfig are streamlined and core as possible moving everything not absolutely compulsary into plugins which is a choice.
Pros: Keep ISPConfig small and managable