Tim,

Without your hard work and dedication, I would probably have never had any
momentum on my PR's, and I would not have become engaged with the Django
code and community. You've been hard-working, dependable, methodic,
knowledgable, an inspiration, and overall excellent. It will be hard for
any new fellow to match you.

Thanks for all the work and enjoy your well-deserved guilt-free break,

Adam

On Tue, 8 Jan 2019 at 18:23, Matthew Pava <matthew.p...@iss.com> wrote:

> On behalf of myself and on behalf of everyone else I speak for, thank you,
> Tim, for doing such an outstanding job with Django!
>
>
>
> I know that I only made one contribution, and you played such an important
> role in helping me understand what I was doing wrong and how to fix it.
> And I appreciate that to this day.  I would love to become a more
> consistent contributor, but my own lack of time prevents it.
>
>
>
> Thank you,
>
> Matthew Pava
>
>
>
> *From:* django-developers@googlegroups.com [mailto:
> django-developers@googlegroups.com] *On Behalf Of *Tim Graham
> *Sent:* Tuesday, January 8, 2019 10:45 AM
> *To:* Django developers (Contributions to Django itself)
> *Subject:* thoughts for Django fellowship applicants
>
>
>
> Hello,
>
>
>
> If you haven't seen the post*, I'll be stepping down as a Django fellow at
> the end of March. Applications are open until this Friday if you're
> interested in joining Carlton in the position.
>
>
>
> I wanted to give a brief retrospective on some aspects of my experience,
> with the hope that it'll be helpful for the future of the program.
>
>
>
> There are a number of reasons for my decision, but mainly I've felt a need
> to disconnect for a while and take a break. I want to explore other things
> besides computers. I don't have the same excitement for the work as when I
> started. Django development was less structured back then. It was fun to
> set up continuous integration and a regular release schedule and bring
> order to chaos. Now with those things in place, I think Django will
> continue to plod along just fine without me.
>
>
>
> It's been tough for me to take a guilt-free vacation because there's not
> much "excess capacity" in the fellowship staffing. Even with another fellow
> working part-time, there's a backlog of review work that accumulates when a
> fellow takes a break. It's easy to feel overwhelmed when you return. Maybe
> this is fine. If the fellowship were overstaffed, that wouldn't leave
> anything for volunteers to do which would be bad for new recruits. Even so,
> it's difficult to feel good when contributors are pinging you asking why
> their patch isn't reviewed in a couple days or weeks. I've tried to
> emphasis that *anyone* (except the patch author) can review patches and
> mark the ticket as "ready for checkin", but there are still many more code
> contributors than patch reviewers these days.
>
>
>
> If I were starting as a new fellow, I would set up a separate email
> account for all my Django activity so that I don't see those notices in my
> personal mail on evenings and weekends.
>
>
>
> I grew tiresome of teaching new contributors. Most regular contributors
> submit high quality patches that are generally easy to review but most new
> contributors don't take time to read our style guide and follow the patch
> review checklist. Only a very small number of contributors become regular
> contributors and sometimes I've thought that the effort to teach new
> contributors who don't stick around is very inefficient. I guess this is
> fine as long as fellows recognize that their job is partly educational.
>
>
>
> I could write more but I want to put something out before Friday. If
> you're thinking of applying and have a question or doubt, please ask.
>
>
>
> *
> https://www.djangoproject.com/weblog/2018/dec/21/django-fellow-applicants/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/184aa8ec-69f4-4b79-9ea9-2a555c2fc75e%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/184aa8ec-69f4-4b79-9ea9-2a555c2fc75e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/ce8d083516834789b9af517449a4d268%40iss2.ISS.LOCAL
> <https://groups.google.com/d/msgid/django-developers/ce8d083516834789b9af517449a4d268%40iss2.ISS.LOCAL?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2g7OH4mieXRbzfyh%2BH9TR47HPsiQ1LKhUD1HRXF0nDvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to