[Info-vax] Open source usage, Was Python and various libraries updated

[Scott Dorsey]

=?UTF-8?Q?g=c3=a9rard_Calliet?=  <gerard.calliet at pia-sofer.fr> wrote:
>
>VSI doesn't help encouraging collaboration on Open Source, and thinks 
>there is not sufficient strength outside that can be usefull,
>
>The community - little for now - doesn't engage with strength on 
>collaboration, and is discouraged by the lack of interest on 
>collaboration by VSI.
>
>Something has to be done to unlock this. Community License is a very 
>good point. Making more standardfully available Open Source developments 
>will be the next good point.

For this to happen, VSI has to hire many more people.  Right now VSI is only
a small handful of people, and they are all busy working on the x86 port
and have little time left over for anything else.  Even very important things
are being put on hold in order to get the x86 port finished.

VSI doesn't have additional people in part because finding good VMS people
is difficult, and in part because VSI doesn't have a lot of revenue coming in.

If you want VSI to get engaged with the open source community, and to get
them to hire a lot more people to get more stuff working under VMS and get
some good marketing going to get people to think of VMS as a new and exciting
thing instead of a dead or old thing--- then the BEST thing that you can do
is to buy lots of VMS licenses and send them some money.

>More generaly VSI and the community have to quit the old paradigm of the 
>marvelous company and the passive users. We have all to rebuild trusted 
>collaboration, and adopt some ways from the Open Source paradigm. And we 
>have also to be more conscious of the specific qualities of OpenVMS 
>which can be "selled" to other people.

I think the paradigm that VSI is operating under right now is the "get this
port done as fast as possible and everything else be damned" paradigm.  That
is how it should be, but it won't be that way forever.
--scott
-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."