cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lucas Gonze <lu...@gonze.com>
Subject Re: introduction
Date Wed, 26 Nov 2014 00:43:43 GMT
I attempted to clear my memory and revisited the page. From that POV the
link title worked for me.

Following the instructions at IssueWorkflow for submitting a patch, I
forked https://github.com/apache/cordova-plugin-file-transfer , made the
edit, and submitted a pull request. Per those instructions I am pasting the
pull request link in an email (this email) to the mailing-list:

https://github.com/apache/cordova-plugin-file-transfer/pull/50


The instructions at IssueWorkflow say I should fork dev, not master, but
the dev branch of that plugin says that it is obsolete and master should be
used instead.

I discovered after making the pull request that should have called out
someone to review my change by picking a reviewer from the component list
<https://issues.apache.org/jira/browse/CB#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel>.
I should have pinged Max Woghiren
<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CB+AND+resolution+%3D+Unresolved+AND+assignee+%3D+max.woghiren+ORDER+BY+priority+DESC&mode=hide>.


I made a change to the top-level index.md, but not the translations. I
don't yet know how to find documentation on the procedure for keeping
translations in sync.


On Tue, Nov 25, 2014 at 3:13 PM, Josh Soref <jsoref@blackberry.com> wrote:

> Lucas wrote:
> >My path was via http://wiki.apache.org/cordova/ContributorWorkflow.
> >I read that and hit all the links except for the one labeled "Work on an
> >issue”,
> >which leads to http://wiki.apache.org/cordova/IssueWorkflow, which has
> >the information I needed.
>
> Ouch.
>
> >I didn’t hit that “Work…” link because performing the work was implicit
> >in doing a git checkout and modifying the source tree,
> >which I knew how to do without hitting that link.
>
> Arg, you're right.
>
> >My error could be considered a discoverability problem in the “Work on an
> >issue” list item.
>
> Agreed.
>
> > It might be rewritten as “Get to know _Issue Workflow_."
>
> I've updated that page. Please try to forget what you've read in this
> thread and revisit the page.
> If that's too hard (most people are bad at forgetting stuff), see if you
> can find a friend to walk through it.
>
> Otherwise, we'll have to wait and see if someone else stumbles again.
>
>
> Thanks very much. From my perspective, you've just provided a great first
> contribution!
>
>

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