<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">My opinion:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">- we should let the working groups use whatever tools they want, as long as:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"> - the communications are archived, and the archives can be browsed without any further credentials</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">- for general communication, we should continue to use email</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Nov 11, 2018 at 8:53 AM Georg Link <<a href="mailto:glink@unomaha.edu">glink@unomaha.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hi CHAOSS community,</div><div><br></div><div>I invite you to discuss whether we should start using Discourse and, if so, how we want to go about it.</div><div><br></div><div>Background: The CHAOSS project is evolving and over the last 1.5 years, we created new mailing lists and abandoned others. We also use GitHub repositories and weekly calls on different days to separate out conversations. From the beginning, we discussed using a flexible forum software, like Discourse, to satisfy our evolving communication needs. In the past, we opted for simplicity but are now hitting the limits.</div><div><br></div><div>Discourse agreed to sponsor free hosting for us: <a href="https://discourse.chaoss.community/" target="_blank">https://discourse.chaoss.community/</a><br></div><div><br></div><div>On this week's call, a question was asked about email-compatability of Discourse: Everyone can watch topics on discourse and receive email notifications. Responses can be sent via email.<br></div><div></div><div><br></div><div>One concern with using Discourse is that we divide the community across more communication channels. The question is, what is the overall communication strategy within our community? What role does each communication channel (mailing list, IRC, GitHub, Discourse, weekly calls) have?<br></div><div><br></div><div>I open the discussion with my opinion:</div><div>
Discourse allows us to create new categories (like email lists), use
tags, and have an organically evolving structure while maintaining all
benefits of mailing lists. I think we can transition from email lists to Discourse.</div><div><br></div><div>Best,</div><div>Georg<br></div><div><br>-- <br><div class="m_3451117995702561406gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Georg J.P. Link<br>PhD Candidate<br>College of Information Science and Technology | PKI 367<br>University of Nebraska at Omaha | <a href="http://www.unomaha.edu" target="_blank">www.unomaha.edu</a><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div></div></div>
_______________________________________________<br>
CHAOSS mailing list<br>
<a href="mailto:CHAOSS@lists.linuxfoundation.org" target="_blank">CHAOSS@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/chaoss" rel="noreferrer" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/chaoss</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--dmg<br><br>---<br>Daniel M. German<br><a href="http://turingmachine.org" target="_blank">http://turingmachine.org</a><br></div>