sontek

haha, that was the first thing I said. Obviously not a curated list because anything AWS maintained is not a good place to start your OSS journey

I was surprised to see AWS projects at the top of the list. In my experience contributing to anything maintained by them isn't a great time for first timers.

I think you are confused here because kubernetes is heavily subsidized but the kubernetes providers:

- https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1

It is opensource so there is still a lot of volunteer work going on there but the infrastructure (CI/CD, image hosting, etc) is also paid for by corporations and not by the community. Its millions of dollars a year in contributions.

Is this supposed to be like Zapier but embedded in the product more tightly?

I'd love the opportunity to opt-in to a severance package! Can start interviewing over the next 3 months and then have paid time off before you start your new gig.

I really love this tool:

https://github.com/jesseduffield/lazygit

Which seems to be an alternative

Its because there is no free/OSS alternative that is as good.

- Good RBAC controls for managing your community and making sure there aren't bots - Nice API access for building bots - Free without any necessary system administration overhead

Discord is just an easy to get into system to start a community without any large commitment on hosting.

Having FIPS validated Rust Crypto is great and all but I'm mostly excited about pure rust Crypto :)

Updating the status page in the middle of the incident is always an art. Sometimes you can truly define impact and update the status page without weak language but other times you can't.

You still want to notify customers they may be seeing issues even if you aren't confident on the percentage of impacted customers yet.

https://www.booksloth.com/ is a goodreads alternative that doesn't suck

Being good at using terraform is very different than being an opensource maintainer and community builder.

  I'd love to emphasize that many of us tried to contribute to Terraform in the past, but HashiCorp became somewhat hesitant to review and accept PRs which massively slowed down innovation for Terraform.

Do you have links to PRs people from your organization pushed that weren't reviewed/accepted by HashiCorp?

  Trust the foundation that takes over the project

But part of the value the foundation is pitching is that it has companies donating engineering time to keep the project well managed.

My concern is spacelift and some of the other companies have no track record of being GOOD at opensource. Not as part of the terraform community or opensourcing things they've built in-house.

  we support our employees working on open source during their Friday projects

This is very different than hashicorps model of paying people to work on the opensource project during their working hours. Making it a core part of their job.

If we are to accept that the OpenTF foundation is going to be a better maintainer of terraform we need something better than "Hack on opensource if you want to!"

Spacelift doesn't have a good track record of contributing to opensource so the current model isn't working.

Also, Jacob started OctoSQL before ever joining Spacelift so its pretty odd to use that as an example of spacelift doing OSS well. Especially since his activity on his has tanked since joining you.

I'm concerned that people who do not have a provable track record for contributing to terraform believe they can fork and be good stewards of the project. Looks like the top contributors to the foundation are:

  - https://www.scalr.com/ - https://github.com/Scalr
  - https://gruntwork.io/  - https://github.com/gruntwork-io
  - https://www.massdriver.cloud/ - https://github.com/massdriver-cloud
  - https://spacelift.io/ - https://github.com/spacelift-io
  - https://digger.dev/ - https://github.com/diggerhq

Gruntwork and Digger do some decent opensource but the others haven't been great stewards of opensource. Looking at their githubs they don't seem to give much of anything back. So why should we trust them over hashicorp?

Nice, this looks close to https://terramate.io/ stacks

