-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communication #71
Comments
I'm ok with Gitter though. At madewithlove we use slack, but I don't mind using Gitter. It keeps an archive and sends email notifications if you are mentioned. What do you need more? |
Just a few thoughts:
|
If you want me in, i also use slack so this is painless for me |
Slack channel created. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey guys,
I have been thinking about if we could improve the communication. Github issues are awesome, but we could do better. Since this is the first time for me to be part of such a large group (I usually did things alone so far), I only have a few guesses how it could be done in an organized way. If any of you have better ideas, I am open to them.
So we have github issues. Great, but sometimes direct communication would be better.
We have a gitter room, but let's admit: noone really wants to use yet another communication channel.
I was thinking about slack. In theory, it can be made public as well using slackin.
Other possibilities: email, skype, twitter.
So what do you think guys? What do you use at FOS/Made with Love?
The text was updated successfully, but these errors were encountered: