Create a Website to Chat Within Online about slick HOT 19 CLOSED

@Henne you mentioned you might be able to help here? :)

It would be cool if we can get Shout configured to make new people automatically join freenode with #opensourcedesign. And maybe even some other open source design channels (#drupal-usability, #wikimedia-design, #owncloud-design etc)

from slick.

Sorry I should have mentioned in the title of the issue -- a Web Chat

from slick.

@una
The idea is great but i think shout add some complexity.

Here is my point of view :

• People here have all a GitHub account
• They want to talk simply without create another Login / password

Gitter is perfect for that https://gitter.im

What do you think ?

from slick.

We're working on an open source Web app to fix IRC for humans, but it's too young to use yet. You can follow our progress here: https://twitter.com/join67p

Until then, you can already use a simple IRC widget with the base tech we're using. There's a node.js open-source commodity server called Sockethub doing the connections, and talking to client-side apps/websites via JSON Activity Streams. We have a chat widget for embedding IRC in websites called Guppy. It's pretty easy to add and style.

Let me know if you're interested in this, and we can help you set it up. /cc @silverbucket

from slick.

@flexbox I'm hesitant to locking ourselves into Github, and also expecting all designers to have an account on Github, I'd prefer something open like IRC.

@skddc That sounds pretty exciting, I'd love to find out a bit more.

from slick.

@flexbox @simonv3 yeah, this idea is specifically about lowering barriers. We can’t expect all designers to have a Github account. Shout, with some modifications, makes for an easy way for anyone to join the #opensourcedesign chat via web.

from slick.

Would love to get insight from designers who don't have a Github account, but I do think it is reasonable to ask designers to create a free Github account to join the community.

Seems like a pretty small barrier that could solve more communication barriers in the future.

Getting designers onto Github is actually a solution in my opinion, even if they aren't pushing code.

from slick.

I agree with @jancborchardt. Creating an account is always a small barrier – in particular if people (here: designers) are not sure about the value of the service (github) for them.

@jancborchardt did you ever try/configure shout on you own node instance?

from slick.

@jdittrich @jancborchardt the service is free, however. I think ultimately, designers will need to create an account to have a say. It is similar to a message board in that aspect.

from slick.

@una @jdittrich @jancborchardt my concern also stems from the equating github (a not opensource but for-profit company) with opensource software angle. It's not a huge issue, I love the service they provide, and I think they do it really well, and the majority of OSS is hosted on it, but I feel like saying "you have to have a github account to participate in OSS" does send a message along those lines, whereas that's not the case at all.

On the other hand, for the sake of a minimum meaningful product, having a chat room now that's powered by gitter might be a good temporary solution while Shout is figured out.

On that note, what is actually blocking on Shout? *Edit: * if it's installing on a server, I'm happy to try to get something going on mine, but that probably wouldn't fall nicely underneath the current website, though we could probably propagate shout.opendesign.com to that.

from slick.

I'd rather see a "stackoverflowy" style website, so that communications stay searchable and relevant for the rest of the community. Askbot is a free such solution, or we could just try creating a stack exchange site.

Just an idea.

M.

On Feb 24, 2015, at 2:26 AM, Simon [email protected] wrote:

@una https://github.com/una @jdittrich https://github.com/jdittrich @jancborchardt https://github.com/jancborchardt my concern also stems from the equating github (a not opensource but for-profit company) with opensource software angle. It's not a huge issue, I love the service they provide, and I think they do it really well, and the majority of OSS is hosted on it, but I feel like saying "you have to have a github account to participate in OSS" does send a message along those lines, whereas that's not the case at all.

On the other hand, for the sake of a minimum meaningful product, having a chat room now that's powered by gitter might be a good temporary solution while Shout is figured out.

On that note, what is actually blocking on Shout?

—
Reply to this email directly or view it on GitHub #1 (comment).

from slick.

I think this is about text/live chat, not link sharing and commenting.

from slick.

Today @bnvk indicated that http://chat.opensourcedesign.net may someday be an IRC bridge to a http://matrix.org client but in the meantime I suggested pointing http://chat.opensourcedesign.net to https://kiwiirc.com/client/irc.freenode.net/opensourcedesign

I find that kiwiirc client to be a better user experience than https://webchat.freenode.net/?channels=opensourcedesign , which is where http://chat.opensourcedesign.net points right now.

It would be an easy change to make for now. Longer term I'm interested in seeing if the Matrix idea works out.

from slick.

Okay, after testing out, they both have similar functionality -- so its not a huge deal, but I do like the kiwiirc interface better. So, I agree with @pdurbin about pointing http://chat.opensourcedesign.net to https://kiwiirc.com/client/irc.freenode.net/opensourcedesign :)

from slick.

@pdurbin @una @jancborchardt @skddc @simonv3 just a lil update where I'm at with this ;)

I've been working quite a bit on exploring options towards this goal and contributing to various projects like the matrix client and Shout IRC. The former is a bit too rough in terms of amount of dev needed + user adoption to justify building on top of it just yet. The later is very close to being good enough and with tad bit more hacking will be.

I hope to work & improve upon Shout to expand the robustness of their theme-ing feature as then what is useful for our little community will be useful to other communities while being based on open + free IRC instead of using Slack.

from slick.

This has finally been setup at chat.opensourcedesign.net so I'm closing this issue and will track other more design improvements to Slick in separate issues!

from slick.

from slick.

@qwazix there you go:
opensourcedesign/organization#70

from slick.

from slick.