Patterns/Framework

Patterns framework should discuss:

1. status: present, wishes, future plans, time table
2. methods: how to determine package groups (top-down, bottom-up), how to determine where package has to be included (functionality, code maturity, ...)
3. pattern properties:
   1. type by:
      1. code maturity (experimental, production, ...),
      2. functionality (see article Software Categories and Hardware Categories)
   2. level (top, sub, basic/core)
   3. completness (standalone, component)
   4. configuration (desktop, server, ...)
4. dependencies (list of)
5. tools to: build, store and retreive patterns,

The list is probably incomplete, and has to be expanded. See editor comments.