Big +1 for doing this within existing ASF infrastructure. Maybe indeed current SVN publishing a release snapshot + mirroring is the best way.
IMHO such 'released' charts do not have to have commit history at all (except 'release' commits) - just release 'snapshots' is enough. For all the other development uses, whatever the source repository is, you will be able too install 'development' chart from the sources. Still having clear guidelines on how to approach Docker images and 'rebuildability' by the users from sources is an important aspect IMHO. J. pt., 4 wrz 2020, 10:15 użytkownik Bertrand Delacretaz < bdelacre...@apache.org> napisał: > Hi, > > On Fri, Sep 4, 2020 at 9:22 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > ...I think having ASF "apache/chart" for all "officially released" helm > > charts is the best solution.... > > Sounds like a good idea but please use a more specific name, "charts" > is very generic. > > If distributing those Helm charts does not requires more than a web > server (with some metadata files I suppose) that can probably go in a > specific folder under https://dist.apache.org/repos/dist/release/ > > The next question is what kind of traffic is expected there, and can > the clients which will download those Helm charts handle redirects to > distribution mirrors? If yes the mechanism of > http://www.apache.org/dev/release-download-pages.html comes to mind, > if you can piggyback on that mirroring infrastructure that's a big > plus IMO. > > I guess the way to move forward is for the people interested in this > to list the technical and licensing/legal requirements on a wiki page > or equivalent, to discuss with the ASF infrastructure team how to best > support them. > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
