Opened 4 months ago

Last modified 4 months ago

#30250 new enhancement

we should retire the 'rpm packaging' trac component

Reported by: arma Owned by: hiviah
Priority: Medium Milestone:
Component: Core Tor/RPM packaging Version:
Severity: Normal Keywords:
Cc: asn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

[I'm starting this ticket out in the Tor component, so it can get an opinion from the network team folks before it moves to the Trac component.]

We have a trac component "Core Tor / RPM packaging", which up until yesterday had zero open tickets in it, and currently has one:
https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Core+Tor%2FRPM+packaging&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority

Hiviah is long gone as our RPM maintainer, meaning we don't have one -- or rather, meaning we are at the mercy of whatever maintainer fedora and centos decide, or don't decide, to have for themselves.

Having an RPM packaging component on our trac can mislead people into thinking that we have people looking at our trac who might work on RPM packaging.

We should move the component to the trac attic, like other components that have lived a happy life but now it's time for them to move on.

Child Tickets

Change History (3)

comment:1 Changed 4 months ago by mikeperry

Component: Core Tor/TorCore Tor/RPM packaging
Owner: set to hiviah

I disagree. If there are issues with old RPM packages in the wild, and some brave soul who likes RPM comes to report one, they should at least know that we don't have anyone currently doing this work.

They should also know the current issues with existing, deprecated RPM packages, which they would presumably base their work off of, or at least look at for reference.

I would only retire this component if we were forever deciding never to support RPM ever again, perhaps because of some kind of organizational decision. As Triage Overlord For A Day, this is my absolute and binding decree. (The next Triage Overlord For A Day can make a different call for completely different and unrelated reasons, of course, of course. ;)

comment:2 in reply to:  description Changed 4 months ago by teor

Replying to arma:

[I'm starting this ticket out in the Tor component, so it can get an opinion from the network team folks before it moves to the Trac component.]

Trac isn't a good tool for working out what we should do, or getting opinions from the network team.
Please send an email to the tor-dev list instead.

We have a trac component "Core Tor / RPM packaging", which up until yesterday had zero open tickets in it, and currently has one:
https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Core+Tor%2FRPM+packaging&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority

I moved that ticket into Core Tor, because it had nothing to do with RPMs.

Hiviah is long gone as our RPM maintainer, meaning we don't have one -- or rather, meaning we are at the mercy of whatever maintainer fedora and centos decide, or don't decide, to have for themselves.

I removed hiviah as the default owner of RPM Packaging tickets.

Having an RPM packaging component on our trac can mislead people into thinking that we have people looking at our trac who might work on RPM packaging.

I agree. But if that's our criteria, we should apply it consistently across all Trac components.

We should move the component to the trac attic, like other components that have lived a happy life but now it's time for them to move on.

Ok, but let's do that after getting consensus on tor-dev@.

comment:3 in reply to:  1 Changed 4 months ago by teor

Replying to mikeperry:

I disagree. If there are issues with old RPM packages in the wild, and some brave soul who likes RPM comes to report one, they should at least know that we don't have anyone currently doing this work.

I have removed hiviah as a default owner of RPM Packaging tickets.

But Trac default owners aren't a good way to communicate the maintenance status of a project.
Maybe moving a project to the Attic is a good way to communicate that.
But even then, that's a bit subtle.

Let's work out how to communicate project status by sending an email to tor-dev@, and asking how we should do it.

They should also know the current issues with existing, deprecated RPM packages, which they would presumably base their work off of, or at least look at for reference.

Moving this component to the Attic doesn't change their ability to find out about previous bugs.

I would only retire this component if we were forever deciding never to support RPM ever again, perhaps because of some kind of organizational decision. As Triage Overlord For A Day, this is my absolute and binding decree. (The next Triage Overlord For A Day can make a different call for completely different and unrelated reasons, of course, of course. ;)

If we don't have anyone to do the work, we are effectively deciding not to support this component.

Note: See TracTickets for help on using tickets.