wkix: /
content /
4
001: '''The following should be implemented:'''
002:
003: * Search in documents with authorised read access.
004: * View the configuration for all plugins configured for the current view.
005:
006: * Multiple views via multiple viewing plugins (done in KixFw-1.10).
007: * Suppress the raw view - via configuration?
008:
009: '''Wish List for More Plugins'''
010:
011: * Add perl compilation view plugin.
012: * Add export to file plugin - done but not yet published.
013: * Add simple copy new document content to new version in dependent - ideal for staging of work.
014: * Add event multiplexing plugin for event distribution to multiple event handling plugins.
015: * Release KixPlugin::Wiki2Html (to be called KixPlugin::Wiki?).
016: * Add plugins to support standard Microsoft Office documents. What open source to start from?
017:
018: '''Other Functional Improvements'''
019:
020: * Provide a '''documentation interface for plugins''' - display relevant plugins with relevant metadata.
021: * Add submit metadata (comment) to version creation and document upgrades.
022: * Send notification to owner of a document, when a responsible person performs significant document operations.
023:
024: Provide a '''model view''' over CFW configuration data.
025:
026: * Create accounts with default stake holder document and focus set at it.
027: * Improve management of responsible when new folders and documents are created.
028: * Improve management of responsible when items are given away.
029:
030: '''Authentication'''
031:
032: Provide login and account creation support for '''OpenId'''.
033:
034: '''Authorisation:'''
035: * Develop authorisation plugin interface point.
036: * Introduce KIX roles - plugin to authorise role change.
037: * Introduce authorised control over export of content and indexes.
038:
039: '''Improve Style:'''
040: * General style upgrade.
041: * Move main display to scroll-able division.
042: * Improve the notification e-mail.
043:
044: Use '''quri for configuration''' info, including how to locate plugins. This should enable configuration for remote displays.
045: (Use Wiki2Html as starting point.)
046:
047: '''KIX Development Testing'''
048:
049: * Develop regression testing for all perl modules.
050:
051: '''New Physical Bindings for the Kix Data:'''
052: * Develop a file based binding of raw content.
053: * Develop a SVN based binding of raw content.
054: * Develop a KIX input binding from polling a file system?
055:
056: '''X3P:'''
057:
058: Introduce a PGP encryption option in the X3P protocol.
059:
060: '''KIX Promotion'''
061: - develop KIX perspectives:
062: * live document repository
063: * integrated decision making
064: * integrated product and service development
065: * publisher - dependency
066: * web conferences
067: * peer-to-peer
068: * database
069: * RDF
070: * stake-holder
071: * work-flow
072: * processing
073: * result export
074: * integrated knowledge development
075: * integrated knowledge use
076: * organisational memory
077: * incentives
078: * ad hoc collaborations - by default
079: * structured collaborations - via plugins
080:
081:
082: '''Patterns of collaboration - support by plugins'''
083:
084: Are there suitable patterns already defined?
085: * Is DSDM a suitable pattern for a management plugin?
086: * Is Scrum a suitable pattern for a management plugin?
087: * Requirements engineering - what patterns exists?
088:
- Search in documents with authorised read access.
- View the configuration for all plugins configured for the current view.
- Multiple views via multiple viewing plugins (done in KixFw-1.10).
- Suppress the raw view - via configuration?
Wish List for More Plugins
- Add perl compilation view plugin.
- Add export to file plugin - done but not yet published.
- Add simple copy new document content to new version in dependent - ideal for staging of work.
- Add event multiplexing plugin for event distribution to multiple event handling plugins.
- Release KixPlugin::Wiki2Html (to be called KixPlugin::Wiki?).
- Add plugins to support standard Microsoft Office documents. What open source to start from?
Other Functional Improvements
- Provide a documentation interface for plugins - display relevant plugins with relevant metadata.
- Add submit metadata (comment) to version creation and document upgrades.
- Send notification to owner of a document, when a responsible person performs significant document operations.
Provide a model view over CFW configuration data.
- Create accounts with default stake holder document and focus set at it.
- Improve management of responsible when new folders and documents are created.
- Improve management of responsible when items are given away.
Authentication
Provide login and account creation support for OpenId.
Authorisation:
- Develop authorisation plugin interface point.
- Introduce KIX roles - plugin to authorise role change.
- Introduce authorised control over export of content and indexes.
Improve Style:
- General style upgrade.
- Move main display to scroll-able division.
- Improve the notification e-mail.
Use quri for configuration info, including how to locate plugins. This should enable configuration for remote displays. (Use Wiki2Html as starting point.)
KIX Development Testing
- Develop regression testing for all perl modules.
New Physical Bindings for the Kix Data:
- Develop a file based binding of raw content.
- Develop a SVN based binding of raw content.
- Develop a KIX input binding from polling a file system?
X3P:
Introduce a PGP encryption option in the X3P protocol.
KIX Promotion - develop KIX perspectives:
- live document repository
- integrated decision making
- integrated product and service development
- publisher - dependency
- web conferences
- peer-to-peer
- database
- RDF
- stake-holder
- work-flow
- processing
- result export
- integrated knowledge development
- integrated knowledge use
- organisational memory
- incentives
- ad hoc collaborations - by default
- structured collaborations - via plugins
Patterns of collaboration - support by plugins
Are there suitable patterns already defined?
- Is DSDM a suitable pattern for a management plugin?
- Is Scrum a suitable pattern for a management plugin?
- Requirements engineering - what patterns exists?