6,861 karma · joined February 1, 2016
Founder of https://n8n.io
n8n is an open and extendable workflow tool, enabling you to create powerful automations. With a fair-code distribution model, run n8n locally or in the cloud and augment with custom functions, logic and apps. n8n's node-based approach makes it highly versatile, enabling you to map anything to everything. https://github.com/n8n-io/n8n
Open positions: Full Stack Developer - Mid level/Senior, Technical writer intern
Yes would actually be perfect for it, but never had the time to set something like that up. Maybe someday in the future. For now, I only have a simple Google Alert set and regularly check HN and Google Analytics which is a good indicator when it got mentioned somewhere.
About the "robust" part. A startup I know had a lot of issues with Zapier and switched to n8n and are quite happy as they did not have any issues since. I am sure you are right and you did your research but would love to hear what exactly you are referring to as it will help me to improve n8n. The same with the limitations. Anything specific?
If you are unsure about if you can use it, simply explain what you want to do in an email to "license@n8n.io".
The goal with the license was not keeping people from using it. The main goal was to start it in a way to make the project long term sustainable which I thought would be in the interest of all people using it.
Also does not mean that people can never use it in a way which the license prohibits by default. It simply means that away has to be found which is beneficial to all sides. So just like anywhere in life.
I tried (apparently not successfuly) to write everywhere very clearly that the Commons Clause got applied and if somebody contributes to it he would normally have spend some time with the project and he should be aware of the license situation. Would never have expected that somebody would find out later that it is not the case and he would then be upset about it. But thanks, not sure that it would happen but still one more thing for me to consider (as you are right that it could happen).
The only reason I am hesitating is that I fear to confuse more people than I help. If people (including myself) would know what (actually had to look up the term again) "source-available" means I would have used it from the start. But nobody does. So the question is, is it worth confusing a big group of none-vocal-people to make a small group of vocal-people happy? But I can understand definitely understand their point. So have to decide on that the next days.
Sorry, can you elaborate? I invested probably around 1 year in writing n8n and I allow now everybody to use it for free (with the limitations discussed). I assume that over 90% of the people use it and I do not receive a single Pull-Request or Dollar (which is fine and I am totally OK with) and of the other 9% I guess they spend between a few hours to maybe a week in total in contributions (again also fine). Then there is probably less than 1% which does more than that. How am I asking for more than I give?
But also think debatting right now further about it would not really help. Will think about it at least a night (maybe more) to make a decision. Advice also the other side to do the same to see and understand my side. If the decision is that I change it. Everything is solved anyway. If my decision is to keep it we can proceed here:
Great to hear that the docs are helpful! They were actually the main reason why I did not launch on Product Hunt/Hackernews earlier. It was very important for me to have something in place which is at least reasonable. Nothing more annoying than bad docs. Anyway, still a lot on my list to add documentation for. But it will get better, I promise!
I can totally understand if a person says "I do not want to contribute code to a project for free when somebody else can make money with it". But then they can not contribute code to any OSI approved Open Source licensed project. Because with that license everybody can make money with it. And very often is that somebody the wrong one (like for example Amazon).
The only difference with the Commons Clause is that now still somebody can make money. But that somebody is now the entity behind the project. And they normally put that money right back into the project (by for example hiring developers) and make so sure that it improves and stays around a long time. So I personally would prefer to contribute code to a project which uses the Commons Clause then one which does not.