Solved E-Mails to port maintainer are bouncing

J

jbo@

Developer
I've (tried to) e-mail the maintainer of an existing port to get some information regarding plans/schedules/expectations/roadmap information on updating the port to the latest version available from upstream. However, the e-mail bounces back. I've already tried to contact the same port maintainer several months ago with the same result.

What's the standard procedure for a situation like this?
 
jbodenmann said:
What's the standard procedure for a situation like this?
Click to expand...
Post the issue to freebsd-ports@ mailing list. This probably needs a maintainer timeout, then the maintainer might get reset if the original maintainer doesn't respond. Sometimes maintainers change email addresses and sometimes maintainers just go AWOL.

www.freebsd.org

Policies of the Ports Management Team: Maintainers and Committers

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org
 
When posting to the ports mailing list, I assume that I can bluntly name the maintainer / maintainer's e-mail given that this is public information anyway?
 
I think that should be fine. Make sure to mention the specific port too. Maintainer may have changed email addresses but forgot to update the port with the new address, that sometimes happens.
 
This is something I meant to ask/investigate for a while now but didn't: Can one post to a mailing list and receive replies to that thread without actually being subscribed to the list itself?
 
jbodenmann said:
Can one post to a mailing list and receive replies to that thread without actually being subscribed to the list itself?
Click to expand...
No, I don't think that's possible. But it's a nice list (I do maintain a port) to keep track off. Volume is not as high as you might expect. And you could always unsubscribe again when the issue has been dealt with.
 
If the maintainer already got three time-outs[1] in a row he/she can (and should) be removed at any time, and the port can then be assigned for you (or somebody else) to maintain, or returned to the pool.

[1] the time-outs are supposed to be logged on the commit messages.
 
You must log in or register to reply here.
Back
Top