Whats the difference between this and vcluster (https://github.com/loft-sh/vcluster)?

What do you mean we aren't on the same page? These are two options when opensourcing things:

- GitLab went with Open Core and kept most of their features closed source and not available to the community

- Companies that choose BSL provide all their features to the community both from a source available standpoint AND a usage standpoint.

In my opinion BSL is a MUCH better place to be in than the open core model.

I just responded with the same thing but think you said it in a better way!

https://news.ycombinator.com/item?id=36971490#36973675

This is open source to most of us. I can read the code, use the code, and contribute to the project. I don't care if I can't make a SaaS offering of it.

All the features they exclude from the MIT code base and only include in the The GitLab Enterprise Edition...

https://about.gitlab.com/pricing/#compare-options

There is a box for "Open Source - MIT License". You'll notice most of the features are not covered under it.

Practically speaking from an enduser standpoint who:

- Likes to self-host stuff for homelab purposes

- Has business needs for shipping self-hosted services in airgapped and on-prem solutions where SaaS isn't available.

Every piece of BSL licensed software that I run (CockroachDB, Couchbase, MariaDB, Sentry, etc) are all open source to me. I can read the code, I can contribute, and I can track changes being added by others.

Your metaphor doesn't hold up because from an user standpoint this IS opensource. I'm not creative enough to come up with a good metaphor but it'd be something closer to:

"I've created a community book collection that anyone is free to take from. But you aren't allowed to take the books and sell them"

GitLab is a good example of not actually opensource. They are open corse which is much worse than BSL. There are tons of features they don't allow you to use even if you self-host unless you purchase a license.

BSL lets you use all features and self-host as long as you aren't a reseller. It is the best model I've seen.

    And there are other situations in which a constant connection to the cloud might not be preferable

I know this is only discussing the few places where constant connectivity is still rare such as airline travel but there are plenty of times where I'm on a limited connection. Such as being throttled on AT&T at concerts, at the mall, etc.

I'd love to see more applications built in a "local first" manner where I'd be able to do what I need without thinking about the throttling and they just sync my changes when its possible.

I hate when my connection drops and slack says "Couldn't send!" and forces me to decide when to retry... just hold on to my message and send it when you see connectivity again!

I have more experience running large MySQL databases. Both at SurveyMonkey and Zapier our primary databases were MySQL and were massive as you can imagine from massively scaled consumer products. I won't list the data here since this is about postgres but wanted to provide the context.

The largest postgres I've personally administered is on RDS:

  * postgres 13.4
  * db.m6g.2xlarge (8vCPU, 32 GB RAM)
  * 1.3tb storage
  * Largest tables: 317GB, 144GB, and 142GB

I effectively treat this database as an analytics database and write massive queries with joins against those largest tables and postgres handles it just fine.

I have had random bad query plans when using CTEs that get cached and take down the entire DB for a bit but usually been able to fix it with `vacuum analyze` and the customizing the query to convince postgres to choose a better plan.

Overall I think postgres can do a lot of work with very little.

Start-ups in general don't have a lot of cash and burn rate is the death of most of them. The standard deal from YC is $500k. So if they pay $80k/yr after operating costs, insurance, etc. They can probably hire 3 people outside of themselves and only be able to do it for 1 year.

If they competed with companies who are paying at the 90th percentile they wouldn't even make it a year if they hired 1 person.

I had no idea who David Peter was but drilled in and saw "sharkdp" and was like, YES! THANK YOU SO MUCH!

I love the work he has done and glad I clicked into this even though I never learned his real name.

This is awesome! I utilize `nix` on Linux and Mac but I haven't "drank the kool-aid" so I utilize `nix profile` and a makefile:

https://github.com/sontek/homies/blob/master/justfile

Fleek basically replaces my hacked together work flow with something that I'd actually utilize on a daily basis! Nix shouldn't be an all or nothing thing and this is one step closer to making it a generally available set of technology.

Looks like the author posted it over here:

https://news.ycombinator.com/item?id=35540566

Another article I saw on HN awhile back where someone did this:

https://webapp.io/blog/postgres-is-the-answer/

I think its a reasonable option and the webapp.io people scaled it out pretty high. At Zapier we utilize RabbitMQ heavily and I cannot imagine scaling the amount of tasks we handle each day on postgres.

This article mostly is lesson learns and misconfigurations of RabbitMQ though. Which is probably a good reason to simplify if you don't need its power. No reason to have to learn how to configure it if postgres is good enough.

In my annual review: "You need to think about your audience with your communication.

Then Twitter to all contacts that will clearly publicize anything they say:

    We contacted Twitter about the lawsuit today. The company continues to auto-reply with a poop emoji to all requests sent to its public relations email address.

I use just and it is amazing.