Skip to content

Latest commit

 

History

History
229 lines (130 loc) · 8.16 KB

blender_evaluation_01.md

File metadata and controls

229 lines (130 loc) · 8.16 KB
Raw

Blender:

Evaluating Person or Team:

Mark @markflaherty

Project Data

  1. Project description: 
Free and open source 3D creation suite.

  1. Project website/homepage:

    https://www.blender.org/

  2. Project repository:

    https://github.com/blender

License

  1. What is the project's license? 
GNU Public License, Version 3

Code Base

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

    C

  2. What is the development environment?

    They have dev enviroments for mac and windows, they recommend using Xcode or or VScode. The IDE needs to support CMake.

  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?

    They have extensive instructions on how to do each of these. The instructions are very step by step and give CL commands for you to copy and paste into your commandline.

  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?

    It is dependent upon having CMake on your machine. The external libraries are included in the downloading of blender itself (as per the download instructions).

  5. Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.

    The codebase is very extensive and takes a good amount of knowledge of image rending to understand. There are files with hundreds of MACRO's being used so I think it would take a beginner like me a solid amount of time to get a grasp on it.

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

    The project is massive, based off of openhub, there are 2.13M lines of code.

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

    The project does have a tests repository, however, the development page does not specify whether or not contributors are expected to write tests for the code they have written. They ask that you speak with an already established contributor when developing for the first time.

Code and Design Documentation

  1. Is there clear documentation in the code itself?

    Documentation is not very clear, things are outlined, but code is not explained.

  2. Is there documentation about the design?

    Somewhat, they point to very specific things, but general design tactics are added at the top of most of the files that I looked at.

Activity Level

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

    167 to master, 317 to all branches

  2. When was the most recent commit?

    4 hours ago to master. (1:30pm 3/3/20 ET)

  3. How many issues are currently open?

    I do not see any issues on their github. Issues are reported at https://developer.blender.org/.

  4. How long do issues stay open?

    Anywhere ranging from a couple hours to a week depending on size of issue. Most I found were solved same day, but a couple took a week.

  5. Read the conversations from some open and some closed issues. Is there active discussion on the issues?

    Yes, they have a whole forum dedicated to resolving the issues where contributors can comment on posts.

  6. Are issues tagged as easy, hard, for beginners, etc.?

    No, they are not tagged in such a fashion, but there are "User projects" where people have identified if they are beginners.

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

    The developer forum does not have an analytics page for this statistic, but off the sheer number of issues and resolutions I bet it is very high.

  8. Is there information about how many people are maintaining the project?

    The forum is extremly indepth where they have tabs for design forums and bug forums alike, in total they have 25 forums.

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

    64

  10. How many open pull requests are there?

    0, they use the developers forum.

  11. Do pull requests remain un-answered for a long time?

    I cannot tell, but the issues are resolved very quickly

  12. Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?

    Since they use a developers forum it is very open to all conversation and debate on the bugs.

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

    I cannot find this because their pull request tab is empty, I know that 64 people have pushed to master in the past month thus assuming that they must have had to merge them.

  14. When was the last pull request merged?

    I know that 64 people have pushed to master in the past month thus assuming that they must have had to merge them.

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.

    It is on their website. It is very clear cut.

  2. Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?

    There is code of conduct on both their developer forum. They do not have consequences, but they do seem to be pretty clear about how their community is built and it would bad if you broke their code of conduct.

  3. Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.

    Yes, extensively.

  4. Are people friendly in the issues, discussion forum, and chat?

    Very much so!

  5. Do maintainers thank people for their contributions?

    In the forums 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?

    The process was very easy. Since it is very clearly outlined

  2. how long it take you?

    No more than a half an hour.

  3. did you need to install additional packages or libraries?

    I already have CMAke on my machine so no.

  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?

    No.

  6. any other comments?

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?

    No, I definetly feel as if their code base is too large for me to make a meaningful contribution by the end of the semester. If it wasn't so extensive and I have had previous expierence in rending software then it could be possible.

  2. Would you be interested in contributing to this particular project?

    I have used blender in the past, and I like what they stand for. However, I am not very interested in working with rendering software and feel as if there is a high barrier to entry given my current skillset.