I’ve also brought this to Apache INFRA [1] and is being discussed in the
slack channel. Please feel free to chime in with Apache Infra team.

[1] - https://the-asf.slack.com/archives/CBX4TSBQ8/p1738586183227509



On Mon, Feb 3, 2025 at 7:48 AM Gonzalo Muñoz <gmuno...@apache.org> wrote:

> Thanks for bringing this to the mailing list.
> Currently, the PR proposals are for tests mainly, and when using
> Testcontainers -even in examples- are transparent to the final user, as
> there's a env variable ( TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX
> <https://java.testcontainers.org/features/image_name_substitution/> that
> acts as prefix on the fly). Only when using Quarkus devservices this won't
> work, as that's why some additional properties were added to the
> application.properties files, but they're for tests also.
> For kie-tools repo, probably needs more refinement, I'm not familiar with
> that repo, and some help there is highly appreciated.
>
> Kind regards,
> Gonzalo
>
> El lun, 3 feb 2025 a las 13:12, Alex Porcelli (<porce...@apache.org>)
> escribió:
>
> > With Docker’s recent policy changes affecting image pulling, many
> > companies, particularly vendors building downstream products, are
> > facing challenges. While vendors play a crucial role in maintaining a
> > healthy open source ecosystem, it’s important that we minimize any
> > negative impact on users.
> >
> > To address this, I propose the following guidelines for using Docker
> > Hub mirrors in the codebase:
> >
> > - Limit mirror usage to tests only.
> > - Ensure no user-facing code is affected (including examples).
> >
> > These guidelines aim to balance vendor support and user experience.
> > I’d appreciate your feedback and suggestions.
> >
> > -
> > Alex
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > For additional commands, e-mail: dev-h...@kie.apache.org
> >
> >
>

Reply via email to