Project Documentation

[SpaceManiac]

List of things I want to get done to document Glowstone as a project. For code documentation (javadocs), see #96.

Encouraging contributions:

• [x] Friendly "How to help" page: Code, documentation, wiki, testing
• [x] CONTRIBUTING.md file
• [x] Code style and PR handling wiki pages

Administrative stuff

• [ ] New logo that isn't Mojang assets
• [ ] More formal IRC rules (if needed?)
• [ ] A decent roadmap, covering which issues are considered "priority"
  • See "Important Stuff" milestone.

Random meta

• [ ] API coverage scripts, maybe?
• [ ] Distill // todo comments onto github?
• [ ] Setting up the test server to auto-update
• [x] Closing of issues that are old and/or non-useful

[mastercoms]

I made a new "how to help" page. https://github.com/GlowstoneMC/Glowstone/wiki/How-to-Help

[valleydev]

Can someone please help me setting up eclipse for debug the project? There are many references missing ...

[PaulBGD]

@valleydev before building this project you should probably read the main file to find that this project is dead.

[aramperes]

@valleydev @PaulBGD ... and that the project has moved to a new repository.