BananaSpace

A (Craft)Bukkit plugin that generates spaceworlds and offers many features to make survival in space lots of fun.

BukkitDev link: BananaSpace on dev.bukkit.org

Authors

Bolded authors are currently active.

iffa - original creator (empty chunk generator, helmets, suits, etc)

kitskub - collaborator, active guy making commits

Canis85 - planet generation, /space back etc

BR - ceiling checking code

License

                BANANACODE PUBLIC LICENSE
                  Version 1, July 2011

Copyright (C) 2011 Ben L. nightgunner5@llamaslayers.net

Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed.

                BANANACODE PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. Any binary distribution of this software or software derived from this software must be accompanied by source code. For example, this can be a link to a GIT repository, the inclusion of source code in the JAR, or a "source code" link on the same page as a "download" link.
1. This license may not be removed from projects directly or indirectly derived from a project containing this license, unless it is replaced with a newer version of the BANANACODE PUBLIC LICENSE.
2. All JavaDoc @author tags must be retained when java code is copied from a file containing such tags. You may add your name in an additional @author tag, but not change the contents of existing @author tags.
3. Releasing this software and claiming you are the original author is a violation of this license. Any such violations will be dealt with by one or more of the following: Murder, pulling your toenails out in slow motion, politely asking you to stop, stealing your first born, and/or legal action.

Coding and Pull Request Conventions

• We generally follow the Sun/Oracle coding standards.
• No tabs; use 4 spaces instead.
• No trailing whitespaces.
• Organize imports properly.
• If you make major changes to a class, add an author-tag for you.
• No 80 column limit or midstatement newlines (usually).
• No fucking ugly Eclipse formatting (unless you have modified it to actually look good).
• Proper javadoc for each method added/changed to describe what it does.
• The number of commits in a pull request should be kept to a minimum (squish them into one most of the time - use common sense!).
• No merges should be included in pull requests unless the pull request's purpose is a merge.
• Pull requests should be tested (does it compile? AND does it work?) before submission.

Follow the above conventions if you want your pull requests accepted.