Skip to content

Latest commit

 

History

History
203 lines (91 loc) · 8.14 KB

File metadata and controls

203 lines (91 loc) · 8.14 KB

Project Evaluation Activity

Project Name: cryptomator

By: Polina Belova


Finding info about contributing on the website.

In the following section you should only enter the information that you found on the project website. Some of the answers will be impossible to find, others may be very hard to find. Do not google for answers.

Project website: Website

What is the purpose of the project: "Cryptomator is a simple tool for digital self-defense. It allows you to protect your cloud data by yourself and independently. Cryptomator secures and encrypts your sensitive data in your favorite cloud service. So you can rest assured that only you can access your data."

How easy was it to find information about contributing on the website? Relatively easy: at the very bottom of the site, there is a CONTRIBUTE section with the link to their GitHub, how to donate, and translate. No direct link to the contributing instructions.

Contributing instructions: Here

URL for the code repository: Code repository

Bug/Issue tracker link: Bug/Issue tracker

Mailing list: N/A

Chat channel: N/A

Other communication channels:

GitHub Discussions

Cryptomator Community


Finding info at the project repository and bug/issue tracker.

License: License

Is it OSI approved license: Yes

Programming Language(s): Java, CSS, FreeMarker

URL for contributing instructions: Contributing instructions

Are the contributing instructions clear? Yes, short and clear + they alsready have automatic templates for Issues and PRs that the contributor's required to use.

URL for code of conduct / community norms / community guildelines: Community Guidelines

URL for instructions for users to download and install the package: here.

Are these instructions clear? Do you think they would be easy to follow? Yes, they even have a separate first timer guide on how to get started.

URL for instructions for how to install development environment: here

Are these instruction clear? Do you think they would be easy to follow? Yes, it's very descriptive

Number of contributors: 62 contributors

Usernames of three contributors with largest number of commits; for each of them list the link to their latest commit:

  1. overheadhunter (2,004 commits) - Their Latest Commit
  2. infeo (1,127 commits) - Their Latest Commit
  3. tobihagemann (298 commits) - Their Latest Commit

Number of commits: 5,607 commits

Latest commit

  • link to the commit: Latest commit

  • who made that commit: infeo

  • what type of work was commited? (was it a fix to a bug, implementation of a new feature, ...) Switching between models: from 20.04 to 22.04 for building the deb package.

Issues

  • how many open issues are there: 251 Open Issues

    • url for the last issue created: Last issue created

    • how many users discuss the issue: 2 person

    • when was the issue reported: 02/28/2025

  • how many closed issues are there: 2,009 closed issues

    • url for the last issue closed: Last issue closed
    • how many users discussed the issue: 1 person
    • when was the issue reported: 2/26/2025 by core contributor
    • when was the issue closed: 2/26/2025 closed by the same core contributor
  • how active is the discussion on the issues: Almost every issue gets comments from core contributors so I would say pretty active

  • are there issues marked "good for newbies", "beginner" or some other indicators that imply that they are good for beginner contributors: Yes, marked as good first issue

    • how many of such issues are there? 19 issues

    • look at a few of them, do they look beginner friendly? Yes and No: some ask to fix typos and quick feature add-ons, while others are more field-focused, a lot about dealing with vaults

  • are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific): Yes, marked as type:documentation

    • how many of such issues are there? 0 issues

    • look at a few of them, do you think you could submit a fix? N/A

Pull requests

  • how many open pull requests are there: 12 pull requests

  • how many closed pull requests are there: 588

    • url for the last pull request closed: Last Pull Request closed

    • how many users discussed the pull request: 2 users

    • when was the pull request made: 02/26/2025

    • when was the pull request closed: 02/28/2025

  • do maintainers respond quickly to pull requests when they are opened? YES!

Development Environment

Each member of your group should attempt to configure the development environemnt for this project. Complete the following for each member:

Name: Polina Belova

Operating system: MacOS

Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) Yes!

How long did the whole process take? 4 min


Summary assesment

How friendly is this project for beginner contributors? I would say 7.5/10 friendly level.

Do the maintainers respond helpfully to questions in issues? Yes, always with some feedabck that will either solve the issue or help solving it.

Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)? No one says hello and the converations are very strict, dry and to the point, but they do respond very frequently.

Do pull requests get reviewed? Yes

Do maintainers thank people for their contributions? No

Are there special skills required to contribute to the project? If so, what are they? Basic understansing of Cloud Storages, how to future-proof vaults, and an understanding of what is a vault.

Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they? None