crap, sent too early... maybe some "rules" or rather guidelines about what content (dev-questions, announcements, etc..) can be sent to which list (users, dev) should be put on the wicket-stuff wiki...
gerolf On 8/14/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > > tbh, i didn't even realize that there were 'stuff-mailing lists. > and posts like [0] didn't even let me come up with the idea to look for > wicketstuff specific mailing lists ;) > > maybe some "rules" or rather guidelines > > [0] > http://www.nabble.com/wicket-stuff-GMap%3A-New-Exciting-Features%3A%29-tf3726142.html#a10428027 > > On 8/14/07, Nick Heudecker <[EMAIL PROTECTED]> wrote: > > > > I agree with using the Apache-based lists for Wicket Stuff. I don't > > think > > the traffic is high enough to warrant dedicated mailing lists and it's > > easy > > to use subject line prefixes, like "[TinyMCE] ...", for non-core > > discussions. > > > > On 8/14/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > > > 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/ > > > > > > > > > > > -- > > Nick Heudecker > > Professional Wicket Training & Consulting > > http://www.systemmobile.com > > > > Eventful - Intelligent Event Management > > http://www.eventfulhq.com > > > >
