This project is not being actively maintained. The source has not been updated since July, 2012. We will attempt to provide help and answer questions. However, the source and docs are presented as-is. There are currently no plans to update this project.
The most up-to-date version of the release notes issues is available online.
The release notes include information about:
If you would like to become involved in the development of the CQRS Journey sample application and guidance, you can contribute in many different ways:
Reviewing the CQRS Journey guidance and code, asking and answering questions, reporting bugs and making feature requests are critical activities of the project community: we value your feedback!
In order to become familiar with the functionality of the reference implementation you can obtain the source code from GitHub (see "Obtaining the source code" below) and compile it locally. While you become familiar with the functionality, you can report bugs or request new features (see "Report bugs and request features" below). You can also download the current draft of the documentation from GitHub.
We would love to hear your thoughts, be it comments, suggestions, ideas or anything else. However, in the end we are creating Microsoft guidance. So we'll happily take your feedback but you need to understand that by providing us feedback in any form you are agreeing that (i) we may freely use, disclose, reproduce, modify, license, distribute and otherwise commercialize your feedback in any Microsoft product, technology, service, specification or other documentation, (ii) others may use, disclose, reproduce, license, distribute and otherwise commercialize your feedback in connection with our products and services, and (iii) you will not be compensated for any of these things. We may incorporate ideas or make changes based on comments you make, or we may make changes to the product that are indirectly influenced by discussions that we have with you and other folks in the community.
There are three project repositories:
We are also hosting our project web site on GitHub - http://cqrsjourney.github.com
You can ask questions via Disqus on the http://cqrsjourney.github.com web site or by posting them as Issues with the "question" prefix in GitHub to the project's cqrs-journey-code or cqrs-journey-doc repositories.
In order to obtain the source code you can either download it as a zip file from the GitHub or clone the repository by using Git.
Follow these steps to download the source code in a zip file:
To clone the source repository using Git, see instructions from the Checkout the latest code section.
The draft content of the guide is available in the cqrs-journey-doc repository on GitHub. You can read it online. You can also download or clone this repository in the same way that you obtain the source code.
Issues and feature requests are submitted through the project's Issues section on GitHub. Please use the following guidelines when you submit issues and feature requests:
The core team regularly reviews issues and updates those with additional information. Sometimes the core team may have questions about particular issue that might need clarifications, so please be ready to provide additional information.
In order to become a contributor to the project you must sign the Contributor License Agreement (CLA). Signing the Contributor License Agreement (CLA) does not grant you rights to commit to the source code or doc repositories but it does mean that we will consider your contributions and you will get credit for them if we use them.
You can download the Contributor License Agreement (CLA) by clicking the following link: http://cqrsjourney.github.com/docs/Contribution%20License%20Agreement.pdf. Please fill in, sign, scan and email it to cla@microsoft.com with the "CQRS Journey Project CLA" as the subject line.
You do not need to sign a separate agreement if you have already submitted one to contribute to the project's documentation or to other Microsoft OSS projects (such as Windows Azure SDK) and if your employer hasn't changed.
In order to obtain the source code you need to become familiar with Git (see http://progit.org/book/) and GitHub (see http://help.github.com/) and you need to have Git installed on your local machine.
You can obtain the source code from GitHub by following the following steps on your local machine:
git clone git@github.com:[USERNAME]/cqrs-journey-codecd cqrs-journey-codegit remote add upstream git@github.com:mspnp/cqrs-journey-codegit fetch upstream/devgit merge upstream/devWe are using the Fork+Pull Model of collaborative development.
You make modifications of the code and commit them in your local Git repository. Once you are done with your implementation follow the steps below:
git checkout devgit pushNote: It's a good idea to create a branch before submitting a pull request, just in case there are improvement suggestions to the submitted contribution that need to be incorporated before it's accepted. That way, the pull request points to the entire branch and changes to it can be incorporated using the same pull request sent initially (which will hold discussions and comments about the improvements, etc.).
Note: All changes and pull request should be done against the dev branch. Changes will be integrated in the master branch by the core team.
Please keep in mind that not all requests will be approved. Requests are reviewed by the core team on a regular basis and will be updated with the status at each review. If your request is rejected you will receive information about the reasons why it was rejected.
Before you start working on bug fixes and features it is good idea to discuss those broadly with the community. You can use the forums as described in Asking and answering questions for this purpose.
Before submitting your changes make sure you followed the guidelines below:
In order to speed up the process of accepting your contributions, you should try to make your check-ins as small as possible, avoid any unnecessary deltas and the need to rebase.
In order to become a contributor to the project you must sign the Contributor License Agreement (CLA). Signing the Contributor License Agreement (CLA) does not grant you rights to commit to the source code or doc repositories but it does mean that we will consider your contributions and you will get credit for them if we use them.
You can download the Contributor License Agreement (CLA) by clicking at the following link: http://cqrsjourney.github.com/docs/Contribution%20License%20Agreement.pdf. Please fill in, sign, scan and email it to cla@microsoft.com.
You do not need to sign a separate agreement if you have already submitted one to contribute to the project's source code or to other Microsoft OSS projects (such as Windows Azure SDK) and if your employer hasn't changed.
In order to obtain the latest docs you need to become familiar with Git (see http://progit.org/book/) and GitHub (see http://help.github.com/) and you need to have Git installed on your local machine.
You can obtain the docs from GitHub by following the following steps on your local machine:
git clone git@github.com:[USERNAME]/cqrs-journey-doccd cqrs-journey-docgit remote add upstream git@github.com:mspnp/cqrs-journey-docgit fetch upstream/devgit merge upstream/devWe are using the Fork+Pull Model of collaborative development.
You make modifications of the docs in your local Git repository. Once you are done with your changes follow the steps below:
dev with the following commandgit checkout devgit pushNote: All changes and pull request should be done in the dev branch. Changes will be integrated in the master branch by the core team.
Please keep in mind that not all requests will be approved. Requests are reviewed by the core team on a regular basis and will be updated with the status at each review. If your request is rejected you will receive information about the reasons why it was rejected.
Before you start working on new document sections or make major revisions to the existing ones it is good idea to discuss those broadly with the community. You can use the forums as described in Asking and answering questions for this purpose.
Before submitting your revisions to the doc repository, make use you followed the guidelines below:
In order to speed up the process of accepting your contributions, you should try to make your check-ins as small as possible, avoid any unnecessary deltas and the need to rebase.
An easy way to review the docs and comment on them (without using Git, GitHub, or Markdown) is via the simple document review site, which allows you to see the docs with inline comments of others and submit your own commentary. Please note that this site only shows the latest version of the docs. As the new versions of the docs are produced and the comments are acted upon, the comments are removed from the pages but remain visible via the history of check-ins in the main document repository (https://github.com/mspnp/cqrs-journey-doc).
For any further inquiries, contact the project leader, Grigori Melnik, at grigori dot melnik at microsoft dot com