News for hackers. Stuff that matters.

A comment on Please don't use Slack for FOSS projects. Parent comment

Re:Please don't use Slack for FOSS projects by nilkn on Monday February 01, 2016 @01:10PM (#11013768)
> Also, the article is trying to make you aware of a fundamental reason to NOT use slack for FOSS -- it's closed source.

Surely this suggestion can only seriously be made for projects that are also not hosted on GitHub.

[ Parent | on HN ]
Re:Please don't use Slack for FOSS projects by hardwaresofton on Monday February 01, 2016 @01:19PM (#11013866)
This is a good point, and the case can certainly be made that source code hosting should be done on sites that are powered completely by FOSS.

Neither Github nor Bitbucket (I use bitbucket more than github) are open source.

The shining hope is the darkness is Gitlab (https://about.gitlab.com/) though, which is a wonderful tool. That, and someone with deep enough pockets to start a publicly hosted gitlab that everyone in FOSS can use.

[ Parent | on HN ]
Re:Please don't use Slack for FOSS projects by scbrg on Monday February 01, 2016 @06:18PM (#11016453)
Not that I know much about Slack, but by using GitHub you don't give up control over your repository, or its history. Every single project member has a fully working copy that can be used if GitHub for some reason decides to go rogue, and it's accessible through open source software.

How about your communication in Slack? Can it be withheld or otherwise become inaccessible, or is it completely accessible through open source tools and possible to export continuously to a useful format? If not, then there's quite a difference.

[ Parent | on HN ]