Taiga6 is almost here! See what's coming!

[Pablo Ruiz Múzquiz]

Hi Taiga community!

We have big plans for 2021. Part of it is to rethink a bit how to better structure the different community spaces there are. Should we go for a forum? chat? We are still undecided but one thing's clear, much is to be done in terms of engagement.

Taiga is growing! We have bigger team now and it will continue to grow in 2021. During 2020 we worked hard in both Taiga5 and the upcoming Taiga6 major release.

I'd like to share the blog post we just published. It gives you a taste of what's to come. Enjoy!

https://blog.taiga.io/taiga6-pre-announcement.html

All the best

Pablo

Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, y pudiendo contener información confidencial sometida a secreto profesional, o cuya divulgación esté legalmente prohibida. Cualquier opinión en él contenida es exclusiva de su autor y no representa necesariamente la opinión de la empresa. Si ha recibido este mensaje por error, le rogamos nos lo comunique de forma inmediata por esta misma vía y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. El correo electrónico vía Internet no es seguro y no se puede garantizar que no haya errores ya que puede ser interceptado, modificado, perdido o destruido, o contener virus. Cualquier persona que se ponga en contacto con nosotros por correo electrónico se considerará que asume estos riesgos. KALEIDOS OPEN SOURCE se reserva las acciones legales que le correspondan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente del mismo. INFORMACIÓN PROTECCIÓN DE DATOS. Responsable: KALEIDOS OPEN SOURCE (B86241973) Le informamos que sus datos identificativos y los contenidos en los correos electrónicos y ficheros adjuntos pueden ser incorporados a nuestras bases de datos con la finalidad de mantener relaciones profesionales y/o comerciales y, que serán conservados mientras se mantenga la relación. Si lo desea, puede ejercer su derecho a acceder, rectificar y suprimir sus datos y demás reconocidos normativamente dirigiéndose al correo emisor o en los datos del responsable. Para información y consultas visite nuestra web  https://kaleidos.net

[German Porta]

Hi Pablo and the community. How is Taiga6 coming along? According to the preview article you sent, it seems it will be a very impressive release. Any target date that you can share?

Thanks in advance, and great work!

German

[Pablo Ruiz Múzquiz]

Hi German

It should hit shelves by the end of January :)

Stay tuned.

Pablo

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/3d10910a-12e9-443e-8773-ff71492eb1c8n%40googlegroups.com.

[German Porta]

Thanks Pablo! I'll be standing by to give it a shoot as soon as it becomes available. If it works for my group, then I'll be contacting you to see if we can contribute somehow with the project.

Best regards, and wishing you and this great community a Happy 2021!

German

[German Porta]

Hi Pablo and Taiga community. We just installed an instance of Taiga 6 to take a look at it, and it looks really nice. Great job to everyone involved!

Pablo, we are a group of developers that are at the moment using Jira (we have bought a permanent licence which we currently host for our group) but I have to admit that I love the design and simplicity of Taiga. We would like to consider start using it, and at the same time contribute some work to the community, although our expertise is not exactly in these technologies (we do .Net Core and React, but we have some team members that know a bit of Angular and Python so I think we can help). If there is any chance you can contact me directly to my email to understand if there is a way our group can help, please do. Best regards!

[German Porta]

Sorry, one more question: For Taiga 5 there was a very handy container officially maintained by the Taiga group which included all pieces required by the tool, while for Taiga 6 we had to install all the different containers involved. Is there a plan to create/maintain a single container option as Taiga 5 had? If not, is there any interest, in which case our group can maybe create just a container and maintain it so the community can use it? Although I understand for prod it may be better to keep the containers separated, I think the single container option is very handy for those that want to give it a try, or for small non-critical projects. Just a thought.

[Pablo Ruiz Múzquiz]

Hi German

Sure! I'll write you this Monday and see what options are available. We'd love to have some nice contributions from your team!

As for the docker for Taiga5, I guess you mean https://github.com/taigaio/docker-taiga-5. It was originally maintained by devinsolutions. It was simple & straightforward but not exactly how we believe a docker solution for Taiga should be handled for production (which is our target).

We don't plan to continue to work on such docker for Taiga5 but we're open to ideas for docker for Taiga6. Yamila Moreno, in cc, is in charge. You can reach her and see what she plans for the future.

Thanks for your support and kind words!!

Pablo

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/9c602fa1-59c9-4a21-8028-f6a3be454a49n%40googlegroups.com.

--

	Pablo Ruiz Múzquiz CEO & Co-founder  (+34) 639635072 (+44) 07719222665  kaleidos.net

[quen...@electropositive.co.nz]

I''m certainly on the bus for a one container solution - this container is crazy complicated - the complete opposite of what docker should be.  Mattermost do it with their omnibus container, so I think Taiga could too.

I've never managed to get events working with Taiga, which makes it really challenging to work with.

Finally got Taiga 6 dockers working - lots of challenges that were unexpected and still events don't work lol.  That's the whole reason why I want it.

Anyway, not trying to hijack thread, just saying, I agree - one container would be great, or at least get rid of these annoying docker links that have been used.  Proper docker variables with config options is all we really need.

[German Porta]

Excellent! Standing by.

German

[Yamila Moreno]

Hi there!

@German, should you have any questions, we'd be happy to answer.

@Quentin

> I''m certainly on the bus for a one container solution - this container is crazy complicated - the complete opposite of what docker should be.  Mattermost do it with their omnibus container, so I think Taiga could too.

There are different approaches, and this docker is intended to give freedom to the deploy to those people who want it, as well a simple way to configure a multi-service platform.

> I've never managed to get events working with Taiga, which makes it really challenging to work with.

I suggest you open a new thread on this topic and we can help you; don't forget to share your configuration and the specific problems you're finding. As far as we know, the events are properly working.

> Finally got Taiga 6 dockers working - lots of challenges that were unexpected and still events don't work lol.  That's the whole reason why I want it.

Please, tell us which challenges did you find so we can go through them and document better or fix whenever it's needed.

> Anyway, not trying to hijack thread, just saying, I agree - one container would be great, or at least get rid of these annoying docker links that have been used.  Proper docker variables with config options is all we really need.

What would be "proper docker variables with config options"? there are plenty of variables. I'm guessing we can simplify the docker-compose removing the optional ones (which default to "false"), and it would be better to read.

What do you miss in the docker-compose.yml? [I would request a new thread for this as well].

Thank you everybody!

--

	Yamila Moreno Suárez COO & Cofounder   kaleidos.net