#2580 Non-responsive maintainer callkalpa
Closed: Invalid 3 years ago by churchyard. Opened 3 years ago by aperezbios.

I have been trying to contact the current maintainer of a number of sugar activities (see below) for over a week, without any success. I am raising this request to take over eight sugar activity packages from him, so I can maintain them moving forward.

The packages are: sugar-paint, sugar-nutrition, sugar-locosugar, sugar-labyrinth, sugar-jukebox, sugar-fractionbounce, sugar-fototoon, and sugar-flip

I e-mailed him 11 days ago, and have not had a response. He has not logged in via FAS in nearly a year, according to fedora-active-user

I've filed bugs for each package, and the bug IDs are 1931240, 1931241, 1931242, 1931244, 1931245, 1931246, 1931247, 1931248, and 1931249


Metadata Update from @ngompa:
- Issue tagged with: nonresponsive maintainer

3 years ago

The Non-responsive maintainer policy has several necesery steps to follow.

I've seen you filed several bugzillas:

https://bugzilla.redhat.com/buglist.cgi?bug_id=1931240%2C1931241%2C1931242%2C1931244%2C1931245%2C1931246%2C1931247%2C1931248%2C1931249&list_id=11703940

One would have been enough. The next step is:

Post to the Fedora devel list with a link to the bug report and ask if anyone knows how to contact the maintainer. CC the maintainer. Links to all other bug reports open on all neglected packages from the same maintainer should be included.

Later, after a week passes, please reopen this ticket following this template:
https://pagure.io/fesco/new_issue/?template=nonresponsive-maintainer&title=Nonresponsive%20maintainer:%20Kalpa%20Welivitigoda%20callkalpa

Thanks.

Metadata Update from @churchyard:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Apologies, the email to devel was actually sent: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ET5NU3JTOQYSL6GMUFNWIB3VCXB7OXFR/

Either way, after a week, please open a ticket following the template.

Login to comment on this ticket.

Metadata