[apluslist] Community Contriibutions

[John.Mizel at MorganStanley.com]

Hi Steve,

A+ is a mature "product" so there isn't alot of new development.  I am
still doing support for both the internal and external A+ releases, but
most of my time is now spent on working on an A+ application.

The documentation changes planned for 4.20 are just to re-package the html
files as separate package.  The changes for the release are in Changelog
for 4.20 are fairly minor.  So if you don't require any of the fixes I'd
recommend that you continue to use 4.18.

If anyone does wish to submit a patch, I'd recommend discussing it on this
mailing list and sending it to me.

Thanks,
John

>
> Message: 1
> Date: Mon, 26 Jul 2004 21:00:36 -0500
> From: "Steven H. Rogers" <steve at shrogers.com>
> Subject: [apluslist] Community Contriibutions
> To: apluslist at aplusdev.net
> Message-ID: <4105B744.2000305 at shrogers.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> While there have been some community contributions to A+, there haven't
> been many.  I'm torn between A+ and J and the fact that J has an active
> user community is one of its strong points.  I appreciate Morgan
> Stanleyl open sourcing A+, but it seems rather moribound.
>
> I have A+ 4.18 installed on my main system and 4.20 one which sees less
> use.  Which should I use?  I've been holding off on installing 4.20 on
> my main machine until the documentation catches up.  Any idea when this
> might happen?
>
> I gather that the Morgan Stanley A+ developers have been assigned other
> duties, though they still support A+.  Priorites are unclear and Morgan
> Stanley's continued support may be in question.  If so, would community
> participation have an impact on decisions in this area?
>
> How can the community help?  Some things are obvious, e.g. you need more
> example programs, but a todo list might inspire some of us to do
> something.   If we get inspired enough to submit patches to the C/C++
> code, what is the procedure?
>
> Regards,
> Steve
>

This communication is intended for the addressee(s) and may contain
confidential and legally privileged information.  We do not waive
confidentiality or privilege by mistransmission.  If you have received
this communication in error, any use, dissemination, printing or
copying is strictly prohibited; please destroy all electronic and
paper copies and notify the sender immediately.