> > I haven't used the Chapel IRC, so my only thought would be is the > conversation worth logging? >
Want to respond to this bit, as it’s an excellent question. We use (Russel plug your ears) Slack at my office quite extensively. One reason we chose Slack was because of the “channels”. We have several based on several topics. Two of which are “Fresh Pot” and “Engineering”. Fresh Pot is centered on announcing coffee-related activities, like Regina just put on another pot and thank God for her. There is almost no reason to save the material in here. “Engineering” is the expected channel. This is certainly worth saving, it became the collected intelligence of when and why certain systems have gone down, which ports on the VPN are being opened / closed and a large library of code snippets under discussion. We search the history of that channel frequently. There is plenty of chit-chat on Engineering as well, but it doesn’t get in the way when you need to find something. I am often on the Chapel IRC and I feel there are certainly bits that should be preserved. This would be much more true if there were more people discussing code and design. However, it’s not used very often. Having the IRC as an additional could be extremely useful if (a) it was more populated and (b) the internal Chapel team used it more for discussions. Right now the habit seems to be to break out into 1:1, which means no casual listening. My feeling is that with more use (under our control) and a good search index, it would be worth saving. ~~~~~ May All Your Sequences Converge ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
