[CHAOSS] Opening discussion on using Discourse Forum for CHAOSS

Jocelyn Matthews jocelyn at storj.io
Mon Nov 12 03:38:43 UTC 2018


actually upon further inspection, I think the person who told me RC offers
a forum was just confused. There is a RocketChat forum, but it is actually
just a Discourse that is used to discsuss RC as a topic. I'll mark this
mystery solved for now!

On Sun, Nov 11, 2018 at 7:35 PM Jocelyn Matthews <jocelyn at storj.io> wrote:

> I totally agree about chats vs forum, especially for tihs use case. rm
> I've been told that RocketChat also offers a forum-type solution, but i
> havent been able to find out much about it.
> I do hear consistently good things about Discourse however
>
>
> On Sun, Nov 11, 2018 at 6:04 PM Georg Link <glink at unomaha.edu> wrote:
>
>> Thanks for the initial responses.
>>
>> @Daniel: I agree with your requirement that "archives can be browsed
>> without any further credentials". Mailinglist archives cannot be navigated
>> by topic, but Discourse can, making it more accessible.
>>
>> @Jocelyn: I liken Rocket Chat to a chat program (IRC or Slack) and
>> Discourse to a forum (phpBB). I personally prefer the organization of
>> conversations within Discourse and have a hard time keeping up with chats.
>>
>> @Emma: I agree with your assessment regarding Accessibility and Open by
>> Design. I would appreciate if you can make the connection to someone who is
>> more experienced with Discourse.
>>
>>
>> The conversation continues. I invite your to share your opinion.
>>
>> Best,
>> Georg
>>
>> On Sun, Nov 11, 2018 at 4:38 PM, Emma Irwin <eirwin at mozilla.com> wrote:
>>
>>> I Georg,
>>>
>>> Thanks for raising this question. When I think of communication,* I
>>> think less of what the majority prefers, but more of what will bring more
>>> voices, and contributors. * Assuming that is a shared goal across all
>>> of CHAOSS, this good chance to put into practice our the principles of
>>> inclusion this project is leading in open source through the D&I working
>>> group.
>>>
>>> I'm currently organizing my thoughts this way:
>>>
>>> 1) *Accessibility* - from a usability standpoint, but also for
>>> non-native English speakers, and those with bandwidth, or limited access to
>>> technology, screen readers)
>>> 2) *Open by Design*  - can people easily find (including lurking), read
>>> and contribute to discussion? Are we aware of topics or discussion that
>>> might require 'safe spaces' , where those topics might result in trolling?
>>> Can community members co-create discussion experiences (i.e. flagging
>>> inappropriate content )
>>>
>>>
>>> *For Accessibility, some measurements might be:*
>>>
>>>    - Ease of translation for non-English Speakers
>>>    - Accessibility review including screenreaders
>>>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.comprend.com_blog_2017_test-2Dyour-2Dwebsites-2Daccessibility_&d=DwMFaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=P2SSJg6nDRqSw6MK6ZVW76NaDtv69G3wvyOnOxwzqv0&m=Km5fyjVbgpJSRs3IXbaHGzbr4LZ-ATCMnOYKHzOBfu0&s=VMjmBKOxNFEMthk-OYvYMDSbSZXb3-xshKH8Lu0r-KY&e=>
>>>
>>>
>>> *For Open by Design*
>>>
>>>    - Ability to read archives without logging in (allows people to lurk
>>>    and access the community, for various reasons )
>>>    - Ability to provide secure channels for sensitive discussions, or
>>>    those that might put an individual at risk (happy to explain (off-list)
>>>    scenarios offline, about why underrepresented people don't engage in open
>>>    source forums on specific topics for fear of trolling/threats).
>>>    - Strong Moderation tools
>>>    - Acceptance to our Code of Conduct as part of joining/posting .
>>>
>>>
>>> Discourse sends email, that functionality is provided by both.   We've
>>> been using Discourse at Mozilla for a while now, being intentional about
>>> centralizing communication channels with Discourse has been very positive.
>>> And I can  introduce you to someone who can share more detail benefits, and
>>> challenges of that work (instead of learning on our own ).
>>>
>>> My preference is for Discourse knowing it does better in the categories
>>> I've listed.  Also personal peeve, I hate 'trying to find the right mailing
>>> list'.
>>>
>>> On Sun, Nov 11, 2018 at 8:53 AM Georg Link <glink at unomaha.edu> wrote:
>>>
>>>> Hi CHAOSS community,
>>>>
>>>> I invite you to discuss whether we should start using Discourse and, if
>>>> so, how we want to go about it.
>>>>
>>>> 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.
>>>>
>>>> Discourse agreed to sponsor free hosting for us:
>>>> https://discourse.chaoss.community/
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__discourse.chaoss.community_&d=DwMFaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=P2SSJg6nDRqSw6MK6ZVW76NaDtv69G3wvyOnOxwzqv0&m=Km5fyjVbgpJSRs3IXbaHGzbr4LZ-ATCMnOYKHzOBfu0&s=51F6ZVg_UglxniGGCu86Y3bV-MsPGZfHYEcrlwKx3xY&e=>
>>>>
>>>> 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.
>>>>
>>>> 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?
>>>>
>>>> I open the discussion with my opinion:
>>>> 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.
>>>>
>>>> Best,
>>>> Georg
>>>>
>>>> --
>>>> Georg J.P. Link
>>>> PhD Candidate
>>>> College of Information Science and Technology | PKI 367
>>>> University of Nebraska at Omaha | www.unomaha.edu
>>>> _______________________________________________
>>>> CHAOSS mailing list
>>>> CHAOSS at lists.linuxfoundation.org
>>>> https://lists.linuxfoundation.org/mailman/listinfo/chaoss
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.linuxfoundation.org_mailman_listinfo_chaoss&d=DwMFaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=P2SSJg6nDRqSw6MK6ZVW76NaDtv69G3wvyOnOxwzqv0&m=Km5fyjVbgpJSRs3IXbaHGzbr4LZ-ATCMnOYKHzOBfu0&s=_QlPTLfNaBvuz0UEVily9PMymuqY-NgLjthzUvLX1Zw&e=>
>>>>
>>>
>>>
>>> --
>>> Emma Irwin (she/her)
>>> Community Development
>>> Open Innovation Team
>>>
>>
>>
>>
>> --
>> Georg J.P. Link
>> PhD Candidate
>> College of Information Science and Technology | PKI 367
>> University of Nebraska at Omaha | www.unomaha.edu
>> _______________________________________________
>> CHAOSS mailing list
>> CHAOSS at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/chaoss
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/chaoss/attachments/20181111/2b2e095f/attachment.html>


More information about the CHAOSS mailing list