Initial commit

Author: cfilipov

.gitignore

@@ -0,0 +1,223 @@
+#########################
+# .gitignore file for Xcode 7 Source Projects
+# can be used for watchOS, tvOS, iOS, OSX, Swift development
+#
+# February 2016
+#
+# Save this file as .gitignore in your repository's working directly.
+# Note: Don't confuse the working directory with the .git directory. It will not work if you put it there.
+#
+#####
+# OS X temporary files that should never be committed
+#
+# c.f. http://www.westwind.com/reference/os-x/invisibles.html
+
+.DS_Store
+
+# c.f. http://www.westwind.com/reference/os-x/invisibles.html
+
+.Trashes
+
+# c.f. http://www.westwind.com/reference/os-x/invisibles.html
+
+*.swp
+
+#
+# *.lock - this is used and abused by many editors for many different things.
+#    For the main ones I use (e.g. Eclipse), it should be excluded 
+#    from source-control, but YMMV.
+#   (lock files are usually local-only file-synchronization on the local FS that should NOT go in git)
+# c.f. the "OPTIONAL" section at bottom though, for tool-specific variations!
+#
+# In particular, if you're using CocoaPods, you'll want to comment-out this line:
+#*.lock
+
+
+#
+# profile - REMOVED temporarily (on double-checking, I can't find it in OS X docs?)
+#profile
+
+
+####
+# Xcode temporary files that should never be committed
+# 
+# NB: NIB/XIB files still exist even on Storyboard projects, so we want this...
+
+*~.nib
+
+
+####
+# Xcode build files -
+#
+# NB: slash on the end, so we only remove the FOLDER, not any files that were badly named "DerivedData"
+
+#DerivedData/
+
+# NB: slash on the end, so we only remove the FOLDER, not any files that were badly named "build"
+
+#build/
+
+
+#####
+# Xcode private settings (window sizes, bookmarks, breakpoints, custom executables, smart groups)
+#
+# This is complicated:
+#
+# SOMETIMES you need to put this file in version control.
+# Apple designed it poorly - if you use "custom executables", they are
+#  saved in this file.
+# 99% of projects do NOT use those, so they do NOT want to version control this file.
+#  ..but if you're in the 1%, comment out the line "*.pbxuser"
+
+# .pbxuser: http://lists.apple.com/archives/xcode-users/2004/Jan/msg00193.html
+
+*.pbxuser
+
+# .mode1v3: http://lists.apple.com/archives/xcode-users/2007/Oct/msg00465.html
+
+*.mode1v3
+
+# .mode2v3: http://lists.apple.com/archives/xcode-users/2007/Oct/msg00465.html
+
+*.mode2v3
+
+# .perspectivev3: http://stackoverflow.com/questions/5223297/xcode-projects-what-is-a-perspectivev3-file
+
+*.perspectivev3
+
+#    NB: also, whitelist the default ones, some projects need to use these
+#!default.pbxuser
+#!default.mode1v3
+#!default.mode2v3
+#!default.perspectivev3
+
+
+####
+# Xcode 4 - semi-personal settings
+#
+# Apple Shared data that Apple put in the wrong folder
+# c.f. http://stackoverflow.com/a/19260712/153422
+#     FROM ANSWER: Apple says "don't ignore it"
+#     FROM COMMENTS: Apple is wrong; Apple code is too buggy to trust; there are no known negative side-effects to ignoring Apple's unofficial advice and instead doing the thing that actively fixes bugs in Xcode
+# Up to you, but ... current advice: ignore it.
+*.xccheckout
+
+#
+#
+# OPTION 1: ---------------------------------
+#     throw away ALL personal settings (including custom schemes!
+#     - unless they are "shared")
+# As per build/ and DerivedData/, this ought to have a trailing slash
+#
+# NB: this is exclusive with OPTION 2 below
+#xcuserdata/
+
+# OPTION 2: ---------------------------------
+#     get rid of ALL personal settings, but KEEP SOME OF THEM
+#     - NB: you must manually uncomment the bits you want to keep
+#
+# NB: this *requires* git v1.8.2 or above; you may need to upgrade to latest OS X,
+#    or manually install git over the top of the OS X version
+# NB: this is exclusive with OPTION 1 above
+#
+#xcuserdata/**/*
+
+#     (requires option 2 above): Personal Schemes
+#
+#!xcuserdata/**/xcschemes/*
+
+####
+# XCode 4 workspaces - more detailed
+#
+# Workspaces are important! They are a core feature of Xcode - don't exclude them :)
+#
+# Workspace layout is quite spammy. For reference:
+#
+# /(root)/
+#   /(project-name).xcodeproj/
+#     project.pbxproj
+#     /project.xcworkspace/
+#       contents.xcworkspacedata
+#       /xcuserdata/
+#         /(your name)/xcuserdatad/
+#           UserInterfaceState.xcuserstate
+#     /xcshareddata/
+#       /xcschemes/
+#         (shared scheme name).xcscheme
+#     /xcuserdata/
+#       /(your name)/xcuserdatad/
+#         (private scheme).xcscheme
+#         xcschememanagement.plist
+#
+#
+
+####
+# Xcode 4 - Deprecated classes
+#
+# Allegedly, if you manually "deprecate" your classes, they get moved here.
+#
+# We're using source-control, so this is a "feature" that we do not want!
+
+#*.moved-aside
+
+####
+# OPTIONAL: Some well-known tools that people use side-by-side with Xcode / iOS development
+#
+# NB: I'd rather not include these here, but gitignore's design is weak and doesn't allow
+#     modular gitignore: you have to put EVERYTHING in one file.
+#
+# COCOAPODS:
+#
+# c.f. http://guides.cocoapods.org/using/using-cocoapods.html#what-is-a-podfilelock
+# c.f. http://guides.cocoapods.org/using/using-cocoapods.html#should-i-ignore-the-pods-directory-in-source-control
+#
+#!Podfile.lock
+#
+# RUBY:
+#
+# c.f. http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
+#
+#!Gemfile.lock
+#
+# IDEA:
+#
+# c.f. https://www.jetbrains.com/objc/help/managing-projects-under-version-control.html?search=workspace.xml
+# 
+#.idea/workspace.xml
+#
+# TEXTMATE:
+#
+# -- UNVERIFIED: c.f. http://stackoverflow.com/a/50283/153422
+#
+#tm_build_errors
+
+# Swift Package Manager
+#
+# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
+# Packages/
+.build/
+
+# CocoaPods
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# Pods/
+
+# Carthage
+#
+# Add this line if you want to avoid checking in source code from Carthage dependencies.
+# Carthage/Checkouts
+
+Carthage/Build
+
+# fastlane
+#
+# It is recommended to not store the screenshots in the git repo. Instead, use fastlane to re-generate the 
+# screenshots whenever they are needed.
+# For more information about the recommended setup visit:
+# https://github.com/fastlane/fastlane/blob/master/docs/Gitignore.md
+
+fastlane/report.xml
+fastlane/screenshots

