Page History

...

1. RVM (http://rvm.io/)
2. Homebrew (http://brew.sh/)
3. Qt (brew install qt)
4. git (from Xcode developer tools)

Obtaining Code

...

Earthdata Search has been open sourced and is available at https://

...

github.com/nasa/earthdata

...

-search.

If you are a developer on the EDSC dev team, you will need to see your team leader to request the appropriate accounts and permissions to be added to the NASA Github account. Once that is done you'll be added to the EDSC project and can clone the repo.

...

If you are an external contributor, please fork the EDSC repo from https://

...

github.com/nasa/earthdata-search.

Running Code

Start by updating the project:

...

JIRA Project: https://bugs.earthdata.nasa.gov/browse/EDSC.earthdata.nasa.gov/browse/EDSC

Github site: https://github.com/nasa/earthdata-search

Git Stash site: https://git.earthdata.nasa.gov/projects/EDSC

...

• Stand-ups occur daily at 10:00 AM. (877) 847-0013,8518026#
• Sprint planning meetings occur as part of the EED2 SAFe efforts. Typically on the first day of each sprint.
• Retrospectives and sprint overviews take place on the Friday before the start of the sprint.
• Developers should use NASA Jabber EOSDIS Slack accounts for chat and join the Jabber group chat edsc@conference.im.nasa.gov. Developers use Messages or Screen Hero for remote screen sharing#edsc-dev channel for team communication. See your team lead for an invitation to the channel.

Contact the project lead for up-to-date meeting invitations.

...

Changes to shared environments must be deployed through Bamboo via the Earthdata Search deployment project. Any successful build of the master branch will result in a deployment to the EDSC SIT environment (https://search.sit.earthdata.nasa.gov).

Development Style Guide

Introduction and Concepts

...

When building the interface, use the History API to ensure that history entries are pushed to the stack appropriately. Push entries to the stack when the user reaches points they would reasonably expect to bookmark. Avoid pushing entries so frequently that backing out of a state using the back button becomes tedious or impossible.