> On Mar 6, 2025, at 3:20 PM, PJ Fanning <fannin...@apache.org> wrote: > > We do have a Clutch Report. > > https://incubator.apache.org/clutch/ > > And you can drill in on each podling to get some finer grained progress > details.
The clutch report depends in part on our ancient status xml files which are hand edited. There are also some yml files that are partially integrated with Whimsy. I tried to improve this some 7 years ago, but ran into also needing to develop Whimsy (a very steep learning curve and a members only environment at that time.) Improving how work with the xml and yml and moving these to git would help better codify required incubation steps including the Champion / Mentor steps. The clutch analysis process is in svn and is run through on Jenkins triggered by svn commits. The key program is `clutch2.py` which should be improved by working on a local checkout. This gathers information about all current podlings. Best, Dave > > On Fri, 7 Mar 2025 at 00:17, Kranti K. Parisa <kranti.par...@gmail.com> wrote: >> >> I think, it makes total sense to do the name search after approval but >> before onboarding, provided the name search can be done quickly (1-2 weeks >> max? I'm not sure). >> >> Perhaps a separate topic, it would be beneficial to conduct a survey to >> assess the current onboarding process and identify any areas for >> improvement. This could involve implementing a progress bar to visually >> indicate the poddling’s progress through the process and highlight any >> challenges they encounter in specific phases. >> >> Best, >> Kranti >> >>> On Mar 6, 2025, at 10:08 AM, Dave Fisher <w...@apache.org> wrote: >>> >>> >>> >>>> On Mar 6, 2025, at 9:20 AM, Niall Pemberton <niall.pember...@gmail.com> >>>> wrote: >>>> >>>>> On Thu, 6 Mar 2025 at 14:53, PJ Fanning <fannin...@apache.org> wrote: >>>>> >>>>> Seems best to allow the discussion thread to proceed and if things seem >>>>> ok, then start the name approval step. The vote only happens after the >>>>> name >>>>> is approved by Brand Management. >>>> >>>> >>>> Does it have to be strict in where it takes place in the process? The main >>>> issue AIUI, is leaving the name search until close to graduation - throwing >>>> away possibly years of building their “brand”. ASAP at the start of >>>> incubation would avoid that issue - but is it a big deal whether it’s just >>>> before being accepted or very soon after? >>> >>> Yes, this has proven to be a serious and expensive issue for a podling >>> recently - in this case Apache Fury was denied. >>> >>> And for another (Apache Hunter now Otava) it is a slow problem as changing >>> resources for Infra is not automatic and we get into a series of back and >>> forth to test that every resource has been properly adjusted. >>> >>> It really is a problem. I think that it is now important enough that the >>> Champion should be responsible for this. If a prospective project really >>> loves their name and yet they cannot use it at the ASF then it’s only fair >>> to have that happen before spending years in the Incubator. >>> >>> The old policy wasn’t so bad 15 years ago when Incubation time was shorter >>> and resources were less. >>> >>> Best, >>> Dave >>> >>> >>>> >>>> Niall >>>> >>>> >>>> On 2025/03/06 14:45:45 Calvin Kirs wrote: >>>>>> If the Brand team has no objections, then I’m absolutely +1. >>>>>> >>>>>> But procedurally, should this happen after the discussion and before the >>>>>> vote? >>>>>> >>>>>> On Thu, Mar 6, 2025 at 10:32 PM PJ Fanning <fannin...@apache.org> wrote: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> This has been discussed on the private mailing list and ASF members >>>>>>> can view the main discussion here [1]. >>>>>>> >>>>>>> Mark Thomas, VP of Brand Management, has suggested a willingness to do >>>>>>> the Podling Name Search at the start of the onboarding process. >>>>>>> >>>>>>> Can I suggest that we trial out having the Champions for new podlings >>>>>>> submit the Podling Name approval application before we commence the >>>>>>> vote for new podlings? >>>>>>> >>>>>>> The main advantage of the early name check is that it is less >>>>>>> disruptive for podling name changes when the podling resources have >>>>>>> not yet been set up and announcements and PR has not yet been done. >>>>>>> >>>>>>> We have a few applications in the early stages. We can try the process >>>>>>> change out for a few months and discuss making it a permanent change >>>>>>> to the process at that point? >>>>>>> >>>>>>> Discussion is welcome but let's not discuss specific cases on this >>>>> public >>>>>>> forum. >>>>>>> >>>>>>> Thanks, >>>>>>> PJ >>>>>>> >>>>>>> [1] https://lists.apache.org/thread/y94f70sfzf2d959k6kl1bkbhmkklk260 >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> Best wishes！ >>>>>> CalvinKirs >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>> >>>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
