Evaluating Person or Team:
Anastasia Riawan Soenjoto - anastasiasoenjoto
-
Project description:
This project is a React UI framework that helps to render React components to make it look nicer without the hassle of styling it. This project is used by any web developers that use React. Its useful because styling different elements like buttons, list, etc is made so much easier with it. For example with buttons if we were to style it without material ui we would need alot of style rules to make it look nice, but with material ui we can define a button and the type of button we want.
-
Project website/homepage: https://material-ui.com/
-
Project repository: https://github.com/mui-org/material-ui
- What is the project's license?
MIT License
-
What is the primary programming language in the project? Javascript (96.9%)
-
What is the development environment?
Any text editor will work.
-
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 instructions in their github repository and on their website. It was fairly easy to find since its in their readme file and on their website I didnt need to scroll that much. It seems clear and 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?
Material-UI is used within a web application, but it doesnt require any additional software modules to use. -
Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.
I think the code is quite easy to understand, although the code was lacking comments. -
Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub.
Yes it is a big project, it has 178K lines of code.
-
Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?
Yes the repository has tests and code contributors are expected to write tests for newly added code.
-
Is there clear documentation in the code itself?
No there isnt much comments on the code itself. -
Is there documentation about the design?
No I dont think there are specific documentations about the design.
-
How many commits have been made in the past week?
63 commits. -
When was the most recent commit?
Mar 5 2020 -
How many issues are currently open?
353 issues. -
How long do issues stay open?
Around 1 day.
-
Read the conversations from some open and some closed issues. Is there active discussion on the issues?
Yes there are active discussion on the issues, and they reply fairly quick. -
Are issues tagged as easy, hard, for beginners, etc.?
They have a tag 'good first issue' for beginners to take on. -
How many issues were closed in the past six months?
Around 925 issues. -
Is there information about how many people are maintaining the project?
There are 1675 contributors to this project. -
How many contributors has the project had in the past six months?
24 contributors in the past six months. -
How many open pull requests are there?
23 open pull requests. -
Do pull requests remain un-answered for a long time?
No, most of the pull requests are merged the same day that they were opened.
-
Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?
Yes there are, most of the discussions were on why the person who opened the pull request decided to implement it the way they did and suggestions on how to improve their code. -
How many pull requests were opened within the past six months?
1119 that were closed and 23 that are still open so 1142 in total. -
When was the last pull request merged?
14 hours 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 document on their github repository. It seemes easy to read and understand and it is very thorough, they provide code samples on how to create pull requests, the coding style, etc. -
Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?
Yes there is a code of conduct document. They mentioned that the project maintainers will remove, edit, reject any comments or commits or code or other contributions that violate the code of conduct, they will also either permanently or temporarily ban contributors that present inappropriate behavior.
-
Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.
Yes everybody responds helpfully to questions, they will help if a person has misunderstood something, and they respond fairly quick. -
Are people friendly in the issues, discussion forum, and chat?
Yes everybody is friendly and replies really quickly in discussions. -
Do maintainers thank people for their contributions?
Yes for some of the pull requests that have been merged they do thank people for their contributions.
Install the development environment for the project on your system. Describe the process that you needed to follow:
-
how involved was the process?
It was fairly easy, all I needed to do was follow the instructions on the readme file, I just need to npm install and I could use it already. -
how long it take you?
Less than 15 minutes. -
did you need to install additional packages or libraries?
No. -
were you able to build the code following the instructions?
Yes I was. -
did you need to look for additional help in installing the environment?
No the documentation on the repository was enough. -
any other comments?
Their documentations are very thorough.
-
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 think this project would be possible to contribute to, they have tagged several issues where they thought was easy for beginners to do. Moreover it seems that the people are very helpful when it comes to answering questions.
-
Would you be interested in contributing to this particular project?
Yes I would be interested in contributing to this project because I have used this in my projects before and have found it useful. Moreover since most of the project is done in Javascript I think that understanding the code wont be as hard compared to projects that are written in other languages.