See other reply to Boris. Anyone can pick it up and become the maintainer of WS. But it's going to take a group of people who set some rules about it and then follow them. The problem with that is that then people *will* whine because they always wanted WicketStuff to be a no-rules repo. I would like to see the wicketstuff-core things that I reorganized last year (and the year before) to continue to make progress and be released consistently. But I don't have the time, and when I asked for help, although there were offers, no one ever stepped up to the plate. So, if the community doesn't care that much, why should I? I'd rather put my time into things that I can actually control and make a positive effect with.
-- Jeremy Thomerson http://www.wickettraining.com 2010/3/17 Major Péter <majorpe...@sch.bme.hu> > I always thought, that Jeremy was the maintainer of WicketStuff. Guess I > was wrong. :) > Sidenote: > Also, I really wanted to write docs for the javaee-inject project, but I > don't have confluence access, and the signup gives: > org.springframework.transaction.UnexpectedRollbackException: Transaction > rolled back because it has been marked as rollback-only > > I guess this isn't working since the overspammed confluence event. I > already wrote two e-mails to the dev list, but still no answer, so I'm > confused too about the wicketstuff's future... > > Regards, > Peter > > 2010-03-17 20:25 keltezéssel, Boris Goldowsky írta: > > It sounds like whoever is responsible for wicketstuff needs to make a > > clear choice here. > > > > Is Wicketstuff going to be maintained as a place where lots of useful > > add-ons will live? If so, it needs someone to take a slightly more > > active role as curator; make sure the releases are done in parallel with > > wicket releases, make sure modules don't get dumped there without at > > least some documentation; and weed out modules that are abandoned, where > > no one volunteers to take on maintenance, or whose function has been > > absorbed into wicket's core. > > > > Alternatively, make it clear that wicketstuff is NOT going to be > > maintained, and people like me who would like to share modules will > > share them in some other way - on Google code, a personal website, or > > whatever. > > > > Either way is ok I think, it just would be useful for those of us who > > are interested in contributing modules to know. > > > > Thanks > > Bng > > > > > > Jeremy Thomerson wrote: > >> Really, it should match what's at trunk of Wicket, which should be > >> 1.5-SNAPSHOT. There should be a branch for 1.4.x that is 1.4-SNAPSHOT. > >> But, nobody is really maintaining it any more, so it's a free-for-all. > >> That's always been the problem with WicketStuff. > >> > >> -- > >> Jeremy Thomerson > >> http://www.wickettraining.com > >> > >> > >> > >> On Tue, Mar 16, 2010 at 1:00 PM, Boris Goldowsky > >> <bgoldow...@cast.org>wrote: > >> > >> > >>> The wicketstuff-core is calling itself version 1.4.2 in the HEAD of > SVN. > >>> Shouldn't this be updated to 1.4.7 now to keep in sync with Wicket? > >>> > >>> Bng > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
