Skip to content

Latest commit

 

History

History
225 lines (130 loc) · 6.68 KB

Gatsby_evalutaion_02.md

File metadata and controls

225 lines (130 loc) · 6.68 KB

Project Name: GatsbyJS

Evaluating Person or Team: Sijia (sm7515)


Project Data

  1. Project description:

    Gatsby is a blazing fast modern site generator for React. It is a free and open source framework based on React that helps developers build websites and apps.

  2. Project website/homepage:

    gatsbyjs.org

  3. Project repository:

    gatsby

License

  1. What is the project's license?
    MIT

Code Base

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

    JavaScript 93.6%; TypeScript 2.8%;

  2. What is the development environment?

    you need to use npm to install Gatsby CLI, so node.js.

  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?

    There are step by step instructions for you to set up everything and get your first gatsby project running, very easy to find and follow.

  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?

    No. You only need to install Gatsby CLI.

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

    Yes. The code is easy to understand, especially if you know javascript and typescript.

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

    172K lines of code. It is a large project.

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

    Yes, the repo has a test folder and contributors are expected to write reproducible test cases.

Code and Design Documentation

  1. Is there clear documentation in the code itself?

    Yes.

  2. Is there documentation about the design?

    Yes. Docs on Design

Activity Level

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

  2. When was the most recent commit?

    Mar 6, 2020

  3. How many issues are currently open?

    602

  4. How long do issues stay open?

    usually within 1 or 2 days.

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

    Yes.

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

    Yes, for example, there are good first issue tag and Hacktoberfest tag.

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

    1866

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

    The about page on their website lists the core contributors

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

    97

  10. How many open pull requests are there?

    142

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

    No, they are usually closed within one or two days.

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

    Yes.

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

    128 open, 2533 closed

  14. When was the last pull request merged?

    Mar 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, it is easy to follow along.

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

    Yes, and there are consequences for violating it.

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

    Yes.

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

    Yes.

  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?

    It is pretty easy to install.

  2. how long it take you?

    a couple of minutes.

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

    No, since I already have node installed.

  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?

    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?

    Yes. I think the community is helpful and responsive. They welcome people to contribute and have beginner friendly tickets. They also have good and detailed documentations so it would be easy to learn and troubleshoot issues.

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

    Yes, because I am interested in web development and have done a couple of react project before, so I am familiar with writing Javascript code and reading typescript code. It would be relatively easy for to start becuase I can understand the code base better.