Description
Contribute with Code
If you are looking for a code change to work on, then checkout the open issues or look for a new feature or task on the unoffical roadmap. Specifically the items labelled as Good First Issue should be good options for beginners.
Another great place to check for easy tasks to get started with is the list of code smells on SonarCloud. Some of these are more complex, but others are as simple as removing code that has been commented out or removing an unused variable. The list can be filtered for a specific Rule in the left pane. In most cases, it probably makes sense to make a separate PR per rule fixed. When possible add an eslint rule to prevent future issues of the same type.
If you have any questions or encounter any development issues, feel free to reach out via chat in one of our development chat rooms. Details can be found on the Contact page.
Adding new features
- Complex features or changes to core functionality should start as discussions on the meta repo with a general implementation plan. Sign off on the planned implementation by the Jellyfin team should be given before opening a PR. This ensures the implementation follows best practices and falls inline with team goals.
- New code should use the target architecture when possible: TypeScript, Jellyfin TypeScript SDK, TanStack Query, and React.
- Additionally the Dashboard and Experimental app should use the MUI component library.
Other Ways to Contribute
- Triage open issues by testing to see if an issue can be reproduced and comment with your findings.
- Test and review open PRs and leave comments with your findings.
- Specifically any issues tagged with the needs testing label could use additional help with testing.
- Contribute to translations.
Activity