Housekeeping #3257
Remove dead repositories
0%
Description
Corresponding abslibre directories:
- retired/
- unmaintained/
- ~*/
-- aurelien/
-- lukeshu/
-- megver83
-- smv
History
Updated by bill-auger about 2 years ago
- Status changed from open to duplicate
this is essentially the same discussion as #3258 - lets just use that one ticket for this discussion
note that these are actually discussions - they are not bugs - so, there really should not be any tickets yet - i will give my brief bug tracker primer - though even this comment has no place on a bug tracker - this sort of on-baording should happen on some informal channel, best in-person really - but as i do not remember seeing your nick on IRC or the mailing lists; i have no alternative - it would be better if you did use those, for anything which you are not certain needs any work done
bug trackers are for tracking the progress of work that is being done - each item on a bug tracker should represent bugs and/or work items which have been decided, as needing to be done - for anything else, discussion forums and mailing list serve that purpose, until it is decided that a bug exists or that some work should be done
the only exception on the parabola bug tracker is that it is also has a category for packaging requests - that is effectively promoting all feature requests immediately to "work to be done items" - it really should not be that way
unfortunately, many people do not know the difference, thanks to github - many github users use the bug tracker for all communication - we can do better than that; because we do not rely on third-parties to provide our tools - i would describe those so called "forges" as "light-weight, unified and centralized, project management systems" with a generous dash of "webby-web-web" - they cater to noobs, web fans, and others who for some reason, can not manage their own infrastructure; but they also encourage bad habits - we can use the proper tools for each job - IRC for real-time chat, forums and mailing lists for discussions, and a bug tracker for tracking bugs and work items
using the proper tools for each job, also means parabola users never need to use a web browser to communicate with the parabola team; because a web browser is not the proper tool for communication - what follows from that, is that parabola devs do not necessarily read the web forum or this bug tracker; though most of them will read the mailing list
Updated by gap about 2 years ago
I understand, I thought it would be best to have a formal reference to this ticket to refer people to instead of an ephemeral chat or long-buried mailing list discussion.
Once SourceHut becomes stable enough I propose we switch https://labs.parabola.nu and https://git.parabola.nu over to a self-hosted instance, as it fixes the issues you mentioned by moving web stuff over to mail and having minimalistic modules instead of a monolithic forge.
Updated by bill-auger about 2 years ago
these tickets get buried too - it is no different, other than
semantically - people looking for historical information about
some work that was done, can search the bug tracker - if nothing
is found on the bug tracker; then people can search the mailing
list archive
the main point is that there is no reason to preserve any
discussion, unless it it decided that something should be done
about it - mailing lists get clutter for exactly that reason,
because they contain random discussions other than the important
work that was done - either are worse for it, when there is a mix
of both concerns
the one thing i know i would like done, is to remove the
repos which are not in the default pacman.conf from the
"packages" web interface - if they were not presented there,
probably most people would never know that they exist