Skip to content

Commit

Permalink
First commit
Browse files Browse the repository at this point in the history
  • Loading branch information
gwens committed Nov 30, 2016
0 parents commit a54722c
Show file tree
Hide file tree
Showing 19 changed files with 102 additions and 0 deletions.
1 change: 1 addition & 0 deletions .gitattributes
@@ -0,0 +1 @@
*.zip filter=lfs diff=lfs merge=lfs -text
3 changes: 3 additions & 0 deletions 9781430248996/Beg Game Dev with Unity 4.x Assets2-6.zip
Git LFS file not shown
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 07.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 08.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 09.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 10.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 11.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 12.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 13.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 14.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 15.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 16.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 17.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 18.zip
Git LFS file not shown
3 changes: 3 additions & 0 deletions 9781430248996/Chapter 19.zip
Git LFS file not shown
27 changes: 27 additions & 0 deletions LICENSE.txt
@@ -0,0 +1,27 @@
Freeware License, some rights reserved

Copyright (c) 2013 Sue Blackman

Permission is hereby granted, free of charge, to anyone obtaining a copy
of this software and associated documentation files (the "Software"),
to work with the Software within the limits of freeware distribution and fair use.
This includes the rights to use, copy, and modify the Software for personal use.
Users are also allowed and encouraged to submit corrections and modifications
to the Software for the benefit of other users.

It is not allowed to reuse, modify, or redistribute the Software for
commercial use in any way, or for a user�s educational materials such as books
or blog articles without prior permission from the copyright holder.

The above copyright notice and this permission notice need to be included
in all copies or substantial portions of the software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS OR APRESS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.


15 changes: 15 additions & 0 deletions README.md
@@ -0,0 +1,15 @@
#Apress Source Code

This repository accompanies [*Beginning 3D Game Development with Unity 4*](http://www.apress.com/9781430248996) by Sue Blackman (Apress, 2013).

![Cover image](9781430248996.jpg)

Download the files as a zip using the green button, or clone the repository to your machine using Git.

##Releases

Release v1.0 corresponds to the code in the published book, without corrections or updates.

##Contributions

See the file Contributing.md for more information on how you can contribute to this repository.
14 changes: 14 additions & 0 deletions contributing.md
@@ -0,0 +1,14 @@
# Contributing to Apress Source Code

Copyright for Apress source code belongs to the author(s). However, under fair use you are encouraged to fork and contribute minor corrections and updates for the benefit of the author(s) and other readers.

## How to Contribute

1. Make sure you have a GitHub account.
2. Fork the repository for the relevant book.
3. Create a new branch on which to make your change, e.g.
`git checkout -b my_code_contribution`
4. Commit your change. Include a commit message describing the correction. Please note that if your commit message is not clear, the correction will not be accepted.
5. Submit a pull request.

Thank you for your contribution!

0 comments on commit a54722c

Please sign in to comment.