Skip to content

Latest commit

 

History

History
194 lines (130 loc) · 6.96 KB

godot_evaluation.md

File metadata and controls

194 lines (130 loc) · 6.96 KB

Project Name: godot

Evaluating Person or Team: Thomas / tk2487


Project Data

  1. Project description:
    A free 2D/3D cross-platform game engine made for game developers.
  1. Project website/homepage:
    https://godotengine.org/

  2. Project repository:
    https://github.com/godotengine/godot

License

  1. What is the project's license?
    MIT License

Code Base

  1. What is the primary programming language in the project?
    C++

  2. What is the development environment?
    Anything that can run and compile C++ and Scons files.

  3. Are there instructions for how to download, build, and install? How easy is it to find them? Do they seem easy (relatively speaking) to follow?
    Yes, they have a docs page setup that shows how to compile for each platform. Everything is detailed step by step and easy to find.

  4. Does the project depend on external additional software modules such as database, graphics, web development, or other libraries? If so, are there clear instructions on how to install those?
    Yes, they have instructions for installations on the same page as the setup guide.

  5. Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.
    Code is neatly written but barely any comments to explain the code so it's hard to understand what's going on unless you are somewhat knowledgable about the project.

  6. Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub.
    From OpenHub, it says there are 1.2 million lines of code.

  7. Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?
    Yes, there are tests but contributors are not expected to write any.

Code and Design Documentation

  1. Is there clear documentation in the code itself?
    Barely any documentation. Maybe small descriptions for a line here and there but no overall explanation of the code.

  2. Is there documentation about the design?
    Yes, they have a whole section in the docs page about design.

Activity Level

  1. How many commits have been made in the past week?
    116 commits in the past week.

  2. When was the most recent commit?
    March 6, 2020.

  3. How many issues are currently open?
    5,544 issues currently open.

  4. How long do issues stay open?
    Average is around 1 hour.

  5. Read the conversations from some open and some closed issues. Is there active discussion on the issues?
    Yes, there is extensive discussion on most issues.

  6. Are issues tagged as easy, hard, for beginners, etc.?
    No, but there is a tag called "junior job" which I assume is meant for easy issues.

  7. How many issues were closed in the past six months?
    2280 issues were closed in the past six months.

  8. Is there information about how many people are maintaining the project?
    On their github page it shows that there are 1092 contributors to the project.

  9. How many contributors has the project had in the past six months?
    52 contributors in the past six months.

  10. How many open pull requests are there?
    606 open pull requests.

  11. Do pull requests remain un-answered for a long time?
    No, most pull requests are answered within 1 day (usually 1-5 hours).

  12. Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?
    No, most of the activity is just approving pull requests.

  13. How many pull requests were opened within the past six months?
    2283 pull requests were opened within the past six months.

  14. When was the last pull request merged?
    March 6, 2020.

Welcomeness and Community

  1. Is there a CONTRIBUTING document? If so, how easy to read and understand is it? Look through it and see if it is clear and thorough.
    Yes, the document details each way to contribute and the steps to do them.

  2. Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?
    Yes, the consequence for violation is 'exclusion from the community in the form of a ban from one or all platforms.'

  3. Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.
    Yes, everyone gets to the point and responds concisely.

  4. Are people friendly in the issues, discussion forum, and chat?
    People are polite, but not exactly friendly.

  5. Do maintainers thank people for their contributions?
    Yes.

Development Environment Installation

Install the development environment for the project on your system. Describe the process that you needed to follow:

  1. How involved was the process?
    Simple as the instructions are super clear.

  2. How long it take you?
    ~3 minutes.

  3. Did you need to install additional packages or libraries?
    Yes (Scons).

  4. Were you able to build the code following the instructions?
    Yes.

  5. Did you need to look for additional help in installing the environment?
    Yes, but it was a minor error.

  6. Any other comments?
    No.

Summary

  1. Do you think this is a project to which it would be possible to contribute in the course of a few weeks before the end of this semester?
    As of now, probably not. Only because I have no knowledge of the code base so far but I am interested in this project and wouldn't mind attempting to learn it. If not, then I can always stick to documentation contributions in this project.

  2. Would you be interested in contributing to this particular project?
    Yes, as stated before I would probably stick with documentation instead of actual code unless there is some elementary issues that don't require extensive knowledge of the code base.