Contributing to Wicket

How to give back to Open Source

Transcript

1. Contributing To Wicket London Wicket User Group & jWeekend Wicket Bug Fix Night
2. Wicket Bug Fix Night • When was it? - 11th Feb 2009 • Where was it? - Kindly hosted by Cemal at jWeekend • Who was there? - Cemal Bayramoglu, Al Maw, Wille Faler, Anthony Stubbs, Richard Wilkinson, Oli Evans, Charlie Dobbie.
3. Wicket Bug Fix Night
4. Wicket Bug Fix Night
5. Contributing To Wicket • All very good, but... • How can I contribute to Wicket?
6. Contributing To Wicket • Report Bugs • Prove a Bug Exists • Submit a Fix • (Go to a bug fix night, participate in a user group, donate to apache etc.)
7. Reporting Bugs • It’s easy, but not trivial. Some things to remember: • Always search for an existing bug report • Be concise • Add any supporting evidence • Watch the issue
8. Using Apache’s Jira • http://issues.apache.org/jira/browse/WICKET • Project: Wicket • Issue Type: bug • Status: Open, In progress, Reopened
9. Wicket Bug Fix Night
10. Prove a Bug Exists... ...or doesn’t • Create A Quickstart or a jUnit test • Keep it as simple as possible • If you can’t recreate it, say so.
11. Create a Quickstart • It’s a Wicket project with just enough code to demonstrate the issue. • Maven really is the easiest way • For you (just one command)... • ...and for them (standard layout etc.)
12. Submit a Fix • For this you will need to: • Check out the Wicket source code from the Subversion repository. • Build it via mvn or IDE plugin. • Solve the problem • Package your fix as a Subversion patch file.
13. Oli’s recipe for working with Wicket • Eclipse - the kitchen sink • Subclipse - browse and checkout code • m2eclipse - maven support • Obviously there are other ways and IDE’s, but this path works for me.
14. Step 1- Getting Wicket • Add the repository • ‘Checkout as maven project’ • Go for a walk... • Automagic has occurred
15. Step 2 - Kick the tires • Match your quickstart’s pom.xml version to the Wicket project one • m2eclipse will now use the workspace Wicket instead of the .jar • Click through to a Wicket class from your quickstart. You should be taken to the source in your Wicket project.
16. Step 3 - Fix something • An exercise for the interested reader • Consider supplying a jUnit test with your code, so the bug doesn’t reappear
17. Step 4 - Create a patch • Right click on your changed file • Team > Create patch > Save in File... • Patch Root: Project • Attach the file to the bug report
18. Step 5 - Bask in the admiration of your peers • Your milage may vary. • Can depend on the kind of peers you hang about with. • Find humble reward from the Jira contribution report: • http://issues.apache.org/jira/secure/ConfigureReport.jspa? versionId=-1&issueStatus=all&selectedProjectId=12310561&repor tKey=com.sourcelabs.jira.plugin.report.contributions %3Acontributionreport&Next=Next
19. Come along next time!
20. Notes and links • You can find more info on the Wicket Wiki - http://cwiki.apache.org/WICKET/ contributing-to-wickethtml • Talk by Oli Evans, on behalf of the London Wicket User Group • http://code.google.com/p/londonwicket/ • http://oli.needleandthread.org