Evaluating Person or Team:
Selamawit Moges
sm6957
-
Project description:
OpenRefine is a Java-based power tool that lets users load data, understand it, clean it up, reconcile it, and augment it with data coming from the web. -
Project website/homepage:
-
Project repository:
- What is the project's license?
Open refine is under the BSD liscence which means that users are able to use it commercially and privately, modify it, and distribute it.
-
What is the primary programming language in the project?
Java, javascript, Shell, CSS, and HTML -
What is the development environment?
Unix/Linux or Windows -
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?
The instructions are very easy to follow and even come with videos, FAQs, and a Wiki page. They also provided a developers guide which has a roadmap that provides a big picture of the project. -
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?
Developers will need to install Java JDK and Apache Maven. -
Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.
Since I am fairly familiar with Java, the code seems fairly easy to understand. Although there were minimal to no comments, the variable names are discriptive enough to follow what the code is trying to accomplish. -
Is this a big project? If you can, find out about how many lines of code are in it, perhaps on OpenHub.
OpenRefine is relatively large with 125 contributors and 127,000 lines of code. -
Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?
No, there are no test repositories
-
Is there clear documentation in the code itself?
There are very few comments in the code that relate to the functions/classes itself. Most of the comments are at the top describing the license that the code is under. -
Is there documentation about the design?
Under The Developers Guide and Architecture discusses the overall design of the code and the technology stack.
-
How many commits have been made in the past week?
There have been 34 commits this week. -
When was the most recent commit?
The most recent commit was two days ago. -
How many issues are currently open?
There are 423 issues open. -
How long do issues stay open?
Issues are open for about 6 days. -
Read the conversations from some open and some closed issues. Is there active discussion on the issues?
There is no active discussions but while the project was open, people were consistently talking and help each other debug problems. -
Are issues tagged as easy, hard, for beginners, etc.?
Most, if not all, issues are tagged. -
How many issues were closed in the past six months?
114 issues were closed in the last 6 months. -
Is there information about how many people are maintaining the project?
There are 54 current contributors -
How many contributors has the project had in the past six months?
There are 54 current contributors -
How many open pull requests are there?
There are 14 pull requests -
Do pull requests remain un-answered for a long time?
No, it takes less than a week for people to respond and commit the changes. -
Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?
There seem to be very active conversations and people also respond with encouraging comments. -
How many pull requests were opened within the past six months?
All of them -
When was the last pull request merged?
Two 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.
They have a Wiki page that is broken down into "How to Start", "Feature Areas", "Recipes and Worked Examples", "Expressions", "References", and "External Sites". Based on what I've seen in each category, they are fairly easy to read. -
Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?
Yes there is a code of conduct and those who do not follow it will be under investigation by the project maintainers. Repercussions are determined by project leadership on a case-by-case basis. -
Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.
Yes, they are constructive and many come with images/pictures attached to provide clarity. -
Are people friendly in the issues, discussion forum, and chat?
Absolutly, people seem to be a lot more receptive to newbies and provide positive, encouraging feedback. -
Do maintainers thank people for their contributions?
Yes! They also provide encouraging feedback and suggestions for the future.
Install the development environment for the project on your system. Describe the process that you needed to follow:
- how involved was the process?
It took a while to install everything correctly although the instructions were clear, it was a bit tedious. - how long it take you?
~30-45 minutes - did you need to install additional packages or libraries?
Yes, I needed to download JDK 8 and Apache Maven - were you able to build the code following the instructions?
Yes! - did you need to look for additional help in installing the environment?
No, the FAQs/ other peoples questions generally helped answer mine. - any other comments?
N/A
-
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 because they offer a lot of support, encouragement, and they have many issues labeled "good-first-issue". -
Would you be interested in contributing to this particular project?
Not really because I would want to contribute to an open source project that interests me or software that I use frequently