{"action":"created","issue":{"url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/8","repository_url":"https://api.github.com/repos/fsharp/fssf-ask-the-board","labels_url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/8/comments","events_url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/8/events","html_url":"https://github.com/fsharp/fssf-ask-the-board/issues/8","id":315669874,"number":8,"title":"Communication Platforms for FSSF - Request for Feedback","user":{"login":"ReedCopsey","id":5280922,"avatar_url":"https://avatars0.githubusercontent.com/u/5280922?v=4","gravatar_id":"","url":"https://api.github.com/users/ReedCopsey","html_url":"https://github.com/ReedCopsey","followers_url":"https://api.github.com/users/ReedCopsey/followers","following_url":"https://api.github.com/users/ReedCopsey/following{/other_user}","gists_url":"https://api.github.com/users/ReedCopsey/gists{/gist_id}","starred_url":"https://api.github.com/users/ReedCopsey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ReedCopsey/subscriptions","organizations_url":"https://api.github.com/users/ReedCopsey/orgs","repos_url":"https://api.github.com/users/ReedCopsey/repos","events_url":"https://api.github.com/users/ReedCopsey/events{/privacy}","received_events_url":"https://api.github.com/users/ReedCopsey/received_events","type":"User","site_admin":false},"labels":[{"id":644082236,"url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2018-04-18T22:55:02Z","updated_at":"2018-04-23T17:14:03Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"# Description\r\n\r\nThe Board had a lengthy discussion related to the Open Communication (#7 issue), as well as other various issues related to Slack and the current community communication platforms. We would like comments and feedback on a proposal for how to move forward.\r\n\r\n# Motivation and impact\r\n\r\nWhile the F# Software Foundation Slack team has been a **huge success** in many respects, there are numerous disadvantages and issues with the current setup. In addition, recent changes have caused this to become even less ideal than in the past.\r\n\r\nMembers have repeatedly reported issues with the current setup, including:\r\n\r\n- Lack of history (10000 message limit)\r\n- Poor searchability\r\n- Technical issues with client/notification/etc\r\n- Difficulty in signups/high barriers to participation\r\n- Reliance on closed software platform(s)\r\n\r\nUnfortunately, the worst of these issues will only get _worse_ over time as more members participate. The 10000 message history limit already restricts us to less than a week of archives in many situations. In addition, SlackArchive, our current workaround, stopped working in Feb, and the developers have informed me that there are no definitive plans on when or if they will get it up and running again. This means that we currently have extremely limited history, which will get shorter and shorter over time, and no archiving.\r\n\r\nIn addition, over the last couple of years, we have had multiple members point out that \"chat\" is not necessarily the ideal medium for many discussions. Technical questions, for example, often function better in a threaded, more permanent and searchable form. \r\n\r\n# Proposed solution\r\n\r\nThe Board is proposing the following solution to these issues, which is based on two parts:\r\n\r\n1. Keep Slack as a real-time chat platform for Foundation members, but reorganize it internally to have fewer channels, and try to focus conversations on real time discussions, social interaction, and non-technical questions.\r\n\r\n2. Create a _public_ forum using [Discourse](https://www.discourse.org/) for technical questions and answers, as well as topics which would benefit from history/searchability over time. The Foundation would manage this, but it would be intended for the F# community at large to use, not just members\r\n\r\n# Drawbacks\r\n\r\nThe main drawback is that this will add \"yet another\" place to look for F# content. However, there are integrations which we could use to add notifications in the Slack team when topics are added in Discourse, which should ease this. \r\n\r\n# Other thoughts\r\n\r\nThese are some of the goals and concerns taken into account with this proposal:\r\n\r\n- Try to not disrupt the existing community\r\n  - Slack is generally working well for our existing membership\r\n  - Changing to a different platform would likely have huge repercussions, and potentially cause more issues than it'd solve\r\n- Discourse is a popular, fully open source option for the forum\r\n  - This would provide a means for people to participate who want open platforms\r\n  - Discourse provides fully retained history, with reasonable searching mechanisms\r\n- Make the forums open to the public (not member only)\r\n  - Discourse has reasonable community-driven moderation tools for flagging, etc, which should help with spam/Code of Conduct issues/etc\r\n  - There have been concerns with newcomers to the F# ecosystem who may be hesitant to become a member until they've had time in the community, which hopefully could be addressed by providing this platform\r\n\r\n# Specific Feedback Requested\r\n\r\n- Do you like this approach for the Foundation moving forward?\r\n- Have you experienced Discourse previously? Do you believe it would be a good fit for the Foundation?\r\n- Are there alternative platforms or approaches we should consider?\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/comments/383651998","html_url":"https://github.com/fsharp/fssf-ask-the-board/issues/8#issuecomment-383651998","issue_url":"https://api.github.com/repos/fsharp/fssf-ask-the-board/issues/8","id":383651998,"user":{"login":"ReedCopsey","id":5280922,"avatar_url":"https://avatars0.githubusercontent.com/u/5280922?v=4","gravatar_id":"","url":"https://api.github.com/users/ReedCopsey","html_url":"https://github.com/ReedCopsey","followers_url":"https://api.github.com/users/ReedCopsey/followers","following_url":"https://api.github.com/users/ReedCopsey/following{/other_user}","gists_url":"https://api.github.com/users/ReedCopsey/gists{/gist_id}","starred_url":"https://api.github.com/users/ReedCopsey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ReedCopsey/subscriptions","organizations_url":"https://api.github.com/users/ReedCopsey/orgs","repos_url":"https://api.github.com/users/ReedCopsey/repos","events_url":"https://api.github.com/users/ReedCopsey/events{/privacy}","received_events_url":"https://api.github.com/users/ReedCopsey/received_events","type":"User","site_admin":false},"created_at":"2018-04-23T17:14:03Z","updated_at":"2018-04-23T17:14:03Z","author_association":"CONTRIBUTOR","body":"In addition to @rbauduin 's negatives (which I think are all valid), I don't think the .NET Foundation forums are necessarily a good fit.\r\n\r\nI do wish there was more F# activity on there - I'd love to see more F# people regularly chime in on topics (as well as a couple of F# projects join the .NET Foundation! ).\r\n\r\nHowever, the purpose of the .NET Foundation forums is not \"general discussion\", they are for topics related to the Foundation itself. This is their own legal info, as well as categories related to projects within the Foundation, etc.  You can see this by looking at their [categories](https://forums.dotnetfoundation.org/categories) - there are no language specific categories (ie: no C# category), so I think it's probably not an appropriate venue for trying to use for general F# discussion.\r\n\r\nWe were at least hoping for a more \"general purpose\" F# discussion - where people could ask for help, discuss ideas, etc. That doesn't really line up with the purpose of their forums, so I think we're better off with our own."}}
{"actor":{"display_login":"ReedCopsey"}}