Date
1 - 2 of 2
[Hyperledger Project TSC] hyperledger-tsc Digest, Vol 9, Issue 11
|
Mark Morris <markamorris2003@...>
Where can I find the genesis thread or conversation that started this abrupt suggested move to this Slack alternative called Discourse? True we need to replace Slack. We are not making a knee-jerk or biased decision are we? Because there are several alternatives and competitors to Slack. I've been away for a few days, so I ask, was this move put to the community for discussion prior to selecting this Slack alternative (I cannot find any prior conversation)? Was there a list and community voting? Or was this decided by the maintainers and Hyperledger authoritative members? I am asking these questions because I want to understand how decisions are made and where the proposals like these come from. I just want to understand the decision making dynamics within Hyperledger. Thanks.
On Tue, Oct 11, 2016 at 7:00 AM, <hyperledger-tsc-request@...> wrote: Send hyperledger-tsc mailing list submissions to
|
|
|
|
Todd Benzies <tbenzies@...>
Hi Mark, Thanks for the note -- all really great questions. At this juncture, we are simply evaluating Discourse (discuss.hyperledger.org) as a potential solution (we are not forcing an abrupt end to Slack, nor definitively moving forward with Discourse). We feel that it is important for the technical community to be able to "kick the tires" and test out a platform's functionality. But, given the limitations of Slack (and sometimes mailman lists) as raised by many in the technical community, we are hopeful to find a suitable solution to resolve any concerns. Discourse is not necessarily meant to replace Slack in its entirety, but there are many discussions happening on Slack (or mailman lists) that likely make more sense on a different platform (from searchability, transparency, and ease of engagement from the broader community). The initial discussion started in a variety of places, but was more formally raised in the Technical Steering Committee call in early September (and has remained on the weekly agenda, since). If you are not already participating in these calls, please do -- they are open to all. (Call-in details at https://github.com/hyperled The main concerns with Slack are a 10,000 message limit (which has made a vast amount of historical context unavailable), a paid platform that is unaffordable, as well as poor search functionality (and lack of threading). Discourse seemed to solve many of these concerns which led to us setting up this test instance. Obviously the real-time chat functionality of Slack remains important. Some discussion on this has since started at http://discuss.hyperledger. Ultimately we are trying to find a steady-state suite of tools to enable the community to operate efficiently and transparently, as well as create an environment that is easy for newcomers to navigate and get up to speed. Please have a look at Discourse and let us know both the good and bad on the thread mentioned above. We really value the feedback from the technical community. We will also discuss this in this week's TSC call. Regards, Todd
On Tue, Oct 11, 2016 at 10:36 AM, Mark Morris via hyperledger-tsc <hyperledger-tsc@...> wrote:
--
Todd Benzies Senior Program Manager The Linux Foundation +1 (415) 412-0310 (m) Skype: tbenzies
|
|
|