Personally I'd not really like this solution. For some sponsors which have tons of time and can always take on people to mentor it will be great for those folks. For people who get "assigned" to sponsors that don't necessarily have time and don't update their status to unavailable or whatever at a given time it will be a bad experience for those seeking sponsorship.
What about a mailing list for people seeking sponsorship to email into that would go to all sponsors and the person seeking sponsorship could introduce themselves, etc. and then available sponsors could perhaps chat back and forth a bit in that list to find out if it might be a good fit for them.
As was mentioned, sponsorship requires a time commitment but it also needs to be a good fit between two people for it to be fruitful when they work together.
On Sun, Apr 2, 2023 at 10:34 AM Jakub Kadlcik <jkadlcik@xxxxxxxxxx> wrote:
I tried to get some numbers to see how many packagers we sponsor each
year but FAS tells me only group members but not when they joined the
group. Do any of you at least have a rough estimate of what number are
we talking about? I wouldn't propose any auto-assign system for
package reviews because there is thousand of them each year. That
would be insane. But how many new contributors that need to be
sponsored do we have each year? My guess is that not even every
sponsor would get a ticket within the year.
Jakub
On Sun, Apr 2, 2023 at 5:07 PM Jakub Kadlcik <jkadlcik@xxxxxxxxxx> wrote:
>
> > 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ý <msuchy@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
Jonathan Wright
AlmaLinux Foundation
AlmaLinux Foundation
Mattermost: chat
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
