I’ve never been especially proactive in evangelizing swaks, but its usage number have grown to the point in the last 10 years that I think I probably am probably hurting users by not having more communication channels to receive and provide updates. So, here’s a quick breakdown of what channels exist right now, and where I want to go in the future
- Website – http://jetmore.org/john/code/swaks
- Update list – There’s no UI for this, but emailing email@example.com and asking to be notified of new releases will get you on the notify list.
- This blog. This is my personal blog, but I am maintaining a swaks category at http://www.jetmore.org/john/blog/c/swaks/. This category has a dedicated RSS feed at http://www.jetmore.org/john/blog/c/swaks/feed/.
- Twitter – http://twitter.com/SwaksSMTP
- Google+ - https://plus.google.com/u/0/110270727761256449657
- I don’t really have any desire to run a mailing list myself but there have been some requests for one (which I assume would be very, very low traffic).
- swaks.net – I own this domain, at some point in the future I think it makes sense for the swaks distribution to move to it.
- Trac – swaks’ “todo” list is not huge, and not especially hard to hold in my head, but I like the idea of Trac or something similar because of its ticket/commit cross reference and the timeline to help remember the history of the development. Not sold on this being worth the effort of maintaining yet.