I think it’s time we create a coalition of open source projects that band together and re-license in a way that requires that companies fund their dependencies. In my proposal, I’m trying to maintain as many of the freedoms of free software as possible (to run, study, modify, distribute), while adding simple license terms that force companies that use and make money off of the software to give back.
Let me know if you have any questions or feedback, I’d love to make something work for a wide spectrum of projects!
Congrats on the launch! I’ve been following this project and I’m really excited to see how much it has matured. For projects currently on GitHub, what’s the best way to migrate? Is there a mirror mode as we test it out?
Thanks! There is no mirroring built-in yet, though this is something we're looking into. It should theoretically be as simple as setting up a `cron` job that pulls from github and pushes to radicle every hour, eg.
In addition, in order to migrate your GitHub issues to Radicle (which the above doesn't cover), there's this command-line tool [1] that should get you most - if not all - of the way there.
Migrating GitHub Pull Requests (PRs) to Radicle Patches is somewhat more involved, but that should still be possible (even if it involves some loss of information along the way, due to potential schema mismatches) ...
The main value capture at Github is issue tracking, PR reviews and discussion. Maybe not today, but is there an automated way to migrate these over in the future?
I’ve been using Plasmic for the last 6 months to build rich featured Dapps in the web3 space. It takes some time to import all the React components I need but once you do, it is really incredible how much this speeds up my development. We now have non-developers (like designers and PMs) regularly shipping entire features to production without developer help. Really takes some of the pressure off the engineering team while drastically improving team velocity.
Just for fun during the ETHDenver hackathon, I shipped an LLM-powered NFT generator, with 0 lines of code in 3 hours, and won a cash prize. This tool completely changes the game for me and my team.
Hi there! OP here, very open to feedback and questions. Because there doesn't seem to be a single canonical way to do localization in React, I got stuck down a rabbit hole of exploring all the different options (and there are many!). Here's a write up of my findings, which I hope might be useful to someone else in the planning stages. In other words, you haven't already decided you want to use a particular library, but want to see at a high level the pros and cons of different approaches (e.g. i18n libraries, CMS'es, automated services etc).
On the other side of this, it's fascinating how often people fall susceptible to arguing why something should or shouldn't exist for someone else, rather than just making a limited statement about utility for themselves. Something to stay cognizant of, this article is a good lesson on empathy!
Hi everyone! Author here. Happy to answer any questions or take any feedback.
I was inspired to write this post when exploring all the many different ways to do implement personalization, and realizing just how powerful Next.js middleware is. So I thought I'd share some of those learnings and a step-by-step guide on how to actually implement it. Totally changed the game for me, makes it so easy to make custom content for different segments while maintaining high performance for my site.
If you live in California, I recommend getting involved in your local housing element. This program will have huge implications in how zoning and development occurs in the state for years to come.
https://www.hcd.ca.gov/community-development/housing-element...
Here's an interesting notion -- that a lot of wisdom is simply bound up in the integral over time of personal life experience.
Thus, the value of wisdom is individual, and non-transferrable -- it can neither be carried "backwards over time", nor handed over to another human via a "brain dump".
The best one can hope for, is to distill personal lessons from our own experience (compute that integral), and invite others to sample it (no guarantees that it'll stick in any way, but their journey might be similar, allowing them to compute their own integrals faster, by seeing our own).
I think it’s time we create a coalition of open source projects that band together and re-license in a way that requires that companies fund their dependencies. In my proposal, I’m trying to maintain as many of the freedoms of free software as possible (to run, study, modify, distribute), while adding simple license terms that force companies that use and make money off of the software to give back.
Let me know if you have any questions or feedback, I’d love to make something work for a wide spectrum of projects!