<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;">Nice idea, Axel.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;">I’m open to collaborate, despite my basic skills on Docker, k8s and many other relevant software involved in the “new” Alfresco.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;">Now that Alfresco is ignoring deliberatively the Community (ACS 6.1 will be published without having a Community equivalent), it’s time to act. Probably providing a deployment and developing environment for everyone is the right approach.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;">I’m not able to organise this initiative, but let me know if I can help in any way.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; margin: 0px; line-height: auto;">Best,</div> <br> <div id="bloop_sign_1543221187793185024" class="bloop_sign"><span style="font-family:helvetica,arial;font-size:13px"></span><p style="font-family: Helvetica; line-height: normal; font-size: medium; color: rgb(34, 34, 34);"><span style="font-size: 10pt; color: rgb(31, 73, 125);">Angel Borroy</span><span style="font-size: 10pt;"><br></span><span lang="EN-US" xml:lang="EN-US" style="font-size: 9.5pt; font-family: Arial, sans-serif; color: rgb(94, 198, 242);">keen</span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14.666666984558105px;"><span lang="EN-US" xml:lang="EN-US" style="font-size: 9.5pt; font-family: Arial, sans-serif; color: rgb(58, 55, 59);">soft </span></b><span lang="EN-US" xml:lang="EN-US" style="font-size: 8pt; font-family: Arial, sans-serif; color: rgb(153, 153, 153);">a </span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14.666666984558105px;"><span lang="EN-US" xml:lang="EN-US" style="font-size: 9.5pt; font-family: Arial, sans-serif; color: rgb(192, 0, 0);">UST </span></b><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14.666666984558105px;"><span lang="EN-US" xml:lang="EN-US" style="font-size: 9.5pt; font-family: Arial, sans-serif; color: rgb(127, 127, 127);">Global </span></b><span lang="EN-US" xml:lang="EN-US" style="font-size: 8pt; font-family: Arial, sans-serif; color: rgb(153, 153, 153);">company</span></p><p style="font-family: Helvetica; line-height: normal; font-size: medium; color: rgb(34, 34, 34);"><span style="font-size: 9pt; color: rgb(31, 73, 125);">email: </span><a href="mailto:angel.borroy@keensoft.es"><span style="font-size: 9pt; color: blue;">angel.borroy@keensoft.es</span></a><span style="font-size: 9pt; color: rgb(31, 73, 125);"><br>web: </span><a href="http://www.keensoft.es/"><span style="font-size: 9pt; color: blue;">http://www.keensoft.es</span></a><span style="font-size: 9pt; color: rgb(31, 73, 125);"><br>móvil: <a href="tel://+34 655 47 47 55">+34 655 47 47 55</a></span></p><p style="font-family: Helvetica; line-height: normal; font-size: medium; color: rgb(34, 34, 34);"><span style="font-size: 9pt; color: rgb(153, 153, 153);">CONFIDENCIALIDAD:</span></p><p style="font-family: Helvetica; line-height: normal; font-size: medium; color: rgb(34, 34, 34);"><span style="font-size: 9pt; color: rgb(153, 153, 153);">La presente comunicación y, en su caso, los ficheros que lleve adjuntos, pertenecen exclusivamente a las personas a las que va dirigido y puede contener información confidencial. Si usted no es el destinatario de este mensaje (o la persona responsable de su entrega), considérese advertido de que lo ha recibido por error y que cualquier uso, difusión, reenvío o copia están prohibidos legalmente. Si ha recibido este mensaje por error, por favor notifíquelo al remitente y proceda a destruirlo inmediatamente.</span></p><p style="font-family: Helvetica; line-height: normal; font-size: medium; color: rgb(34, 34, 34);"><span lang="EN-US" xml:lang="EN-US" style="font-size: 9pt; color: rgb(153, 153, 153);">This message and the attached documents may contain privileged/confidential information and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient (or responsible for delivery of the message to such a person) be advised that you have received this message in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this message in error please notify it to the sender and destroy it immediately.</span></p></div> <br><p class="airmail_on">On 25 November 2018 at 22:57:06, Axel Faust (<a href="mailto:axel.faust.g@googlemail.com">axel.faust.g@googlemail.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hello guys,<br><br>TL;DR: Instead of revisiting our previous pre-bundled Community build<br>idea, maybe more short-term / easier to realize value could be gained by<br>collaborating on guides / documentation / examples regarding Docker<br>deployments to help community members make the switch, AND/OR create a<br>standard build setup (in lieu of an updated Alfresco SDK that may never<br>arrive) incorporating the new deployment approach and achieving full<br>compatibility with the most recent Alfresco releases.<br><br>This mail is a revisit of a mail Daren sent in the middle of the thread<br>for volunteers for the DevCon talk submission review ([1]). I don't know<br>how many actually read the mail considering the misleading subject line.<br>In it he asked if there is interest in revisiting our previous work<br>around a pre-bundled Alfresco Community build (at the time using puppet)<br>and maybe adapted / updating that to be in line with the current Docker<br>/ Kubernetes approach.<br><br>In the last two months I have had the (dis-)pleasure to familiarize<br>myself with the current state of the Alfresco Docker and Helm charts /<br>Kubernetes work in preparation for a training at an Alfresco partner.<br>Anyone following me on Twitter might have seen a rant or two. It<br>certainly is not the most intuitive and not helped by the fact that<br>Alfresco tends to break stuff shortly after providing an initially<br>working state.<br><br>Given how tricky it can be for community members / customers to switch<br>over to the new approach without any prior experience, I would say that<br>any guides / documentation that we as the Order could collaboratively<br>put together would be much more valuable/needed at this point than<br>simply revisiting the pre-bundled build. As both the Docker Compose<br>scripts and Helm charts from Alfresco should only be considered as a<br>starting point / reference rather than a ready-to-use setup, we might<br>also want to look into providing improved variants for these (Helm may<br>be a lower priority as it/Kubernetes likely is not relevant for most<br>community users). I know that Angel has already done work in the area of<br>an improved compose reference ([2]) - maybe that could be a starting<br>point to flesh out / improve upon...<br><br>In my training I have also integrated the new Docker images as a runtime<br>environment for ("not-really-rapid") application development in my Maven<br>setup, and also used it for the integration tests therein. In another,<br>personal project I have started to use Docker containers even for my<br>regular unit tests.<br>Alfresco has still not released a SDK natively compatible with Alfresco<br>6, and given their long-term goal of moving customers/users off of<br>in-process extensions may likely not provide an updated version anytime<br>soon. I know most people in the Order have sufficient skill to adapt the<br>current SDK to work with 6, but that is likely not true for most<br>community users out there. So maybe we as the Order should look into<br>providing a reference build setup of our own, using the new<br>incorporating the new Docker approach as best as possible. And maybe<br>such work will naturally lead us to general improvements / definition of<br>a base image e.g. with regards to image size, code+test round-trip time<br>etc...<br><br>Regards<br><br>Axel<br><br><br>[1]<br>http://lists.xtreamlab.net/pipermail/ootb-hive/2018-September/001028.html<br><br>[2] https://github.com/keensoft/docker-alfresco<br><br>_______________________________________________<br>OOTB-hive mailing list<br>OOTB-hive@lists.xtreamlab.net<br>https://lists.xtreamlab.net/mailman/listinfo/ootb-hive<br></div></div></span></blockquote></body></html>