You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Paul Spencer <pa...@mikon.com> on 2001/10/13 10:26:08 UTC

Purposed Bugzilla Components

Please review and comment on the list of component for Bugzilla.  With
24 component, the list seems a little long. 

Paul Spencer

***************
***** 
***** Suggested Bugzilla Components for Jetspeed
***** 
***************

* = Different from what is currently configured in Bugzilla

*Name......... Aggregation Engine (was aggregation engine)
*Owner........ jetspeed-dev@apache.org
*Description.. Aggregates the output of all the Jetspeed managed
components

*Name......... Cache (was cache)
*Owner........ jetspeed-dev@apache.org
*Description.. Local and Disk cache systems for storing portlet content

 Name......... Customizer
*Owner........ jetspeed-dev@apache.org
*Description.. Tool use to define portlets the appear in a user's, or
group's
               named portal, i.e. default.psml

*Name......... Database ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Problems around the database interaction.
 ** Note **... Is this not covered by the component the is iterating 
               with the database, i.e. PSML, Login, Registry...?

*Name......... Documentation ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Jetspeed Documentation

*Name......... Distribution ( was webapp )
*Owner........ jetspeed-dev@apache.org
*Description.. Problems specific to packaging and distribution. 
Includes the 
               contents of the tar, war, and zip files

*Name......... Examples ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Problems with the Examples include with Jetspeed.

*Name......... JSP ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. JSP processing and the Jetspeed Tag Library

*Name......... Layout (was layout components)
*Owner........ jetspeed-dev@apache.org
*Description.. Components the affect the how portlet content is
presented in the
               portal.  This includes Controllers, Controls, Skins.

*Name......... Login ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. User login and authentication

*Name......... Miscellaneous ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Problem/Bug does not fit into any other component.

*Name......... Portlet API (was portlet API)
*Owner........ jetspeed-dev@apache.org
*Description.. The interface between Jetspeed and portlets.

*Name......... Portlet Container (was portlet container)
*Owner........ jetspeed-dev@apache.org
 Description.. The container handles the registration, creation and
destruction
               of portlets as well as dispatching the user requests to
the
               appropriate portlet and gathering the generated output

*Name......... Portlets (was portlets)
*Owner........ jetspeed-dev@apache.org
*Description.. Default portlets provided with Jetspeed. This includes
the JSP,
               RSS, Turbine, Velocity, WebPagePortlet, and XSL portlet
types. It
               excludes the Customizer and JSP/Turbine/Velocity related
problems.
               
*Name......... Profiler (was profiler)
*Owner........ jetspeed-dev@apache.org
 Description.. Profiler
 ** Note **... What is the profile?

*Name......... PSML ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Management of Portal Structure Markup Language (PSML)

*Name......... Registry ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Management of Registry entries like Controllers,
Controls, Portlets,
               and Skins

*Name......... Security ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Management and application of Portlet security
 ** Note **... Is this not already covered by the Customizer, Login,
Portlet,
               and Registry components ?

*Name......... Syndication (was syndication)
*Owner........ jetspeed-dev@apache.org
 Description.. OCS Feeds and RSS channels management

*Name......... Turbine ( was Turbine toolbox)
*Owner........ jetspeed-dev@apache.org
 Description.. Main interface between the Turbine layout system and
Jetspeed
               aggregation and customization engines

*Name......... Velocity ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Velocity processing and content generation.

*Name......... Web Services ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. 
 ** Note **... What are the Web Serves?

*Name......... WebPage ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Interaction between Jetspeed and a Web Server.  Examples
include
               problems interacting with Firewalls or Proxy servers, 
and the
               manipulation of the content return by a Web server into
portlet
               content.  This component usually includes problems
specific to 
               the WebPagePortlet.
               
*Name......... WML ( new component )
*Owner........ jetspeed-dev@apache.org
*Description.. Problems related to the WML media-type.
 ** Note **... Should this be general Media-Type component that include
HTML
               Browser, PDAs,  and Mobile Phones?


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: Purposed Bugzilla Components

Posted by Paul Spencer <pa...@mikon.com>.
I just realized the owner should be jetspeed-dev@jakarta.apache.org, not
jetspeed-dev@apache.org.

Paul Spencer



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org


Re: Purposed Bugzilla Components

Posted by Paul Spencer <pa...@apache.org>.
The components in Bugzilla have been updated.

Paul Spencer


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>