[jira] Commented: (WICKET-1586) Add a "how to contribute" page to wicket.apache.org

["Martijn Dashorst (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649641#action_12649641 ] 

Martijn Dashorst commented on WICKET-1586:
------------------------------------------


h2. How to contribute to Wicket

There are several ways to contribute to the Wicket project: do community work or actual coding. Note that both are very important aspects of open source development: you need code people can use, and you need documentation and marketing to help users find and use your code. This document describes how *you* can help.

h3. Community work

The mailing lists are always in need of people answering questions. The core team tries to answer most questions and help resolve problems, but even us geeks have a life that extends beyond the monitor and keyboard. So helping out on the mailing lists is really beneficial for the community and yourself: helping out can be very rewarding.

But the community work doesn't end with the mailing lists. You can help evangelizing Wicket to the larger community: write a blog entry, or article for JavaWorld or your local software development magazine. You can spread the word by giving talks at conferences and user group gatherings. All these things help build our community.

h2. Code work

When you want to contribute code the first thing you'll need is to get the sources. You can grab them from our subversion repository:

{code}svn co https://svn.apache.org/repos/asf/wicket/trunk wicket-1.x{code}

This command will check out the trunk of all our projects to your workspace in a sub directory called wicket-1.x. 

Next you might want to get maven if you haven't gotten it already. If you have, you might want to upgrade to the latest stable release.

Setting up your development environment is highly dependent on your IDE of choice. If you're on a recent build of IntelliJ or Netbeans you'll be able to open the project directly with the integrated maven support. If you're on Eclipse and don't use the Maven plugin available for eclipse, you'll have to run "mvn eclipse:eclipse" which will setup your classpath and project files. Next you'll have to import the projects using the import existing projects menu item.

Now you'll be able to work on your issue. Here's a list of steps you might consider:

* create a JIRA issue for your bug/feature/improvement
* comment that you'll be working on it
* make your changes, ensure the unit tests keep running
* ensure you are developing against Java 5 (if working on wicket 1.4 or newer) *not* Java 6 or newer

If your [... TODO ...]

> Add a "how to contribute" page to wicket.apache.org
> ---------------------------------------------------
>
>                 Key: WICKET-1586
>                 URL: https://issues.apache.org/jira/browse/WICKET-1586
>             Project: Wicket
>          Issue Type: Improvement
>          Components: site
>            Reporter: Igor Vaynberg
>            Assignee: Martijn Dashorst
>             Fix For: 1.4-RC2
>
>
> we need something like this [1] on our website because a few users have requested the info.
> [1] http://wiki.apache.org/hadoop/HowToContribute

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.