"php-vm" is kind of snappy also.
_S
On 03/13/2012 12:33 PM, Sean wrote:
The name is not a very big issue to me, but I would suggest considering a change. The domain name "php-virt-control" and product / documentation don't really have to change, but I would suggest the final product release might go by a shorter moniker such as "PVC" so as to be more memorable and easier. This would only affect the RPM, debian, and / or tar-ball releases (pvc.rpm, pvc.tar, etc). Beyond that you could maybe change the base URL of the entry point and if you really wanted to, also the UI.
Using "PVC" has a few advantages; Other than being short and quick, it does not require the project name to change (because it is simply an abbreviation), it may remind the user of "Poly Vinyl Chloride" (a material used in quick-assembly plumbing and high fashion, among others), and it doesn't partly rhyme with "birth control" (an unfortunate coincidence). Even the source repository does not need to be renamed.
Again, I don't think it's a huge issue. The bigger the change the more things it affects. I think "VMC" is too close to "VNC". "web-virt-control" is a pretty simple difference. "webvirt" sounds kind of cool as one word. Anything with more than one hyphen seems troublesome, and anything with "virt-control" has that rhyming problem. "virtigo"? "php-machine"?
I just hit bugzilla.php-virt-control.org 3 times. "Request for new user account 'sean.channel@pacbell.net' submitted" --No love. Network / firewall problem? Default configuration? _S
On 03/13/2012 05:43 AM, Michal Novotny wrote:
Well, the bugzilla on the link ( http://bugzilla.php-virt-control.org )I provided should send you the link ASAP. I've seen the database however I didn't see you registration here. Please register to this bugzilla first.
About the package naming I've never thought about it however the project is already having a name and a domain is registered. If applicable we should think of better naming for not just this project but all virtualization-related projects that are not officially supported, like virt-backup and maybe others that could be useful (if we find any).
Or do you mean renaming the debian package to pvc as php-virt-control ? Theoretically we could think about the name of virtual-machine-controller (VMC) since the php-virt-control was badly chosen. There's no need to specify the platform it uses in here (PHP in this case). It could be Virtual Machine Controller, or Web-virt-control, instead. Any name suggestions?
For bugzilla on php-virt-control there are 2 namespaces as this is intended to be a personal bugzilla as well so please look to the "Virtualization related" namespace/classification.
Michal
On 03/12/2012 11:01 PM, Sean wrote:
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project& site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotnyminovotn@redhat.com To: Virtual machine control for PHPphp-virt-control@lists.fedorahosted.org CC: Seansean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control