There are always several ways you can contribute to make Jersey even better…
Issue reporting is central to open-source projects. If an issue is not reported,
we cannot fix it. Please report any bugs, feature, and/or improvement requests in our
Have a fix or a feature you'd like to share? Open an issue, if not opened
already, and link a gist containing your patch with details on what you're resolving
and how you've resolving it. Or simply open a new GitHub pull request.
Good documentation is an important aspect of any software project. We've
taken several strides in improving our documentation, but there's always room
for improvement. If you see anything missing or an area that could be improved,
let us know or submit a patch.
Are you using Jersey? We'd love to hear how you're using it in your projects.
Write about it on your blog and drop us a note. We will consider adding a link
to your blog to our list of development blogs.
More eyes on the code means better quality. Review our code for style issues,
potential issues, or glaring bugs. Anything helps!
Are you a Jersey power-user? Have insight on an issue another is having? Speak up!
Join our mailing lists or follow the questions tagged with