Conor MacNeill wrote:
> If there was one list for the commons, more people will be exposed to each
> component of the commons. It will make the components more well known.
> People may not need a component now but they may remember later a
> discussion about some capability. I feel that one of the keys to the
> success of the commons will be how well its components are known, because
> only then will they be reused.
That's a good point. Not only is it important that the packages in the
Commons be better known, but also that other reusable packages in
Apache-land be better known.
An important part of the Commons is the catalog, which will be designed
to promote packages. This is where we would try to steer people when
they are looking for a a new package.
--
(1.5.2) the directory
The subproject will also catalog packages and other resources available
to the public related to other Jakarta
subprojects and ASF projects. This will be a dynamic catalog, like
Bugzilla and Jyve, similar in functionality to download.com, cpan.org,
or SourceForge.net. New entries may be added by Jakarta committers,
developers, and users. Entries by developers and users will be approved
by a committer before being made public.
--
Of course, whenever a a new package, or a new version, is released, it
would be posted to Jakarta-Announce, and give us another opportunity to
hype the Commons catalog.
My fear about traffic is that it is a two-edged sword. Once a list
becomes too heavily traffic and covers too many diverse topics, people
unsub away. (I know I do.) By then, breaking the list up becomes a
round-to-it, and tends not to happen.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
