<commit_before># BikeBinder for Free Ride

## Objective

Reproduce all functionality that exists with the current paper binder system.


## Getting up and running

### Afther the first clone
Take the following actions to get a cloned/pulled version to run locally

* rename "config/database.yml.sample" to "config/database.yml"
* run "bundle install"
* run "rake db:populate"

### After each time you pull updates

* Run "bundle install"
* run "rake db:populate"

## Running tests

* run "rake db:test_setup"
* "bundle exec guard"

(See http://guides.rubyonrails.org/testing.html#preparing-your-application-for-testing)

--------------------------------------------

## Feature Scope

In order to get a functional prototype running, we need to adhere to a limit scope. We can add features later. If a feature is desired, but not in scope, it can be added to the outside scope list.

### Original Scope

* Bike info sheet: Location, Characteristic (Size, mfg, model, color), Notes, Value, Departure & Arrival Dates
* Youth projects sheet: Program name, State (Active/inactive)
* Bike location tracking: Hook associations to bikes

### Complete Features

* Bike info sheet: Location, Some characteristic, Notes, Departure Dates
* Youth projects sheet: Program name, State (Active/inactive), Inspection
* Bike location tracking: Hook associations to bikes
* Bike state
* Safety inspection
* Project progress

### Remaining scope

* Bike info sheet: Characteristic (Size, mfg, model, color), Value, Arrival Date
* Hook: hook lookup

### Additional work

* Youth Project: repair log
* User permissions
* Searching & filtering: bikes, hooks, projects
* Bike demographics (replacing hand-typed characteristics with suggestions or other databased backed data entry)


## UI Considerations
While we do not have an official guideline for the UI, I want feedback and suggestions to go here. I will start listing ideas and notes I have about what will keep our interface uncluttered and what will make it intuitive and easy to use.

### UI Todos
-standardize visual elements to represent different interactions with the bike binder.
eg, a blue underline link represents a Navigational action such as going to the Bikes index page.
-rounded buttons represent actions that have to to with creating and editing data 
	  eg, The Submit Note, Create New Bike buttons represent instantiating new comment or bike objects
-use icons effectively. We want them to help guide the user experience and not act only as eye candy.
     eg, a blue, underlined anchor may represent an action that manipulates data, so an icon can cue the user of the extra option. See one in use on the single bike overview page.
-sensible color scheme. Bootstrap is too minimalist. 


### Future inspirations
-visual diagrams/photos demonstrating bike measurement jargon?
-display the bike color when rendering a bike view
- bike/freeride branding elements? bike with wings logo faded in background of header on certain pages?


# Copywrite

(c) 2012 Free Ride Bicycle Project, See license for details






<commit_msg>project milestones<commit_after># BikeBinder for Free Ride

## Objective

Reproduce all functionality that exists with the current paper bike binder and departed bikes binder system.


## Getting up and running

### Afther the first clone
Take the following actions to get a cloned/pulled version to run locally

* rename "config/database.yml.sample" to "config/database.yml"
* run "bundle install"
* run "rake db:populate"

### After each time you pull updates

* Run "bundle install"
* run "rake db:populate"

## Running tests

* run "rake db:test_setup"
* "bundle exec guard"

(See http://guides.rubyonrails.org/testing.html#preparing-your-application-for-testing)

--------------------------------------------

## Feature Scope

In order to get a functional prototype running, we need to adhere to a limit scope. We can add features later. If a feature is desired, but not in scope, it can be added to the outside scope list.

### Scope for Milestone 1

* Bike info sheet: Location, Characteristic (Size, mfg, model, color), Notes, Value, Departure & Arrival Dates
* Youth projects sheet: Program name, State (Active/inactive)
* Bike location tracking: Hook associations to bikes

### Complete Features

* Bike info sheet: Location, Some characteristic, Notes, Departure Dates
* Youth projects sheet: Program name, State (Active/inactive), Inspection
* Bike location tracking: Hook associations to bikes
* Bike state
* Safety inspection
* Project progress
* Youth Project: repair log
* Hook: hook lookup

### Remaining features

* Bike info sheet: Characteristic (Size, mfg, model, color), Value, Arrival Date


### Features for future milestones

* User permissions
* Searching & filtering: bikes, hooks, projects
* Bike demographics (replacing hand-typed characteristics with suggestions or other databased backed data entry)


## UI Considerations
While we do not have an official guideline for the UI, I want feedback and suggestions to go here. I will start listing ideas and notes I have about what will keep our interface uncluttered and what will make it intuitive and easy to use.

### UI Todos
-standardize visual elements to represent different interactions with the bike binder.
eg, a blue underline link represents a Navigational action such as going to the Bikes index page.
-rounded buttons represent actions that have to to with creating and editing data 
	  eg, The Submit Note, Create New Bike buttons represent instantiating new comment or bike objects
-use icons effectively. We want them to help guide the user experience and not act only as eye candy.
     eg, a blue, underlined anchor may represent an action that manipulates data, so an icon can cue the user of the extra option. See one in use on the single bike overview page.
-sensible color scheme. Bootstrap is too minimalist. 


### Future inspirations
-visual diagrams/photos demonstrating bike measurement jargon?
-display the bike color when rendering a bike view
- bike/freeride branding elements? bike with wings logo faded in background of header on certain pages?

--------------------------------------------

# Project Milestones

## Mileston 1: Youth project implementation to be fully functional

* All of the necessary features and interations to be able to successfully user the application for youth  projects.

## Milestone 2: Searching/Sorting and User roles and authorization

* UI elements to search the site
* Ability to sort filter and get basic reports for bikes and projects
** Bike demographic data implemented to assist with searching/sorting/filtering
* Mechanism implemented to provide user roles
* Locks in place to require different role based authorization
** Roles and authorization to allow application to go live without risk to data being corrupt

# Milestone 3: All project types implemented and fully functional

* Youth, Earn-a-bike, Fix-for-sale, Scrap, As-is purchases
* Inspections customized for each project
* Role based authorization for each project type as needed

# Milestone 4: Deployment and support infrastructure

* Site is live and in-use
* Infrastructure support for
** Back-ups and restore
** Monitoring & notifying system status
** Admin functionality to fix problems/take care of unexpected issues



# Copywrite

(c) 2012 Free Ride Bicycle Project, See license for details







{'fraction_non_alphanumeric': 0.07411414660535569, 'fraction_numerical': 0.0017581823099810658, 'mean_word_length': 4.135416666666667, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2705255', 'n_tokens_mistral': 1920, 'n_tokens_neox': 1791, 'n_words': 1004}