Possible Contributions

The following list is a collection of all the places where a todo item was included, because there is more work to do. Please consider picking one of those up helping to complete the documentation.

That’s left to do:

Todo

what should you do to continue to run the environment?

(The original entry is located in /home/mollekopf/src/docs/source/administrator-guide/index.rst, line 48.)

Todo

Document the concepts of a sealed system.

(The original entry is located in /home/mollekopf/src/docs/source/architecture-and-design/index.rst, line 46.)

Todo

Administration Guide topic for LDAP deployments with single trees growing over 1.000 entries.

(The original entry is located in /home/mollekopf/src/docs/source/architecture-and-design/ldap.rst, line 111.)

Todo

Somewhere other than here, document the process of scaling up from one single server on to multiple servers.

(The original entry is located in /home/mollekopf/src/docs/source/deployment-guide/index.rst, line 117.)

Todo

We probably need to explain why we choose to use SMTP rather than LMTP.

State something about pre-authorizing LMTP, it happening over the network, murder topologies and LMTP proxying, the use of LDAP holding the mailHost attribute, accounting, etc.

(The original entry is located in /home/mollekopf/src/docs/source/deployment-guide/multi-server.rst, line 666.)

Todo

Document an inventory of products and components along with the method of creating the inventory.

(The original entry is located in /home/mollekopf/src/docs/source/developer-guide/bugzilla.rst, line 139.)

Todo

Document the inventory of package versions, product streams and product versions that are supported, along with the methodology of creating such inventory.

(The original entry is located in /home/mollekopf/src/docs/source/developer-guide/bugzilla.rst, line 147.)

Todo

Install the NEEDSINFO extension, so that not only can the status be set, one can explicitly supply from whom the additional information is needed, said person is notified, and said person can “clear” the NEEDSINFO state when the requested information is supplied.

(The original entry is located in /home/mollekopf/src/docs/source/developer-guide/bugzilla.rst, line 423.)

Todo

Write the section on running the Hosted Kolab Customer Control Panel from source.

(The original entry is located in /home/mollekopf/src/docs/source/howtos/build-kolab-from-source.rst, line 603.)

Todo

Write the section on running Chwala from source.

(The original entry is located in /home/mollekopf/src/docs/source/howtos/build-kolab-from-source.rst, line 611.)

Todo

Write the section on running iRony from source.

(The original entry is located in /home/mollekopf/src/docs/source/howtos/build-kolab-from-source.rst, line 618.)

Todo

The installation chapter for SUSE Linux Enterprise Server should be written.

(The original entry is located in /home/mollekopf/src/docs/source/installation-guide/kolab-3.3/suse.rst, line 5.)

Todo

A separate set of credentials should be supplied for wallace, freebusy, replication and proxy for the purposes of maintaining a more well-informed audit trail.

(The original entry is located in /home/mollekopf/src/docs/source/puppet/module/kolab.rst, line 201.)

Todo

1. Add a setting imap_proc_path.

2. Add a setting webadmin_api_memcache_hosts

3. Add a setting hkccp_memcache_hosts

(The original entry is located in /home/mollekopf/src/docs/source/puppet/module/kolab.rst, line 536.)

Todo

Is this list complete?

(The original entry is located in /home/mollekopf/src/docs/source/upgrade-guide/kolab-3.1.rst, line 212.)

Todo

Is this list complete?

(The original entry is located in /home/mollekopf/src/docs/source/upgrade-guide/kolab-3.1.rst, line 220.)