so its foo, bar, kazam. interesting. -igor
On 4/25/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I think that blatant errors can be fixed by anyone with write access. In this particular case it should not lead to discussion :) Complete rewrites of functionalities is something that should be discussed before undertaken, even by 'project owners'. This is because we're trying to build a community. And to build one we need to communicate. So giving a heads up to @dev with something like "I fixed the foo in the bar project because I ran into kazam" would be nice. It gives the projects more visibility and opens development for discussion. Martijn On 4/25/07, Bart Molenkamp <[EMAIL PROTECTED]> wrote: > Hi, > > I found an error in wicket-contrib-scriptaculous-examples/pom.xml. It > has a dependency to wicket-contrib-scriptaculous (of course), but the > group ID should be 'org.wicketstuff', not 'wicket-stuff'. > > I guess the group ID renamed, and you all have a version for the old > group id in your local repositories. > > I have a fix here, but I want to know, Am I allowed to commit it? I have > been given commit access for wicket-contrib-dojo, but I think that means > that I have commit access for anything in wicketstuff. And that's just > the technical side, I also want to know if there is any policy regarding > these 'subprojects' in wicketstuff for new committers like me? > > Thanks, > Bart. > -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
