[Info-vax] Python and various libraries updated

[David Goodwin]

On Monday, August 10, 2020 at 5:22:17 AM UTC+12, Arne Vajhøj wrote:
> On 8/9/2020 11:54 AM, Scott Dorsey wrote:
> > =?UTF-8?Q?Jan-Erik_S=c3=b6derholm?=  <jan-erik.soderholm at telia.com> wrote:
> >> Den 2020-08-08 kl. 18:30, skrev Scott Dorsey:
> >>> =?UTF-8?Q?Jan-Erik_S=c3=b6derholm?=  <jan-erik.soderholm at telia.com> wrote:
> >>>>
> >>>> Maybe it is simply that the goal for VSI is not to contribute to the
> >>>> open soure world as such, just to provide their customers access to
> >>>> some open source tools that might be of value (to the customers).
> >>>
> >>> The thing is that many open source licenses -require- that any changes
> >>> or additions to their code be made available in source form...
> >>
> >> Sure! But "made available" is not the same thing as "contributing to
> >> the open source world".
> >>
> >> VSI can do additions and share them with the (few) VMS users that are
> >> interested. But they do not need to, what ever it is called, send it
> >> upstreams to the main source code repository.
> > 
> > This is true.  However, if you don't get your changes included in the
> > main distribution, you can give up any chance of being able to incorporate
> > updates from the main distribution in the future.  It is a -lot- more work
> > to maintain software this way.  You can do it, if you have to.
> > 
> > And really, it's not very difficult to get your updates incorporated in the
> > main distribution, if they don't affect non-VMS systems.
> > 
> >> I think there is a difference there...
> > 
> > There is.  It's the difference between creating your own software distribution
> > and using someone else's.  There are some arguments in favor of both, but when
> > your labour is limited and you expect the software to have any longevity, it's
> > easier to get someone else to do the maintenance.
> 
> Yes. And that is important because open source will not be a tiny
> exotic corner of VSI software - it will be a huge part.
> 
> It is difficult to predict about the future, but my crystal
> ball says that in 2025 then the software VSI distribute will be
> 1/3 closed source (written by VSI or licensed from HPE) and 2/3
> open source.
> 
> LLVM, OpenJDK, Python, Apache, PHP etc..

I hope someday VSI can just acquire the copyrights from HPE and then they're free to license OpenVMS and its layered products however they like. It would be certainly nice to see the source for the various layered products that don't really see any maintenance or sales released if only to preserve them.