> If they wait for months, I think they don't want to be sponsored. I respectfully disagree here, IMHO we communicate a message that a sponsor will find the contributor, not the other way around. Just so I don't repeat the same message in my own words, everything that Miroslav said, sounds true to me.
> Please exclude me from such spam. Sure, no problem with me. As I said in my initial proposal, I'd provide an easy way to opt out (probably multiple ways, so it is convenient for everybody). > I don't think it's fair to expect that all sponsors are available to do this > at any time. Well sure, I agree. Mentoring somebody is a time commitment and nobody has sponsoring people as the #1 priority. But as I said in the proposal "If a sponsor is not able or willing to work on a ticket, they could either set NEEDINFO on another sponsor or just drop themselves. The ticket would then get a new sponsor next week" - to me this sounds very reasonable. Jakub On Sun, Apr 2, 2023 at 4:12 PM Miroslav Suchý <msu...@redhat.com> wrote: > > Dne 02. 04. 23 v 11:54 Vitaly Zaitsev via devel napsal(a): > > I'm always willing to review and sponsor new maintainers, but they need to > show explicit consent by posting on IRC/Matrix/ML or direct email. > > Let me check the history of > > > https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#how_to_find_a_sponsor > > Right now we tell users to: > > Usually, a sponsor finds you through your sponsorship request in Bugzilla or > the packager sponsors pagure instance. In case you are waiting to be > sponsored for longer than desirable, take a look at Sponsors page. It will > help you find the right sponsor for you based on programming language > preference, domains of interest, native language, and other criteria. > > This is not there for long time. Actually since 2021 when Jakub wrote that > "Sponsor page". Previously there was: > > If you are submitting a new package for review in Bugzilla, > you can make the review request block the > https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] > tracking bug. > > Otherwise, you can file a ticket in the > https://pagure.io/packager-sponsors/[sponsors ticketing system]. > > So previously - and even now - we tell newcomers to to block FE-NEEDSPONSOR > and wait. And only if they wait too long (whatever it means) to start looking > for sponsors directly. > > I personally think that Jakub's proposal is great and I welcome it. Not > everyone is brave to initiate a conversation and asks for being sponsored. We > have to realize it often means that junior developer has to reach senior > developer and juniors often hesitate to do this step. This proposal remove > one road blocks for juniors. > > If other people does not find it useful, then I propose to at least alter our > documentation and tell users to start looking for sponsor immediately after > blocking FE-NEEDSPONSOR. > > Miroslav > > > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
