Chapter 1
Introduction
TODO: explain the purpose of your project
*TestingPleaseIgnore2* is a __________ that _______.
TODO: explain why your project is important
TestingPleaseIgnore2 is exciting because:
- It lets you _______.
- Its core contains less than __________ lines of code.
- It _______.
TODO: explain why your project is better than its competitors
These features distinguish TestingPleaseIgnore2 from the competition:
1.1 Logistics
- Release notes — history of project releases.
- Source code — obtain via Git or browse online.
- API reference — documentation for source code.
To get help or provide feedback, simply contact the author(s).
Version numbers
TestingPleaseIgnore2 releases are numbered in major.minor.patch form according to the RubyGems rational versioning policy, which can be summarized thus:
What increased in the version number? | The increase indicates that the release: | ||
Is backward compatible? | Has new features? | Has bug fixes? | |
---|---|---|---|
major | No | Yes | Yes |
minor | Yes | Yes | Yes |
patch | Yes | No | Yes |
1.2 License
Copyright 2009 Your Name your@email.here
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Chapter 2
Setup
2.2 Installation
You can install TestingPleaseIgnore2 by running this command:
gem install testing_please_ignore2
To check whether the installation was sucessful, run this command:
testing_please_ignore2 --version
If the installation was successful, you will see output like this:
project: TestingPleaseIgnore2 version: 0.0.0 release: 2009-01-18 website: http://testing_please_ignore2.rubyforge.org install: /home/sun/tmp/testing_please_ignore2
If you do not see such output, you may ask the author(s) for help.
2.3 Manifest
You will see the following items inside TestingPleaseIgnore2’s installation directory, whose path you can determine by running this command:
testing_please_ignore2 --version
TODO: list important files your project provides here
-
bin/
- testing_please_ignore2 — the main TestingPleaseIgnore2 executable.
-
lib/
-
testing_please_ignore2.rb — the main TestingPleaseIgnore2 library.
-
testing_please_ignore2/
TODO: list sub-libraries your project provides here
-
-
doc/
-
api/ — API reference documentation.
-
index.erb — source of this user manual.
-
-
LICENSE — copyright notice and legal conditions.
Chapter 4
Usage
4.1 Command-line interface
When you run this command:
testing_please_ignore2 --help
You will see this output:
TestingPleaseIgnore2 - TODO: put a single line description of your project here. TODO: Explain the command-line usage of this program here. Usage: testing_please_ignore2 [Option...] Arg1 Arg2 Arg3... --manual, -m: Show the user manual --version, -v: Print version and exit --help, -h: Show this message
TODO: explain the command-line arguments
4.2 Ruby library interface
TODO: explain how to use your project’s Ruby library from inside another Ruby program or library
4.3 Tutorial
This tutorial shows how TestingPleaseIgnore2 is used to _______.
TODO: give examples for doing common tasks
TODO: explain how to do more (advanced) things
Chapter 5
History
TODO: put a brief history about your project here
TODO: put release notes for your project here – newest first, oldest last.
5.1 Version 0.0.0 (2009-01-18)
TODO: write a short summary of the changes in this release
This release changes _______, adds____, and fixes____.
Contributor kudos
TODO: list everyone who contributed to this release and what their contribution was
-
__________ contributed __________ which _______.
-
__________ fixed __________ which _______.
-
__________ added __________ which _______.
Incompatible changes
TODO: list all backward-incompatible changes in this release
-
__________ has been __________ to _______.
-
_______.
-
_______.