Imo, if any of the core developers think it makes a good addition, he
can put it in without too much fuzz. Unless it is code that is
arguable, in which case we should have at least say three votes for it
and no against.

Furthermore, we have to keep pointing out that our preferred way of
accepting contributions - like any open source project - is by patches
attached to bug reports/ feature requests.

Eelco


On 11/21/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> All,
>
>  I've seen several nice code contributions posted to the mailinglists
> (Christian Essl was the last one), and I was wondering whether we
> could/should include these small components into the extensions package? I'd
> hate to see such contributed code go unused.
>
>  Should there be some voting mechanism for this?
>
>  Martijn
>
> --
> Living a wicket life...
>
> Martijn Dashorst - http://www.jroller.com/page/dashorst
>
> Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to