Skip to content

Latest commit

 

History

History
162 lines (98 loc) · 5.39 KB

LibreOffice_evaluation.md

File metadata and controls

162 lines (98 loc) · 5.39 KB

Project Name: LibreOffice

Evaluating Person or Team: Eva evading1998

Project Data

  1. Project description:
    LibreOffice is a successor to OpenOffice. It includes different applications, such as word processing, spreadsheets, presentations, etc. It is used by people all over the world to enhance productivity.

  2. Project website/homepage: https://www.libreoffice.org/

  3. Project repository: https://cgit.freedesktop.org/libreoffice

License

  1. What is the project's license?
    Mozilla Public License v2.0 

Code Base

  1. What is the primary programming language in the project? c++, XML, Java

  2. What is the development environment?
    Not-sure: It has many development environments, including Linux, Windows, macOS, Android...

  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?
    Yes, there is a developer's guide on the website. They are clear and informative, hence relatively easy to 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?
    On Mac, it is required to download Xcode, and the instructions are clearly listed. There is a list of building dependencies for Linux, with the downloading instructions clearly listed. Visual Studio is required on Windows machines.

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

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

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

Code and Design Documentation

  1. Is there clear documentation in the code itself?
    Yes.

  2. Is there documentation about the design?
    Yes, there is.

Activity Level

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

  2. When was the most recent commit?
    6 hours ago

  3. How many issues are currently open?

  4. How long do issues stay open?

  5. Read the conversations from some open and some closed issues. Is there active discussion on the issues?
    Yes, there are around 7-8 conversation lines per issue.

  6. Are issues tagged as easy, hard, for beginners, etc.?
    No, none of the issues are tagged with regards to difficulties. There is a column called size with (XS S M L XL) referring to the issue size.

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

  8. Is there information about how many people are maintaining the project?
    There is no accurate number, but there are lots of maintainers

  9. How many contributors has the project had in the past six months?
    There is no accurate number, but there are lots of contributors

  10. How many open pull requests are there?
    350

  11. Do pull requests remain un-answered for a long time?
    There are very few old pull requests from even over 5 years ago. But the normal pull requests are answered very fast. Average: 1 day (3-4 hours to be exact)

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

  13. How many pull requests were opened within the past six months?
    More than 10,000.

  14. When was the last pull request merged?
    5 hours ago

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 very clear

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

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

  4. Are people friendly in the issues, discussion forum, and chat?
    Could not tell, they are pretty formal

  5. Do maintainers thank people for their contributions?
    Not really

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?
    The guidelines are very clear. I only needed to download Xcode as a Mac user, but I already have it installed.

  2. how long it take you?
    Less than 5 minutes

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

  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?

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?
    In terms of code, the langauges are familiar to us. However, the entire structure of the project is very intricate, it will require some time to get to know where to start. The community responds pretty quickly, so when help is needed, the responds can be found quickly.

  2. Would you be interested in contributing to this particular project?
    I think the project is very useful and interesting. However it does not overlap with my interest area.