On 3/13/2025 8:01 AM, VMSgenerations wrote:
The second issue of our news letter is already here.
We hope you'll enjoy it. And we look forward to receiving your feedback.
You'll find this document at URL: https://www.vmsgenerations.fr/la-lettre-de-vmsgenerations-n2-EN/
I think there are a lot of good points in this.
A public "list price" list would be nice. That would set
everybody expectations. And don't tell me that high prices
scare customers away - nothing is as scary as an unknown price,
because that will make everybody expect crazy high.
I believe that the vast majority of future VMS customers
will be fine with VM's, but there are still a minority
that prefer bare metal. We know that VMS runs on bare metal
x86-64. So it makes sense if VSI certify one or two
bare metal configs. I hope that VSI will get to that when
the dozens of higher priority items have been delivered.
Obviously SPD's and other documentation should be uptodate.
Again I hope that VSI will catch up on this when the
higher priority items have been delivered.
When the CLP was changed, then I did not believe that the new
approach would fix the problems. And I still don't. But it is
also my impression that most of the actual contributors are
on either Ambassador program or ISV program with few CLP
users. And CLP is creating a lot of questions in the VSI forum.
Depending on perspective on can say that proves either
that Ambassador program is the right model or that CLP is fine
as is. Anyway before changing the current setup, then I think
it would be nice to actually see how it turns out: will VSI
be happy with ambassador program or not? will we continue to
see lots of CLP user question in the VSI forum or is it just
a startup thing?
There is an important topic that is only briefly covered:
"Open Source products whose source code is never published—yet, as the
name suggests, "open source" should be open."
"Contributors have repeatedly pointed out that VSI’s restrictive and
complex approach to source sharing discourages participation."
The open source world is huge. VSI is a very small company compared
to HPE/HP/CPQ/DEC. The group of VMS open source contributors are
very small. VMS can simply not afford any waste of open source
effort.
I strongly recommend that:
* VSI move all their open source repos to public Github repos
* VSI invite non-VSI people to contribute
* if there are some code that cannot be made public (closed source
copyright by HPE or similar) then put Alpha, Itanium and
x86-64 OLB's in the repo
* if there is a concern about control of direction then make
a VSI person the "Linus" or "Guido" for the project
* make unsupported community builds available from Github
for Alpha, Itanium and x86-64
* for those open source products deemed important enough
then VSI can do a special VSI build producing a signed PCSI
to be distributed from VSI SP an "enterprise build" (no functional
differences please)
Arne
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)