[70103] trunk/dports/lang/parrot/Portfile

Blair Zajac blair at orcaware.com
Fri Jul 30 08:38:29 PDT 2010


On Jul 30, 2010, at 3:24 AM, Thomas Keller wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Am 30.07.10 07:53, schrieb Rainer Müller:
>> On 2010-07-30 03:55 , Thomas Keller wrote:
>>> Am 30.07.10 03:47, schrieb Ryan Schmidt:
>>>> Were your changes approved by the port's maintainers, by the way?
>>> 
>>> Actually not, but as the port was largely outdated I did this (and the
>>> earlier) NMU without the create-ticket-wait-72-hours-finally-continue
>>> workflow. The port is also still not 100% usable (and was not before I
>>> took my hands on it), see <http://trac.parrot.org/parrot/ticket/344> for
>>> more details. Further updates will follow.
>> 
>> You should announce that you are taking advantage of maintainer timeout
>> in the log message. I added a sentence to the guide to clarify this
>> (r70119).
>> 
>> As the ticket was sitting 6 months without attention should we call port
>> abandonement for parrot?
> 
> I'd vote for a less bureaucratic way to handle all this, i.e. less
> ticket work and less restrictions. One simple rule could be to make a
> port automatically nomaintainer or at least openmaintainer if no updates
> happened for so and so long.

If you have a stable port, such as Python 2.5, that sees almost no updates, I still wouldn't want that to be made openmaintainer.  Is this what you're suggesting?

Blair



More information about the macports-dev mailing list