-
Notifications
You must be signed in to change notification settings - Fork 127
Dev_About Developer Pebbles
William French edited this page Aug 7, 2014
·
1 revision
Also visit http://join.chronozoomproject.org for project information.
A ChronoZoom Developer Pebble or ‘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.
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)
- 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!"
- Once a Pebble is approved, it awards one Pebble of credit to the author who must be a Github contributor
- Once a Pebble has been ‘moved’ after an integrated pull request, it awards one Pebble of credit to the implementer.