[crossfire] Remove or keep contact email addresses from map headers?

[Nathaniel Kipps]

Personally, I wouldn't want to be in the position of trying to
determine whether some contact method is valid or not, so I would not want
to be directly involved in such a project.

I suggest first implementing a policy ("No contact info in future map
headers, only internet handles"), then confirm if you want to retroactively
apply such a policy to existing mapfiles.

--DraugTheWhopper

On Fri, Jun 16, 2023 at 1:37 PM Rick Tanner <leaf at real-time.com> wrote:

>
> Hello,
>
> While working on numerous maps, I have noticed that some map authors
> (and/or map editors) included a contact email address in the map header.
>
> Nearly all of these addresses are no longer valid. For instance, some
> are University (College) addresses. And, many are from people I have not
> "seen" online in many years.
>
> Given the different methods of communication we now have available -
> IRC, Discord, and the mailing list -- those are the preferred ways to
> reach out to a map author for questions, comments, discussion, etc.
> instead of direct emails to the author.
>
> Does anyone have any concerns in regards to removing the email addresses
> from the map headers?
>
> If there are no issues or concerns, I will take care of updating all the
> maps to remove this content. To give this discussion some time, I would
> look at starting to make this change in 2023-July.
>
> Thank you.
> _______________________________________________
> crossfire mailing list
> crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire
> IRC: http://crossfire.real-time.com/irc/index.html
> Discord: http://crossfire.real-time.com/discord/index.html
> Project Site: https://sourceforge.net/projects/crossfire/
> Wiki: http://wiki.cross-fire.org/
> Website: http://crossfire.real-time.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.metalforge.org/pipermail/crossfire/attachments/20230618/05e70d12/attachment.htm>