CHANGELOG.md

@@ -0,0 +1,22 @@
+# Copyright Assignment Agreement for Open Source Project: Cristian Filipov
+
+You agree, understand, and state that:
+
+1. The term "Assigned Contributions" means the all contributions made to the specified Open Source project, in the case of computer code, automatically include the code in both binary and source forms, and any documentation and other files that accompany the code.
+
+2. You have received good and valuable consideration, and you agree to assign and do assign to Cristian Filipov your ownership of copyright in the Assigned Contributions, for the full duration thereof, and for any renewals or extensions thereof. To any extent that this assignment is ineffective, you grant to Cristian Filipov a nonexclusive, royalty-free, no-charge, worldwide, irrevocable and perpetual right to use, modify, and distribute the Assigned
+Contributions as it wishes.
+
+3. You will execute any documents and perform any acts Cristian Filipov requests to implement the letter and spirit of this agreement, except that you are not required to do anything that would impose an unreasonable time or cost burden on you.
+
+4. Cristian Filipov grants back to you a non-exclusive, royalty-free, no-charge, worldwide, irrevocable and perpetual right to use, modify, and distribute the Assigned Contributions as you wish.
+
+5. Cristian Filipov will make the Assigned Contributions available under an agreement approved by the OSI (Open Source Initiative), and may also make the Assigned Contributions available under other license terms.
+
+6. You will not assert any patent that is necessarily infringed by exercising copyright rights in the Assigned Contributions against anyone who receives the Assigned Contributions under an agreement approved by the OSI.
+
+7. You have the legal right to make this copyright assignment.
+
+8. If your employer(s) or others (“Third Parties”) generally have rights to some intellectual property that you create, you have permission to make this copyright assignment on behalf of such Third Parties, the Third Parties have waived such rights, or the Third Parties have no such rights with respect to the Assigned Contributions.
+
+9. Except for the statements you have made in this agreement, you provide the Assigned Contributions on an “AS-IS” basis, with all faults, defects, and errors, and without express or implied warranties of any kind, including any implied warranties of merchantability, fitness for a particular purpose, and non-infringement

CLA.md

@@ -0,0 +1,25 @@
+# Contributing
+
+By contributing to Muscle Book, you agree to [assign copyright of any contribution back to the project](COPYRIGHT.md) under the [nominated license](LICENSE.md) (AGPL). We are open to, and grateful for, any contributions made by the community.
+
+## How to contribute
+
+Contributions to Muscle Book are very welcome. Please read the [Non-Goals section of the README](README.md#non-goals) before spending any considerable effort on a pull request.
+
+## What to Contribute
+
+Take a look at the [issues page](https://github.com/cfilipov/MuscleBook/labels/help%20wanted) to see if there's anything you can help with. Contributions don't have to be limited to what's in the issues, but if you don't know where to start this should give you an idea.
+
+## Non-Technical Contributions
+
+Don't shy away from contributing just because you can't program. In fact, I believe the most valuable contributions at this point are non-technical in nature. There's more to this project than just code. Here is a list of at least a few non-technical areas where contributions are highly welcome (also have a look at the [issues page](https://github.com/cfilipov/MuscleBook/labels/help%20wanted) page):
+
+* Iconography
+* Exercise illustrations
+* Exercises (copy, accuracy verification, metadata)
+* Documentation (README file, instructions, help info)
+* Corrections (is an exercise improperly defined? Spelling error in the UI? Did I get the math wrong somewhere?)
+* Math (lots of calculations everywhere, suggest new ones or identify areas where the math is done incorrectly)
+* Exercise Science   
+	* Share research papers that might be relevant to the app. Point out areas that might go against established research.
+* UX and design advice