<commit_before>---
layout: project
title: Join Us
---

.row-fluid
  .hero-unit
    %h1 Join Us!
    %p Take the red pill.
  .row-fluid
    .span12.well.post-bg
      %h2 Why should I join?
      %p WildFly is not only 100% open source, it is also developed for and by its community of users.  Developers join from all over the world, and they contribute in many different ways. We are grateful for all contributions, whether it be a new feature, a bug fix, wiki entires, helping other members, or even just filing a bug report. The relationship is symbiotic, every contribution you make encourages others to in turn contribute in ways that will likely benefit you. The experience is also rewarding. Let's look at why. 
      .row-fluid
        .span6
          %h4
            %i.icon-rocket
            Build Awesome New Technology
          %p You get to work on the latest and greatest technology. It's extremely exciting working on what defines the future of application development. It's always changing and never boring.
        .span6
          %h4
            %i.icon-trophy 
            Challenge Yourself
          %p Working on server runtimes and development frameworks is no slice of pie. But what fun is the easy level? While it can be challenging, solving tricky problems leaves you feeling a real sense of accomplishment.
      .row-fluid
        .span6
          %h4 
            %i.icon-book
            Learn Something New
          %p WildFly is a big project covering many areas. You are bound to learn something new with every contribution you make. Even our top contributors are learning something new everyday, and they love it.
        .span6
          %h4
            %i.icon-group
            Build Relationships
          %p When contributing you get to work with some amazing people, and forging relationships with other sharp minds is always great professionally and personally.
      .row-fluid
        .span6
          %h4
            %i.icon-certificate
            Prove Yourself
          %p Experience contributing to WildFly looks fantastic on a resume, and on a contracting reference list. It demonstrates talent and personal commitment beyond a normal job.
        .span6
          %h4
            %i.icon-globe
            Be a Part of Something Big
          %p Your contribution will be forever archived on the internet, and will benefit many others. They will tackle a hard problem using your work, they will learn by reading your work, and they will likely return the favor.
      .row-fluid
        %h2 How do I get started?
      .row-fluid
        .span6
          %p Getting involved is easier than you think. All resources that you need are available on the internet.
          %h4
            %i.icon-wrench 
            Build It
          %p 
            The first step to get started is to build WildFly yourself. This requires creating a
            %a{:href=>"http://github.com"} GitHub
            account, forking WildFly, and cloning your private fork. The
            %a{:href=>"https://community.jboss.org/wiki/HackingOnWildFly"} "Hacking On WildFly"
            wiki article contains complete instructions for this and the patch construction and submission process. 
          %h4
            %i.icon-search
            Find Something To Work On
          %p 
            After you are comfortable building the server, the next step is to find something that you would like to work on. Scan through
            %a{:href=>"http://issues.jboss.org/browse/WFLY"} bug tracking system
            and look for an issue you would like to fix. We also stick features that have not been scheduled / assigned into a special version called
            %a{:href=>"https://issues.jboss.org/browse/WFLY/fixforversion/12321689"} Awaiting Volunteers.
            It is usually best to start with something small though like a minor priority bug. If you need help locating a task, feature, or bug to work on, just 
            %a{:href => "irc://irc.freenode.net/#wildfly"} join our IRC channel 
            and ask for help. When you do locate an issue be sure to announce you intention in the JIRA so that others don't end up duplicating your effort.
          %h4
            %i.icon-envelope
            Subscribe to our Mailing List
          %p 
            If you are intending to contribute, it's a good idea to 
            %a{:href => "https://lists.jboss.org/mailman/listinfo/wildfly-dev"} join the development mailing list.
            All design and general development discussions take place on this list. We also will send out important notifications, like release schedule updates and system availability.
          %h4
            %i.icon-github 
            Submit A Pull Request
          %p Follow the directions in the above linked wiki article on how to submit the pull request. Once your pull request is submitted our automated CI environment will test it, and report any test failures. You will get email notifications in case this happens. A reviewer will also perform a human review, and request additional changes or clarification if required.
          %h4
            %i.icon-bullhorn  
            Brag
          %p After your patch is successfully merged, it's time to celebrate!
        .span6
          .row-fluid
            .span12.well
              %h3 Key Resources
              %p Getting up to speed as a contributor is much easier if you know where to look. Here is the most common set of resources to assist you.
              %p
                %ul.list-with-icons
                  %li
                    %i.icon-github
                    %a{:href => "https://github.com/wildfly"}Source Code
                  %li
                    %i.icon-pencil
                    %a{:href => "http://jira.jboss.org/browse/WFLY"}Issue tracker
                  %li
                    %i.icon-road
                    %a{:href => "https://issues.jboss.org/browse/WFLY#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel"}Road Map
                  %li
                    %i.icon-comments
                    %a{:href => "irc://irc.freenode.net/#wildfly"} IRC 
                  %li
                    %i.icon-envelope
                    %a{:href => "https://lists.jboss.org/mailman/listinfo/wildfly-dev"}Developer Discussions Mailing List
                    (
                    %a{:href=>"http://wildfly-development.1055759.n5.nabble.com"}archive
                    )
                  %li
                    %i.icon-wrench
                    %a{:href => "https://community.jboss.org/wiki/HackingOnWildFly"} Hacking On WildFly Guide
                  %li
                    %i.icon-puzzle-piece
                    %a{:href => "https://docs.jboss.org/author/display/WFLY8/Extending+WildFly+8"} Extending WildFly
                  %li
                    %i.icon-book
                    %a{:href => "http://git-scm.com/book"} Pro Git Book
          .row-fluid
            .span12.well
              .row-fluid
                %h3 Recommended books
                %p We highly recommend the following books, which we consider essential to working on system code.<commit_msg>Links to Core and HipChat, drop IRC refs<commit_after>---
