The maintainer has not "refused", the maintainer has not replied. Please follow the non-responsive maintainer policy if you plan to take over the package, otherwise try contacting the owner directly. This particular package happens to be owned by Christoph Wickert who is generally very responsive to direct inquiries, but is probably just too busy to notice the Bugzilla activity.

Please do not bring issues like this to FESCo until and unless an actual conflict has occurred.

Replying to [comment:1 sgallagh]:

The maintainer has not "refused", the maintainer has not replied. Please follow the non-responsive maintainer policy if you plan to take over the package, otherwise try contacting the owner directly. This particular package happens to be owned by Christoph Wickert who is generally very responsive to direct inquiries, but is probably just too busy to notice the Bugzilla activity.

Please do not bring issues like this to FESCo until and unless an actual conflict has occurred.

what are your questions it is possible here to write . I am the shield that is my problem worthy of attention.

why have you closed if not solved my problem

Because it is not the responsibility of this committee to solve your problem when you did not follow the process set up to solve these kinds of problems.

Replying to [comment:4 jwboyer]:

Because it is not the responsibility of this committee to solve your problem when you did not follow the process set up to solve these kinds of problems.

can you clarify what exactly do you do . and why a Committee was formed .
sorry for English

or it solved the issues on the server and the cloud are important to RedHad .

will be the answer to my question.

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers is the policy you should follow.

Replying to [comment:8 ausil]:

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers is the policy you should follow.

I believe he acted on this instruction