my opinion differs slightly, I'm not too worried about duplicates.
seeing a second approach to something can often be very helpful. in
fact, I think having 2 different developers work on different threads
can really help spur innovation.
My philosophy is, if you have an itch, scratch it. Take what you're
interested in and do it.
David
Elliot Metsger wrote:
Yup, the key is just communicate on what you're working on so efforts
aren't duplicated, or so efforts can be combined.
E
Marc Veary wrote:
Hey... thanks for the advice.
On 7/4/07, Ralph Goers <[EMAIL PROTECTED]> wrote:
If there is no patch attached feel free to submit one. Even if someone
is actively working on a fix at worst you might waste some of your time.
However, you can always update the Jira issue and ask if the owner would
mind you submitting a patch.
Ralph
Marc Veary wrote:
> Hi,
>
> What is the general etiquette for selecting what to do to help out?
> For instance, most of the entries in JIRA are assigned and I don't
> want to tread on anyone's toes.
>
> Kind regards,
> --
> Marc
