News for hackers. Stuff that matters.
Re:Why Slack is inappropriate for open source communications by Arzh on Tuesday April 11, 2017 @05:26PM (#14092612)
Why do you want a chat client to integrate with gitlab or jenkins?
Re:Why Slack is inappropriate for open source communications by aiiane on Tuesday April 11, 2017 @06:30PM (#14093115)
Oftentimes the 'sync' conversations are either triggered or resolved by commit/build events.
Re:Why Slack is inappropriate for open source communications by Arzh on Wednesday April 12, 2017 @11:41AM (#14098759)
Do you mind expanding on this and showing a full flow? That sounds a little wonky to me but I could be missing something.
Re:Why Slack is inappropriate for open source communications by frikk on Wednesday April 12, 2017 @01:31PM (#14099799)
Our flow is like this:

1) Person pushes to dev branch

2) Chat log shows the feature pushed

3) Chat log shows Jenkins received push and is downloading

4) Chat log shows whether tests were successful (yay) or not (boo).

^^ that's the basis. It helps keep everyone up to speed on what's going on, especially for testing.

One more example: Notifications when merge requests are made / merged in the chat.