> Dify is licensed under the Apache License 2.0, with the following additional conditions ...
I am totally fine with closed-source/commercial licenses, but please don't do a "Like Apache 2.0 but not really" type of license. It just confuses everyone.
You can pick from SSPL, BSL, Elastic license among others if you don't want to roll out your own.
> 2. As a contributor, you should agree that: a. The producer can adjust the open-source agreement to be more strict or relaxed as deemed necessary.
b. Your contributed code may be used for commercial purposes, including but not limited to its cloud business operations.
This is not very contributor-friendly.
You could consider keeping an open-source core, and extensions for paid features.
You've put it way too politely IMHO. It's a license designed to attract contributors to help build their product for free, but leaves space for them to just re-license the product and sell it when the opportunity arises. It's not like we haven't seen this play already, and it hurts both contributors and users...
Wow I've never seen so many fake accounts on a HN post before. So then is it fair to say the Github stars for this project could also perhaps be artificially inflated? This month they started to go exponential: https://github.com/langgenius/dify?tab=readme-ov-file#star-h...
Well, I think a lot of the uptick happened last week because that's when it was published in the Toughtworks Tech Radar for this quarter. The audience is large, presumably larger than HN, and that's how I found out about it and have been toying with it since then. I have no idea what I'm doing, but as far as I can tell, this seems like a legitimate project.
I created insights for the last 4 weeks and number of new contributors and stars peaked last week. This project has all the signs of a successfully organically grown project.
Very slick and potentially very powerful. After a few minutes playing with it, I have a few recommendations:
- Variables should have more types, like an array of objects
- Prompting should incorporate Jinja2/Nunjucks
- For every prompt, I should be able to create many different test examples, along with an answer key, and measure how well it does across many tests
- It should auto-save. I did a lot of prompting work and then clicked another icon. When I came back, all my work was gone. (In fact, I don't see where to save at all! Maybe I'm just missing it.)
what we're trying do with Dify currently is to let people put together prototypes quicker and either get to production or fail at a faster rate.
we've seen it being helpful for non-technical folks to collaborate on a project well (e.g. importing documents for knowledge base, creating no-code workflow apps, etc)
Cool! Thanks for sharing. It explains why this type of ui is being used so often. Building this from scratch isn’t the hardest thing in the world, but I can imagine it is somewhat of a challenge to get just right
Yeah, that's kind of weird - Apache, except totally not Apache. They probably meant to do a source-available license with free non-commercial use allowing inbound contributions - makes sense for a startup, but... please get a lawyer and clean it up :).
I am totally fine with closed-source/commercial licenses, but please don't do a "Like Apache 2.0 but not really" type of license. It just confuses everyone.
You can pick from SSPL, BSL, Elastic license among others if you don't want to roll out your own.
> 2. As a contributor, you should agree that: a. The producer can adjust the open-source agreement to be more strict or relaxed as deemed necessary. b. Your contributed code may be used for commercial purposes, including but not limited to its cloud business operations.
This is not very contributor-friendly.
You could consider keeping an open-source core, and extensions for paid features.
reply