That is precisely what I wish to establish:
- if they wish to continue the project as Open Source
- and what is the status of assets already provided to the Open Source community hitherto
- and whether alternate cached repos can dish out removed code.
The OpenVZ template was provided by the BlueOnyx Project of their own accord to the Proxmox VE Wiki at: http://pve.proxmox.com/wiki/BlueOnyx .
It was fully functional at that time as it is now, only that the download is not available from all IPs worldwide and the template file name does not conform to the current strict naming conventions in Proxmox VE.
I have provided a detailed article as to how to update an OpenVZ Template with this template as an example and stated it's potential concerns as a measure of full disclosure so as not to sully the fair name that Proxmox has earned over time. I have not attempted to debate whether their blocking access due to commercial reasons was fair or not as it has no place in a knowledgebase except that it exists and what to watch out for. In fact the wiki lacked articles on updating an OpenVZ template so far (and that too a non Debian based one at that) and all info was to be searched for in the forums hitherto.
In case they object officially, we can remove all clickable links (nowiki tag) to their repos here. They still have the prerogative of allowing only their paying clients to download their code should they think it proprietary. Nearly all the RPMs in the link stated in this post are from some pre-created community template or other from OpenVZ.org. Their ISOs run in the Proxmox QEMU quite stably even now. Since these are in use by Proxmox users, I see nothing wrong in information on "how to use them" to remain in the Wiki here.
A lot of Proxmox users and the general public have begun to rely on the Proxmox Wiki as a trusted source of valid info sans spam and a very vigilant userbase in the true spirit of Open Source.
It is quite clear that immediately after reading the post here, they have decided to remove the said file. We can also provide a fresh template for the project after stripping it of all their repos and ioncube encoded stuff that has no business being in an Open Source disrtibution.
If anyone is willing to donate a repo, I'll be glad to create the OpenBlueOnyx distro! Purely OpenSource!
In view of potential disagreements with the blueonyx project admin(s) and their commercial PKG vendors, the Open Source BlueOnyx user community has begun a Wiki on the lines and fair terms obtaining here - called OpenBQBO. Should anyone want access to it from a consultants point of view - to help them run their business (and partake of the Open Source PKGs) - please ask pm at nm dot tm.
Once it's open source, where you use it is nobody's business except yours.
- if they wish to continue the project as Open Source
- and what is the status of assets already provided to the Open Source community hitherto
- and whether alternate cached repos can dish out removed code.
The OpenVZ template was provided by the BlueOnyx Project of their own accord to the Proxmox VE Wiki at: http://pve.proxmox.com/wiki/BlueOnyx .
It was fully functional at that time as it is now, only that the download is not available from all IPs worldwide and the template file name does not conform to the current strict naming conventions in Proxmox VE.
I have provided a detailed article as to how to update an OpenVZ Template with this template as an example and stated it's potential concerns as a measure of full disclosure so as not to sully the fair name that Proxmox has earned over time. I have not attempted to debate whether their blocking access due to commercial reasons was fair or not as it has no place in a knowledgebase except that it exists and what to watch out for. In fact the wiki lacked articles on updating an OpenVZ template so far (and that too a non Debian based one at that) and all info was to be searched for in the forums hitherto.
In case they object officially, we can remove all clickable links (nowiki tag) to their repos here. They still have the prerogative of allowing only their paying clients to download their code should they think it proprietary. Nearly all the RPMs in the link stated in this post are from some pre-created community template or other from OpenVZ.org. Their ISOs run in the Proxmox QEMU quite stably even now. Since these are in use by Proxmox users, I see nothing wrong in information on "how to use them" to remain in the Wiki here.
A lot of Proxmox users and the general public have begun to rely on the Proxmox Wiki as a trusted source of valid info sans spam and a very vigilant userbase in the true spirit of Open Source.
It is quite clear that immediately after reading the post here, they have decided to remove the said file. We can also provide a fresh template for the project after stripping it of all their repos and ioncube encoded stuff that has no business being in an Open Source disrtibution.
If anyone is willing to donate a repo, I'll be glad to create the OpenBlueOnyx distro! Purely OpenSource!
In view of potential disagreements with the blueonyx project admin(s) and their commercial PKG vendors, the Open Source BlueOnyx user community has begun a Wiki on the lines and fair terms obtaining here - called OpenBQBO. Should anyone want access to it from a consultants point of view - to help them run their business (and partake of the Open Source PKGs) - please ask pm at nm dot tm.
Once it's open source, where you use it is nobody's business except yours.