Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
OpenLayers 3
JavaScript Python Other
branch: master
Failed to load latest commit information.
apidoc_config Doc menu update (futile, I know).
art Unmixing line endings. No functional change.
build Update copyright year to 2010
doc mike adair, for mapguide layer and some other work
doc_config Doc menu update (futile, I know).
examples removed svn:executable property. Non functional change
img move close button image for popups into the theme (references #1472)
lib - Added multipleselected event. Triggered when multiple features are …
tests Removing properties added to global Event.
theme/default removed svn:executable property. Non functional change
tools mergejs: Remove white space around filename. No functional change. (c…
authors.txt Adding an authors file with syntax specific to git-svn. This file mus…
license.txt Update copyrights to 2008.
news.txt update news.txt
readme-dev.md Adding a readme with details for people that will be pushing to the c…
readme.md Updating the main readme for work toward 3.0. A more complete readme …
release-license.txt
repository-license.txt

readme.md

OpenLayers 3

This document describes a bit about the working going toward OpenLayers 3.0.

OpenLayers v3 development is taking place in git, with a central repository hosted on GitHub. To contribute to development, it's important to be comfortable working with git. The help pages on GitHub provide a nice starting place for this.

The repository contains a master branch and a 2.x branch. Other branches may come and go as people work on specific features. The master branch should be the closest stable thing to OpenLayers 3.0 (and this readme should get updated before 3.0 is released). However, at any time before the 3.0 release, the master branch should not be considered stable. The 2.x branch is used to merge in changes from any ongoing development in the v2 line of development.

If you are interested in contributing, please fork the central repository, make changes, and issue a pull request. We may change the process along the way, but for now, developers with access to the subversion trunk will be able to push to the central git repository. We welcome your contributions and thank you for helping us work toward OpenLayers 3.

Something went wrong with that request. Please try again.