GPLv3 doesn't prevent anyone from using the covered software. Rather than adding a TODO item onto the list of the person who has already gifted this to us, where that item would involve the labor of enumerating over a set of scenarios, composing a response to you, and hoping that it answers your question, how about helping both them and yourself by inverting the workload and elaborating on what you mean? So, given that the GPL says these things, and the author has selected the GPL for this project, by a reasonable guess the answer to your question is, 'people who would otherwise do/not do those things'. Gratis or for a fee, You must make sure that they, too, receive or can get the source code If you distribute copies of such a program, whether We wish to avoid the special danger that patents applied to a free program could make it effectively proprietary In particular, wrt 'whom are you trying to prevent from using this', it mentions things such as: GPLv3 has an elaborate preamble, which should be able to answer some of your questions. There have always been big players in this market (Microsoft, IBM, Salesforce, etc.) It is good to see smaller players coming into their own in recent years, and this specific one is open source, which is a nice differentiator between it and many others. Low-code CRUD builders with DB integration and some basic workflow, reporting, and security now have hit that mark. You need to build the tool AND have some unique perspective and value prop that escalates it above all the others. to the point that it is no longer a unique value prop to just build a tool that solves problem X. The same has occurred over the years in multiple niches - a tool that would have been a terrific SaaS at one point gets built out, normalized, and well understood. That heydey lasted a couple years before Wordpress and other such tools came around and basic CMS was more of a solved problem than a unique product. I feel like low-code apps like this have hit commodity level.Ī bit of history - in the late 90s, you could (and we did) build a multi-million dollar product doing basic content management for plain old web pages. That's nice, and probably a good focus for a project like this.Įd: as for mocking/integration testing apis - which might be useful here, there's 'vcr':

The others appear to be empty scaffolds (which imnho is worse than no tests, really), eg:Ĭlass FoldersControllerTest and I have recently setup Cypress for component testing

Open source filemaker pro alternative