-
Notifications
You must be signed in to change notification settings - Fork 28
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
suggestions #7
Comments
Hey @hyqneuron one thing that was suggested here: #5 is having each repo as a starting point for collecting relevant work, sources and such. I believe each project do have a google-group for now as well. Also, It could depend on each group's preference perhaps for different discussion different platforms can help. There might be a slack channel coming (I believe), but from experience (Gitter) has been a more open-friendly approach, while Slack could be slower for onboarding, though it has been used for more focused conversations. edit: @odellus, yup. A good case study is the Keras / OpenAI chat, that is open and can have back and forth conversation. Meanwhile as I mentioned earlier, for specific projects (in my experience, it comes down to the group) I do open research and we use tools like:
|
+1 for gitter over slack. |
I attempted to create a AION Gitter but ran into issues (bugs in the Gitter web API -- seems to be a frequent occurrence). Please feel free to create one yourself, if you can! |
Additionally, I would advise against using Skype. We should stay in touch via platforms that have free unlimited searchable archives of communications. |
Sounds good! I will add it to the Main Repo + Site as well. Hopefully this can be used for topic discussions and as an open communication style 😄 edit: Thanks @cicobalico , I'm adding it to the main repo as well in a bit :). |
Gitter link seems to be broken |
@cicobalico https://gitter.im/ai-open-network/Lobby seems to work for me. Maybe Gitter was down |
try this link ᐧ On Wed, Oct 26, 2016 at 5:12 AM, Michele Moretti notifications@github.com
|
The text was updated successfully, but these errors were encountered: