[Info-vax] Python and various libraries updated

[Arne Vajhøj]

On 8/6/2020 3:07 AM, gerard.labadie at gmail.com wrote:
> If a student or anybody wants to fix a bug or add a feature in a VSI port, without access to the sources, how does he do?

You obviously need access to the source (unless you feel comfortable
doing a binary patch :-) ).

If change relate to generic source code => you get code code from and 
submit changes to the open source project

If change relate to VMS specific code where open source project has 
accepted changes from VSI => you get code code from and submit changes 
to the open source project

If change relate to VMS specific code where open source project has not 
accepted changes from VSI and VSI has released source code => you get 
code code from and submit changes to VSI

If change relate to VMS specific code where open source project has not 
accepted changes from VSI and VSI has not released source code => you can't

Regarding the 4th scenario then as stated in another post then I
certainly expect VSI to comply with license terms. And it is also
my impression that VSI is very much pro open source, so that their
preference is scenario 2 is better than scenario 3 that is better
than scenario 4. So I would expect scenario 4 to only happen if license
allows it *and* VSI cannot legally release the source code (most
like reason being that the code is owned by HPE and VSI only have
right to use the code not release it).

Arne