Evaluating Person or Team: David, Flydx1234
-
Project description:
Open Food Facts is a food products database. It basically contains information on foods from all around the world and allows anyone to add more foods to their database. Currently there are 1,173,440 products in the database. I would imagine that their userbase contains people from all over the world, broadly encompassing as it is simply a search engine for food. -
Project website/homepage: https://world.openfoodfacts.org/
-
Project repository: https://github.com/openfoodfacts/openfoodfacts-server
- What is the project's license?
The project's license is the: GNU AFFERO GENERAL PUBLIC LICENSE.
-
What is the primary programming language in the project? The primary programing language in the repository I have chosen is HTML.
-
What is the development environment?
This is an online website that uses Project Opener ran on Docker for its server. -
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 instructions on how to install are pretty easy to find, as they have a wiki as well with all the information that is needed. They seem easy enough 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?
The project depends on many external libraries: zbar, imagemagick, graphviz, tesseract, installation instructions for these are clear. It also depends on many pearl modules as well as MongoDb to run, installation instructions for the pearl modules is clear, but as for MongoDb, all it states is to install it. They also use an Apache web server that also has some config instructions, but it seems there is nothing about how to install or run it. -
Is the code easy to understand? Browse some source code files and make a judgment based on your random sample.
I think most of the HTML code is easy to understand, and there are comments as well. -
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 pretty big, and has over 553 thousand lines of code. -
Does the repository have tests? If so, are the code contributors expected to write tests for newly added code?
The repository has tests, although there are no expectations for code contributors to write tests for newly added code.
- Is there clear documentation in the code itself?
The HTML code seems pretty self explanatory and is documented. Other code files such as the JavaScript seem to contain links to documentation. - Is there documentation about the design?
They have a wiki with documentation about their design.
-
How many commits have been made in the past week?
Over 35 commits have been made in the past week. -
When was the most recent commit?
At the time, 3/2/2020 3:00 PM, the most recent commit was 6 hours ago one 3/2 9:00 AM. -
How many issues are currently open?
715 issues are currently open. -
How long do issues stay open?
Issues stay open for an average of 6.6 days.
-
Read the conversations from some open and some closed issues. Is there active discussion on the issues?
There exists active discussion on most of the issues. -
Are issues tagged as easy, hard, for beginners, etc.?
There are issue tags for "good first issue", but none for medium/hard. -
How many issues were closed in the past six months?
182 issues were closed in the past six months. -
Is there information about how many people are maintaining the project?
There are 53 contributors to the project. -
How many contributors has the project had in the past six months?
About 18 contributors have been active in the project in the past six months. -
How many open pull requests are there?
There are 32. -
Do pull requests remain un-answered for a long time?
No, the pull requests are usually merged in an average of 2 days. -
Read the conversations from some open and some closed pull requests. Is there active discussion on the pull requests?
The open pull requests have a great amount of conversation in them. While the closed ones do have conversations, many of them are brief. I assume that's why many of the pull requests are closed so fast. -
How many pull requests were opened within the past six months?
19 pull requests. -
When was the last pull request merged?
March 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.
There is a contributing document. It is pretty easy to understand. -
Is there a CODE OF CONDUCT document? Does it have consequences for acts that violate it?
There is a code of conduct, although it is an HTML document. Violators may be temporarily or permanently blocked. -
Do the maintainers respond helpfully to questions in issues? Are responses generally constructive? Read the issue conversations.
Although there are 53 contributors only a few actively respond to the issues. But the responses are genrally constructive. -
Are people friendly in the issues, discussion forum, and chat?
Yes. -
Do maintainers thank people for their contributions?
Yes.
Install the development environment for the project on your system. Describe the process that you needed to follow:
-
how involved was the process?
Initially the process was not really involved, most of it was following instructions on the website and waiting for modules to install. The hardest part, and the part that included the most involvement was setting up the Apache server, which required a lot more libraries and other downloads not listed in their guide in order to get running. There was also no real instructions on how to install apache itself, just how to configure it. Every time I ran ./configure, there would be another file/library that was missing that I had to install. -
how long it take you?
About 3 hours. -
did you need to install additional packages or libraries?
Installed cpan for perl to install the perl modules. Also had to install Apache Runtime and Apache Runtime Util. Also had to install PCRE library for perl, and zlib1g-dev. Had to install, libapr1-dev, and libgdbm-dev. -
were you able to build the code following the instructions?
I was not able to build the code following the instructions. The instructions for the apache server was unclear, and I ran into a lot of issues. After following all the instructions, I had no idea how to start the apache server, or their server product opener. Furthermore, due to lack of information for the apache installation, I am not sure if I did it correctly. -
did you need to look for additional help in installing the environment?
I had to search up how to install the packages for zbar and tesseract as the linux install name was not specifically listed. There was basically no install instructions for Apache, and I encountered a lot of issues that I had to search up. -
any other comments?
I did not know to install Apache from source, I installed it using the terminal command initially. Which resulted in me spending a lot of time trying to figure out what I did wrong. The wiki does say to install from source, but I wasn't aware of what that exactly meant since this is the first time I encountered the specific method of installation using ./configure.
-
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?
It's definitely possible for me to contribute to, as most of the code is written in HTML. I think that the environment setup is probably the hardest part. Furthermore their website design, at least in my opinion is pretty unrefined, and could be worked on. -
Would you be interested in contributing to this particular project?
I would be interested in contributing to the project, it's a pretty interesting search engine, and seems like one that many people can use to find nutrition facts about food. Also seems like a site that I would use as well.