2026-08-27 16:39 UTC
Replies (4)
-
@MrJico@infosec.exchange 2026-08-27 19:40
@codingjoe@fosstodon.org when i was a team lead, i made it very clear for the team and the owners that we will be spending time on open source, so either give the money or the time, sometimes it was money, sometimes bug fixes or community work, also when hiring although very far and few of them, i was always looking for talent who had an interest in open source, it saddens me to say we where not using Django so none of it made it there, but for other frameworks we have landed many patches and closed many issues, by sheer will power 😅. P. S: Management doesn't really see the point but you have to convince them somehow.
-
@codingjoe@fosstodon.org 2026-08-27 16:40
And yes, being profitable enough to make an meaningful and lasting impact its already on the list ;)
-
@nanorepublica@indiehackers.social 2026-08-27 17:16
@codingjoe@fosstodon.org I'm thinking guaranteeing time per month/week to do the OSS work. Also baking it into the job description and hiring is possible for what the project needs given enough overlap with the company work. Last year Thibaud mentioned to me that Django could do with some paid security work, not sure if that's changed for the better yet. Also the Open Source Pledge is worth a look in terms of monetary amounts per dev.
-
@adamchainz@fosstodon.org 2026-08-27 17:41
@codingjoe@fosstodon.org blog about what you do in such a way as to encourage more companies to do it. Peer “pressure” works. Also helps when someone wants citations to provide to their boss why they should be allowed to fix an upstream bug or sponsor a project or whatever.