If it is just a patch for the javadocs then you may skip Jira. No need to explain the same in several tools. It should be easy for you to contribute.
On Tue, Jul 24, 2012 at 4:25 PM, Bertrand Guay-Paquet <[email protected]> wrote: > Hi Martin (and other devs), > > Must a Jira issue accompany each pull request? Also, is it ok to use a > feature branch (based on the snapshot branch) for the pull request? > > Bertrand > > > On 23/07/2012 3:15 AM, Martin Grigorov wrote: >> >> Hi, >> >> You can create tickets in our Jira with attached patches if you don't >> know how to use GitHub or you don't want to use it. >> >> If you want to try GitHub: >> 1) create an account at GitHub (https://github.com/) >> 2) go to https://github.com/apache/wicket and click the "Fork" button >> 3) clone the fork locally: git clone >> https://github.com/MY_ACCOUNT/wicket.git (replace MY_ACCIUNT with your >> real username.) >> 4) make your improvements in the code >> 5) git commit >> 6) git push >> 7) go to https://github.com/MY_ACCOUNT/wicket and press the "Pull >> Request" button >> >> That's it. >> >> On Mon, Jul 23, 2012 at 12:27 AM, Paul Bors <[email protected]> wrote: >>> >>> I second improving the current code documentation as I recently migrated >>> a >>> mid-size project to Wicket 1.5.7 from 1.3.7 and I've notice myself having >>> to >>> dig into the framework implementation more often than normal because of >>> the >>> weak or at times wrong JavaDocs. >>> >>> I won't mind submitting small patches if someone would point the way. >>> Last I >>> asked I was told to submit a push via git hub. Is there a wiki page on >>> how >>> to submit such code changes patches to a wicket branch? >>> >>> At the same time I do feel that a book explaining the inner works of >>> Wicket >>> will also benefit everyone to better understand the framework faster and >>> be >>> able to contribute as needed. I remember couple of years ago when I first >>> started working with Wicket and how lost I was until after I read two >>> books >>> on the subject just to learn how to use it. >>> >>> That's my 2 cents :) >>> >>> ~ Thank you, >>> [email protected] >>> >>> -----Original Message----- >>> From: snekse [mailto:[email protected]] >>> Sent: Sunday, July 22, 2012 2:23 PM >>> To: [email protected] >>> Subject: Re: I think it's time for a new book.... Igor and Co ? >>> >>> Putting in my 2 cents. >>> >>> I'd rather see more people put in time and effort to submit patches for >>> documentation that would reduce the need to dig into the guts of Wicket. >>> >>> Now that I'm more familiar with Wicket, I'll try to start doing this. I >>> hope others will too. >>> On Jul 22, 2012 10:55 AM, "Michael Mosmann" <[email protected]> wrote: >>> >>>> I would put the bell on the cat .. but maybe someone would join.. >>>> >>>> Mm:) >>>> -- >>>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail >>>> gesendet. >>>> >>>> >>>> >>>> Igor Vaynberg <[email protected]> schrieb: >>>> >>>> lol. my thoughts exactly :) >>>> >>>> -igor >>>> >>>> On Sun, Jul 22, 2012 at 12:53 PM, Josh Kamau <[email protected]> >>>> wrote: >>>>> >>>>> Who will bell <http://en.wikipedia.org/wiki/Belling_the_cat>; the cat ? >>>>> >>>>> On Sun, Jul 22, 2012 at 12:51 PM, Michael Mosmann >>>>> <[email protected] >>>>> wrote: >>>>> >>>>>> Had the same idea... >>>>>> -- >>>>>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail >>>>>> gesendet. >>>>>> >>>>>> >>>>>> >>>>>> mlabs <[email protected]> schrieb: >>>>>> >>>>>> The title would be ... 'Wicket Internals' ... >>>>>> Dive DEEPER into the parts other programmers never reach.... >>>>>> The inner workings of response cycles... what really happens ... >>>>>> Oh and esp the Ajax stuff... jQuery integration ... etc... >>>>>> >>>>>> TIA >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> >>>> http://apache-wicket.1842946.n4.nabble.com/I-think-it-s-time-for-a-new >>>> -book-Igor-and-Co-tp4650687.html >>>>>> >>>>>> Sent from the Users forum mailing list archive at Nabble.com. >>>>>> >>>>>> _____________________________________________ >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>> _____________________________________________ >>>> >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
