#847 Require housekeeping for Fedora Hosted.org projects?
Closed: Fixed None Opened 15 years ago by mdehaan.

It is a nice thing to be able to point users to FedoraHosted.org to let them browse things we are hosting.

However currently what seems like half of our projects have never edited their Trac homepage, and I suspect some are not using their version control or bug tracker.

Ideally these projects would be removed from the index after failing to launch for X months. I am not as concerned with dormant code, that should be fine, but projects not using Fedora hosted just make the index longer.


Yeah, there's bound to be some sort of cleanup process we can figure out with the trac instances too. Some of them I suspect thought "hey, it'd be great to have a trac instance with this" but then never needed it, only the source control repo.

I'll think on this some more.

Has there been any progress on this yet, as this seems to be still useful?

I think we all like the idea of housekeeping... we just need to write up some exact guidelines as to what would happen when and start enforcing them. Ideally in some kind of scripted/automatic way.

Perhaps as a first cut:

  • Projects that have not had a SCM commit in one year.

  • Projects that have not had a mailing list post in one year.

  • Projects that have not had a trac change in one year.

Would be flagged. The owner of this project would be pinged. If no answer in a month, the project would be moved to 'archived' status (no longer appears, but we still have the data).

I'm not sure how hard it would be to script this. We should probibly discuss on list.

Drafted a list of things we could do; sent out to the mailing list.

I've drafted some ideas, which can be found at http://paste.fedoraproject.org/107594/

If I could get some people to assist me with making this work and working out the specifics, I would be extremely grateful, as I do not possess the permissions and/or skill to do so myself in a timely manner.

Thanks for working on this again. ;)

So, you should have access to hosted03 where the fedorahosted data is stored. From there, we would need some kind of script to gather info on:

  • last commit to scm
  • last change in trac
  • some kind of check for trac wiki front page? (see if it's default, etc).

This info might also be possible to just scrape from the net anywhere.

Still working on some ideas; need a bit of support to get it handled properly.

We should probably start with getting the projects that just never launched out of the way; then move to the smaller stuff. As long as we get it cleaned up a bit, that's good enough of a band-aid to keep it clean until we have more support behind the rest of the changes (or at least the parts we decide we want to implement).

Also, I would like to at some point go over the list I've got with some people that are closely involved with the fedorahosted side of things and get the parts we actually want to implement hammered out. Maybe a meeting or something? I'm not anywhere near close enough with how this stuff works, and I want to make sure I've got everyone's approval.

Replying to [comment:8 billwood09]:

Still working on some ideas; need a bit of support to get it handled properly.

Sure. ;)

We should probably start with getting the projects that just never launched out of the way; then move to the smaller stuff. As long as we get it cleaned up a bit, that's good enough of a band-aid to keep it clean until we have more support behind the rest of the changes (or at least the parts we decide we want to implement).

Sounds reasonable. So, we need a list of projects that have the default trac page and/or mailing lists with 0 posts and/or git repos with 0 content.

Also, I would like to at some point go over the list I've got with some people that are closely involved with the fedorahosted side of things and get the parts we actually want to implement hammered out. Maybe a meeting or something? I'm not anywhere near close enough with how this stuff works, and I want to make sure I've got everyone's approval.

Sure. we could do that at a weekly meeting if you can make it to one (thursdays at 18UTC) or we could schedule some other time? Either way works.

Opening it up in case anyone else decides they have the resources to work on this. School and trying to get a job have been taking it out of me lately.

Since we are looking at getting active projects to move to pagure.io now, not much point in implementing things in fedorahosted.

Login to comment on this ticket.

Metadata