Project Name: Nuclear
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: Nuclear.js
What is the purpose of the project: The project provides a music player that gives users access to free songs without ads, tracking, or profiling.
How easy was it to find information about contributing on the website? Fairly easy their website is simple and straightfoward
Contributing instructions: Here
URL for the code repository: Code repository
Bug/Issue tracker link: Bug/Issue tracker
Mailing list: None
Chat channel: Chat channel
Other communication channels: https://discord.com/invite/JqPjKxE https://twitter.com/nuclear_player
License: License
Is it OSI approved license: Yes.
Programming Language(s): TypeScript, Javascript, SCSS, HTML
URL for contributing instructions: Contributing instructions
Are the contributing instructions clear? Yes, they are short and to the point.
URL for code of conduct / community norms / community guildelines: None
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 are very clear. Yes. they are easy to follow.
URL for instructions for how to install development environment: here
Are these instruction clear? Do you think they would be easy to follow? Yes, they are very clear compared to other project's instructions. I think they are easy enough for any cs student to follow.
Number of contributors: 174 contributors
Usernames of three contributors with largest number of commits; for each of them list the link to their latest commit:
- [Nukeop] (1592 commits) - Their Latest Commit
- [Trekiteasy] (126 commits) - Their Latest Commit
- [Haidang666] (112 commits) - Their Latest Commit
Number of commits: xxxx commits
Latest commit
-
link to the commit: Latest commit
-
who made that commit: nukeop
-
what type of work was commited? It was to fix an issue created to fix the bug of having a grey effect over the visualizer when in full screen.
Issues
-
how many open issues are there: 178 Open Issues
-
url for the last issue created: Last issue created
-
how many users discuss the issue: 2 person
-
when was the issue reported: 7 hours ago 3/3/24
-
-
how many closed issues are there: 660 closed issues
- url for the last issue closed: Last issue closed
- how many users discussed the issue: 2 people
- when was the issue reported: 2 weeks ago
- when was the issue closed: 2 weeks ago
-
how active is the discussion on the issues: Very little active discussion on this issue
-
example of a lot of good discussion: Good discussion
-
example of an issue that does not have much discussion: Not much discussion
-
-
are there issues marked "good for newbies", "beginner" or some other indicators that imply that they are good for beginner contributors: Yes
-
how many of such issues are there? 24 issues
-
look at a few of them, do they look beginner friendly? They do not look beginner friendly many are feature requests or large bug fixes.
-
-
are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific): No
-
how many of such issues are there? None
-
look at a few of them, do you think you could submit a fix? No
-
Pull requests
-
how many open pull requests are there: 9 pull requests
-
url for the last pull request created: Last Pull Request created
-
when was the last pull request made: Last Pull Request created 3 days ago
-
url for the oldest pull request created: Oldest Pull Request created
-
when was the oldest pull request made: Nov 1, 2023
-
-
how many closed pull requests are there: 656
-
url for the last pull request closed: Last Pull Request closed
-
how many users discussed the pull request: 10 users
-
when was the pull request made: 16 hours ago 3/3/2024
-
when was the pull request closed: 12 hours ago 3/3/2024
-
-
do maintainers respond quickly to pull requests when they are opened? Yes
Each member of your group should attempt to configure the development environemnt for this project. Complete the following for each member:
Name: Johan Gallardo
Operating system: MacOs
Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) Yes it was successful
How long did the whole process take? About 20 mins
How friendly is this project for beginner contributors? I think this project is fairly friendly for beginner contributors. The code itself is not beginner friendly I would say but the maintainers seem to be very helpful.
Do the maintainers respond helpfully to questions in issues? Yes, the main maintainer Nukeop seems to respond quickly to every question in an issue and offers useful insight.
Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)? Yes, there were all polite and coridial in the issue and discussion forum.
Do pull requests get reviewed?
Do maintainers thank people for their contributions? No, not really.
Are there special skills required to contribute to the project? If so, what are they? None.
Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they?
None.