It's not HN-speak. A "post-mortem" can be a scheduled part of development, even if a project succeeds. It's just a review after the project (or milestone) is declared complete. It's for finding lessons to apply to future projects, since it's too late for the current project :)
Sorry to hear. I think it's admiring to see how you tried to build a product, but lack of selling/marketing always creates a bump in the road to a successful product.
We're currently using Slack. It supports both IRC and XMPP, has a webinterface and bouncers. It also gives you more detailed stats about the users, has integrations with other services and so on: https://slack.com/r/024fus8f-02566qu1 (shameless referral link.. k, thx, bye).
4 comments
[ 4.6 ms ] story [ 21.0 ms ] threadFirst known use: 1846
(next to "Party leaders are conducting a postmortem of the election to try to find out what went wrong.")
We're currently using Slack. It supports both IRC and XMPP, has a webinterface and bouncers. It also gives you more detailed stats about the users, has integrations with other services and so on: https://slack.com/r/024fus8f-02566qu1 (shameless referral link.. k, thx, bye).