Would `records` benefit from a backup maintainer

Similarly to tablib (see kennethreitz/tablib#329) records project could benefit from additional maintainer.

Facts:

• @kennethreitz is Development lead (184 commits)
• apart from that, nobody seems to be assigned as a maintainer
• commits:
  • @chadwhitacre has 11 commits
  • @hrldcpr and @mcdallas have 6/5 commits
  • @Tethik, @gdtroszak, @Brobin have 3 commits
  • other 5 contributors with 2 commits
  • 18 other contributors with 1 commit
• Issues: 47 closed, 34 open
  • 17 open issues younger than 12 month
• pull requests: 56 closed, 6 open
  • all are fresh (created by me)
  • last merged ones are from February (relatively not long time ago)
• last version 0.5.2 is from September 2017
• git repo has 4246 stars (versus 2917 at tablib). I do not have numbers from pypinfo (run out of free tier today)

To summarize:

• clear interest from users as well as from contributors
• development (resolving issues and accepting PRs) goes relatively well
• the biggest risk is, the project probably relies on only one (bright) person.

Proposal for next actions:

• @kennethreitz would you consider assigning backup maintainer or propose another option to make your great records playing well in long term?