OpenChange

h1. Getting Involved

{{>toc}}

The OpenChange project welcomes anyone who would like to become involved in the project. We particularly need people with an interest in (in alphabetically order, not priority):

* bug triage

* development / coding in C, C++, Python or Perl (and possibly other languages depending on your development goals)

* documentation / proof reading

* system administration (especially with Exchange servers, although other mail / calendaring / task based tools and general sysadmin support would also be useful)

* testing and bug reporting

To become involved, we suggest you start by:

# joining the main mailing list (see "subscription information":http://mailman.openchange.org/listinfo/devel and the "archive of previous posts to the mailing list":http://mailman.openchange.org/pipermail/devel/ for more information)

# "Register":http://tracker.openchange.org/account/register on the tracker and post your questions in the "Forums":http://tracker.openchange.org/projects/openchange/boards.

# and if possible, also join the "IRC":http://en.wikipedia.org/wiki/Internet_Relay_Chat channel we use - #openchange on "Freenode":http://en.wikipedia.org/wiki/Freenode (server: irc.freenode.net, channel: #openchange).

Your next stage is then to set up a development environment (either from scratch, or starting with a pre-build appliance). Guides on how to do this are provided below. If you have trouble, please ask questions on the IRC channel (preferred) or on the mailing list.

We have an incomplete list of tasks (including bugs to fix and features to implement) on the "issue tracker":http://tracker.openchange.org/projects/openchange/issues. Please let us know what you are working on before getting too far into it, to prevent any issues coming up at merge time, and also to allow us to provide guidance / suggestions where appropriate.

Thanks for your interest in OpenChange!

h1. Task guide

h2. Getting OpenChange appliance

The easiest way to get an OpenChange system up and running for development or evaluation is to use a pre-built virtual machine. 

Follow the instructions available in the [[OpenChange Appliance|OpenChange Appliance Installation Tutorial]].

h2. Install OpenChange from source

Follow the instructions in this guide which explains [[HowTo Install OpenChange From Source]].

h2. Update OpenChange and Samba from source

Follow the instructions in this guide which explains [[HowTo Update OpenChange and Samba From Source]].

h2. Server setup

Follow the instructions in this guide which explains [[HowTo Setup OpenChange Server]].

OpenChange server - beside its native compatibility with Microsoft Outlook - offers a pluggable storage's mechanism called mapistore. It provides a scalable solution to MAPI data storage allowing user to transparently store MAPI data on a large set of services and databases:

* "SOGo":http://www.sogo.nu/about/overview.html: [[HowTo build your own OpenChange/SOGo appliance]].

h2. Client setup

Follow the instructions in this guide which explains [[HowTo Setup OpenChange Client]].

h2. Outlook setup

Follow the instructions in this guide which explains [[HowTo Setup Outlook with OpenChange Server]].

If you experience severe problems with Outlook, then the [[Engaging with Microsoft on Outlook]] guide may be of use.

h1. Administrator Guides

h2. [[HowTo build your own OpenChange/SOGo appliance]]

Follow this guide if you want to setup an OpenChange appliance from scratch with SOGo backend.

h1. Developer Guides

h2. MAPIStore 1.0 development guide

This document describes the API used to write backends for OpenChange Server: [[MAPIStore 1.0 Development Guide]]

h2. OCSManager Specifications

OCSManager is the OpenChange Service Manager. It is used to send notifications from a remote system to OpenChange Server and advise clients on remote changes.

This document covers the OCSManager installation, configuration and protocol specifications for authentication and notifications: [[OCSManager Specifications]]

h1. Useful documentation

h2. OpenChange Server Documentation

*  *mapiproxy and mapistore:* http://mapiproxy.openchange.org

h2. OpenChange API Documentation

* *client libraries:* http://apidocs.openchange.org

h2. ExchangeRPC Investigation

The OpenChange project scope includes both implementing the "as documented" protocols from Microsoft, and also investigating and verifying the protocol (and its documentation). See [[Protocol Information]].

h2. Fast Transfer

We have an implementation of the "Fast Transfer" operations described in MS-OXCFXICS. See [[Fast Transfer]] for more details.

h2. Project infrastructure

The OpenChange project has a strong commitment to appropriate infrastructure. A description of some of it is available in [[OpenChange Project Infrastructure]].

h2. HowTo Guides

h3. Installation

* [[HowTo Install OpenChange From Source]]

* [[HowTo Update OpenChange and Samba From Source]]

* [[HowTo Setup OpenChange Server]]

* [[HowTo Setup OpenChange Client]]

* [[HowTo Setup Outlook with OpenChange Server]]

* [[OpenChange Appliance|HowTo Install OpenChange Appliance]]

* [[HowTo install an Exchange test lab]]

** [[HowTo Create Windows 2008 base image]]

** [[HowTo Create Exchange 2010 Virtual Machine]]

** [[HowTo Create Exchange 2007 Virtual Machine]]

h2. Development status and tips

[[Overview of ExchangeRPC]] provides a starting point for developers (working with OpenChange libraries, or working on OpenChange).

The [[Client Side Function]] list shows where we are up to with particular Remote Operations. You can also look on the Issues list.

We have some [[Test Ideas]], some of which are implemented by the [[OpenChange Project Infrastructure]].

h2. Architecture thoughts

* [[Seattle Meeting - Day 1]]

* [[mapistore v2]]

* [[Searching]]

h2. Meeting Plans and Records

* [[Plugfest - Jan 2011]]

* [[Meeting of 2010-07-30]]