[Info-vax] Looking to find a way to pull all the Open Source / Freeware folks together

[RobertsonEricW]

On Oct 1, 1:58 pm, Jojimbo <jjgessl... at gmail.com> wrote:
> On Oct 1, 1:40 am, IanMiller <g... at uk2.net> wrote:
>
> > There are certainly informal links.  What would you want from such a
> > link?
>
> I'll tell you what I want.
>
> 1) all the current GNV source code and build scripts into source forge
> 2) HP designated owner to accept patches and integrate fixes into code
> base
> 3) going forward, a community process to grow around GNV and it's
> improvement.
>
> Bottom line, I want to be able to check out GNV from sourceforge,
> build it and have the latest stable version.
> And the ability to submit changes and get them integrated if they are
> worthy.
>
> That's what open source is all about, which is different from what we
> have now.
>
> Regards, Jim

The company I work for is particularly interested in seeing the
OpenVMS Open Source initiative portion of the overall "OpenVMS
Awareness Program" from the OpenVMS Community succeed. Currently, the
basic problem with Open Source Development using OpenVMS is the
deplorable state of its Open Source tool set (GNV). The company I work
for is a participant in the Developer and Solution Partner Program
(DSPP). Through this program (and through other channels as well) we
have been in conversation with John Egolf (OpenVMS Integrity Migration
Manager), Sujatha Rumani (HP India Software Optns), and in particular
Mandar Jagannath Chitale (TSG ESS STSD Shared Optns HP India Software
Optns). Mandar is one of the principals involved in generating the
list of enhancements targeted by the new OpenVMS Engineering group in
India for planning Development activities for new features of OpenVMS
and other related HP OpenVMS products (such as GNV). I had E-mailed
Mandar in particular about the plans for GNV and about the increasing
frustrations of OpenVMS Developers with GNV. I also pointedly asked
him if OpenVMS GNV Engineering was going to resurrect the SourceForge
GNV site so that the people already independently making improvements
to GNV software could collaborate with each other and with HP OpenVMS
GNV Engineering to move the functionality of the GNV tool set forward
into the future. His response to my E-mail indicated that he and
others were already in the process of hammering out a plan to move GNV
forward with the specific intent of allowing Open Source contributors
(with or without an existing HP affiliation) to participate in
enhancing the GNV tool set. Mandar indicated that they would solidify
and then "announce" (not sure what form the "announcement" will take)
their plans for GNV development before the Thanksgiving holiday
season.

If you would like me to keep you apprised of my company's efforts to
move GNV forward let me know and I will keep you up to date.

Eric