[Slackbuilds-users] nginx maintenance

[B. Watson]

On Sun, 1 Sep 2024, David Chmelik wrote:

> Please do so!  Once a friend took over one of my SlackBuilds but wanted 
> to leave my name & information as the maintainer, and not add his, due 
> to SlackBuilds being copyrighted, and did so for at least one update. 

We'd rather people not do that.

> After I asked and the original creator finally agreed to switch to WTFPL 
> my friend was finally willing to update to list his information.  Among 
> FLOSS programmers, I doubt he's the only person that dislikes copyright,

I hate the need for it. But you were right to ask the original author,
instead of just changing the license without permission.

> so we need to clarify if it's not allowed to leave the burden on the old 
> maintainer as the official contact person and not have people even know 
> you took it over.

If the old maintainer could "bear the burden" of being the contact
person and maintaining the script, there wouldn't be any need for a
new maintainer. When you take over a build, you leave the previous
maintainer(s) names in the comments at the top of the script, to give
them credit... but *you* are the contact person, if it's your script
now.

I tend to remove the old maintainer's email from the comment, to avoid
him getting unwanted email. If someone *really* needs to contact the
original author for some reason, there's always the git history.