#406 Request for sponsor status
Closed: accepted by kevin. Opened by rohara.

I'm requesting sponsor status. I've been maintaining several Fedora packages for many years and was recently working with a coworker to create packages for the HAProxy REST API (a Go application). This coworker is a new packager and needs a sponsor. I am willing to be his sponsor as well as co-maintainer for the new packages.


Here are the 5 BZs requesting new packages for the HAProxy Dataplane API service and the 4 dependencies.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1773716
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1773717
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1773718
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1773719
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1773720

As mentioned, I am willing to sponsor the new packager as well as be co-maintainer. Packaging was done together at HAProxyConf last week with member of HAProxy upstream.

Ryan,

I know you and know you understand the packaging process in great detail. I would be happy to +1 this request. For others to evaluate your request can you describe:

  • Owned or maintained and packages.
  • A listing of all package reviews with a total count.
  • When you joined the packager group.

Cheers
Steve

Ryan,
I know you and know you understand the packaging process in great detail. I would be happy to +1 this request. For others to evaluate your request can you describe:

Owned or maintained and packages.

Currently owner/maintainer of haproxy, keepalived, ipvsadm and co-maintainer of ipset.
Previously owner/maintainer of foghorn, piranha, galera and mysql-galera.

A listing of all package reviews with a total count.

Honestly I don't know. I dug through years or email and bugzillas and could not find my reviews. I know I've done a few. I'll keep looking.

When you joined the packager group.

The earliest commit I can find to a package I owned/maintained is from April 2011. I looked on my FAS account details to see if there were details about when I joined the packager group, but I did not see anything of interest. It is possible there is an email record of this in old email archives prior to the email switch.

-1 As you haven't done the required reviews

https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&email1=%20rohara%40redhat.com&emailassigned_to1=1&emailtype1=substring&list_id=10658598&query_format=advanced

@rohara's packages: https://src.fedoraproject.org/user/rohara/projects

Yeah, we can't sponsor you into the sponsors group if you haven't done any reviews, sorry.
It would be great if you could review those 6 packages you listed above, and one or two more non-go ones from https://fedoraproject.org/PackageReviewStatus/NEW.html. At least for me this would be enough to change my vote to +1.

@rohara's packages: https://src.fedoraproject.org/user/rohara/projects
Yeah, we can't sponsor you into the sponsors group if you haven't done any reviews, sorry.
It would be great if you could review those 6 packages you listed above, and one or two more non-go ones from https://fedoraproject.org/PackageReviewStatus/NEW.html. At least for me this would be enough to change my vote to +1.

I'm in the process of reviewing all 5 of the packages needed to get the HAProxy Dataplane API service introduce to Fedora, ie. all 5 packages I mentioned above.

@rohara any news here? Should we close this and you can reapply when ready?

I'll wrap this up soon. Sorry. We've had some high priority things come through lately.

OK. All 5 reviews are complete. Thanks.

Would sponsors like to look at those reviews and vote again/now?

+1 Ryan will be a good mentor.

+1

I am still +1 :)

Cheers
-steve

On Wed, May 20, 2020 at 5:51 AM Mukundan Ragavan pagure@pagure.io wrote:

nonamedotc added a new comment to an issue you are following:
+1

To reply, visit the link below or just reply to this email
https://pagure.io/packager-sponsors/issue/406

It's been 7 days. I see 7 +1's and 0 -1's, so this request is approved.

Use your powers wisely!

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

Metadata