Project Name: Jellyfin
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: Jellyfin
What is the purpose of the project: Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached. Your media, your server, your way.
How easy was it to find information about contributing on the website? Very easy.
Contributing instructions: Here
URL for the code repository: JellyFin Github
Bug/Issue tracker link: Bug/Issue tracker
Mailing list: Mailing list
Chat channel: Chat channel
Other communication channels: Contacts
License: License
Is it OSI approved license: Yes.
Programming Language(s): C# and Javascript, also uses Python, Brightscript, Java/Kotlin
URL for contributing instructions: Contributing instructions
Are the contributing instructions clear? Yes, they're very detailed.
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? They're very clear. Seems straightforward.
URL for instructions for how to install development environment: here
Are these instruction clear? Do you think they would be easy to follow? Yes
Number of contributors: 249 contributors
Usernames of three contributors with largest number of commits; for each of them list the link to their latest commit:
- [LukePulverenti] (13424 commits) - Their Latest Commit
- [Bond-009] (2433 commits) - Their Latest Commit
- [crobibero] (1549 commits) - Their Latest Commit
Number of commits: 25389 commits
Latest commit
-
link to the commit: Latest commit
-
who made that commit: crobibero
-
what type of work was commited? It was a feature change that stores lyrics into a database.
Issues
-
how many open issues are there: 432 Open Issues
-
url for the last issue created: Last issue created
-
how many users discuss the issue: 1 person
-
when was the issue reported: Feb 26, 2024
-
-
how many closed issues are there: 5069 closed issues
- url for the last issue closed: Last issue closed
- how many users discussed the issue: 1 people
- when was the issue reported: Feb 24, 2024
- when was the issue closed: Feb 25, 2024
-
how active is the discussion on the issues: Depending on the issue, there could be a lot of discussion. Typically, however, most issues have 0-1 comments.
-
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, they are marked "good-first-issue".
-
how many of such issues are there? 5 issues
-
look at a few of them, do they look beginner friendly? Some of them seem decently easy.
-
-
are there issues marked "documentation" or some other indicators that imply that they are documentation (user or developer specific): They have a different repository for their documentation upkeep. Link.
-
how many of such issues are there? 23
-
look at a few of them, do you think you could submit a fix? No, doesn't seem like good issues for us to fix.
-
Pull requests
-
how many open pull requests are there: 77 pull requests
-
url for the last pull request created: Last Pull Request created
-
when was the last pull request made: Feb 26, 2024
-
url for the oldest pull request created: Oldest Pull Request created
-
when was the oldest pull request made: 2021
-
-
how many closed pull requests are there: 4520
-
url for the last pull request closed: Last Pull Request closed
-
how many users discussed the pull request: 1 users
-
when was the pull request made: Feb 25, 2024
-
when was the pull request closed: Feb 25, 2024
-
-
do maintainers respond quickly to pull requests when they are opened? They respond pretty fast, within 1-5 days.
Each member of your group should attempt to configure the development environment for this project. Complete the following for each member:
Name: Allyson
Operating system: Windows 10
Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) It was successful, there were some hiccups that involved me trying different combinations of the various methods of installation Jellyfin wrote in their README.md and closely inspecting console logs for any errors that may be causing issues. This project required a lot of prerequisite software to be installed outside of the usual Node.js/.Net/etc., such as FFMPEG and the Jellyfin web server.
How long did the whole process take? About an hour.
Name: Julissa
Operating system: macOS
Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) It was successful in the end, however, there were a lot of redos, my teammates helping me, and searching online. The good part was that there were different methods to use for the installation but not all worked on my computer. The installation of DotNote that they mentioned did not work for me, instead, I had to use Brew. There were a lot of steps to follow that made a bit confusing, and I had to recheck my steps to see if I had everything set up and downloaded. There were a couple of times that I forgot to download a prerequisite.
How long did the whole process take? Two hours
Name: Johan
Operating system: macOS
Was the installation successful? (if not, explain what went wrong and what you did to try to remedy it) The installation was successful after a long process of re-reading the documentation and trying different options to start the server. Jellyfin gave a lot of details on different ways to set up the project but it was always missing small tiny details in some given options which caused me to continue searching for more details before going on to the next option. Also, there were many dependencies required for the project which all had their own long instructions which tired me out from reading. I was easily able to have the project installed using one method but then I worked longer to figure out a different method which seemed more practical as it combined the client with the server automatically. I also used my previous knowledge of node to help me debug some errors I recieved when building the client and the server.
How long did the whole process take? An hour and a half
How friendly is this project for beginner contributors?
About average, the project is pretty big and if a user isn't super familiar with the functionality of the project, it could be difficult to get started. Depending on the level of experience a beginner contributor has with full-stack, it could be more or less difficult.
Do the maintainers respond helpfully to questions in issues? They respond quickly and often, the project is very active and has a lot of contributors.
Are people friendly in the issues, discussion forum, and chat (for example, IRC or Slack)?
People are friendly and try to be helpful, there is a Code Of Conduct and maintainers try to enforce good behavior.
Do pull requests get reviewed?
Pull Requests do get reviewed.
Do maintainers thank people for their contributions? Not particularily.
Are there special skills required to contribute to the project? If so, what are they? Nothing special, but maybe more experience with web development.
Are there any special hardware/software requirements to be able to contribute to the project? If so, what are they? No special hardware. There are a lot of prerequisites to download like Node.js, FFMPEG, etc.