No updates for 4 years

[nickl-]

I suggested to someone they should look at using Respect/Rest and their immediate response was there's been no updates for 4 years.

This is certainly something which is right there in your face when you open a repo and I never thought about it but perhaps we are biased to projects with no activity. It is true that if there is nothing needed to change then it nothing wont be changed (double negative) but maybe we do subconsciously expect there to be improvements regardless.

Perhaps a touch all recursive commit to bring things up to date would suffice?

What do you think, is this an issue or not?

[boussou]

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

;-)

[nickl-]

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

Nice quote, but we're not talking about perfection but rather perception.

Do you judge a project's health based on commit activity?

[dcorrea777]

@nickl- I particularly see it as a problem yes.

I always see the date of the last commit and the time the issues are open without a resolution.

I have not yet used this project in production, only in some personal tests.
I think it's an amazing package, but I have to agree that it's a bit outdated.

[filhodanuvem]

I Agree with @danilosilva87 mainly about opened issues without activity. For example I opened one in 2014, and I didn't appear there after answers, which means that it could be closed, I guess.

I'm living the same problem in a personal project; old issues that I know they're old enough to be there, response time not so good, etc. Maybe the best solutions are: archive the project/make it read only or communicate on readme that the team is not prioritising this repository in favor of others.

[nickl-]

Thank you for your feedback guys! Much appreciated.

There are many factors you can consider when judging the health of an open source project. My usual routine follows along the lines of.

From the landing page in no particular order:

• Yes open issues is certainly one of them
• Number of stars
• Number of watches
• Number of forks

Before you try and contribute

• Open pull requests
• Number of contributors

For further investigation

• How many project maintainers are there
• Look at the open issues for content (issues can be anything), response by maintainers

The surest sign of a problem are forks that are ahead with their own forks, for example

But again the first thing I look at when I went to the @augustohp fork was this and I dismissed it:

Telling myself afterwards that I compared it with what I know is the 4 years displayed here but now I am starting to doubt myself. Have I always subconsciously judged a project by the latest commit active and if so then other do too.

@danilosilva87 states it is outdated, what exactly are you basing this remark on? I have a suspicion it is based on the latest commits, am I right? What will make you consider it to be up to date?

The router is based on HTTP/1.1 which has been around since 1997 and still the predominant protocol in use today. What more can we do with it besides going off scope? I have used it for years and it still does what it needs to do, nothing more nothing less. There is nothing I needed that it can't do or I certainly would have added that feature by now. If people are simply dismissing a project based on updates then perhaps we should do something about it.

[dcorrea777]

now I was confused @nickl- 😄 , I was marked wrong ?

[nickl-]

Well at least we have a new release now so that should be cheerful. \o/

[dcorrea777]

Yes @nickl- , I saw you mixed some PR, I'm very happy, I think this project is fantastic.
I will study it and try to contrubuir with something.

[apteles]

@nickl- I subscribed today on website CodeTriage, when i saw this project I made my subscription to receive issues and help maybe. I've seeing that the project is a little abandoned, there a lot of updates that we can do. Anyway, I would like know is, what is direction this project will take? We are in php version 7.4, what we can do for at least keep this project updated and keep compatibility?
See, I really want help, but for where we begin?

Sorry about any typo.

[anatolykazantsev]

Well at least we have a new release now so that should be cheerful. \o/

I think there's a regression in this release. Please have a look at my comment: #123 (comment)

Should I re-post it as a separate issue?

[nickl-]

@anatolykazantsev start new issue please.

Closed: New release resolved this

[nickl-]

@apteles I didn't forget about you, see: #142