Bug 44075

Summary: Maintainer Update phpSysInfo
Product: Ports & Packages Reporter: bob
Component: Individual Port(s)Assignee: Alan Eldridge <alane>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description bob 2002-10-15 04:50:01 UTC
	Update port to 2.1, update maintainer.
Comment 1 Alan Eldridge 2002-10-15 05:40:29 UTC
On Mon, Oct 14, 2002 at 11:41:15PM -0400, Bob Bomar wrote:
>
>>Number:         44075
>>Category:       ports
>>Synopsis:       Maintainer Update phpSysInfo
	
>>Description:
>	Update port to 2.1, update maintainer.

Hey bob, got some questions for ya....

1. Where's the patch?
2. What's your right email address?
3. Why did it take you 5 weeks to do anything?
4. Why didn't you notice that ports/42630 to update it was already
   there?
5. You want me to maintain it - i'm a committer and i wrote a good
   part of the bsd stuff, as well as getting <24 hour response to 
   patches sent to author?
6. Why shouldn't I close this as a dupe of 42630?

-- 
Alan Eldridge
Unix/C(++) IT Pro, 20 yrs, seeking new employment.
(http://wwweasel.geeksrus.net/~alane/resume.txt)
KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)
Comment 2 Alan Eldridge freebsd_committer freebsd_triage 2002-10-15 05:45:18 UTC
Responsible Changed
From-To: freebsd-ports->alane

*I* get this one. Hehehe.
Comment 3 Alan Eldridge 2002-10-15 06:37:12 UTC
On Tue, Oct 15, 2002 at 12:12:58AM -0500, Bob Bomar wrote:
>On Tue, Oct 15, 2002 at 12:40:29AM -0400, AlanE wrote:
>> On Mon, Oct 14, 2002 at 11:41:15PM -0400, Bob Bomar wrote:
>> >
>> >>Number:         44075
>> >>Category:       ports
>> >>Synopsis:       Maintainer Update phpSysInfo
>> 	
>> >>Description:
>> >	Update port to 2.1, update maintainer.
>> 
>> Hey bob, got some questions for ya....
>> 4. Why didn't you notice that ports/42630 to update it was already
>>    there?
>> 5. You want me to maintain it - i'm a committer and i wrote a good
>>    part of the bsd stuff, as well as getting <24 hour response to 
>>    patches sent to author?
>> 6. Why shouldn't I close this as a dupe of 42630?
>
>I apologize for takeing so long.  As for being a dup of 42630 
>why didnt anybody commit it?  If you want to take the port, take
>it.  

Understood, but at least keeping the email updated should be a priority.
My policy (from my mentor) is that if the maintainer email is broken,
then either take the port or give it to ports@.

I took responsibility for it, and then was sick for almost 2 months
with pneumonia. I was going to do it tonight, in fact, about 15 minutes
after your mail arrived. 

If you don't mind, I'd appreciate it. I know the code inside out, and
can get bugfixes into the author's tree in a  matter of hours.

I'm going to break with std policy and use a CVS version and host the
tarball, since I use it, fix it and keep up with it.

Thanks. I wasn't angry, but I was annoyed. I appreciate your fast
response.

-- 
Alan Eldridge
Unix/C(++) IT Pro, 20 yrs, seeking new employment.
(http://wwweasel.geeksrus.net/~alane/resume.txt)
KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)
Comment 4 Alan Eldridge freebsd_committer freebsd_triage 2002-10-24 04:08:19 UTC
State Changed
From-To: open->closed

I'm handling this as new maintainer and phpSysInfo contributor.