BiblioPlus never used since its creation on May 11 2015.
Description
Event Timeline
The extension is undevelopped for years. All commits in past three years are mostly TWN updates and the rest is all of accommodation to global practices (coding conventions, global code migrations etc.) type.
None of what you have said is an argument for closing the project. The current practice is that as long as there is code in the Git repository that we host, the project should still stay open. If you want to propose archiving the repository, you are more than welcome to.
I'm not going to war and re-close this task as declined, but that's what I suggest doing.
@Legoktm Well, those actually are valid arguments, but your one seems to be heavier and thanks for pointing it out. OTOH I would like to see that practice documented somewhere, so it could be followed everywhere, as I've seen other discrepancies around which are breaching it.
Setting Stalled then, not even speaking that all archiving tasks have Low priority by default and are (except for one exception recently) being proceeded occasionally...
If archiving the repo means setting it read-only but keeping the code, then it makes a sense. Deletion perhaps no (even though the extension is both undevelopped for years and relying on third party (commercial or limited) services) unless there is any other mirror repo.
@Danny_B, you wrote that "the extension is undevelopped for years". I provided a link about "code repositories with no recent activity". I see some relation, you don't, but we might still want to consider extending the scope of the existing wiki page.
Perfect timing! I just got access to Gerrit and will be pushing an update to the code today and then there is another update planned for changing api access to HTTPS.
Please do not close this project.
@vtingey Thank you for updates.
Please update accordingly the project description page as well as extension page on mediawiki.org.
Thank you.