Hi Shane, My personal preference is to check the following two things first:
1. Am I interested in the project so that I can allocate time and energy to its incubation journey? 2. Does the project have a solid initial committers group so that it looks like a sustainable one? After ensuring that both the initial committers and mentors can allocate enough time and energy on the project, I'd guide the initial committers to [1][2][3]. [1] https://incubator.apache.org/cookbook/ [2] https://incubator.apache.org/guides/proposal.html [3] https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal The most important part here is letting the initial committers draft their proposal so that I can check their motivation again and learn more about their current status. After that, I'll focus on the following three setups: 3. Migrating their infra to ASF infra. This is a big setup change after previous self-managed projects. 4. Release the first version and understand our basic policies on release, license, and brand. 5. Define the target users and extend the committer group by one new member. Since then, the project should be able to run itself mostly. Mentors would participate by voting, advising, or acting on their own interest in the project. > I think it’s important to do this via an online meeting, not offline via email. This allows the mentors and initial committers to meet each other, build trust, and makes it easier to ask dumb questions. On trust, I agree that understanding both sides' commitment is important, as in point (2), while I've experienced different methods to understand it, both online and offline :D Best, tison. Best, tison. Julian Hyde <jhyde.apa...@gmail.com> 于2025年4月1日周二 07:15写道： > Shane, > > Not exactly what you asked, but when a project starts incubation, I think > it is helpful to preview the incubation process. As a mentor I done this > for a couple of podlings (Hop and Baremaps) [1]. > > I think it’s important to do this via an online meeting, not offline via > email. This allows the mentors and initial committers to meet each other, > build trust, and makes it easier to ask dumb questions. > > At the start of incubation, I recommend that the project focuses on making > a first release, that it will require collaboration on the dev list, give > them an idea of what the voting process for that release will look like, > and emphasize that it will be far from perfect. > > Julian > > [1] > https://www.slideshare.net/slideshow/what-to-expect-when-youre-incubating/248315316 > > > On Mar 31, 2025, at 7:04 AM, Shane Curcuru <a...@shanecurcuru.org> wrote: > > > > When someone asks you questions like "should our project X come to the > ASF", how - specifically - do *you* start advising them? > > > > While some advice may be personal or answers to someone's actual > questions, I'm most interested in general details around the incubation > process you share with newcomers: > > > > - What specific URLs do you point newcomers to? > > > > - How do you explain those URLs, and why did you choose those? > > > > - Are there any bullet points or major topics you always cover, to make > sure a newcomer thinking about coming to the ASF also thinks about all the > steps or aspects that incubation requires? > > > > I know we've had people build friction logs for newcomers at a couple of > places across the ASF in the past: descriptions of specific steps that were > hard, or information that wasn't clear for someone new. Here, I'm asking > for what we as IPMC folks who write to people when they first ask one of us > "what is incubation, anyway, and do I want to do it?" > > > > If anyone has a standard boilerplate email or the like they share with > people asking, I'd love to see those as well (and can help organize them > somewhere later, once I learn the incubator website again). > > > > Thanks! > > > > -- > > - Shane > > Member > > The Apache Software Foundation > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > >
