I know it's not code related, but documentation and guides come to mind. Maybe let people contribute more freely to the upstream wiki as they work on tickets?

On Tue, Aug 9, 2016 at 6:34 AM, Jakub Hrozek <jhrozek@redhat.com> wrote:
On Thu, Aug 04, 2016 at 10:20:37AM +0200, Jakub Hrozek wrote:
> Hi,
>
> Over the last couple of weeks, I've talked to several people, mostly
> engineers with not too much development experience, who said they would
> like to start contributing little fixes to SSSD. I would like to find some
> tasks that they can easily handle without making their had spin from
> looking at harder stuff like asynchronous tevent code :-)
>
> In the past, we used the 'easyfix' tag in the sssd tickets. We still had
> some, but not enough.  I tagged quite a few today, but if anyone knows
> about more easy fixes, please tag them as well.
>     https://fedorahosted.org/sssd/report/34
>
> Can anybody think of more tasks to ask newcomes to do? I know adding
> tests would be great, tests don't require C knowledge, but only Python.
> But we would have to document how to write new tests, currently the
> process is very convoluted.
>
> We also need to improve and fix documentation on the wiki.
>
> Anything else?

btw I amended the Contribute page with so that the tasks for newcomers
are better visible:
    https://fedorahosted.org/sssd/wiki/Contribute?action=diff&version=46&old_version=45
_______________________________________________
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/sssd-devel@lists.fedorahosted.org