On 08/03/17 00:59, Philip Prindeville wrote:
On Mar 3, 2017, at 3:07 PM, Karol Babioch <ka...@babioch.de> wrote:
Hi,
Am 03.03.2017 um 17:55 schrieb Mauro Mozzarelli:
I would like to suggest, that when a new potential contributor is
putting forward his proposed change, an expert buddy is assigned to
guide the new contributor through to getting his changes reviewed and
pushed into the mainstream code. A successful contribution would mean a
lot and inspire more work.
I totally agree on that. There is nothing worse than having people
contributing code, which is not merged for some odd reason and is flying
around in some bugtracker. This was a huge problem with OpenWRT, and I
thought that one of the reasons of the whole fork was to reduce the
friction and make the whole project more community-centric. I really
would like for this not to be messed up again ;).
So this mentor kind of approach might be doing the trick. Other projects
have often something similar in place.
Best regards,
Karol Babioch
Moving to GitHub and scrapping SVN and patchworks was a giant step forward.
It’s a lot easier to post patches, make sure they don’t get mangled by mailers,
and ensure that everyone is always looking at the latest copy.
-Philip
Thanks to Alberto who just updated the developer's guide.
I reported my experience after trying to contribute a very small change.
The process to post patches is substantially simple, but until today the
documentation was incomplete.
Posting patches via email has not worked for me.
To date still no progress and thus I do not see that giant step Philip
mentions.
I made another attempt today via git.
Mauro
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
