Re:Please don't use Slack for FOSS projects
by rimantas on Monday February 01, 2016 @01:56PM
(#11014274)
You should also be aware, that not everybody buys into RMS's ideology, nor does it make sense for everyone. Also, the guy dos not have a monopoly on FOSS.
> Very disappointed in the level of understanding of these
> things on hn lately.
Re:Please don't use Slack for FOSS projects
by davidw on Monday February 01, 2016 @02:00PM
(#11014315)
I don't buy into it either, and spend my days working on proprietary stuff. But I use a ton of open source projects, and pretty much everything I do interacts with open source protocols, like HTTP.
Re:Please don't use Slack for FOSS projects
by st3v3r on Monday February 01, 2016 @05:37PM
(#11016177)
" Let's say you want a good chat app but it needs to be secure, and you don't want to trust another company (slack)."
Counter-example: What if I don't care about that?
Re:Please don't use Slack for FOSS projects
by arca_vorago on Monday February 01, 2016 @07:53PM
(#11016971)
I don't understand questions like this at all. Is it not completely obvious that if you dont care about the that then go right ahead and do whatever you want? What are you even asking for? Seriously, what kind of reaponse do you imagine can even be given?
Qnd thats not even a counter example... Its just... Lazy.
1. Freedom the run the program, for any purpose. 2. Freedom to study and change the program (source code required) 3. Freedom to redistribute copies. 4. Free to redistribute your modifications. (source code required)
For the kind of people who frequent hacker news, I would expect you to be familiar with these very basic principles of software ideology. If you disagree with them, that's fine, but let's not pretend that proprietary is anywhere close to FOSS in the realm of freedom. Sometimes you must sacrifice functionality and usability to use FOSS, and that's a choice that only you can make, but what I don't want is you making that choice for me because you don't understand the basic ideas of software freedom.
On the subject of Slack, I can give you a quick example of this. Let's say you want a good chat app but it needs to be secure, and you don't want to trust another company (slack). So obviously you want to self-host internally right? Oh, sorry, no source code, no self hosted version, too bad, fuck off and wait until slack releases a self-hosted version. Oh, and if they do, and you want to implement your own internal feature X, too bad, fuck off, you get what you are given.
Very disappointed in the level of understanding of these things on hn lately.