Evaluating Person or Team: Anastasia Github: anastasiasoenjoto
- Project description:
Blockly is a library that helps us code by using visual blocks. The library essentially adds an editor that allows us to add puzzle like blocks representing what we want our code to do. For example if want to create a loop, we choose a loop puzzle block and pick the type of loop (while, until, etc) and it also allows us to modify other factors such as variable name, etc. Once we place these blocks in our editor it will create the code according to the language of choice. The purpose of this project is to allow users to implement programming concepts without having to worry about syntax for different languages. Since it is a library, it is used for developers to integrate to their web or mobile app (mostly educational). Some of the users of Blockly include, App Inventor, Microsoft MakeCode, etc.
-
Project website/homepage: https://developers.google.com/blockly/
-
Project repository: https://github.com/google/blockly
- What is the project's license?
Apache License 2.0
-
What is the primary programming language in the project?
The primary programming language in the project is JavaScript (92.9%).
-
What is the development environment?
It is a library that gets used with web and mobile (deprecated) applications, so we just need a text editor.
-
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 there are instructions for how to download and use Blockly within another project on their website. They provide images, some code samples and clear instructions that make it easy to follow.
-
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?
I don't think there are external additional software modules.
-
Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.
Looking at the appengine directory (redirect.html) I think their code is not so hard to understand, there are many comments that explain what that code does which makes it easy to follow, however since it is a large project it might be a little difficult to follow.
-
Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub.
It seems like it is a big project with 144K lines of code.
-
Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?
This repository has a folder for tests. It is stated that after adding code contributors should run existing unit tests and also consider writing more. The project also allows for contributions to improve test coverage, so people can contribute by writing tests.
-
Is there clear documentation in the code itself?
Yes throughout the code there are comments explaining what the code does.
-
Is there documentation about the design?
I don't think there is a design documentation for this project.
-
How many commits have been made in the past week?
There has not been any commits since Feb 3, 2020.
-
When was the most recent commit?
The most recent commit was on Feb 3, 2020.
-
How many issues are currently open?
There are 405 issues that are open.
-
How long do issues stay open?
They stay open at an average of 10 days (newer issues were resolved faster old issue took longer to resolve).
-
Read the conversations from some open and some closed issues. Is there active discussion on the issues?
Yes, for some of the closed issues that I read there are conversations about how to best solve the issue, etc.
-
Are issues tagged as easy, hard, for beginners, etc.?
No, they are tagged as the type of fix that is wanted, which feature it involves, etc.
-
How many issues were closed in the past six months?
Around 150.
-
Is there information about how many people are maintaining the project?
According to their GitHub there are around 127 contributors.
-
How many contributors has the project had in the past six months?
Between October 2019 - March 2020 there are 27 contributors.
-
How many open pull requests are there?
27 open pull requests.
-
Do pull requests remain un-answered for a long time?
No it takes an average of 1 day to get pull requests to be merged.
-
Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?
Yes there is active discussion on the pull requests.
-
How many pull requests were opened within the past six months?
Around 375.
-
When was the last pull request merged?
5 days ago.
-
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 there is a contributing file, its easy to read and understand but not so thorough. Their contribution document on their website has more information.
-
Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?
No I couldn't find a code of conduct document on their repository.
-
Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.
Yes they are generally constructive and they respond quickly.
-
Are people friendly in the issues, discussion forum, and chat?
Yes they all generally seem friendly .
-
Do maintainers thank people for their contributions?
No they don't.
Install the development environment for the project on your system. Describe the process that you needed to follow:
-
how involved was the process?
Following the steps that were outlined on the website, I had to get the code then create an html document that calls the different scripts all of which were outline clearly on their website.
-
how long it take you?
Not long, around 20 minutes.
-
did you need to install additional packages or libraries?
No.
-
were you able to build the code following the instructions?
Yes I was although at first I ran into some problems and wouldn't get the blocks to display.
-
did you need to look for additional help in installing the environment?
No their documentation was thorough.
-
any other comments?
The code samples on their website were helpful.
-
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?
I don't think its possible to contribute to this project in the course of a few weeks since this is a large project and there are a lot of different parts of the project that needs to be read through and understood.
-
Would you be interested in contributing to this particular project?
Yes I am interested in contributing to this project seeing as its a project that I myself see using. Even though I haven't personally used it myself, while I was playing around with the project I found it quite useful. In the long run this is definitely a project that I would want to contribute to.