Skip to content

Latest commit

 

History

History
204 lines (111 loc) · 5.69 KB

LibreOffice_evaluation_2.md

File metadata and controls

204 lines (111 loc) · 5.69 KB
Raw

Project Name: LibreOffice

Evaluating Person or Team:

Prince (@PrinceCarter)

Project Data

  1. Project description:

    Do more - easier, quicker, smarter. LibreOffice is a free and powerful office suite, and a successor to OpenOffice.org (commonly known as OpenOffice). Its clean interface and feature-rich tools help you unleash your creativity and enhance your 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++

  2. What is the development environment?

    It varies depending on machine.

  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?

    There is a developer guide. It is 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?

    For Mac, XCode is required. For Windows, Visual Studio is required. For Linux, there are many other dependencies.

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

    It is relatively easy 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.

    ~10M line of code.

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

    Yuh and yuh.

Code and Design Documentation

  1. Is there clear documentation in the code itself?

    Yuh.

  2. Is there documentation about the design?

    Yuh.

Activity Level

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

    264

  2. When was the most recent commit?

    ~1 hour ago

  3. How many issues are currently open?

    Unsure.

  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 is.

  6. Are issues tagged as easy, hard, for beginners, etc.?

    No difficulty rating, only issue "size".

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

    Unsure.

  8. Is there information about how many people are maintaining the project?

    I cannot tell, but from what I see, alot.

  9. How many contributors has the project had in the past six months?

    I cannot tell, but from what I see, alot.

  10. How many open pull requests are there?

    ~400

  11. Do pull requests remain un-answered for a long time?

    The average wait time for a pull request is ~5 hours.

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

    Yuh.

  13. How many pull requests were opened within the past six months?

    10,000+

  14. When was the last pull request merged?

    ~1 hour 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.

    From what I see, it is very clear and easy to understand.

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

    From what I see, nah.

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

    From what I see, responses are generally helpful and constructive.

  4. Are people friendly in the issues, discussion forum, and chat?

    From what I see, yes.

  5. Do maintainers thank people for their contributions?

    From what I see, 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?

    Not very involved. It is like downloading any other development environment.

  2. how long it take you?

    ~5 mins

  3. Did you need to install additional packages or libraries?

    Nah.

  4. Were you able to build the code following the instructions?

    Yuh.

  5. Did you need to look for additional help in installing the environment?

    Nah.

  6. Any other comments?

    Nah.

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?

    This is very large project and seems very intimidating in terms of contribution. I think although the code languages is familiar to me, it would take me a while to figure out what I would want to contribute and how to even contribute. I would have to learn how most of the software is pieced together and then finally start thinking of feature addition and then FINALLY implement that feature, which I would think would take much longer than the end of the semester.

  2. Would you be interested in contributing to this particular project?

    Not really interested in the project. Although it sounds like a cool and useful project, I want to work on a project that I actually use (or would use).