New release? Maintainers needed or?

[decentral1se]

From https://github.com/Grokzen/pykwalify/releases/tag/1.7.0, I see:

38 commits to master since this release

I am wondering if there is a plan to make a new release? Also, since that release was some time ago, I am also wondering about maintainership status of this project? This project really solves a need for me and I would like to see it go on.

(More of a general question, apologies on scrapping the issue template...)

[Grokzen]

@decentral1se Dont worry about the issue template, they are there for code specific issues.

Yes i think i can pull together a minor release and push it out to get out the latests commits that is not yet published. Looked through the delta and it dont look that big or bad/much to release out.

The other main thing is that i dont really know what i want to do with this project right now and what direction i want to move it in. The main reason for that is that the original idea of this project was to have a kwalify compatible python runtime for that specification and language and not to continue to develop and make one of my own, because what i have ended up with now in the end is that most feature requests and things people want to be included is the same things and solutions already existing in all other validation languages including the most used one JsonSchema. So i figured that what the point is to implement all of them here when they are already implemented and probably better implemented over there. And on top of that, in the end the only difference would be that i support partials, includes & can load yaml kinda (maybe there is more stuff but that is the more common ones mentioned). Also factor in to this that i need to keep backwards compatibility with kwalify that was the original idea and not to skew the language to much with new features that would in the end drop the original work in favor of a new improved validation language.

One of my big features that i wanted to implement but never did was to build two different generations of the language and move back the original kwalify into a v1 language and make any new additions ontop of kwalify into a v2 and then make a full refactor and rebuild of the language into a v3 language where all new features would end up into something new that would not keep kwalify support back but just keep moving forward. Right now i dont know if this will happen or not tho, but i do hope one day that i will attempt it to see if it is possible at least to make.

[Grokzen]

@decentral1se release 1.8.0 have been made and published to github and pypi