OK, this is actually a long story, but I'm going to cut it short. (I'll try, anyway.) The story itself is more about people than about programming, but I wanted to put it to you guys and see what you think. Sorry for filling your timeline, but I had to get it out of my system...
Read as much to get the sense; after that I've given my main point in the final section.
XYZ is the school I graduated from this year. The school is an alternative one, focused on community-living and things like that. They have an "Open Library" which is basically open to the students. There is no permanent librarian sitting there; the students go and enter the borrows and returns into the library themselves. However, the software they are using is very old. I mean, it uses a MS Access Database, is written in .NET or something like that, and doesn't work on versions of Windows newer than XP (don't even ask about Linux!).
So, since I do programming as a hobby, they asked if I could design a new software for them. Which I did, using the latest but not (I hope) unstable-ly new. Python, Flask, MongoDB, and Material Design. It basically runs as a server, and you access it from the browser, like Koha and others.
Then the trouble began.
Basically, they weren't certain about my programming skills, so they called Foo and Bar to "manage" the project. Foo knows a bit of coding (C and the like), and used to help out when problems arose (and they did, frequently) with the old project. Bar used to work with databases (relational ones) some while ago. Both happen to be parents of children in the school—and the school also involves parents in several areas so they would be able to easily come and fix the program if something went wrong during the running.
But both Foo and Bar's experiences seemed hopelessly out of date. For example they didn't get Python's naming conventions, and wanted models to be designed like
class UserGroup(Model):
group_name = CharField()
group_ordering_position = IntegerField()
...if you get what I mean. Furthermore, they didn't want to use MongoDB ("which is not even RDBMS"), and instead wanted models that Bar had designed, which, though they may be best for MySQL, already seemed to be using too many hacks in the planning stage itself. Stuff which Mongo does elegantly with lists and the like. Anyway, I said No, and we reached a compromise: the software is to work with both MySQL and MongoDB. The reason is that I was also putting it as an open-source project on GitHub, so I wanted at least other users to have the benefits of Mongo. This all caused a long delay when I couldn't code because I didn't know what database to code for.
Finally we restarted work. Then, Foo and Bar began wanting to see the code I was doing...and "understand" it. Looking at screenshots, they started giving suggestions like "make the model name show on top of the CRUD views", which I couldn't do just yet as I was still on backend logic and hadn't yet got to overriding the Flask-Admin templates. I think they were getting slowly getting put off because I wasn't following every single code-change they asked for.
To make it worse, they didn't understand the whole concept of DRY and OOP inheritance. So once, they were looking at the Flask-Admin-importing admin.py code on GitHub and saying "hey, I can't scroll down!"—and I was trying to tell them "there is no more to scroll down—that's the end of the file!" Finally they gave up saying they can't understand this code and they feel I'm not taking their inputs and there's too much time-constraints and they would look for alternative solutions and the didn't want my code any more. This is when it's almost workable—right up till the data import scripts!
I saved the links till the end so you get an idea of the history first. Here they are.
luna.)Foo and Bar are clear they don't want the code. The Librarian trusts their opinion as "software experts". If it was that simple, I would have said "no-go" long ago. But the thing is, I know the school. I know all the students personally (it's a small school), and I would have liked to give them a good software to work with. I wonder if there's any way of gently getting Foo and Bar to know their views are outdated and convincing the place to reconsider using the software?
Second point: I now have this semi-usable software as an open-source project. I'm thinking of stripping off the MySQL stuff, going completely Mongo, and focusing on completing it for others to use. But do you guys think it's still worth writing the software? Do you think someone out there will find it useful?
I've heard that an open-source project never really dies, and I hope the same can be said of mine ☹
Basically, they weren't certain about my programming skills, so they called Foo and Bar to "manage" the project.
Right here, is when you should of walked away.
If your trying to win "who's way of doing it is right"
Prove it - find articles, websites, etc... on the best practices of writing code in Python - schedule a meeting and nicely, show them the current code, show them the proof that you found to back up the way you did it. If their decent people, they'll understand and let you do it your way. If their stubborn, they'll push back (as they have) and you can deal with that then.
People are generally hired to do a job because the people hiring them think the person their hiring knows what their doing. If their questioning that, they may not be very knowledgeable in what you do (obviously, as many non programmers have a hard time explaining what a programmer does). People also get comfortable and don't like change. If they've worked with Foo and Bar in the past and they asked them to take a look at the code, they obviously trust their opinion. I don't think this has anything to do with you and your skill set - it's more on them and their lack of willingness to work with new people.
I now have this semi-usable software as an open-source project.
There are A LOT of schools across the world. Tens of thousands. Some formal; some alternative; some people home school; if you had a need for this, others might as well. Wether people know they have a need for it is a different issue and getting people to use it will fall to marketing, as any other project would. Will it hurt you to finish it / keep it on Github? So long as you have the time and willingness to work on it, I don't think so. If nothing else, it might look good on a resume. How far you want to take it is of course up to you.
If you really want them to use this software (free or otherwise) - remove your emotion from this equation. Finish up the software / make it look pretty / fix any bugs you can. Schedule a meeting and do a presentation. Explain the value of the software over the old software; perform a demo; explain how it will make this process easier and why you think it's the right way to continue. At this point, your a salesman - you need to sell them on the idea that what you've created works and works well and that they need it, free or otherwise. If they say yes and allow you to implement it / want to use it - great! If they say no - you weren't getting paid for it anyways. Chalk it up to a learning experience and move on.