Motivation Julia has been around for 6 years now, and for the last 2–3 years the number of packages has increased rapidly. As it is inevitable with free software and single-person projects, some packages have received less maintenance after an initial period of activity, and quite a few packages app…

Although I really support what you are saying, and I think there should be some kind of indication of whether projects are abandoned or not, I think the repostatus badges are totally “useless”. If someone who abandoned a repo cared, they could write it on the top line of the readme. If they wouldn’…

It is a generally nice idea. Some scattered thoughts: I dislike the name Inactive because it is too negative sounding for that state. Like there is a state where a package reaches a happy place. It has no known bugs and it does what it set out to do. It is “Inactive”, but it may actually be be…

[image] Datseris: If someone who abandoned a repo cared, they could write it on the top line of the readme. If they wouldn’t do that, I don’t see why they would bother doing the repo status, which takes more effort. You are right; what I propose requires some minimal cooperation from package …

[image] oxinabox: Like there is a state where a package reaches a happy place. It has no known bugs and it does what it set out to do. It is “Inactive”, but it may actually be better maintained than something that is active. I agree that this is indeed possible (I have some Common Lisp libr…

[image] oxinabox: I guess another thing might be activeness does not correspond to supportedness… Something I’d like to see is a “still alive and mainained” notice once a year, or even every 6 months (just have a “last review of issues was after date xyz” entry in the news / readme that you r…

[image] foobar_lv2: Something I’d like to see is a “still alive and mainained” notice once a year Perhaps this could even be automated: packages that have no activity (either on the code or a notice of this kind) for a specified period are notified by a package registry bot, and if there is n…

@Tamas_Papp In BioJulia, we had some threads questioning the status of our packages. As a result I’ve been rolling out the following to every package repo we maintain: A HUMANS.md file containing the names and emails of the specific BioJulia members dedicated to leading the maintainership of the p…

@Ward9250 nice. The LifeCycle badges ( Lifecycle stages • lifecycle ) work a lot better for me than the repostatus badges ( http://www.repostatus.org/ ) badges

BioJulia is extremely organized, the contribution guidelines are a very nice template for other projects, too. I did not know about the lifecycle badges, but they may be more suitable than the repostatus ones. I saw the links in the document to the badges, but I am curious who is maintaining these…

Tidyverse came up with the badges, but since they are just generated with shields.io I think as long as we have them listed and explained in our CONTRIBUTING.md we don’t need to worry about who maintains them, if we decide to change the badges or add or remove some we can just alter our files and le…

Soft signals on commitment to package maintenance

Community

Nosferican June 19, 2018, 11:01pm 18

Topic		Replies	Views
Seeking Community Input on Package Maintenance Status Labels & Criteria Community question , package , community , juliahealth	11	590	April 17, 2026
How fresh is the General package registry? Package Management general-registry	7	556	February 20, 2024
Is BioJulia team maintaining the IntervalTree package regularly? Biology, Health, and Medicine	24	2400	April 7, 2018
Package negligence New to Julia package	26	1717	April 14, 2023
The State of the Julia Ecosystem Community	109	9065	January 31, 2019

Soft signals on commitment to package maintenance

Related topics