Maturity and maintenance

[janwijbrand]

Hi,

Let me start with heartily thank your work on this library! It makes my developer-life a lot easier at the moment, building a translation-layer of sorts between a FHIR-based environment and the application platforms we're building.

Since we're about to commit to depending on this library I have a question regarding your plans on maintenance and how others might try to be of help there to you.

I'm currently specifically looking at how I can present you with tested PRs as currently it appears the testing configuration and infrastructure is somewhat outdated. The tox.ini (https://github.com/nazrulworld/fhir.resources/blob/main/tox.ini) for example lists older (even "end-of-life") versions of Python. The contribution guidelines even mention very old Python versions (https://github.com/nazrulworld/fhir.resources/blob/main/CONTRIBUTING.rst#pull-request-guidelines) and the instructions on running the tests on, for example, version requirement conflicts at the moment. There seems also no CI configured at the moment.

This might all sound like criticism, but that's not my intention. What I would like to know is how others (including me) might offer help on getting this package into CI and give it regular maintenance.

IOW, what are your plans with this library? Can you give some guidance on what you do to run the tests? Would you accept PRs that would try to get CI running, update the list of support Python versions, adapt to changes in dependencies etc.?

Of course I'm also curious to hear from other developers that rely on this library and what you do when developing with and on this library.

[janwijbrand]

There seems also no CI configured at the moment.

Apologies. This is not true, there's Travis CI configured https://github.com/nazrulworld/fhir.resources/pull/138/checks