> Instead Grails would best work to seek an SGA from the author or ask them to > join and personally donate the code via an ICLA.
Did I misread some threads? I suppose it's about Apache Druid and druid-operator. Apache Druid is a TLP and is not Grails .. Where comes Grails? Best, tison. Dave Fisher <w...@apache.org> 于2025年8月10日周日 04:15写道: > > Hi Tison, > > > On Aug 9, 2025, at 12:44 AM, tison <wander4...@gmail.com> wrote: > > > > Hi Razin, > > > > You can follow [1][2] for the process going through the IP clearance. > > Once the IP clearance proposal gets lazy approval, you can file an > > INFRA ticket ask for repo transfer. > > > > [1] https://incubator.apache.org/ip-clearance/ > > [2] https://incubator.apache.org/ip-clearance/ip-clearance-template.html > > The IP Clearance process is surprisingly only meant for PMCs and not for > Podlings. > > Instead Grails would best work to seek an SGA from the author or ask them to > join and personally donate the code via an ICLA. > > Best, > Dave > > > > > However, I noticed that there is an organization named > > https://github.com/druid-io/, which can mislead Druid's > > branding (that's, a third party unofficial org under the name of an > > ASF project). You should work with their people to figure out a > > different name. This can be a separate issue to resolve, though. > > > > Best, > > tison. > > > > Razin Bouzar <rbou...@salesforce.com.invalid> 于2025年8月9日周六 11:14写道: > > > >> > >> Hello, > >> > >> Craig, thank you for the information. > >> > >> The druid-operator project originated with Himanshu Gupta in 2019 under the > >> Apache License, Version 2.0. The first commit in the original repository, > >> data-io/druid-operator <https://github.com/druid-io/druid-operator>, was > >> authored by Himanshu Gupta on Oct 24 10:24:22 2019 with the message "druid > >> operator based on operator-sdk v0.5, written in collaboration with Akash > >> Dwivedi <akash....@gmail.com>" (commit hash bb07f14). In 2022, the > >> repository was forked to datainfrahq/druid-operator </> following community > >> discussion <https://github.com/druid-io/druid-operator/issues/329>. The > >> first commit in the fork matches the first commit in the origin, > >> data-io/druid-operator. > >> > >> Over the lifetime of the project Himanshu Gupta and Adheip Singh have made > >> the majority of contributions to the repo. We fetched contributor activity > >> running `git shortlog -sne`. Himanshu Gupta and Adheip Singh both have > >> Individual Contributor License Agreements (ICLAs) on file. > >> > >> The project has had multiple tagged releases, with a tag history available > >> from the git repository. A detailed log of annotated tags is available for > >> each repo. The LICENSE file in the original and forked repositories has > >> consistently contained the Apache License, Version 2.0. A review of the > >> LICENSE file history via `git log --follow -- LICENSE` confirms that no > >> other license terms have been introduced. A scan of the source code via > >> `grep -R "Licensed under the Apache License"` confirms that appropriate > >> license headers are present in the codebase. We have compiled all > >> supporting documentation from each repo in a shared Google Drive folder > >> <https://drive.google.com/drive/folders/16WHwZdI7iZg8xBSeoPdUzX3qtgZlJyBB>, > >> including full commit logs from both repositories, contributor lists with > >> commit counts, annotated tag metadata, license header scans, and internal > >> records of signed ICLAs. > >> > >> In summary, the druid-operator project has maintained consistent Apache 2.0 > >> licensing from its origin in 2019 through the present. Major contributors > >> have ICLAs on file, and the project history is fully traceable through > >> public git logs. We request guidance on next steps. > >> > >> Sincerely, > >> Razin > >> > >> On Sat, May 10, 2025 at 9:52 AM Craig Russell <apache....@gmail.com> wrote: > >> > >>> Hi, > >>> > >>> The main thing to do is to establish IP ownership of the code to be > >>> donated (in this case, the modifications to the original). If all > >>> significant contributors sign an ICLA, and they retain ownership of the > >>> code, then that should do it. > >>> > >>> If some external entity owns the IP to the code, then a software grant > >>> (SGA) would be appropriate, signed by the representative of the IP owner. > >>> The grant would be filed as part of the process. > >>> > >>> Warm regards, > >>> Craig > >>> > >>> > >>>> On May 9, 2025, at 15:58, Razin Bouzar <rbou...@salesforce.com.INVALID> > >>> wrote: > >>>> > >>>> Dear Apache Incubator Community, > >>>> > >>>> I am seeking guidance on the process for donating the druid-operator > >>>> <https://github.com/datainfrahq/druid-operator> to the Apache Druid > >>>> project. The project is a fork of an original operator > >>>> <https://github.com/druid-io/druid-operator> developed for managing and > >>>> scaling Apache Druid clusters. The project is licensed under the Apache > >>>> License 2.0 > >>>> <https://github.com/datainfrahq/druid-operator/blob/master/LICENSE>, and > >>>> there is community consensus > >>>> <https://lists.apache.org/thread/1t5m030o54n4ckjqcdnbd87z6mpnl8t5> for > >>> this > >>>> donation. > >>>> > >>>> We are familiar with the IP Clearance process but would appreciate > >>>> clarification on: > >>>> > >>>> 1. Any specific licensing considerations given the project's status as > >>> a > >>>> fork. > >>>> 2. Additional legal or procedural steps before IP Clearance. > >>>> > >>>> Looking forward to your guidance. > >>>> > >>>> Sincerely, > >>>> Razin Bouzar > >>> > >>> Craig L Russell > >>> c...@apache.org > >>> > >>> > >> > >> -- > >> RAZIN BOUZAR > >> Monitoring Cloud | Salesforce > >> Mobile: 317-502-8995 > >> > >> <https://smart.salesforce.com/sig/rbouzar//us_mb/default/link.html> > > > > --------------------------------------------------------------------- > > 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