Would `records` benefit from a backup maintainer · kennethreitz/records#144

(2 评论) (0 反应) (0 负责人)Python (7,057 star) (578 fork)batch import

help wanted

描述

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:

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?

技术栈: python
领域: database
议题类型: feature
难度: 2
预计时间: under 1 hour
活动状态: stale
清晰度: clear
前置要求: 无
新手友好度: 20
研究方向: The issue proposes adding a backup maintainer to the records project, inspired by tablib (kennethreitz/tablib#329). It highlights that the project currently relies solely on @kennethreitz. To move forward, the maintainer should consider assigning a co maintainer. There are no code changes required; the focus is on project governance. The issue has not seen recent activity, so reactivating it with a plan might be necessary.