layout: project
title: Join Us
---

.row-fluid
  .hero-unit
    %h1 Join Us!
    %p Take the red pill.
  .row-fluid
    .span12.well.post-bg
      %h2 Why should I join?
      %p WildFly is not only 100% open source, it is also developed for and by its community of users.  Developers join from all over the world, and they contribute in many different ways. We are grateful for all contributions, whether it be a new feature, a bug fix, wiki entires, helping other members, or even just filing a bug report. The relationship is symbiotic, every contribution you make encourages others to in turn contribute in ways that will likely benefit you. The experience is also rewarding. Let's look at why. 
      .row-fluid
        .span6
          %h4
            %i.icon-rocket
            Build Awesome New Technology
          %p You get to work on the latest and greatest technology. It's extremely exciting working on what defines the future of application development. It's always changing and never boring.
        .span6
          %h4
            %i.icon-trophy 
            Challenge Yourself
          %p Working on server runtimes and development frameworks is no slice of pie. But what fun is the easy level? While it can be challenging, solving tricky problems leaves you feeling a real sense of accomplishment.
      .row-fluid
        .span6
          %h4 
            %i.icon-book
            Learn Something New
          %p WildFly is a big project covering many areas. You are bound to learn something new with every contribution you make. Even our top contributors are learning something new everyday, and they love it.
        .span6
          %h4
            %i.icon-group
            Build Relationships
          %p When contributing you get to work with some amazing people, and forging relationships with other sharp minds is always great professionally and personally.
      .row-fluid
        .span6
          %h4
            %i.icon-certificate
            Prove Yourself
          %p Experience contributing to WildFly looks fantastic on a resume, and on a contracting reference list. It demonstrates talent and personal commitment beyond a normal job.
        .span6
          %h4
            %i.icon-globe
            Be a Part of Something Big
          %p Your contribution will be forever archived on the internet, and will benefit many others. They will tackle a hard problem using your work, they will learn by reading your work, and they will likely return the favor.
      .row-fluid
        %h2 How do I get started?
      .row-fluid
        .span6
          %p Getting involved is easier than you think. All resources that you need are available on the internet.
          %h4
            %i.icon-wrench 
            Build It
          %p 
            The first step to get started is to build WildFly yourself. This requires creating a
            %a{:href=>"http://github.com"} GitHub
            account, forking WildFly, and cloning your private fork. The
            %a{:href=>"https://community.jboss.org/wiki/HackingOnWildFly"} "Hacking On WildFly"
            wiki article contains complete instructions for this and the patch construction and submission process. 
          %h4
            %i.icon-search
            Find Something To Work On
          %p 
            After you are comfortable building the server, the next step is to find something that you would like to work on. Scan through our 
            %a{:href=>"http://issues.jboss.org/browse/WFLY"} issue tracking system
            and look for an issue you would like to fix. For the WildFly Core subproject, we use a 
            %a{:href=>"http://issues.jboss.org/browse/WFCORE"} separate project in the issue tracker
            , so it's a good idea to check there as well. We also stick features that have not been scheduled / assigned into a special version called
            %a{:href=>"https://issues.jboss.org/browse/WFLY/fixforversion/12321689"} Awaiting Volunteers.
            It is usually best to start with something small though like a minor priority bug. If you need help locating a task, feature, or bug to work on, just 
            %a{:href => "https://www.hipchat.com/gW90m6pIs"} join our HipChat channel 
            and ask for help. When you do locate an issue be sure to announce your intention in the JIRA so that others don't end up duplicating your effort.
          %h4
            %i.icon-envelope
            Subscribe to our Mailing List
          %p 
            If you are intending to contribute, it's a good idea to 
            %a{:href => "https://lists.jboss.org/mailman/listinfo/wildfly-dev"} join the development mailing list.
            All design and general development discussions take place on this list. We also will send out important notifications, like release schedule updates and system availability.
          %h4
            %i.icon-github 
            Submit A Pull Request
          %p Follow the directions in the above linked wiki article on how to submit the pull request. Once your pull request is submitted our automated CI environment will test it, and report any test failures. You will get email notifications in case this happens. A reviewer will also perform a human review, and request additional changes or clarification if required.
          %h4
            %i.icon-bullhorn  
            Brag
          %p After your patch is successfully merged, it's time to celebrate!
        .span6
          .row-fluid
            .span12.well
              %h3 Key Resources
              %p Getting up to speed as a contributor is much easier if you know where to look. Here is the most common set of resources to assist you.
              %p
                %ul.list-with-icons
                  %li
                    %i.icon-github
                    %a{:href => "https://github.com/wildfly"}Source Code
                  %li
                    %i.icon-pencil
                    %a{:href => "http://jira.jboss.org/browse/WFLY"}WildFly Full Issue tracker
                  %li
                    %i.icon-pencil
                    %a{:href => "http://jira.jboss.org/browse/WFCORE"}WildFly Core Issue tracker
                  %li
                    %i.icon-road
                    %a{:href => "https://issues.jboss.org/browse/WFLY#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel"}Road Map
                  %li
                    %i.icon-comments
                    %a{:href => "https://www.hipchat.com/gW90m6pIs} HipChat
                  %li
                    %i.icon-envelope
                    %a{:href => "https://lists.jboss.org/mailman/listinfo/wildfly-dev"}Developer Discussions Mailing List
                    (
                    %a{:href=>"http://wildfly-development.1055759.n5.nabble.com"}archive
                    )
                  %li
                    %i.icon-wrench
                    %a{:href => "https://community.jboss.org/wiki/HackingOnWildFly"} Hacking On WildFly Guide
                  %li
                    %i.icon-puzzle-piece
                    %a{:href => "https://docs.jboss.org/author/display/WFLY8/Extending+WildFly+8"} Extending WildFly
                  %li
                    %i.icon-book
                    %a{:href => "http://git-scm.com/book"} Pro Git Book
          .row-fluid
            .span12.well
              .row-fluid
                %h3 Recommended books
                %p We highly recommend the following books, which we consider essential to working on system code.
{'fraction_non_alphanumeric': 0.06687423852714228, 'fraction_numerical': 0.0074455123866251525, 'mean_word_length': 1.8606001936108423, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 35, 'https://': 18, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1598798', 'n_tokens_mistral': 3936, 'n_tokens_neox': 3622, 'n_words': 1601}