Martijn Dashorst wrote:
Why? It is part of our documentation. It is maintained by wicket core
devs. There is no reason for it to be at the general wiki. The purpose
of our core site is to add content to it, not keep it a 2 pager.
Hmmm. I edited this before I was a core developer. If your community can
help keeping docs up to date, then I suggest letting them. And that is
best done by keeping things on the wiki.
Unless someone wants to volunteer to be the official documentation
collator and editor, we're best off letting everyone contribute as they
see fit, I've have thought. That means leaving as much stuff on the wiki
as possible.
IMO the only docs that should live on the web site proper are things
that will either never become out of date or are very important to keep
up to date and are therefore unlikely to stagnate.
Examples:
- Official introduction to Wicket.
- Jumping-off points for other documentation, etc.
- Where the IRC channel and mailing lists live.
- Where things are in Subversion.
- Guide to building the project from source.
- How to become a committer.
In short, if a document can legitimately be improved by a community
member, it should live on the wiki. In my eyes, this definitely includes
migration guides.
Al