On Mon, May 15, 2000 at 01:53:52PM -0600, Nathan Torkington wrote:
> Graham Barr writes:
> > Likewise but there has been a lot of silence. Mainly I suspect due to
> > this list does not have the diversity of users to decide on a complete
> > list of modules for an SDK IMO.
> 
> True, but so be it.  We make the best decisions we can, and rely on
> experience to provide the rest.  I figure that once SDK 1 is out the
> door, we'll get plenty of feedback on what worked and what didn't for
> SDK 2.

This is very true. But the feedback you get will more likely be "why was
xyz not added" rather than "why was xyz added". And as it has been said,
removing packages once added will be difficult.

The SDK is supposed to be a package of what modules are most commonly
used, so to get the intial set right we should attempt to discover what
is most commonly used. That means going beyond this list to the users.

Possible things would be posting to all mailing lists/newsgroups you
can think of and request feedback. Or an online web poll with a list
of proposed distributions/modules. I am sure other can think of ways to
get this information.

Basically if we don't attempt to get even the intial module set riht,
or even close. Then the SDK is just going to grow to be a tarball of CPAN.

Graham.

Reply via email to