Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <EA4EA8E8-4801-4B2B-81C4-ACAA347231E2@gmail.com>
References: <181C2BEA-CFF7-453A-BAE6-421F3B1836E1@classsoftware.com>
	<CALorpXet-vAmpjKWVHdh3q73mnePohJyYeVWJgNA26nJ9WYdHw@mail.gmail.com>
	<A25AF30B-AB43-4108-9E43-7043C5629A40@classsoftware.com>
	<EA4EA8E8-4801-4B2B-81C4-ACAA347231E2@gmail.com>
Date: Mon, 11 Mar 2013 07:46:29 -0400
Message-ID: 
 <CALorpXdL2owv-ccE=FaY=1VihYmoQcyiDYmCA_XEkfef5zbjLA@mail.gmail.com>
Subject: Re: JIRA issues with SDK that are simple to fix
From: Nicholas Kwiatkowski <nicholas@spoon.as>
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=20cf307ca1e448e8a304d7a4b914

--20cf307ca1e448e8a304d7a4b914
Content-Type: text/plain; charset=ISO-8859-1

Check out the "Squashing Bugs" section on our website :
http://flex.apache.org/community-getinvolved.html

Essentially, you add a patch to the ticket, and we put them in for you
(after a review).  More (good) patches give you karma and will get you
voted in to be a committer.

-Nick

On Mon, Mar 11, 2013 at 2:47 AM, Harbs <harbs.lists@gmail.com> wrote:

> How would a non-committer work on this?  Most of them specify the needed
> fix. What's the process for getting those fixes in?
>
> i.e. https://issues.apache.org/jira/browse/FLEX-29004
>
> On Mar 11, 2013, at 5:43 AM, Justin Mclean wrote:
>
> > Hi,
> >
> >> I can take a look at them.  I didn't troll those "Easy to fix" in hopes
> >> that some other community members might take them on, but it's probably
> >> best to get them out the door.
> >
> > Yep I was hoping some of the less active committer or people looking to
> be committers would pick them up, but if we want to get a new release out
> the door I think they should be fixed, most have been hanging about for a
> while.
> >
> > Thanks,
> > Justin
>
>

--20cf307ca1e448e8a304d7a4b914--