On Tue, Aug 25, 2015 at 11:35 AM, Branko Čibej <br...@apache.org> wrote:
> And does everyone who's writing these instructions really think this is > a reasonable process for new contributors? Why not just clone from > git-wip-us, make the change on a local branch and either send the patch > to the dev list or attach it to the Jira issue? There's no sane reason > to involve GitHub at all. > > As it is, you're telling him to jump through 4 hoops when he could just > as easily get the same done by jumping through 2. Meh. > To my knowledge, the Apache Ignite community does not enforce Github. It's just an option. The user started the discussion by mentioning Github, that's why it continued in that direction. In my opinion, what's important as a community is to accept contributions from as many major channels as possible. And Github surely is a popular one. - Raúl.
