Does this mean you're also hoping to expand into Delaware PBCs, too? Lots of open source projects are considering this approach due to a combination of poor response to open source nonprofits from the IRS and flexibility in figuring out their funding sources. There's only trivial differences to a C Corp in terms of filing.
I'd been planning to reach out to Stripe about this when it made sense; I probably should've just emailed you! We're advising folks we're bringing onto our Stripe Connect platform as managed accounts to go use Stripe Atlas where possible, but plenty have voiced support for having B Corps be part of that happy path.
Honestly, I might even just pay a lawyer at some point to open up some standardized set of docs for this.
Do you hope to have any way for Connect platforms with managed accounts to more directly refer people into Atlas? Having an API for the application process would be amazing.
Code Corps is intended to be a place to find and volunteer for open source projects you think are worth whatever free time you have. For maintainers, we'd like to make scaling your community trivial: acquire and retain volunteers, onboard newcomers, recommend the right tasks to the right people, and fund your operations.
As an aside, I'm kind of curious how others feel they fare on building new projects. Do you feel slow? I worry constantly about how quickly I'm moving relative to peers.
Stripe did introduce Stripe Atlas. Although this doesn't solve the situation totally, it's at least one of a number of helpful steps in the right direction.
If you want to register and run a us entity it helps but most people don't want that kind of hassle. I've done it from Canada and Australia and unless youre planning on getting us investors is probably not a good idea. Though I haven't accepted my atlas invite yet so not sure how much better it'd be.
Does anyone have resources on how one should design their changes to run side-by-side? I have not been at large companies and don't have the advantage of institutional knowledge to help here. Book, articles, and practical examples would be fantastic.
And since it's often hard to generalize, I work today with Elixir and Postgres. Anything specific around this stack would be exceptional.
I don't know if this helps, but reading up on backwards and forwards compatibility can get you in the right direction. The same concepts apply, but the details may very. For API interfaces read up on or think through best practices around overloading old fields, adding new fields, removing old fields, making them optional. I remember Acro had a "schema evolution" doc that talks through some of these concepts and they may apply to things you care about. For databases, I've seen updates staged as pre-commit, post-commit, and rollback patchs. Pre-commit modifies the database in a backwards compatible way -- for example adding new fields and mutating old fields into them if necessary. Code would be pushed live and could read the "old" or "new" way. After all the code is rolled out and there's high confidence the post commit would cleanup things left behind only for backwards conpatabaility reasons. Rollback only operated on pre-commit, post commit may be destructive.
For Elixir in particular, you should be using appups and relups if you want hot code reloading with the ability to instantly and safely fall back.
It's important to remember, appups and relups are themselves code that needs separate testing. Ericsson engineers spend as much time (if not more!) testing the relups as they do writing new code.
Do you mind sending me an email sometime? You can find one in my HN profile. I'm really curious to hear about what you've done to find maintainers and how you've thought about tackling the fundraising issue.
It's not on our immediate roadmap, but we have had some demand for it. We think we might go about it by building an Erlang SDK. Hopefully a light wrapper on that would work well from the Elixir side.
For the sake of high quality idiomatic code. I'd recommend creating the Erlang library and a separate Elixir one. But to be honest, I'm just so pleased to hear your even thinking if either of them :-D
