On Sat, Apr 11, 2020 at 2:08 AM Daniel Beck <m...@beckweb.net> wrote:
> > > On 11. Apr 2020, at 01:06, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > > > TBH if we use Slack for runtime communications only, even losing history > is not a big deal > > Strongly disagree. Even such conversations have a tendency to contain > useful information, I'm not interested in having to keep a text editor open > to save everything that'll be relevant in the future. I think it's also important then to discuss the role of the on-line communication tool. For me, an on-line communication tool serves the purpose of almost-real-time discussion on various subjects, agree consensus and/or decide on stuff. I do not think however it is the place to use as a documentation reference - in that sense every discussion holds "useful information" and having said that we should keep recordings of every Zoom meeting or anything else. For that purpose, there are Google Docs and GitHub and Jenkins Mailing lists that hold agreements, documentation, change proposals and any kind of "useful documentation", in a versioned and organised manner. For me the availability of on-line archive of online chats, whether it be IRC or Slack is not an argument for the tool, especially for the external communication - for internal communication of the core contributors, it might be different. Having said that, there is an Architecture standard for solving such stuff (similar to JEPs) that could be used to drive such decisions: https://adr.github.io/ https://iasaglobal.org/Public/TOPICS/Architecturally-Significant-Requirements.aspx Maybe we could prepare a fact and quality driven comparison of possible approaches to help agree whether a change is needed and valuable or not? Happy and safe Easter to everyone! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWjD97TaQ6Gks%3DEFJqaJ2%2BK1u9h2zTngzhYufaTxPTeg9w%40mail.gmail.com.
