WIP - Stub out core module

[pohh]

This request is to stub out the core functionality required by an android module which would be shared between the various deployed apps.

At present this set is limited to the wear module (to be completed in another pull), and the app.

The workflow I was thinking was as core functionality is required by features in the wear app, they would be moved from the current onebusaway-android module into the core module to keep the core module as lightweight as possible.

[pohh]

@barbeau would like feedback on:

• package structure
• package name
• module name

[barbeau]

@pohh Thanks! I agree that as functionality is required it should be moved to the core module to avoid unnecessary complexity in the core.

For file system structure, how about:

• /core (as proposed here)
• /wear
• /app (currently "onebusaway-android")

In the current version of Android Studio the default subdirectory for Android apps is "/app" - early beta versions mirrored the "onebusaway-android" project name (IIRC when importing from Eclipse). So, I'm fine with renaming the main app directory if that aids in simplifying the organization/naming conversions. Git should allow retaining history over file moves (although Github history viewer currently does not).

I'll comment inline for the other items.

[barbeau]

This looks good to me.

[barbeau]

This PR was automatically closed by Github due to the deletion of the develop branch - we're moving back to using master as the main branch.

@pohh Is this still something you're interested in working on? Just trying to get a handle of how this PR might look going forward - whether I need to pull into a branch to preserve the initial work for someone else to look at, or whether you want to rebase on master and continue work.