AW: [Init] Project Onboarding Tasks After GitHub Migration to ASF

[Christofer Dutz]

Hi all,

Just noticed that the repo name on github doesn’t contain the prefix 
„incubator-„ Admittedly I like it that way, because then the name doesn’t 
change during graduation, but I’d like to ask if this was intentional and the 
requirements have changed?

Also the link in whimsy points to the wrong repo name (it thinks it has the 
„incubator-„ prefix.

Chris


Von: Calvin Kirs <k...@apache.org>
Datum: Freitag, 30. Mai 2025 um 13:36
An: dev@bifromq.apache.org <dev@bifromq.apache.org>
Betreff: Re: [Init] Project Onboarding Tasks After GitHub Migration to ASF
Great, thanks：）

On Thu, May 29, 2025 at 4:29 PM gujiaweijoe <gujiawei...@foxmail.com> wrote:

> Hi&nbsp;Calvin,
>
>
> Thanks for your support.
> I would like to take on the Maven account and permissions&nbsp;setup.
>
>
> Best regards,
> Gu Jiawei (gujiaweijoe)
>
>
>          Original
>
>
> From:Calvin Kirs <k...@apache.org&gt;
> Sent Time:2025-05-29- 15:42
> To:dev <dev@bifromq.apache.org&gt;
> Subject:[Init] Project Onboarding Tasks After GitHub Migration to ASF
>
>
>
>        Hi&nbsp;all,
>
>
> Now&nbsp;that&nbsp;our&nbsp;GitHub&nbsp;repository&nbsp;has&nbsp;been&nbsp;successfully&nbsp;migrated&nbsp;to&nbsp;the&nbsp;ASF,
>
> we&nbsp;have&nbsp;a&nbsp;number&nbsp;of&nbsp;onboarding&nbsp;tasks&nbsp;to&nbsp;complete.&nbsp;The&nbsp;overall&nbsp;process&nbsp;can
> be&nbsp;referenced&nbsp;here:
> &nbsp;https://incubator.apache.org/guides/transitioning_asf.html↳
>
>
> Below&nbsp;is&nbsp;a&nbsp;summary&nbsp;of&nbsp;the&nbsp;main&nbsp;items&nbsp;we&nbsp;need&nbsp;to&nbsp;take&nbsp;care&nbsp;of:
>
> 1.&nbsp;License&nbsp;Header&nbsp;Check&nbsp;and&nbsp;Replacement
>
> &nbsp;&nbsp;&nbsp;We&nbsp;need&nbsp;to&nbsp;ensure&nbsp;that&nbsp;all&nbsp;original&nbsp;source&nbsp;files&nbsp;include&nbsp;the&nbsp;standard
>
> ASF&nbsp;license&nbsp;header.&nbsp;For&nbsp;any&nbsp;third-party&nbsp;source&nbsp;files,&nbsp;please&nbsp;be&nbsp;extra
> cautious&nbsp;and&nbsp;refer&nbsp;to:
> &nbsp;&nbsp;&nbsp;https://www.apache.org/legal/src-headers.html#3party
>
>
> To&nbsp;help&nbsp;automate&nbsp;this&nbsp;process&nbsp;(and&nbsp;ideally&nbsp;add&nbsp;a&nbsp;check&nbsp;to&nbsp;GitHub&nbsp;Actions),
> we&nbsp;recommend&nbsp;the&nbsp;following&nbsp;tools:
>
>
> apache/skywalking-eyes:&nbsp;Flexible&nbsp;configuration,&nbsp;suitable&nbsp;for&nbsp;modern
> projects.
>
>
> apache/rat:&nbsp;A&nbsp;mature&nbsp;tool&nbsp;widely&nbsp;used&nbsp;within&nbsp;ASF&nbsp;projects.
>
>
> 2.&nbsp;Assembling&nbsp;LICENSE,&nbsp;NOTICE,&nbsp;and&nbsp;DISCLAIMER&nbsp;Files
>
> &nbsp;&nbsp;&nbsp;Please&nbsp;make&nbsp;sure&nbsp;the&nbsp;following&nbsp;files&nbsp;are&nbsp;placed&nbsp;in&nbsp;the&nbsp;root&nbsp;of&nbsp;the
> repository:
>
>
> LICENSE&nbsp;and&nbsp;NOTICE:&nbsp;See&nbsp;the&nbsp;ASF&nbsp;guide&nbsp;for&nbsp;proper&nbsp;content:
> https://infra.apache.org/licensing-howto.html#mod-notice
>
>
> DISCLAIMER:&nbsp;This&nbsp;is&nbsp;mandatory&nbsp;during&nbsp;the&nbsp;incubation&nbsp;phase.
> Reference:&nbsp;
> https://incubator.apache.org/policy/incubation.html#disclaimers
>
>
> Assembling&nbsp;LICENSE&nbsp;and&nbsp;NOTICE&nbsp;files&nbsp;for&nbsp;binary&nbsp;distributions&nbsp;can&nbsp;be&nbsp;a&nbsp;bit
>
> tricky.&nbsp;I’ll&nbsp;provide&nbsp;more&nbsp;detailed&nbsp;guidance&nbsp;on&nbsp;that&nbsp;once&nbsp;the&nbsp;basic
> groundwork&nbsp;is&nbsp;complete.
>
>
> In&nbsp;the&nbsp;meantime,&nbsp;I&nbsp;strongly&nbsp;encourage&nbsp;everyone&nbsp;to&nbsp;read&nbsp;these&nbsp;guides
>
> carefully&nbsp;—&nbsp;they&nbsp;are&nbsp;very&nbsp;informative&nbsp;and&nbsp;helpful.&nbsp;🙂
>
> 3.&nbsp;Release&nbsp;Infrastructure&nbsp;Preparation
>
>
> If&nbsp;we&nbsp;plan&nbsp;to&nbsp;publish&nbsp;Maven&nbsp;artifacts&nbsp;or&nbsp;Docker&nbsp;images&nbsp;in&nbsp;the&nbsp;future,&nbsp;we’ll
> need&nbsp;to&nbsp;coordinate&nbsp;with&nbsp;the&nbsp;Infra&nbsp;team&nbsp;to&nbsp;set&nbsp;up&nbsp;accounts&nbsp;and
> permissions
> on&nbsp;the&nbsp;required&nbsp;platforms.
> https://incubator.apache.org/guides/distribution.html
>
> Would&nbsp;anyone&nbsp;in&nbsp;the&nbsp;community&nbsp;be&nbsp;interested&nbsp;in&nbsp;taking&nbsp;this&nbsp;on?&nbsp;The&nbsp;process
>
> is&nbsp;similar&nbsp;to&nbsp;what&nbsp;we've&nbsp;done&nbsp;before&nbsp;—&nbsp;just&nbsp;submit&nbsp;an&nbsp;Infra&nbsp;ticket.&nbsp;I’m
>
> happy&nbsp;to&nbsp;provide&nbsp;a&nbsp;template&nbsp;or&nbsp;example&nbsp;if&nbsp;needed.
>
>
> I’ll&nbsp;cover&nbsp;branding,&nbsp;website&nbsp;setup,&nbsp;and&nbsp;release-related&nbsp;topics&nbsp;in&nbsp;a
>
> follow-up&nbsp;email&nbsp;—&nbsp;this&nbsp;one&nbsp;is&nbsp;already&nbsp;quite&nbsp;long&nbsp;(and&nbsp;admittedly&nbsp;a&nbsp;bit
>
> delayed&nbsp;😅).&nbsp;If&nbsp;any&nbsp;mentor&nbsp;would&nbsp;like&nbsp;to&nbsp;jump&nbsp;in&nbsp;and&nbsp;help&nbsp;with&nbsp;that,&nbsp;feel
> free!
>
> --&nbsp;
> Best&nbsp;wishes！
> CalvinKirs



--
Best wishes！
CalvinKirs