Bug 797260 - nonresponsive package mantainer
Summary: nonresponsive package mantainer
Keywords:
Status: CLOSED DUPLICATE of bug 770585
Alias: None
Product: Fedora
Classification: Fedora
Component: emesene
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 17:32 UTC by Germano Massullo
Modified: 2012-03-12 21:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-10 19:31:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Germano Massullo 2012-02-24 17:32:23 UTC 
According to Fedora Project policy for nonresponsive package mantainers (Itamar Reis Peixoto in this case), 
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
I opened this bugreport to evidence unresponsiveness about 
https://bugzilla.redhat.com/show_bug.cgi?id=770585
Comment 1 Germano Massullo 2012-03-04 18:24:39 UTC 
Second attempt
Comment 2 Germano Massullo 2012-03-10 16:40:05 UTC 
Sent an e-mail to Fedora devel mailing list
Comment 3 Itamar Reis Peixoto 2012-03-10 19:31:22 UTC 
(In reply to comment #1)
> Second attempt

you can make thousands of attempts.

if you`re not happy with current maintainer you can maintain it yourself.
or include a patch to fix the problem.

*** This bug has been marked as a duplicate of bug 770585 ***
Comment 4 Germano Massullo 2012-03-12 21:17:31 UTC 
Itamar did you read https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers  ???
So am I making thousand of attempts because I am crazy or am I following literally the procedure?
And don't try to get me in the trick of "do it on your own if you don't like" because I am a contributor and I contribute by filling bugs. It is not my task to fix problems because I don't have the skills.
Comment 5 Germano Massullo 2012-03-12 21:20:00 UTC 
*Filling bug reports
Note You need to log in before you can comment on or make changes to this bug.