It will be great to have something like that. Something that you figure out digging at ghc trac wiki pages, mailing lists, google search etc will be a few minutes job for a mentor. It may be a bit taxing on the mentors but they can limit how many newbies they are mentoring and also breed new mentors to keep the cycle going.
-harendra On 25 September 2016 at 11:46, Jason Dagit <[email protected]> wrote: > > > On Sat, Sep 24, 2016 at 6:29 PM, Christopher Allen <[email protected]> > wrote: > >> I'd be willing to help with work required to open up GHC development >> more along multiple lines including: >> >> Bots/automation for Github >> >> Talking to Rust devs about what works, what doesn't >> > > Last year I approached some folks in the rust community because I wanted > to learn how to contribute to the rust compiler. In my experience, the > really special thing they had was an identified pool of contributors who > were willing and able to provide mentoring. I got hooked up with a mentor > and that made all the difference. I had a real live person I could talk to > about the process, the process-meta, and that person had context with me. > Pretty much everything else was just details. > > GHC dev probably has mentors too, but I don't know because I've never > thought to check or ask. > > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
