OhMyForm
-
I've only just started looking into Mautic - and have to say, very impressed - and the form builder in there is decent, plus nicely guides you through CRM orientated data collection.
Just noting here in case anyone hasn't tried, looks well worth working with that to centralise data because any separate form-builder still needs the data processing and you might find Mautic inspires good practice with those submissions and responding to them.
-
Just to add, Nextcloud now has a forms app too, and so people waiting for OhMyForm might want to have a play with that (especially if you're already using Nextcloud anyway).
-
Just adding OhMyForms and Oh My Form and Oh My Forms here to make this easier to find!
Oooh, it's getting close to 1.0
Currently on 0.99
https://github.com/ohmyform/ohmyform/releases -
Oooh, it's getting close to 1.0
Currently on 0.99
https://github.com/ohmyform/ohmyform/releases@jdaviescoates Will be the killer application of all survey industry?
-
@jdaviescoates Will be the killer application of all survey industry?
@p44 I'm not sure about that, but it does look like a nice self-hosted alternative to Typeform
-
@p44 I'm not sure about that, but it does look like a nice self-hosted alternative to Typeform
@jdaviescoates We will see
Meanwhile I hope that this app will be part of Cloudron kit -
@robi It seems the dev isn't interested in learning new things and simply expects a PR.
-
@robi It seems the dev isn't interested in learning new things and simply expects a PR.
I think that's expected. Upstream authors generally have way too many things on their hands. My impression is that in most cases, the "packaging" is usually done by people outside the project. Not even talking about Cloudron here but things like packaging for ubuntu/redhat/centos or some other platform. The Dockerfile's that are usually in upstream repos are also mostly targeted at development rather than deployment.
-
@robi It seems the dev isn't interested in learning new things and simply expects a PR.
I think that's expected. Upstream authors generally have way too many things on their hands. My impression is that in most cases, the "packaging" is usually done by people outside the project. Not even talking about Cloudron here but things like packaging for ubuntu/redhat/centos or some other platform. The Dockerfile's that are usually in upstream repos are also mostly targeted at development rather than deployment.
@girish True, especially about authors being inundated .... although I suspect that them saying "it's targeted at development" is usually cop-out for something like :
-
"I'm a developer, don't expect me to finish things completely, it works here"
-
"I'm a developer, don't expect me to write documentation, it's obvious if you read the code"
-
"I'm a developer, I develop things, I moved on to something else"
I'm not being rude (well, not intentionally). It's just my experience of running software projects and a software house for 15 years. Love developers, awesome people, wish I could do what they do, but <guesstimate> 70% fall in one of the above categories.
-
-
@robi this is normal! please be nice to open source devs, they do a lot of work for free. It's understandable they don't want to learn a packaging system they don't use.
-
Has anyone looked at getting this packaged?
Something has come up that would make this very useful right now.
@robi I think the idea was to wait for 1.0. My plan was to mention the app dev group once that happens
-
Currently 4 issues away from 1.0
