Skip to content

Home

Jump to bottom
William French edited this page Aug 6, 2014 · 33 revisions

Also visit http://join.chronozoomproject.org for project information.

Developer "Pebbles":

A ChronoZoom Developer Pebble is a well formed description of an enhancement to ChronoZoom in support of an existing or future feature that the community would like to see.

To make a Pebble, you need to put together information in a new bug here on Github that will allow a first time developer to dig right in. You can assume generally available documentation on getting started with Visual Studio and ChronoZoom.

To 'move' a pebble, a developer will get the ChronoZoom code, implement the change, test it and submit a pull request.

Please include the following information in the bug:

Title: "Pebble: Here is the name of my new Pebble"

Description:

  • Describe the purpose and desired outcome of implementing this Pebble
  • Reference the ChronoZoom feature(s) which this Pebble supports or extends
  • Describing any applicable design patterns, necessary resources or suggested approach (mini spec)

The process for Pebbles are as follows:

  1. Before a Pebble is approved and labeled, it is reviewed by respected peers in the ChronoZoom developer community. There would essentially be comments on the “Pebble-Prop” marked bug that suggests improvements, or comments to the effect of "go for it!"
  2. Once a Pebble is approved, it awards one Pebble of credit to the author who must be a Github contributor
  3. Once a Pebble has been ‘moved’ after an integrated pull request, it awards one Pebble of credit to the implementer.
Clone this wiki locally