ispCP Omega vs ispCP

[BioALIEN]

I have witnessed the rapid progress around here. One thing I do not agree with regarding the whole project is related to the product name decision making. I think in the end it will cause more confusion for your own users because you want to make life easier for VHCS users.

Firstly, the control panel name was going to be VHCS OMEGA 2.4.8 - to gain the trust of the original VHCS2 users and so they can upgrade. This then changed to VHCS OMEGA 1.0 to avoid any confusion with version numbering (just in case the original VHCS team reforms and come up with a 2.4.8 version).

However, at some point down the road, you are planning to make a name change to ispCP or ispControl which involves a full rewrite of your VHCS2 OMEGA code. This will potentially confuse your users and not to mention the strain on marketing, promoting and gaining public trust for your software.

My advice is to proceed with ispCP 1.0 (or ispControl 1.0) - not VHCS2 Omega - with a clear upgrade path for VHCS2 users. In fact, there should be many migration paths from cPanel, Plesk and other popular panels to ispCP so it doesn't make sense to tie your name with VHCS. This will free you from all negative publicity related to bugs and security of the former VHCS project as well as any ties in case of future VHCS releases (e.g. version 3). Later down the road, you can then have ispCP 2.0 which is a full rewrite to handle "Multi Server Control and Administration Panel without limits". This is more consistent for the community, your team reputation and to gain public trust with a new major release - not to mention trademark disputes and public confusion.

Just my 0.02!