I have tried contacting Siddharth Sharma for a month. I tried via Bugzilla, IRC and dev mailing list. I also saw an older issue for this update that has received no response.
This is my review request for the updated package: https://bugzilla.redhat.com/show_bug.cgi?id=1661595
This is the bug I filed for the out-of-date package: https://bugzilla.redhat.com/show_bug.cgi?id=1651956
This is a bug from December 2017 that did not receive any response either: https://bugzilla.redhat.com/show_bug.cgi?id=1528491
Per the policy, you need to first post to devel list to ask if anyone else knows how to contact them. Please link that post here.
I feel like the policy isn't completely clear on whether you need to file a dedicated bug about the non-responsiveness or if what you did is fine, but I'm inclined to accept the comments on the bug as-is.
CC @siddharths
Thanks for your quick response.
I posted to devel list and asked if anyone else knows how to contact them here:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SOV7MYGU6A3IR2XVQBOYVB3IP6MJJA22/
Please feel free to take this package.
On Sat 22 Dec, 2018, 1:02 AM Randy Barlow <pagure@pagure.io wrote:
bowlofeggs added a new comment to an issue you are following: `` Per the policy, you need to first post to devel list to ask if anyone else knows how to contact them. Please link that post here. I feel like the policy isn't completely clear on whether you need to file a bug about the non-responsiveness or if what you did is fine, but I'm inclined to accept the comments on the bug as-is. CC @siddharths `` To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2039
bowlofeggs added a new comment to an issue you are following: `` Per the policy, you need to first post to devel list to ask if anyone else knows how to contact them. Please link that post here.
I feel like the policy isn't completely clear on whether you need to file a bug about the non-responsiveness or if what you did is fine, but I'm inclined to accept the comments on the bug as-is.
CC @siddharths ``
To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2039
@caravel are you a packager? When I tried to assign the package to you at https://src.fedoraproject.org/rpms/sqlcipher it did not work because you do not seem to be a packager. If you are a packager, please log in to above URL and notify me.
@till I am currently in the process of getting sponsored, so it will probably be a few more days until the package can be assigned to me, if everything goes well.
@caravel @till: What's the status here?
If we need this to move forward, I think we can treat @siddharths statement above as permission to go through the "sponsorship via co-maintainer" route.
"sponsorship via co-maintainer" route is IMHO intended in a case where the current maintainer mentors the new one. Not where the current maintainer just acks that the new maintainer can take the package. I'd prefer if a packaging sponsor works with @caravel trough the standard route of getting sponsored.
@caravel How does that work so far for you? Is somebody working with you to get you sponsored into the packagers group or are you seeking somebody?
Metadata Update from @churchyard: - Issue tagged with: stalled
Metadata Update from @churchyard: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
@caravel Feel free to answer and I'll gladly reopen this.