I know this is a touchy feely issue and we have discussed this over
again. With the migration of Wicket to Apache, the wicket stuff
projects are more remotely administered than before. All the Wicket
mailling lists have been migrated to Apache lists, and our community
is gathering steam again at our new home.
There is one thing that still troubles me: the wicket stuff projects
and the mailing lists of the project.
Wicket stuff can't live currently without the main wicket lists. The
main lists (dev, commits, users) have a solid user base and that base
needs to be informed about new initiatives, new releases etc.
Personally I really don't mind having the discussion concerning 'stuff
projects on our Apache lists, in fact I prefer that, because it keeps
the community together, and allows us to keep monitoring the projects
for possible inclusion at Apache. Furthermore, most of the projects
are maintained by core members, so it is odd to have discussions on
separate lists, where even discussions may have consequences to the
other project.
I propose the following bold move:
shut down the wicket-stuff lists in favor of the apache based lists.
If the 'stuff discussions get out of hand we can always divide and
conquer. For now, these projects need more involvement and publicity.
This can only happen if they are exposed to the grander wicket
community.
WDYT?
Martijn
--
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
