Skip to content

Latest commit

 

History

History
193 lines (102 loc) · 8.45 KB

uBlockOrigin_evaluation.md

File metadata and controls

193 lines (102 loc) · 8.45 KB

Project Evaluation Activity

Project Name:
uBlock Origin


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: Free and opensource content blockers (ads, coin miners, etc.)

How easy was it to find information about contributing on the website? If you scroll to the bottom, there is a text in small font that says "If you're interested in contributing to this project, please get in touch", along with a link to their email. Additionally, on the github repo there is a CONTRIBUTING.md

Contributing instructions: Here

URL for the code repository: Code repository

Bug/Issue tracker link: Bug/Issue tracker

Mailing list: Mailing list

Chat channel: Chat channel

Other communication channels:


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

License: License

Is it OSI approved license: Yes, it is the GNU GENERAL PUBLIC LICENSE Version 3

Programming Language: Some CSS (4.9%) and HTML (3.4%), but mostly javascript (88.4%)

URL for contributing instructions: Contributing instructions

Are the contributing instructions clear? Yes, they describe reporting issues, translation contributions, and more.

URL for code of conduct / community norms / community guildelines: Community Guidelines They don't quite have a code of conduct for the github, but they have a manifesto or a mission statement

URL for instructions for users to download and install the package: There are multiple ways to install this software User Builds. Development Builds.

Are these instructions clear? Do you think they would be easy to follow? Yes, very easy for users, simply a matter of adding an extension or add-on for the browser you prefer.

Number of contributors: 561 contributors

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

  1. [gorhill] (11,359 commits) - Their Latest Commit
  2. [Deathamns] (184 commits) - Their Latest Commit
  3. [chrisaljoudi] (138 commits) - Their Latest Commit

Number of commits: 12,082 commits

Latest commit [de]

  • link to the commit: Latest commit

  • who made that commit: gorhill, the project head made the last commit.

  • what type of work was commited? (was it a fix to a bug, implementation of a new feature, ...) It was an update of the version number for the Firefox build to auto update to

Issues

  • how many open issues are there: 114 Open Issues

    • url for the last issue created: Last issue created

    • how many users discuss the issue: 5 persons

    • when was the issue reported: 3/1/2024

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

    • url for the last issue closed: Last issue closed
    • how many users discussed the issue: 3 people
    • when was the issue reported: 3/2/2024
    • when was the issue closed: 3/2/2024
  • how active is the discussion on the issues: There is pretty active discussion, for example this issue opened a couple weeks ago has a lot of discussion. Additionally, items that are invalid or not worthy of discussion are quickly addressed and closed in a timely manner, for example, the second link below shows the discussion for an invalid issue, and you can see it was opened, addressed, and closed in the same day.

  • are there issues marked "good for newbies", "beginner" or some other indicators that imply that they are good for beginner contributors: There is a label marked "good first issues."

    • how many of such issues are there? 5 issues There are 5 issues, 2 open 3 closed.
    • look at a few of them, do they look beginner friendly? Yes, one of them looks not so beginner friendly, the other one seems to discuss a documentation clarification needed so that seems like a glld first issue
  • are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific): Yes, it is called 'wiki' label, however, there is only 1 issue within that tag.

    • how many of such issues are there? Only 1
    • look at a few of them, do you think you could submit a fix? I think so, this one is not only a 'wiki' label but also under the 'good first issue' label.

Pull requests

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

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

    • when was the last pull request made: [Last Pull Request created](Dec 17, 2023)

    • url for the oldest pull request created: Oldest Pull Request created

    • when was the oldest pull request made: [Last Pull Request created](Apr 21, 2016)

  • how many closed pull requests are there: 3,009 closed pull requests

    • 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: 3/1/2024

    • when was the pull request closed: 3/1/2024

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


Summary assesment

How friendly is this project for beginner contributors? Not extremely extremely friendly, however, it was surprisingly beginnger friendly and with the tags for wiki and good first issues, it looks like they are making an effort to improve beginner friendliness.

Do the maintainers respond helpfully to questions in issues? Sometimes they can be a little brisk if you bring up an issue that has either been disucssed before or perhaps a comment that makes it clear you did not configure your build properly or read the README. Otherwise, the maintainers respond helpfully, critically, and quickly.

Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)? Similar vibe to discussion on github, if you properly report an issue (include your platform, what build, etc.), then people will answer seriously, if you do not, people will ask you to somewhat briskly.

Do pull requests get reviewed? Yes

Do maintainers thank people for their contributions? For the ones I looked at, generally no. The closest thing I saw was a "looks good."

Are there special skills required to contribute to the project? If so, what are they? JavaScript is very helpful since it is a browser extension, similarly, HTML and CSS knowledge also helpful but not as important.

Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they? Very loose ones, this project supports Firefox, Chromium, Thunderbird and Node.js for its development build.