The Python Software Foundation acts as a fiscal sponsor for a much smaller set of orgs (20 listed on https://www.python.org/psf/fiscal-sponsorees/) and it keeps our accounting team pretty busy just looking after those. Hack Club must have this down to a very fine art.
I wrote a bit more about PSF fiscal sponsorship here: https://simonwillison.net/2024/Sep/18/board-of-the-python-so...
I was working with Hack Club students on an experimental VPN client (https://github.com/hackclub/burrow) but never got the momentum to finish it. Made some great friends, though! It's a really fantastic organization.
The students have one big global Slack instance. If you're a student and on here, you should also be in there: https://hackclub.com/slack/
[1] https://www.eff.org/deeplinks/2022/03/podcast-episode-hack-f...
The “understanding through building” mentality is something I never got to experience as a group, the obvious answer is open source and the like but I wonder if there’s something more learning oriented.
In any case, good luck on finding the right community!
>Yes, I'm a teenager ,18 and under
So not actually a teenager but a minor is what they mean and use what I would call deceptive language around it. But why?....
Are you back on Slack as the primary comms channel after their sudden attempt to upcharge you (followed by the U-turn after the PR backlash)? Do you have some mirroring and other kind of fallback strategy if something like that happens again?
(Context for those who missed it: https://news.ycombinator.com/item?id=45283887)
Hack Club's been a fiscal sponsor for about 7 years now (since 2018), and it's evolved quite a bit since the early days. I run engineering & product for the fiscal sponsorship program there and would be happy to chat/share any tips!
oh, and while it's on my mind, the codebase was open-sourced earlier this year (https://news.ycombinator.com/item?id=43519802), and we just launched a mobile app yesterday! https://news.ycombinator.com/item?id=46130402
It might have improved since then?
There was a devtools blackhole era once where if you got in that business you were just giving things away and never got to reap the rewards. Then there was this era of founders who figured out how to make it sticky and capture value in a Pareto-optimal way.
Love to see it.
The Rust Foundation is a 501(c)(6) and not a 501(c)(3). The Rust Foundation would do better for the community if they were a 501(c)(3) and more transparent about finances. Follow this example for the greater good.
So thanks, IBM! <3
That's part of what drew lots of us to HashiCorp in the first place - giving back.
"get asked the same about terminals all the time. “How will you turn this into a business? What’s the monetization strategy?” The monetization strategy is that my bank account has 3 commas mate."
https://x.com/mitchellh/status/1964785527741427940
Take a good guess where the three commas come from.
Even still, whatever high salaries they do give us just flow right back into the neighborhoods through insane property values and other cost-of-living expenses that negate any gains. So, it’s always just the few of us who can win that lottery and truly break out of the cycle.
(It'd be nice if it supported other standard macOS UI conventions[1] too)
[0] https://github.com/ghostty-org/ghostty/discussions/8131
[1] https://github.com/ghostty-org/ghostty/issues?q=is%3Aissue%2...
Seems I will wait a little longer before search is in the regular build (and not nightly ones)
I said in the linked post that I remain the largest donor, but this helps lay bricks such that we can build a sustainable community that doesn't rely on me financially or technically. There simply wasn't a vehicle before that others could even join in financially. Now there is.
All of the above was mentioned in the post. If you want more details, please read it. I assume you didn't.
I'll begin some donor reach out and donor relationship work eventually. The past few months has been enough work simply coordinating this process, meeting with accountants and lawyers to figure out the right path forward, meeting with other software foundations to determine proper processes etc. I'm going to take a breather, then hop back in. :)
(UWash CompSci strikes again, not that I'm biased)
Ghostty is blazing fast and the attention to detail is fabulous.
The theme picker is next level, for example; so are the typographical controls.
It feels like an app made by a craftsman at the top of his game.
Apple and Microsoft are the two most likely parties to do so here. This isn't a theoretical risk.
I'd honestly rather Apple and Microsoft ripped off my work if it meant that my work provided more utility to a larger number of people.
That "friction" is by design. It prevents someone else from screwing over the users.
The people that oppose copyleft are those it was specifically design to protect against.
Copyleft protects the user. The friction is, like you said, by design. It ensures that something that started free, stays free, and can't be rug pulled out from under you.
Big monied interests have been trying, and succeeding, in changing the discourse around free software away from free and to simply just "open source" and moving toward permissive licenses, specifically so community effort can be extracted and monetized without contributing back.
I can take a guess with respect to Linux: that's the kind of software where forcing companies to submit code back to it is enormously beneficial due to the need for an operating system to have drivers for vast ranges of different hardware.
You should watch his talk:
https://www.youtube.com/watch?v=MkJkyMuBm3g
(He used to be a maintainer of busybox, a GNU clone for embedded devices. He then ended up writing toybox, a similar project under the more free MIT license.)
And in some of those cases GPL wasn't enough to prevent it. Niche end user utilities, where original is available for free have little room for monetization. And in many cases existing users are already choosing the open source option despite the existence of commercial solutions, or where it's too niche for commercial solutions to exist.
Only thing that comes to my mind is VScode with all the AI craze. But that doesn't quite fit the pattern neither is the Microsoft underdog, nor it's clear that any of AI based editors derived from VScode will survive by themselves long term.
There are also occasional grifters trying to sell open source software with little long term impact.
VSCode is a proprietary fork of code-oss, the product located at https://github.com/microsoft/vscode. It might not be an example that you're looking for though.
Yeah, OpenAI has shown us that this is more negotiable than we might have believed. Fortunately nobody will ever think terminal emulation is a trillion dollar industry, so I think we’re ok.
FullStory namespace conflict. Please set window["_fs_namespace"]. script.pageview-props.tagged-events.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTUnderstand this error edge.fullstory.com/s/fs.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTUnderstand this error ghostty:1 Access to XMLHttpRequest at 'https://d3hb14vkzrxvla.cloudfront.net/v1/e3d6bbe1-aa48-43cb-...' from origin 'https://hcb.hackclub.com' has been blocked by CORS policy: Request header field beacon-device-instance-id is not allowed by Access-Control-Allow-Headers in preflight response.Understand this error installHook.js:1 Unable to Load Beacon overrideMethod @ installHook.js:1Understand this error installHook.js:1 $ overrideMethod @ installHook.js:1Understand this error d3hb14vkzrxvla.cloudfront.net/v1/e3d6bbe1-aa48-43cb-8f8b-be1e33945bab:1 Failed to load resource: net::ERR_FAILEDUnderstand this error [Violation] Potential permissions policy violation: payment is not allowed in this document.Understand this error rs.fullstory.com/rec/page:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTUnderstand this error 29[Intervention] Unable to preventDefault inside passive event listener due to target being treated as passive. See <URL>
Sorry about that! I've just pushed a fix for one of those errors. Although I wasn't able to reproduce this donation behavior on Chrome, I will continue investigating.
I appreciate you reporting this!