Le samedi 21 octobre 2017, 08:16:35 CEST Stephen Connolly a écrit : > On Sat 21 Oct 2017 at 08:45, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > ok, let's switch directly to the Docker case > > > > I'm not a Docker expert, then I'm discovering things that my be obvious to > > others > > > > IIUC Docker has an "officiel images" project [1] where Carlos provided a > > Maven > > image [2]: then this image is known as "the official Maven Docker image" > > Carlos is an individual, he's also a PMC member of Maven > > > > what do we want to say: the PMC member has provided an official Docker > > image or > > an individual has provided an official Docker image? > > > > depending on the answer, some way of doing has to be changed (Git location > > or > > naming of the official image) > > I’m in favour of creating a repo for the dockerfile, license.txt, read me, > notices, etc ok, here I follow
> and follow the standard release vote lifecycle for that > dockerfile. here, I'm not sure this really has a meaning in these official Docker images cases: IIUC, on a new Maven core release that we want to promote, there are 2 actions that are required: 1. modify the MAVEN_VERSION and SHA values in */Dockerfile in the git repo [1] 2. have a PR merged to Docker official-images to update the sha1 in official- images/library/maven [2] Between the 2 steps, we can choose to vote, or not to vote, I don't know what's the best: we already voted for the Maven release that gets the new recommended version. What is important to me is that anybody from the PMC can do the PR to Docker official-images (if we decide that we maintain the official image, not only Carlos): there is not specific credentials One thing I see is that we can automate a check that the current official-image is our currently recommended Maven version: it's just about adding a new check to dist-tool-plugin that will be checked every day by Jenkins job [3] [1] https://github.com/carlossg/docker-maven [2] https://github.com/docker-library/official-images/blob/master/library/maven [3] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/ > > If we want that dockerfile in Maven-core repo, i’m Fine with that too given the content, a separate repo more reasonable > > Now the other question is how to get the image from that dockerfile into > docker... IIUC, that's the second point I wrote: we don't really put the image but update a commit reference to our Dockerfiles > > I’m happy for Carlos to continue doing in a personal capacity... +1 I'd be happy to just have this as an official PMC asset, with Carlos as our expert who wrote the subtle bunch of images, since IIUC, it's not really one image but a collection that one can choose from Regards, Hervé > > So i’d be > > “The dockerfile has been released by the Maven project and a member of the > PMC has uploaded the image” > > > Regards, > > > > Hervé > > > > [1] https://github.com/docker-library/official-images > > > > [2] > > https://github.com/docker-library/official-images/blob/master/library/mave > > n > > > > Le samedi 21 octobre 2017, 06:58:50 CEST Manfred Moser a écrit : > > > From my perspective it is just like sdkman including the conclusion. We > > > > have > > > > > other tasks at our hands, maintaining a docker images is not something > > > we > > > should bother with. However needs one can easily create one and there > > > > will > > > > > be thousands of variations different users want. > > > > > > Let them create it on their own. > > > > > > Manfred > > > > > > Hervé BOUTEMY wrote on 2017-10-20 18:46: > > > > true, from a general perspective, it's like sdkman > > > > > > > > we need to discuss then decide if we want to maintain Maven Docker > > > > integration (contrary to our current decision to not maintain Maven > > > > sdkman integration but let sdkman community do it) > > > > > > > > can we think about a general solution? perhaps not really a solution, > > > > but > > > > > > a > > > > decision process, yes > > > > > > > > to me, on each tool integration, there are key decision drivers: > > > > - importance of the tool on the market > > > > - interest of Maven devs to actually do integration maintenance > > > > - complexity of integration, technical prerequisites (with IDEs, for > > > > example, a dedicated independant project like m2e is necessary) > > > > - time factor: things evolve over time (e.g. 2 years ago, Docker was > > > > not > > > > > > what it is nowadays) > > > > > > > > any other key driver to document? > > > > > > > > once done, we'll discuss more precisely about the Docker integration > > > > case > > > > > > and probably finish with a vote :) > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > Le vendredi 20 octobre 2017, 11:30:49 CEST Robert Scholte a écrit : > > > >> Isn't this actually the same case as sdkman[1]? > > > >> Just wondering if we need to think about a general solution instead > > > >> of > > > >> pulling everything into our project when possible. > > > >> > > > >> thanks, > > > >> Robert > > > >> > > > >> [1] http://markmail.org/message/oofvszmf56tbr7et > > > >> > > > >> On Thu, 19 Oct 2017 19:30:57 +0200, Hervé BOUTEMY < > > > > herve.bout...@free.fr> > > > > > >> wrote: > > > >> > great idea > > > >> > > > > >> > ok, we need a git repo at ASF > > > >> > > > > >> > what else? > > > >> > Is there some sort of release process? some sort of source to > > > > release? > > > > > >> > Regards, > > > >> > > > > >> > Hervé > > > >> > > > > >> > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit : > > > >> >> Thanks for the pointer, Carlos! I had searched the archives, but > > > > maybe > > > > > >> >> I > > > >> >> didn't go back far enough. > > > >> >> > > > >> >> I think moving these Dockerfiles into an ASF repo would be great > > > > for > > > > > >> >> their > > > >> >> maintainability. > > > >> >> > > > >> >> Thanks, > > > >> >> > > > >> >> Mike > > > >> >> > > > >> >> On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote: > > > >> >> > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7, > > > >> >> > > > >> >> 2014,> > > > >> >> > > > >> >> > 00:23 when I created the image> > > > >> >> > > > > >> >> > > > > >> >> > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com> > > > >> >> > wrote:> > > > >> >> > > > > >> >> > > These images are kindly managed by a PMC member of our project > > > >> >> > > > >> >> (Carlos) > > > >> >> > > > >> >> but> > > > >> >> > > > >> >> > > yes they aren't managed directly by the project> > > > >> >> > > > > > >> >> > > We can easily see with him to improve this IMO.> > > > >> >> > > > > > >> >> > > When he started that (several years ago) Docker wasn't what it > > > > is > > > > > >> >> nowadays.> > > > >> >> > > > >> >> > > With docker being mainstream I agree that we can reconsider > > > > this.> > > > > > >> >> > > The docker image build/distribution could perhaps be part of > > > > our > > > > > >> >> release> > > > >> >> > > > >> >> > > process.> > > > >> >> > > > > > >> >> > > WDYT Carlos ?> > > > >> >> > > > > > >> >> > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob <md...@apache.org> > > > >> >> > > > >> >> wrote:> > > > >> >> > > > >> >> > > > I guess the natural follow-on question is whether the Maven > > > >> >> > > > >> >> community> > > > >> >> > > > >> >> > > > would consider publishing an official set of images? Or > > > >> >> > > > >> >> alternatively> > > > >> >> > > > >> >> > > > whether they should send a takedown notice to protect their > > > >> >> > > > brand > > > >> >> > > > >> >> and> > > > >> >> > > > >> >> > > > trademarks...> > > > >> >> > > > > > > >> >> > > > On 2017-10-18 18:36, "Manfred Moser" <ma...@simpligility.com > > > >> >> > > > >> >> wrote:> > > > >> >> > > > >> >> > > > > No. As you can see from the github URL this is NOT an > > > > apache > > > > > >> >> URL.> > > > >> >> > > > >> >> > > > > https://github.com/carlossg/docker-maven> > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > Mike Drob wrote on 2017-10-18 16:32:> > > > >> >> > > > > > > > >> >> > > > > > Hello,> > > > >> >> > > > > > > > > >> >> > > > > > Are the images at https://hub.docker.com/r/_/maven/ > > > >> >> > > > >> >> considered to > > > >> >> > > > >> >> be> > > > >> >> > > > >> >> > > > official> > > > >> >> > > > > > > >> >> > > > > > maven docker images and blessed/published by the PMC?> > > > >> >> > > > > > > > > >> >> > > > > > Thanks,> > > > >> >> > > > > > Mike> > > > > ---------------------------------------------------------------------> > > > > > >> >> > > > > > To unsubscribe, e-mail: > > users-unsubscr...@maven.apache.org> > > > > > >> >> > > > > > For additional commands, e-mail: > > > >> >> > > > > > users-h...@maven.apache.org> > > > > ---------------------------------------------------------------------> > > > > > >> >> > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > > >> >> > > > > For additional commands, e-mail: > > users-h...@maven.apache.org> > > > > > > ---------------------------------------------------------------------> > > > > > >> >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org> > > > >> >> > > > For additional commands, e-mail: users-h...@maven.apache.org > > > >> >> > > > > > >> >> > > --> > > > >> >> > > -----> > > > >> >> > > Arnaud H�ritier> > > > >> >> > > http://aheritier.net> > > > >> >> > > Mail/GTalk: aheritier AT gmail DOT com> > > > >> >> > > Twitter/Skype : aheritier> > > > > --------------------------------------------------------------------- > > > > > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > >> > For additional commands, e-mail: dev-h...@maven.apache.org > > > >> > > > >> --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- > > Sent from my phone --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
