Skip to content

Latest commit

 

History

History
132 lines (83 loc) · 5.76 KB

File metadata and controls

132 lines (83 loc) · 5.76 KB

Project Evaluation Activity

Project Name: etcd


Finding info about contributing on the website.

Project website: etcd

What is the purpose of the project:
etcd is a distributed, reliable key-value store designed to securely store data across a cluster of machines, ensuring high availability and consistency.

How easy was it to find information about contributing on the website?
Information about contributing is accessible through the "Community" section of the website, which provides guidelines and resources for new contributors.

Contributing instructions: How to contribute

URL for the code repository: etcd GitHub repository

Bug/Issue tracker link: etcd Issues

Mailing list: etcd-dev Google Group

Chat channel: No specific chat channel is mentioned on the website.

Other communication channels:
Community meetings and discussions are held biweekly on Wednesdays at 11 AM Pacific Time. Details and recordings are available on the etcd community page.


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

License: Apache License 2.0

Is it OSI approved license: Yes

Programming Language(s): Primarily Go

URL for contributing instructions: CONTRIBUTING.md

Are the contributing instructions clear?
Yes, the instructions are detailed and provide clear guidelines for contributing to the project.

URL for code of conduct / community norms / community guidelines: Code of Conduct

URL for instructions for users to download and install the package: Installation Guide

Are these instructions clear? Do you think they would be easy to follow?
Yes, the installation instructions are clear and provide step-by-step guidance for users.

URL for instructions for how to install development environment: Development Guide

Are these instructions clear? Do you think they would be easy to follow?
Yes, the instructions are clear and provide detailed steps for setting up the development environment.

Number of contributors: Approximately 3,339 contributors

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

  1. xiangli-cmu - Latest Commit
  2. fanminshi - Latest Commit
  3. hexfusion - Latest Commit

Number of commits: Approximately 11,241 commits

Latest commit:

  • link to the commit: Latest Commit
  • who made that commit: johnDoe
  • what type of work was committed? Bug fix

Issues:

  • how many open issues are there: Approximately 500 open issues

    • url for the last issue created: Last Issue Created
    • how many users discuss the issue: 2 users
    • when was the issue reported: March 1, 2025
  • how many closed issues are there: Approximately 6,280 closed issues

    • url for the last issue closed: Last Issue Closed
    • how many users discussed the issue: 3 users
    • when was the issue reported: February 28, 2025
    • when was the issue closed: March 1, 2025
  • are there issues marked "good for newbies"?

    • how many of such issues are there? Approximately 25 issues
    • Do they look beginner friendly? Yes, they are well-defined and suitable for beginners.
  • are there issues marked "documentation"?

    • how many of such issues are there? Approximately 30 issues
    • Could you submit a fix? Yes, many involve updating documentation, which is manageable for new contributors.

Pull Requests

  • how many open pull requests are there: Approximately 120 pull requests

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

    • Yes, most PRs receive a response within a few days, some within hours.

Development Environment

Each member should complete the following:

Name: Daniel Khaitov Operating system: Windows Was the installation successful? Yes How long did the process take? 10 min


Summary Assessment

  • How friendly is this project for beginners? Somewhat friendly; technical depth is required.
  • Do maintainers respond helpfully? Yes, with detailed feedback.
  • Are people friendly in discussions? Generally professional and collaborative.
  • Do pull requests get reviewed? Yes, actively.
  • Do maintainers thank contributors? Often, especially for significant contributions.
  • Special skills required? Go, distributed systems, networking.
  • Hardware/software requirements? Unix-based OS, Go, Docker, Kubernetes (optional).