Garrett, I also apologize for seeming to strong in my attempt to motivate you to produce a patch. I do know from experience that patches (pull requests) are the best motivators to the committers. So my counter rant was purely motivational (at least an attempt :) to enhance the codebase.
John On Thu, Jul 10, 2014 at 11:32 PM, Garret Wilson <[email protected]> wrote: > John, I sincerely apologize if this came across as a rant. I fully intend > to start contributing to Wicket!! Since I'm new to this group, my intention > was to explain a little about some of the architectural philosophy I will > take in my contributions. I also wanted to engender some discussion of > others' opinions and experiences before I rush off and start spewing out > code. > > In short, once I map out a few areas that I think need improvements, the > discussions on this list will give me an idea of where I can be most useful > to start at. > > Best, > > Garret > > > On 7/10/2014 5:49 PM, John Sarman wrote: > >> Garrett, >> Since Wicket is open source, why not create the desired patch and submit >> it >> to the committers instead of ranting about what caveats (in your opinion) >> exist. Productivity comes from contributions to code, not from >> complaining >> why it does not do it the way you think it should. Once you request a >> patch you will have the long time hard working devs scouring over the code >> to produce a better product. I did this approach and ultimately the long >> time devs rewrote the solution to my issue, and it is beautiful and >> simple. >> >> >> In summary, I'd like you to contribute the changes you desire to the >> codebase making sure that your ideas do not breaks the 1000's of other >> developers usage of the API. >> >> Thanks, >> John >> >> >> >
