Contributing to Cordova

[Oliver Salzburg <ol...@gmail.com>]

Hello list,

we've been working with Cordova for about a year now.
In the process we've opened a couple of issues on the Cordova Jira and
submitted a couple of pull requests on GitHub.

I've noticed that responses to these actions usually take either a very
long time, or don't happen at all.

We've started to maintain forks of several plugins where we have
included required fixes, but I consider this a very sad situation.
I would much prefer to use upstream versions and have our fixes
included in those.

So I'm wondering if I'm not using the correct communication channels.

Please let me know about the best way to have contributions discussed
and included quickly.

Thanks in advance,
Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: Contributing to Cordova

[Joe Bowser <bo...@gmail.com>]

On Wed Nov 26 2014 at 2:23:45 PM Oliver Salzburg <ol...@gmail.com>
wrote:

> Hello list,
>
> we've been working with Cordova for about a year now.
> In the process we've opened a couple of issues on the Cordova Jira and
> submitted a couple of pull requests on GitHub.
>
> I've noticed that responses to these actions usually take either a very
> long time, or don't happen at all.
>
>
That's true. Often what will happen is that people who patiently have a fix
for a plugin or a test will work on it on their own and then by the time
the contributors see this, the patch doesn't work cleanly or something has
changed and the code is stale.

We've started to maintain forks of several plugins where we have
> included required fixes, but I consider this a very sad situation.
> I would much prefer to use upstream versions and have our fixes
> included in those.
>
>
Can you point to these? I think pinging the dev list is probably the best
way to get someone to look at your fixes faster.  I know that everyone
involved will work on their new feature and pull requests by themselves
will probably fall through the cracks.


> So I'm wondering if I'm not using the correct communication channels.
>
>
You are, but posting here is probably the fastest way to get people to look
at your changes.  Simple GitHub pull requests don't make it to my inbox too
often.