Fpm: [QUESTION] Is FPM maintained any longer?

[weakcamel]

First of all, let me thank you for FPM. It is a great project and I absolutely appreciate all the hard work and effort put in it by the author and all contributors!

I couldn't help but notice that there is a growing backlog of issues and PR in this repository. Last release 1.11.0 happened in February 2019. Usually that's a sign that the project maintainer is no longer able to actively work on it (be it for personal or professional reasons) which is absolutely understandable in OSS world.

What I wanted to ask is the plans for FPM: is it reasonable to assume that FPM will no longer be maintained in its current form? Is it useful to be raising new issues at this point or is it just adding more unecessary noise?

Knowing that will let the users (me included of course :-)) make an informed decision whether to use it, not use it or consider a fork of it.

Thank you in advance.

[weakcamel]

Stumbled across related issue from a year ago: https://github.com/jordansissel/fpm/issues/1653

[jordansissel]

I don’t have much time lately to dedicate to this project. FPM is fairly
stable, and though there are bugs to fix, if there is a particular change
you need, filing an issue specific to that bug/issue would be a great next
step.

That said, I welcome contributions (patches, testing/evaluating PRs, docs
improvements, bug reports, etc).

On Fri, Jun 12, 2020 at 8:38 AM Waldek Maleska [e-mail]
wrote:

Stumbled across related issue from a year ago: #1653
https://github.com/jordansissel/fpm/issues/1653

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jordansissel/fpm/issues/1712#issuecomment-643340364,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABAF2R4AKIBLWFIG6MHPLLRWJDY5ANCNFSM4N4I7HMA
.

[weakcamel]

@jordansissel Many thanks for the reply. It's really good to know that this project isn't quite end of life then.

I'll go ahead and raise the issue then and as it's related to sh, I may be able to provide a patch - unfortunately, I'm not a Ruby developer so can't be of much help with the core.

[truckingsim]

@jordansissel would it be possible to do a release for loosening up the JSON versions?

You mentioned doing one when you merged the pr: https://github.com/jordansissel/fpm/pull/1600 but there is now a vuln in JSON <2.3.0.

The fix is in master just not the latest release and would be great to get one with that fix.

[weppos]

@jordansissel would it be possible to do a release for loosening up the JSON versions?

You mentioned doing one when you merged the pr: #1600 but there is now a vuln in JSON <2.3.0.

The fix is in master just not the latest release and would be great to get one with that fix.

I agree, that would be really appreciated :)

[jordansissel]

I’ll see about doing a release soon.

On Fri, Sep 25, 2020 at 4:41 AM Simone Carletti [e-mail]
wrote:

>
>
>
>

@jordansissel https://github.com/jordansissel would it be possible to
do a release for loosening up the JSON versions?

You mentioned doing one when you merged the pr: #1600
https://github.com/jordansissel/fpm/pull/1600 but there is now a vuln
in JSON <2.3.0.

The fix is in master just not the latest release and would be great to get
one with that fix.

I agree, that would be really appreciated :)

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/jordansissel/fpm/issues/1712#issuecomment-698881963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABAF2X3T56DUWY73R2GQOLSHR6U3ANCNFSM4N4I7HMA
.