微软visual c++ libraries team的pranish kumar在12日提议将wtl(windows template library)变成shared source。这在wtl社区正在引起争论。pranish kumar的两个贴子如下:
1,------------------------
2003年4月12日 8:16
hi,
my name is pranish kumar and i work on the visual c++ libraries
team. i wanted to make a posting that would hopefully answer many of
the questions people have asked about wtl. we appreciate feedback on
the message, particularly in what you would like to see happen with
wtl, for example how many of you would be interested in supporting
it as an open source project?
wtl has had an unusual time in microsoft. it was shipped as an
unsupported sample in the platform sdk, a state in which it has
remained. over the years a user-base has built up around wtl, with
support being provided through non-standard channels.
many wtl users ask us why we don't support wtl as an official
microsoft product. there are a number of issues with this, but one
of the major ones is the work required to make wtl an official,
supported product. wtl requires documentation to be written from
scratch, the creation of a complete test suite and testing harness,
and the addition of knowledgeable support personnel to the microsoft
official support channels. there would also likely be significant
changes to the library itself as we moved it forward to the latest
version of atl and the compiler.
the cost of doing this work is several-fold, firstly it would likely
take up all the atlmfc team resources for a full release to complete
this upgrade. the only visible differences for wtl users would be
microsoft support and documentation as well as some bug fixes, for
existing atlmfc users there would be no new features.
because almost every wtl user we talk to today is extremely happy
with the library, and because of the importance of continuing to
develop atlmfc, we do not think that productizing wtl is the best
use of our resources. wtl has solved problems for a portion of vc++
customers through its current release mechanism, this makes it
difficult to justify spending the significant effort required to
make it a supported product. also the wtl community would need to
realize the disadvantages as well as the advantages of having a
productized wtl, some issues that come to mind include frequency of
releases, bug fixing process and working through official support
channels.
having said this, the atlmfc team is always looking to support our
customers in the best way possible, if it turns out that there is an
increased need amongst existing atlmfc customers for wtl, or that
there is a way to productize wtl without incurring the large
overhead, then we would definitely reconsider our position.
related to this the team is investigating various ways that we can
improve the experience for wtl users without incurring the
prohibitive overhead. some of the possibilities we are investigating
include modifying the licensing for wtl so that the wtl community
could support itself with a shared-source project.
the atlmfc and smart devices teams are also working closely together
to provide a better solution for our customers. in the next release
of visual studio, native c++ development for smart devices will be
integrated into the visual studio shell. the devices team is also
investigating what role wtl will play in the evc space.
hopefully this answers most of your questions and concerns, expect
to hear more from the visual c++ team on where we are going with the
language and libraries in the not too distant future.
thanks,
pranish kumar
pranishk@microsoft.com
2,------------------------
date: tue, 15 apr 2003 01:40:58 -0000
sorry for the bad subject, also sorry for condensing everyone's
questions into one response, but it makes it easier. i originally
started including each person's questions, but it didn't make much
sense because many of them were similar.
thanks for all the feedback, this has been very useful.
(1) how does shared source differ from open source?
i called it shared source, because that is the usual name microsoft
gives these projects, if we go down this path then we would have two
main goals, one that people could contribute, two that it could
continue to be used in commercial development.
(2) what will nenad's role be?
if we do go down a shared source path, then their will be a role for
nenad, the range and scope of that role will depend on what we are
