create minimal test pages for tickets, attach to ticket or commit in visual tests as pluginname_ticket_num.html
review tickets that have patches to see if they actually fix the issue, and if they might need refactoring, unit tests, or more review by a dev lead (Scott González or Jörn Zaefferer)
create patches (or commits and pull requests) for tickets that don't have them
All this work will be done in master, discussed on this forum, and managed in Trac.
Development of new plugins
See the list at the top of
for the new widgets we're focusing on right now. These are all in different states. Some, like
, need testing. Others like
, are designed and need to be implemented. Others still have some design work to be done. All need more tests, demos, documentation, and wiki page cleanup.
All this work will be done in individual plugin topic branches, discussed on the individual plugin wiki pages (or this forum where it doesn't fit in wiki comments), and managed on the individual plugin wiki pages.
One of the ways to help according to your comments is development of new plugins. I read about submitting a plugin on http://wiki.jqueryui.com/Submitting-a-plugin. However, it is not clear what is the role of the original author once a submitted plugin is approved and adapted. Can you clarify please?