search for: highfive

...9;s valuable to know someone has at least looked at your code. # How do other projects solve this? I've always been impressed at how Rust has been able to attract a steady stream of new contributors. They have a simple but seemingly effective tool for helping people land their first patch: the highfive bot. Upon a user making their first pull request, it posts a welcome message and assigns someone to review it. # A proposal I propose that we form a group of people who specifically volunteer to help review first-time patches. A simple phabricator bot could assign someone randomly much like Rust...

...me to give a lightning talk. Slides: <https://speakerdeck.com/asb/can-we-improve-the-experience-of-first-time-llvm-contributors> Video: <https://www.youtube.com/watch?v=32fmbEI9WrM> I'm intending to start an RFC thread when I get a chance. The tl;dr is I propose stealing Rust's highfive-bot and forming a team of eager volunteers who want to help improve response times for patches from first-time contributors. Best, Alex

On 9/12/16 11:40 PM, Davide Italiano wrote: > On Mon, Sep 12, 2016 at 10:03 PM, Alfred Perlstein via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hey folks, >> >> I'm new here, wasn't expecting to subscribe but here I am. The reason I'm >> here is that I came across a doc bug, I spent quite a bit of time learning >> all the tips and

Hi all. I'm assuming most people reading this email are familiar with LLVM's code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> as well as LLVM Weekly, the development newsletter I've written and sent out every Monday since Jan 2014. Since that time, it's provided something of a "signal boost" for important mailing list discussions and