chance.
:)
Let’s add some 5-10 issues from Jira.
At least this raise NiFi awareness.
Thanks
Toivo
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/DISCUSS-Using-the-new-help-wanted-tool-from-comdev-tp10222p10233.html
Sent from the Apache NiFi Developer
Helpwanted is currently fairly empty.
This is our chance.
:)
Let’s add some 5-10 issues from Jira.
At least this raise NiFi awareness.
Thanks
Toivo
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/DISCUSS-Using-the-new-help-wanted-tool-from-comdev
Sean,
We talked in the past about being good at tagging JIRAs as beginner.
That still seems like a good approach. Can we simply have the task be
a link to a JIRA report of those tagged items?
Do we have any good information showing that folks interested in
helping apache projects are using
Hi folks!
ASF comdev has put up a great new tool for funneling in new folks:
https://helpwanted.apache.org/
How about we brainstorm a few things here (maybe some beginner JIRAs
we can flesh out a little?) and then file?
-Sean
Totally makes sense. My only comment was just in regards to the fact that
on that Wiki page there is no mention of looking at GH PR's. I agree that
in this day and age looking to GH, may be first inclination for many.
However, perhaps calling that out in the contribution guide would eliminate
The "Patch Available" state in JIRA can mean a patch is attached to the
JIRA, or a PR is submitted.
It is really just a manual state transition on the ticket after
In-Progress... the next state is patch available which tells people there
is something to review.
On Tue, May 3, 2016 at 11:29 AM,
Totally agree on all fronts. Would seem like it makes sense for a
documentation PR to be opened soon with updates to the
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
page to remove the ambiguity.
On Tue, May 3, 2016 at 11:27 AM, Bryan
They are treated with same priority, but as Oleg mentioned, the PRs do make
it easier for collaborative review and has the built in integration with
Travis, although currently some issues to get it consistently working.
On Tue, May 3, 2016 at 11:26 AM, Suneel Marthi wrote:
>
PR is the standard now across most Apache projects.
On Tue, May 3, 2016 at 11:25 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Andrew
>
> Regarding PR vs. Patch.
>
> This has been an ongoing discussion and i’ll let other’s to contribute to
> this. Basically we support both. That
Andrew
Regarding PR vs. Patch.
This has been an ongoing discussion and i’ll let other’s to contribute to this.
Basically we support both. That said, personally (and it appears to be embraced
by the rest of the community) PR is the preference specifically due to the
inline review/comment
Thank you Oleg!
Yeah, that page with the Code Review, has a little refresh link, but it
really just points to this JIRA query:
https://issues.apache.org/jira/browse/NIFI-1837?filter=12331874
As a community is there a preference given to JIRA's with Patch or GH PR's
or are they all treated with
Andrew
Thank you so much for following up on this.
I am assuming you have GitHub account. If not please create one as most of our
contributions deal with pull requests (PR).
Then you can go to https://github.com/apache/nifi , click on “Pull Requests”
and review them by commenting in line (you
Oleg,
I would love to help -- couple of quick questions:
The GH PR's are ~60 as you indicated, but the How To Contribute guide (Code
review process --
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
) shows a JIRA list with patches available.
Guys
I’d like to use this opportunity to address all members of the NiFi community
hence this email is sent to both mailing lists (dev/users)
While somewhat skeptical when I started 6 month ago, I have to admit that now I
am very excited to observe the growth and adaption of the Apache NiFi
14 matches
Mail list logo