incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Brooks <>
Subject Re: Wanting to Contribute to iOS Cordova
Date Thu, 05 Jul 2012 00:23:49 GMT
Welcome Andrew!

As Fil mentioned, knocking out any JIRA issues assigned to 2.0 is a great
starting point. Just comment on the issue to let everyone know that you're
looking into it and ideally link to your Github fork and branch (for the
specific issue). Shazron and Becky are both extremely active, so they'll be
pumped to have another active contributor.

As a general heads up, it's always good to have your hands in on at least
two platforms. Working with multiple platforms broadens your mind and keeps
you away from a platform-specific mindset. This is especially important
with features such as the command-line interface, which needs to
work consistently across every platform. Even occasionally compiling and
running mobile-spec on another platform (*cough* Android, Mr. Chrome
*cough*) is enough remind yourself of what's different between SDKs.


On Wed, Jul 4, 2012 at 5:08 PM, Filip Maj <> wrote:

> Welcome Andrew! It is pretty cool to have someone from the Chrome team
> show interest in our project.
> We keep track of issues here:
> These are issues slates for 2.0, which we plan to deliver around mid-late
> July:
> ry=project+%3D+CB+AND+fixVersion+%3D+%222.0.0%22+AND+resolution+%3D+Unresol
> ved+AND+component+%3D+iOS+ORDER+BY+priority+DESC&mode=hide
> Perhaps other good starting points for contribution are the following
> specific tickets:
> - - this is a native iOS
> test. Tests and documentation are usually pretty low-barrier entries in
> terms of contribution
> - There are a couple issues related to the introduction of the iOS 6 SDK.
> ; if that is your cup of tea.
> - For more code-oriented, API-specific tickets, these might be a good
> start:
> I am pretty sure Shazron and Becky, our two main iOS contributors to
> Cordova, would be thrilled to have anyone else interested in contributing,
> especially via bug fixes. I will defer any specific guidance on
> contribution to their wisdom and opinion :)
> Here's a web-friendly view of the iOS repo:
> ry
> The git-cloneable repo is at
> As Simon said, initially our committer community would treat your commits
> as one-off patches (which we can generally pull in without an ICLA, but it
> is highly recommended [required if you want to become an eventual
> committer]). After a couple patches and a demonstration of some activity
> on this mailing list, we can kick up a DISCUSS+VOTE thread to get you
> voted in as a committer to this project.
> If you have any other questions please feel free to ask.
> Cheers!
> Fil
> On 7/4/12 3:45 PM, "Simon MacDonald" <> wrote:
> >Here's a good link on getting started as a contributor.
> >
> >
> >
> >As your code submissions get accepted and you build up a standing in
> >the community you can be nominated to be a full 'committer' to the
> >project. I'd pick up a bug to fix and start a discussion on it on this
> >mailing list.
> >
> >Simon Mac Donald
> >
> >
> >
> >On Wed, Jul 4, 2012 at 5:22 PM, Andrew Grieve <>
> >wrote:
> >> Hello!
> >>
> >> I'm a member of the Chrome team, and was hoping to start contributing to
> >> the iOS Cordova port. Despite working for Google, I have much more iOS
> >> development experience than I do Android :P. I also have a pretty good
> >> background in mobile web development, although I haven't used
> >> PhoneGap/Cordova before.
> >>
> >> I've signed the ICLA, and was able to fork and run the mobile spec
> >>tests.
> >> Hello World!
> >>
> >> Shazron, judging by the number of bugs assigned to you and your
> >>activity on
> >> the mailing list, I'm guessing you're the main contributor for the iOS
> >> port? I realize it's holiday season in the states right now, but would
> >>love
> >> to get a "state of the project" kind of overview from you at some point.
> >> E.g. what's left to move towards command line project creation, what's
> >>the
> >> state of moving features into plugins, etc.
> >>
> >> Looking at the bug list, it looks like all bugs marked as 2.0 have
> >> assignees. Should I pick up a bug from this list, or should I just look
> >>for
> >> ones without existing assignees?
> >>
> >> Andrew

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message