Wicket itself
Wicket’s code is in apache/wicket on GitHub. Pick an open issue or one you ran into yourself, and send the fix as a pull request: a committer reviews and merges it, and it goes out with the next release of its line. Since Wicket 11 a major release ships every three months, so a change merged today reaches users within a quarter. New features go to master, the next major release. Fixes that the LTS needs also go to wicket-10.x.
- Send a pull request to Wicket Fork apache/wicket, pick the branch of the line you change, and send your fix or feature as a pull request.
- Build from source: check out a branch, build it with Maven and use your own build.
- Set up your IDE: import the projects into Eclipse, IntelliJ IDEA or NetBeans, with the code format.
- Fix a bug or add a feature: from an issue to a pull request.
- For committers, Build a release still describes the release process of Wicket 6 and older and needs an update.
Without writing code
- Answer questions on the users list or Stack Overflow.
- Report a bug in the issue tracker, with a quickstart that shows it.
- Tell us where the documentation is unclear or wrong: every page has a link to improve it on GitHub.
- Show what you built on Built with Wicket.
The site and its documentation
This site and its documentation are Markdown files in apache/wicket-site. Start with the tutorial; the other pages cover the tasks that come up again.
- Make your first change to the site Clone the site, run it on your machine, change a page, and send the change as a pull request.
- Update the site for a release Announce a release on the site, update its version everywhere it appears, and start a new release line when a major release ships.
- Write a blog post Publish a release announcement, a security advisory or an article on the blog, and decide whether it is featured.
- Add a page to the documentation Write a new page for the documentation under /docs/, give it the front matter that files it, and check it in search and on its topic page.
- Carry the reference guide's changes into the documentation At a release, find what changed in the AsciiDoc reference guide in apache/wicket and rewrite those changes into the pages under /docs/.
- Redirect an old URL Keep links in mails, announcements and other sites working when a page moves or disappears.
- Site files and data What each folder and data file of the site holds, the version settings in _config.yml, and the fields of the release lines.
- How the site is built and published Why the built site is committed next to its source, how a commit reaches wicket.apache.org, and why release day only changes data.
Mailing lists
The project discusses its plans, changes and releases on the developers list, dev@wicket.apache.org, with its archive. Subscribe by sending a mail to dev-subscribe@wicket.apache.org.