kennethreitz/records

Would `records` benefit from a backup maintainer

Open

#144 建立於 2018年4月15日

在 GitHub 查看
 (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:

  • 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?

貢獻者指南

技術棧
python
領域
database
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.