But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted