Show HN: We built a developer-first open-source Zapier alternative

Re:Show HN: We built a developer-first open-source Zapier al... by prepend on Thursday February 02, 2023 @07:49AM (#34625808)

I don’t see an ee folder or ee/LICENSE so according to their license, everything in their repo seems open source although annoying they did this instead of just a real OSI recognized license.

Not having install docs isn’t the end of the world if I can figure it out and contribute back. But I don’t want to waste my time if it’s not actually open source and my work will be commercialized by a single org.

I don’t mind contributing for everyone to do whatever (including commercialization) but am not into doing free labor for a profit enterprise.

[ Parent | on HN ]

Re:Show HN: We built a developer-first open-source Zapier al... by gpvos on Thursday February 02, 2023 @09:27AM (#34626902)

The wording suggests to me that there can be ee/ subdirectories scattered all through the directory tree, and there the different licenses apply.

[ Parent | on HN ]

Re:Show HN: We built a developer-first open-source Zapier al... by mattaitken on Thursday February 02, 2023 @11:09AM (#34628562)

All the code that has been pushed so far is under MIT and we currently have no enterprise features (/ee folders). The majority of future code will fall into this same bracket.

Some features that are for "enterprise" will be put in /ee folders – ideally we will put all of that in a single /ee folder in the root but we wanted to cover the case where that's non-trivial to implement.

This open core model (that Gitlab use) is popular because it strikes a nice balance between having an open source project (good for everyone) and it puts off bad actors from building a commercial competitor with zero effort.

[ Parent | on HN ]