Bug 223095 - net/shadowsocks-libev: Maintainer absent without leave
Summary: net/shadowsocks-libev: Maintainer absent without leave
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks: 218294
  Show dependency tree / graph
 
Reported: 2017-10-18 14:12 UTC by Guangyuan Yang
Modified: 2017-10-23 09:39 UTC (History)
4 users (show)

See Also:
xiaoding+freebsd: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Guangyuan Yang freebsd_committer freebsd_triage 2017-10-18 14:12:16 UTC 
The maintainer of the port net/shadowsocks-libev seems to be inactive for quite a while. The commit message of the latest update of this port [1] shows:

"Approved by:	xiaoding+freebsd@xiaoding.org (maintainer, timeout >4 months)"

The maintainership should already be terminated since as stated in the Porter's Handbook, "If the maintainer does not respond within three months, or if there have been three consecutive timeouts, then that maintainer is considered absent without leave, and can be replaced as the maintainer of the particular port in question."

Also, the maintainer seems to have another timeout in the latest PR of the port [3]. IMO the maintainership should be removed from the latest patch to be committed [3], but it is up to portmgr@ to decide.

Thanks.


[1]: https://svnweb.freebsd.org/ports?view=revision&revision=448567
[2]: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html
[3]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218294
Comment 1 Mathieu Arnold freebsd_committer freebsd_triage 2017-10-18 14:20:50 UTC 
No need to involve portmgr on this. Maintainer timeout is 14 days, after 14 days, anyone can commit to a port.
Comment 2 Guangyuan Yang freebsd_committer freebsd_triage 2017-10-18 15:07:03 UTC 
(In reply to Mathieu Arnold from comment #1)

Thank you. I would like to know if it is appropriate to remove the current maintainer from Makefile MAINTAINER.
Comment 3 Sutra 2017-10-18 16:34:58 UTC 
(In reply to Guangyuan Yang from comment #2)
As far as I know, anybody could ask to take the maintainership if he/she like to, and the current maintainer approved or the current maintainer is absent without leave or no maintainer. Search "take maintainership" in this bugzilla to see a lot of cases.
Comment 4 Adam Weinberger freebsd_committer freebsd_triage 2017-10-18 23:46:07 UTC 
(In reply to Guangyuan Yang from comment #2)

Not at this time, no. The rule is 3 consecutive timeouts, or if *this* timeout is 3 months. This will be the second timeout.
Comment 5 Guangyuan Yang freebsd_committer freebsd_triage 2017-10-19 02:18:36 UTC 
(In reply to Adam Weinberger from comment #4)

Thanks for clarifying this. Will close this issue for now.
Comment 6 xiaoding+freebsd 2017-10-23 09:39:17 UTC 
Apologies for being late.

It's OK to take port ownership from me if anyone would like to. Due to my personal reason, I may not have enough time maintaining this port. I will be glad to see this port is being well maintained by the community.

Thanks!