- From: Brian Kerr <brian@kava.io>
- Date: Mon, 04 Feb 2019 19:49:41 +0000
- To: "David Fuelling" <fuelling@ripple.com>
- Cc: "Bhaves Shah" <bhaves.shah@jabjabgroup.com>, "Daniel Carroll" <daniel.carroll@secureblockchains.com>, "Yuriy Dybskiy" <yuriy@dybskiy.com>, ledger@ietf.org, public-interledger@w3.org, "Akash Khosla" <akhosla@berkeley.edu>
- Message-ID: <jrqqwvey.76189ccf-446b-4fed-b06b-1299c4fbcd4c@we.are.superhuman.com>
If we want to expand the community, I definitely would recommend switching to something that isn't forcing people to learn a new app. Adding the hurdle of that will hurt on-boarding and engagement. I'd recommend slack or discord because most people already have the apps and are familiar with how to use them. Brian Kerr Co-founder Kava.io On Mon, Feb 04, 2019 at 9:30 AM, David Fuelling < fuelling@ripple.com > wrote: > > +1 for Slack. As a 2nd choice I would support > https://www.discourse.org (0x forum and chat use that and it seems nice). > > > Agree we need to move off of Gitter. > > On Mon, Feb 4, 2019 at 3:49 AM Akash Khosla < akhosla@berkeley.edu > wrote: > > > >> Gotcha, in that case I'll move the Hyperledger side to bcc to avoid >> confusion - this is focused on the Interledger working group which >> regularly uses Gitter. >> >> On Mon, Feb 4, 2019 at 2:30 AM Silona Bonewald < sbonewald@linuxfoundation.org >> > wrote: >> >> >>> Hello, >>> >>> >>> Silona the VP of community architecture for Hyperledger here >>> >>> >>> I'm afraid this is something we cannot change easily. All of the projects >>> at Hyperledger need to be on the same chat system. >>> >>> >>> Http://Chat.hyperledger.org which is rocket chat. >>> >>> >>> Please follow Ry"s directions earlier about creating an LF ID. A Linux >>> foundation ID. Hyperledger also is a project under the Linux foundation >>> and we also adhere to some of those standards as well. >>> >>> >>> As a community and especially quilt bring an interopability tool has to >>> work within the larger community of Hyperledger. We have a unified >>> standard. You can read up on the Hyperledger project process more on the wiki.hyperledger.org >>> ( http://wiki.hyperledger.org ) >>> >>> >>> Thank you, >>> Silona >>> >>> On Sun, Feb 3, 2019, 23:25 Daniel Carroll < daniel.carroll@secureblockchains.com >>> wrote: >>> >>> >>>> >>>> It would likely be good to have a couple of different platforms. >>>> >>>> >>>> I like Discord and Telegram for community chat and general sharing of >>>> information. But both are limited in how you can breakdown information >>>> into categories and maintain a logical history. >>>> >>>> >>>> I like Slack and Trello for grouping chunks of data within a team >>>> attempting productivity. >>>> >>>> >>>> Dan >>>> >>>> On Feb 3, 2019, at 9:47 PM, Bhaves Shah < bhaves.shah@jabjabgroup.com > >>>> wrote: >>>> >>>> >>>> >>> >>> >> >> >>> >>>> >>>>> I assume when looking at the community at large we want a solution that is >>>>> seccure in nature and also has the feature set to grow as the community >>>>> grows, although cost could be an issue later.. >>>>> >>>>> >>>>> You may want to check - https://flock.com/ >>>>> >>>>> Cheers! >>>>> Bhaves >>>>> >>>>> On 4 Feb 2019, at 10:36 AM, Yuriy Dybskiy < yuriy@dybskiy.com > wrote: >>>>> >>>>> >>>>> >>>>>> Akash, really great proposal! >>>>>> >>>>>> I've been using Discord more and more lately so I'm definitely +1 on that >>>>>> one. >>>>>> Rocket.chat ( http://rocket.chat/ ) is built with Meteor and I used to be a >>>>>> huge fan of it so I'm +1 on that option as well :) >>>>>> >>>>>> >>>>>> Discord might be the easiest to setup and more polished so slight >>>>>> preference there, but long term maybe Rocket.chat ( http://rocket.chat/ ) is >>>>>> a better option. >>>>>> Curious what others think. >>>>>> >>>>>> On Sat, Feb 2, 2019 at 7:02 PM AKASH KHOSLA < akhosla@berkeley.edu > wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> >>>>>>> I was wondering if there would be any interest in moving from Gitter to >>>>>>> another platform. The main reason I bring this up is because Gitter could >>>>>>> be out of the way for a lot of us and the application doesn't encourage >>>>>>> dedicated usage. Email lists are a bit old school and signing up for the >>>>>>> Interledger one is out of the way. I think the reason for such a cryptic >>>>>>> interface for the w3c style/linux foundation emails list is sybil >>>>>>> resistance and anti-spam since there are liberal write permissions to the >>>>>>> lists. I think scaling the community requires something better than email >>>>>>> and Gitter. Would be great to hear thoughts on this. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Couple problems with Gitter: >>>>>>> * Clunky interface >>>>>>> * Poor separation of conversations/rooms >>>>>>> * Bad search function >>>>>>> * Bad mobile app >>>>>>> >>>>>>> >>>>>>> Some alternatives I think users enjoy using, and are well known in dev >>>>>>> communities: >>>>>>> >>>>>>> >>>>>>> *Rocket.chat ( https://rocket.chat/ )* >>>>>>> Pros: >>>>>>> * Open source chat (basically a friendly IRC replacement) >>>>>>> * Self hosting is free, cloud options available, easy to deploy with >>>>>>> scripts >>>>>>> * Slack-like interface >>>>>>> * Good search functionality >>>>>>> * Threads ( >>>>>>> https://github.com/RocketChat/Rocket.Chat/pull/11803#issuecomment-455963816 >>>>>>> ) are being implemented >>>>>>> * Usable mobile applications >>>>>>> * Actively maintained + marketplace integrations >>>>>>> * Can deploy at chat.interledger.org ( http://chat.interledger.org ) (would >>>>>>> be happy to help). >>>>>>> * Easy sign in with GitHub, just like gitter. >>>>>>> Cons: >>>>>>> * Not as well known as discord, slack or gitter from what I can tell, but >>>>>>> I expect it to continue to grow in usage down the line and gain even more >>>>>>> support than it already has. >>>>>>> >>>>>>> * >>>>>>> * >>>>>>> *Discord* >>>>>>> Pros: >>>>>>> * Commonly used >>>>>>> * Free to use unlike sack >>>>>>> * Fast and friendly >>>>>>> * Solid mobile apps >>>>>>> * Actively maintained >>>>>>> * No self hosting or maintenance >>>>>>> * Supports integrations >>>>>>> Cons: >>>>>>> * May not be free forever >>>>>>> * Chat logs are owned by Discord >>>>>>> * More complex interface than Slack/Rocket (some colleagues and I describe >>>>>>> it as heavier >>>>>>> >>>>>>> >>>>>>> This list may not be complete in terms of pros and cons so please chime in >>>>>>> if you have a personal preference or have something to say about these >>>>>>> platforms or others. I've spent some time with both alternatives, you can >>>>>>> generally find demos on their corresponding websites to see what you like >>>>>>> best. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Akash Khosla* >>>>>>> Fourth Year EECS >>>>>>> akhosla@berkeley.edu >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> >>>>>> Yuriy @html5cat ( http://twitter.com/html5cat ) Dybskiy >>>>>> >>>>>> >>>>>> e-mail: yuriy@dybskiy.com >>>>>> phone: +1 (650) 434-2004 >>>>>> >>>>>> Dybskiy.com ( http://dybskiy.com ) / Twitter ( http://twitter.com/html5cat >>>>>> ) / GitHub ( http://github.com/html5cat ) / Linkedin ( >>>>>> http://ca.linkedin.com/in/dybskiy ) >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >>> >>>> >>>> _._,_._,_ >>>> Links: >>>> >>>> You receive all messages sent to this group. >>>> >>>> >>>> >>>> View/Reply Online (#85) ( https://lists.hyperledger.org/g/quilt/message/85 >>>> ) | Reply To Sender ( >>>> ?subject=Private:%20Re:%20Re%3A%20%5BHyperledger%20Quilt%5D%20Proposal%3A%20Switching%20from%20Gitter%20to%20something%20else >>>> ) | Reply To Group ( >>>> quilt@lists.hyperledger.org?subject=Re:%20Re%3A%20%5BHyperledger%20Quilt%5D%20Proposal%3A%20Switching%20from%20Gitter%20to%20something%20else >>>> ) | Mute This Topic ( https://lists.hyperledger.org/mt/29637867/1540173 ) | >>>> New Topic ( https://lists.hyperledger.org/g/quilt/post ) >>>> >>>> Your Subscription ( https://lists.hyperledger.org/g/quilt/editsub/1540173 ) >>>> | Contact Group Owner ( quilt+owner@lists.hyperledger.org ) | Unsubscribe ( >>>> https://lists.hyperledger.org/g/quilt/unsub ) [ sbonewald@linuxfoundation.org >>>> ] >>>> >>>> >>>> _._,_._,_ >>>> >>> >>> >> >> > >
Received on Monday, 4 February 2019 19:50:56 UTC