This is not a way to have bug discussions, or record them. Do you really think I could find this information on a search for a similar issue?
Only thing that makes this bug and the process of the debug visible is this blog post.
Another point is I don't think IRC or any instant messaging app is the correct place for this kinds of discussions. Unless important points are logged to some bug reporting tool, or perhaps a mailing list, or to a blog post like this one, they are useless for historic purposes.
So there is nothing about being proprietary, but just about using IM?
I don't fully agree. IMs are a great place to discuss issues in a semi-synchronous way. Telecon or face-to-face meetings are sometimes better in velocity, but IMs have some edge on bringing random people happen to be online into the discussion. And it can also bring a different audience into the issue than bug reporting tools or mailing list.
When this issue was brought into the group, it just took several hours for curious people there to collaboratively find the conclusion. This is something unlikely to happen in any other form of discussions based on my experience.
But I agree that group chat is not a great way to record it, and that's why the findings are recorded on the GitHub issue, and group members also encouraged the author to write this up. Then it got posted on HN and on /r/rust by two different group members as well. (The author's initial posting on HN was mysteriously taken down, so the op here helped posting it again.)
Oh I missed the github issue. My bad. In fact I searched github and probably my github search foo was not good. Sorry to disregard that fact.
If these are already in place I don't have any reservations against using IMs or Discord. In fact this is particularly great sample how this can be done.
- Bug report is in place
- Blog/Article for historic events , documentation and pointers for related info
- Fast communication for debug sessions
I hope you understand my original message was about pointing out a situation where only left overs are history of these chat tools.
There are lots of communities right now just using discord or IM for support, bug reporting or development purposes.
Only thing that makes this bug and the process of the debug visible is this blog post.
Another point is I don't think IRC or any instant messaging app is the correct place for this kinds of discussions. Unless important points are logged to some bug reporting tool, or perhaps a mailing list, or to a blog post like this one, they are useless for historic purposes.