[MacPorts] #29658: phpstylist should use MacPorts PHP

MacPorts noreply at macports.org
Mon Apr 30 16:06:44 UTC 2018


#29658: phpstylist should use MacPorts PHP
--------------------------+---------------------------------
  Reporter:  face@…       |      Owner:  rudloff@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch maintainer
      Port:  phpstylist   |
--------------------------+---------------------------------

Comment (by pmetzger):

 "Why?"

 First, because the submitter and the owner haven't replied in years, and
 thus are unlikely to every reply again without someone actively soliciting
 input from them.

 But, more generally: because if you make your tracking system into a
 graveyard of dead requests that will never be acted on, you end up with it
 being very difficult for someone to look through it and find things that
 actively need fixing.

 The function of a ticket system is to allow people to keep track of open
 issues and to direct their work so that those issues get resolved. This
 requires that most tickets contain actionable information, so that someone
 looking through the tickets can easily find tasks that they can quickly
 perform.

 (There is a second category of things that can validly be left open
 indefinitely: tickets can be used to record projects that are important
 but might not be acted on for quite some time. This allows for tracking of
 projects that are of interest. But, generally, there are fairly few such
 things that one tracks compared to the number of defects and issues
 reported by users, so they don't generally get in the way of using the
 ticket system to track problems because the nature of such tickets is
 obvious in the description.)

 If a ticket system gets overly clogged up with things that cannot be acted
 on and likely never will be acted on, the things that do need attention
 get lost in the fog. You end up with people waiting years on things that
 could be acted on because no one can see that they're in need of
 attention. Then people get depressed that the problem keeping them from
 getting their work done has been ignored, and wander off, never to return.

 New people looking at the tickets system also get immensely depressed when
 they see that it is not uncommon for people to report an issue and have it
 sit for many years without action. It is, of course, vastly easier to
 clear out actionable requests when you can find them. (And thus, again, it
 is best not to have a lot of things in the system that cannot be acted on,
 because otherwise you need a lot of effort to find the actionable items
 amidst the unactionable ones, with most effort going not to fixing
 problems but to finding the problems that can be fixed.)

-- 
Ticket URL: <https://trac.macports.org/ticket/29658#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list