* James McLaughlin:
I've started a topic ProjectMaintainers and populated it with
the mails received today.
Thanks James,
I added WicketContribDojo and WicketContribVelocity.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Would it make sense to make a wicket-stuff-parent as we have wicket-parent?
Frank
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on
I would suggest making the wiki the main documentation page. The maven
doc generation needs some understanding and not many have the time to
learn it.
As for the wicket parent, I think that would be nice. It would
standardize common things such as wicket dependency, svn repository,
etc.
But this
On 11/22/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
As for the wicket parent, I think that would be nice. It would
standardize common things such as wicket dependency, svn repository,
etc.
But this is for the project maintainers themselves to decide.
Indeed, just a surgestion :)
Frank
On 11/22/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
I would suggest making the wiki the main documentation page. The maven
doc generation needs some understanding and not many have the time to
learn it.
+1 for the wiki... there are a lot of projects in wicket-stuff, and it
would be
added myself as maintainer for wicket-contrib-{tinymce,gmap} and
wicket-contrib-{tinymce,gmap}examples projects.
on wiki page, besides name and website, maybe it worth adding email address
as well.
/iulian
On 11/22/06, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* James McLaughlin:
I've
Right. Spaced that out. Thanks.
This does bringing up what the default permission scheme should be. For now
we are allowing anyone who is logged in to read/write (No more anonymous).
Once we have the maintainers sorted out, would it be better to give write
permission to only maintainers, admins,
On 11/22/06, James McLaughlin [EMAIL PROTECTED] wrote:
This does bringing up what the default permission scheme should be. For now
we are allowing anyone who is logged in to read/write (No more anonymous).
Once we have the maintainers sorted out, would it be better to give write
permission to
On 22/11/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 11/22/06, James McLaughlin [EMAIL PROTECTED] wrote:
This does bringing up what the default permission scheme should be. For now
we are allowing anyone who is logged in to read/write (No more anonymous).
Once we have the maintainers
done!
http://wicket-stuff.sourceforge.net/wiki
Needs de-uglification if someone wants to volunteer for that. I followed the
instructions at http://moinmoin.wikiwikiweb.de/SourceForge pretty much word
for word, so this will show you the install paths.
I've enabled the Anti Spam module, but
On 11/22/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Can't we set up a space for wicket-stuff which content we don't
attribute to the ASF, but provide as a documentation ground for the
wicket-stuff project?
I'd rather have the documentation together in one place than scattered
across the
So that's a yes for installing a WIKI on SF James :)
eElco
On 11/21/06, Upayavira [EMAIL PROTECTED] wrote:
Gwyn Evans wrote:
Not saying don't, but if it's just to track this sort of discussion,
then the main wiki's as good as anywhere for the moment.
Well, yeah. If all that it is needed
Eelco Hillenius wrote:
Let's let the new maintainers decide on that then :) I agree with
Martijn that it might be nice to have everything in one WIKI - if that
would be ok with Apache policy etc - though otoh, it could be good for
the wicket-stuff project to give it it's own feel and dynamics.
I can install moinmoin on sourceforge for wicket-stuff. Should I go ahead
and do it?
On 11/21/06, Filippo Diotalevi [EMAIL PROTECTED] wrote:
On 11/22/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Can't we set up a space for wicket-stuff which content we don't
attribute to the ASF, but
I'd much prefer JPA integration. I don't see one as part of databinder.
I know Cheeser was working on one. Has anyone got a finished version we
could use?
Gili
Igor Vaynberg wrote:
wicket-contrib-data-hibernate-3.0 can prob go to the glue factory now
that databinder.net
On 11/21/06, James McLaughlin [EMAIL PROTECTED] wrote:
I've take a brief look at all the wicket-stuff projects, and here are some
things I think need to be done.
Well done. However, i think it will be difficult to keep track of this
discussion in the mailing list.
Can we use a wiki instead? For
You can consider me being the maintainer of wicket-contrib-examples
and - with very luke-warm support - wicket-contrib-navmenu.
Furthermore, I'm co-maintaining wicket-contrib-yui and
wicket-contrib-yui examples together with Joshua Lim, who is the main
guy for the project.
As far as I am
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I've started work on JPA/toplink support in qwicket but we have a
post-Thanksgiving deadline so everything else is taking a back seat.
cowwoc wrote:
I'd much prefer JPA integration. I don't see one as part of databinder.
I know Cheeser
Well done. However, i think it will be difficult to keep track of this
discussion in the mailing list.
Can we use a wiki instead? For example, can we use the [EMAIL PROTECTED]
http://cwiki.apache.org/WICKET/ ?
Good point.
Eelco
Not saying don't, but if it's just to track this sort of discussion,
then the main wiki's as good as anywhere for the moment.
/Gwyn
On 21/11/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i think if its easy it should be on sf.net
so i would say go ahead
-igor
On 11/21/06, James McLaughlin
+1 for wicket-stuff using the main wicket wiki
On 11/21/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Let's let the new maintainers decide on that then :) I agree with
Martijn that it might be nice to have everything in one WIKI - if that
would be ok with Apache policy etc - though otoh, it
On 11/21/06, cowwoc [EMAIL PROTECTED] wrote:
I'd much prefer JPA integration. I don't see one as part of
databinder.
I know Cheeser was working on one.
I bet you can contribute a patch for DataBinder too. Open source etc.
Eelco
22 matches
Mail list logo
