Non-maintained?

[houmark]

Hello @cmchase

This modules has 375 downloads in the last week. Some people rely on it.

It works, but could need some improvements.

How about updating the README and invite new maintainers and give people who have interest write access, so pull requests can be merged and anyone who wants to improve on it can do so?

I understand there is potential side effects to this, but Citrix Podio has obviously lost all interest in maintaining any of the client libraries, but sitting on them is also not really cool.

[cmchase]

Thanks for your honest and constructive input. Unfortunately, the Citrix Podio team hasn't had the capacity to update the client libraries for quite some time and it's been the topic of more than a few heated debates.

A few of the talking points were:

• How do we properly vet contributors to take on ownership of the repo?
• Do we assume ownership again if they move on to other projects?
• If somebody were to fork and maintain their own repo, would we link to them and effectively endorse their work?

Ultimately, we didn't come up with good answers to those questions and updated the README with No Maintenance Intended.

Personally, I would encourage any interested contributors to fork the code, building upon this repo as a foundation, and I'll be happy to take on the debate again about linking to forked repositories.

[houmark]

Thanks for responding to this one. Your concerns were what I had in mind in my last sentence, so we are on the same page on that.

Vetting is always a concern. But if you try to let in more than one maintainer, then there's a better chance that between them, the outcome is good. Adding code approval by at least one other maintainer would also increase code quality and automated tests which already exists should pass for a merge to happen. Basic rules, that is by most decent open source libraries.

If podio-js changes to a "non-official, but most comprehensive" type library, then people can take that into consideration when using it, because the alternative is to do your own lib from scratch.

No code library is final or perfect. But an outdated library is in my opinion worse. Citrix Podio may have the capacity to keep an eye on the ongoing development and step in if needed.

Linking to other libraries is another option, but considering the fairly long history of this one, others may not get the attention they should, unless this one is taken fully offline sooner rather than later.

In one sentence; You started this, you kept it online, you have a moral obligation to either pass it on for others to improve, or fully retire it.

I'd appreciate if you would re-open this one, so others with interest could comment and maybe a decision could be made from the feedback.

[cmchase]

Sure, let's re-open and we can see where the conversation goes.

Thanks again for your input!

[good3n]

It appears all of the client libraries other than PHP are marked as unmaintained. That's a little confusing considering the popularity of JavaScript and the growing (with no signs of stopping) popularity of JavaScript libraries like React, Angular, Vue, etc.

[cmchase]

The Citrix Podio team is no longer the maintainer of Podio-PHP. A group of people got together and volunteered to take on the maintenance of the repository.

podio-community/podio-php#153

It's entirely possible that this repo could continue on as Podio-PHP has, but the public participation hasn't been as strong and the Citrix Podio team still can't commit to maintaining the client libraries.