Contributors

DWR is maintained by a group of people, lead by Joe Walker. We try to keep clear maintainers for each part of DWR, but we also seek to prevent code ownership from becoming a barrier to refactoring.

The current maintainers are:

There are some 'rules' for contributors. They're not onerous, but are designed to help us develop in harmony.

Getting Involved

We are always on the lookout for more help. If you want to get involved, you should do the following:

  • Join the mailing list. It's probably best to join dwr-dev and dwr-users
  • Get involved by helping users, and seeing how we do things.
  • Play with DWR and see if there is anything that you think is broken or missing.
  • Get an account in our bug tracking system, and either find an issue to work on, or create an issue.
  • Post to dwr-dev with what you are wanting to change to make sure it doesn't clash with some other work.
  • Make the changes and send a zipped patch to the mailing list describing what you've changed.
  • It's not worth applying through java.net for developer status, that method of getting involved doesn't work properly ,and requests always end up getting denied.

There are a number of existing DWR components that we are looking for maintainers for:

  • JSF Integration
  • The Fluent Configuration System
  • Hibernate Integration
  • The Demo Webapp

It would also be great to have a maintainer for DWR version 1.1, and maybe even 1.0. The workload for this is very low, but it might involve a bit of sudden very high priority work.

There are a number of areas of DWR that could do with improvement:

  • Integration with other Ajax toolkits: Dojo, YUI, etc
  • Demo apps that show integration with: Spring, Struts, Webwork, etc

And it's always good to have people that are keen on writing documentation or helping with sending out release announcements.

‹ DevelopmentupThe Maintainer Contract ›