Rename kforge-user mailing list to kforge-announce

[rgrp]

Do not need 2 separate mailing lists for general kforge discussion. Therefore propose:

1. Renaming kforge-user mailing list to kforge-announce (see wiki:MailmanHowto)

• Write to all users indicating that in future this list will just be for announce emails and that kforge-user is deprecated in favour of kforge-dev

[johnbywater]

I know I agreed to this ages ago, but here are my current thoughts about this proposal: I don't think there are two lists for general kforge discussion. We have one list for public discussions about using KForge, and one list for public discussion about developing KForge. It's a common separation, and it's working, so I don't see much point fixing it. It appears we have made it clear to KForge users that they can both receive annoucements about new KForge releases and ask for help on the -users list. We have a growing archive of annoucements and supported inquiries, which is useful for both technical information and indicating the project is alive. So, if I may ask, please can the kforge lists be left alone, at least for the near term? There seems to be little upside, and quite a bit of downside.

I would agree that if the -user list gets too busy (e.g. like the django-users list), we would have cause to create a low-traffic -announce list. If we had more regular committers, or if tickets/commits were emailed to the -dev list, the -dev list would be used more.

So I feel it would be much better for spare admin effort to be directed towards getting emails for ticket changes and repository commits sent to the -dev list again.

[rgrp]

Following previous comment closing as wontfix.