Just found this opensource.com article about Greenpeace becoming an 'open source' organisation. Quite ironic, since a few months ago I met one of their principal IT managers, who openly mocked our efforts to use #foss and #opensource IT in-house. Greenpeace relies 100% on Google's Gsuite. Any comparison with fair trade coffee was met with a "yeah but this is easier, we just don't care about Google's dubious side."
@Gina Interesting. You'd think if they can hit two birds with one stone they'd go for it, metaphorically speaking of course. Straight out mocking anyone trying to make a change is pretty low, but finding open source alternatives to proprietary solutions should be fun for an IT manager.
@vancha Well, I sort of get their point too. Greenpeace is a large organisation. And opensource / foss is hard. If you can just let someone else deal with all the IT for a non-profit price, why not do it? At the same time, as a world bettering non-profit I feel you also have some sort of obligation to critically assess all products and services that you use.
@Gina of course, no one forces them to use anything. It's just the mocking that seems out of place. If the conversation ended with "thank you for your advice, but we don't have the time or money to implement open source technologies to replace the software we already use", the situation would have been a lot different :)
Want to tell me who? I speak truth to power. Pushing open at Greenpeace has been a challenge. There are people at Greenpeace, just like any other organization, who don't get it. And there are people who do. I am an idealist, a believer, a woman in tech. I want Greenpeace to be better. I'm working my ass off trying. I won't apologize for that dude, but I will say - not everyone at Greenpeace agrees with that f'd attitude.
@Gina the author of that piece is part of a co-op with "open" in the name but their daily driver for collaboration is a Slack channel :/ It's not like there aren't free code alternatives, both hosted and self-hostable:
@tyil what about just using a SaaSS that uses free code under the hood, instead of #Slack? Something like:
* #Gitter.im - gratis, owned and hosted by #GitLab
* #Wire - free for personal use, with extended features for paying enterprise users.
* #Zulip - gratis hosting for free code and open source projects
> everybody knows it, so nobody needs to be taught to use it.
Classic #NetworkEffect problem ;) The only way out is for some brave and forward-looking users and orgs to lead the charge.
> I'd have to make a strategy in how to nudge people towards it first, and that will take time.
Of course. The longest journey starts with a single step :)
> One benefit I personally see in Slack is that I can use it with my favourite terminal chat client, WeeChat
I wouldn't count on that lasting. Slack have taken a number of steps to force users to use their Electron monstrosity, including cutting off IRC and XMPP (classic embrace, extend, extinguish):
@clacke ooh, good question. When GitLab acquired Gitter they said:
> we will open source the whole of Gitter
It's important to hold them to that. Their repos are here:
It seems like code for all the user apps is available under free licenses, but I'm not sure if the other repos there constitute the full backend yet or not.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.