Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [krazo-dev] Future of Krazo extensions
  • From: Tobias Erdle <tobi.erdle@xxxxxxxxx>
  • Date: Fri, 5 Aug 2022 15:02:46 +0200
  • Autocrypt: addr=tobi.erdle@xxxxxxxxx; keydata= xsDNBGKOk6YBDADihWl/SZIMwXjrmgCMkMd7STtXb7BEfVuEYObF0L6FAE37b782GpCdTi5D PX2Dy1w9GDLraBB8tVMRF8PuIAk8+wn2GPS+wUmcpj+fMx1qgzhRV2kKgTeQYKSFtZIBkJi/ AdwXrzXbIlV9bZxMTa8AQBia7CE3pWOQTtXiTDi3UPcjScYSn8pE4ibF7+21+mRvuVarbzT2 nQFYLoQ3FnblSQAnq8s186XTIHo7Nxn08W2hcIJP5QSO38eMYtoHWOXU+jEj8NDhI6qF99IP jPVg7lHuUG90Oa7yp+wdlQad4LjPbvaWJ0ZiVXvw+kOMjLDNOPAGiHpd7JMBcVpktIzqive+ G7aSescOLFdRXmsWI9NORvU3fiEq0gFpl4EEi/ovNH6ol29sIhEElDCQ5n2hq2HZAXanoF21 MOC7QnxkVpLy5NA6Wlyq5WluRABxeGOqS95vuhZVzhzcCmmFMfeAyLfRojCC4nkiPmhfH9DZ 9a0Ootx85v5ucNynwwp/g2cAEQEAAc0jVG9iaWFzIEVyZGxlIDx0b2JpLmVyZGxlQGdtYWls LmNvbT7CwRQEEwEKAD4WIQSNwrJ9YQSpNwq230oaRgVugIu4MAUCYo6TpgIbAwUJA8JnAAUL CQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRAaRgVugIu4ML/dDACK0gakaD0ofss4dc0GIggd WzLdlQvH6pmANkMb7erx8FDTk6LymxzybDAVzy3V1NqF1GGDNDxW5f3fX9mzv12ocaNc8FE6 S4dZ2KYkQik2R17fgun61PWQQwhjUyoSzWZAB386BaBDaGSKk8JBvgs+fL8PqVp8zfQ36Osf nAGvs2sH1VUJ7fRf/W/4kY/G1StyE1hNALv0jfuyud+7jtyLSulN7rvebl0Kxv1pm15tpyq9 vN/ONSFpTgbiVtrO9M1gh2wC8uHL+DtT9A2E606kMDYLSzr2/F8uOsWZrZ/+Npv2fc34EbtH qXdpgdvLeaDZWrEe/nCvddehoWS3oYDCqcNXo1LltmXtIKt5rcRDxixcZOBXUgOgEJiu7V+j GzszPZeHe6oOconrCsXN2dNg3hob5UHEiMs8bbUIOfgveSRmvSnY6vJxgFJyPlLZWt1xaxGU WoF1c0DuhJC8HnF8kcGxduwpQ241HPQ+Qi2+h2C6n06+sFGPktLwqFzLKGHOwM0EYo6TpgEM AMFKQ8d/1bcfxeByoNcrBd4HkmkwMsYDsGipwgzldYIi2bbIBDXAA/Lu5zHeJZPUt3OLcNM7 7HBw0fS/GcDQG0DnMH9h8KDFAAfjxW1SNFHhI7gOcakL1ocTXnQdcHRt2NNL025lTqs54qG0 kTflVWtQf7pBP73X+38rEUUHd0nTRs122xmT72670wnnn6Rqw3o6cwB8mBp4MRo3MhYdT4Sm M3w9kIti2olHzRYzqK3I9t9qxYsBqaQqhvgnDvcsNV6JSDeaieCEG82+vvkZsNr2vM5+psFf V4rnaNhLzBoad2HghTtsKxJIsXo2USMuCrRhLqfn3TS9+txQS9ewEOFnNMBToCZVH9djWoi1 Q8LdhA1SjTDdFr5pTDjHPVMewdOkmUfonZYXNaH/1E3Lz55uMDxMDNwUqa8mesDffzuk8qpN sMMIJu+l7boNzddTDxeqED7ghnn7dDbB6CqhqXAI86ZasePEvtlDn+TzJv7h87Ej28cEfDnT 51fSZj3fjQARAQABwsD8BBgBCgAmFiEEjcKyfWEEqTcKtt9KGkYFboCLuDAFAmKOk6YCGwwF CQPCZwAACgkQGkYFboCLuDATCwwAzze5LrFYJDLbGKssqt4rCChl9m24zv6uwbXWZG+NjOTs s+8q9Qr9mfNMTwuEJilqqXT//tkbls8fBBovmfEP9Mp/IHdyMQRusbAgCSpx5v3Nk7PmYRuv bhpwQWpR+51qdkGaFFYZDP/n5pGE/+QzzQ7F1vLr6q+FGjMdZHGS/r8quEEyrRyfPZ3rLKVV kWsEj0cmlnPSyW5uTXWew/14OZL0EcfbDBAXTk2Sb6Z7L2tn10MmNzMm2oztKvzQ6qmqr3Zb mjcmxyYNT6CIevRYLjfJFJp6CrKLwm+bZr/KaGPAyUsYpaSvWcMDiET/5nmvhaL6X36hexQu QobdTWm5Ng56+nimHp+xekvw5BkbxiK1glUJ5wNyyS6p7+E1KEfeljmOccv75ONb1tWeVVyI FIrPNfMGkCEqh2YhVyFO2r8PODhTAdHtfoFSPUxITsYWRUkZgTw9HACYK7B28uB+07pU6Lt6 0/Wp8pmLkHjM/O0XryQOvVMkBdJyFvWQhqj4
  • Delivered-to: krazo-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/krazo-dev/>
  • List-help: <mailto:krazo-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/krazo-dev>, <mailto:krazo-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/krazo-dev>, <mailto:krazo-dev-request@eclipse.org?subject=unsubscribe>
  • User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0

Hello again,

since today the extensions can be found here: https://github.com/eclipse-ee4j/krazo-extensions
All Krazo Committers should've write access to this repository.

Within the next days I'll add the necessary Jenkins jobs and finally remove the extensions from Krazo Core (https://github.com/eclipse-ee4j/krazo/pull/328), so we can start with the release process for Krazo 3.0.0 and MVC 2.1 :)

Have a nice weekend and best regards,

Tobias

On 04.08.22 10:58, Tobias Erdle wrote:

Hi all,

because there was no more feedback and we reached the 4th august, I'm closing the 'poll' by this mail. According to the answers, variant (1) is preferred. So I'm going to organize a repository inside the Eclipse Foundation which will be called 'krazo-extensions' (or similar) and migrate the extensions inside this repository. Also I'll add the required Jenkins jobs so we can build and release these artifacts.

Thanks for your participation and feedback. I'll get in touch with you as soon as the migration has been done.

Best regards,

Tobias

On 01.08.22 21:04, Maarten Mulders wrote:

Thanks for the clarification, Tobias. Then for sure my preference would be (1). It's cool that Krazo can do all these view engines, but maintaining them should not go at the cost of progressing Krazo.

Thanks,

Maarten

On 01/08/2022 20:57, Tobias Erdle wrote:
Hi Maarten,

thanks for your feedback!

A view engine is the integration of a template engine. The specification expects JSP and JSF to be a mandatory view engines in each Jakarta MVC implementation at the moment, so those are part of the Krazo Core. In addition, we have the „Extensions“ (ext module inside the repository), which provide support for additional template engines like Thymeleaf.
So Krazo will always have at least one template engine, but we‘d like to reduce the maintenance effort for additional engines, which is the cause for this mail :)

Thanks,

Tobias
Am 01.08.2022 um 20:30 schrieb Maarten Mulders <m.th.mulders@xxxxxxxxx>:



Hi all,

Thanks for the reminder! First of all, I think it makes sense to focus the limited time there is to what matters most.

Do I understand correctly that a view engine is not always an extension, but view engine could be an extension? If so, I would say we should keep at least 1 view engine in Krazo itself. I guess that would be JSP, since that is available in Servlet Containers anyway.

With the assumption that Krazo would still have at least 1 view engine available "out of the box", I would also prefer option (1).

Thanks,

Maarten

On 31/07/2022 15:38, Christian Kaltepoth wrote:
Hi all,

sorry for the delayed response. I was on vacation and tried to stay away from any kind of computer for some time. ;-)

I agree that having many view engine extensions in Krazo isn't optimal. Especially because most of them were created actually just for showing how easy it is to build a custom view engine. But maintaining them and keeping them updated is a lot of work.

Therefore, I would also prefer option (1) which means that we would move them to a separate repo/project.

Christian

Am So., 31. Juli 2022 um 15:07 Uhr schrieb Tobias Erdle <tobi.erdle@xxxxxxxxx>:
Hello again,

because there was just one reaction to this mail (thanks again), I‘ll extend the feedback period until next thursday, the 08/04/2022. It‘d be great to get any more feedback, even something like „I‘m not interesed in those extensions, do whatever you want“ ;)

Thanks and best regards,

Tobias

> Am 23.07.2022 um 14:46 schrieb Tobias Erdle <tobi.erdle@xxxxxxxxx>:
>
> Hi all,
>
> in the last MVC meeting on Thursday, 07/21/2022, we talked about the future of Krazo Extensions.
>
> For a while now, the situation is that we have hardly any active developers, but a lot of code with external dependencies, which almost always need CQs with every update. Anyone who has ever created one knows how cumbersome this is and how much time it can cost. In addition, the development of Krazo Core is slow. For this reason we want to try to focus more on core development and minimize effort with extensions etc.. To achieve this, there are several ideas:
>
> 1. the extensions are completely outsourced to a separate repository and the maintenance runs in parallel to Krazo, if necessary by other people. Whether this runs under the umbrella of the Eclipse Foundation or not has to be clarified.
>
> 2. only selected extensions are kept in the Krazo repository, for whose engines there are regular updates or which are widely used. For these, however, maintainers should be found.
>
> 3. everything stays as it is, but extensions are kept alive with minimal effort or removed if the maintenance effort becomes too high.
>
> Since this is a breaking change and Krazo 3.0.0 is slowly moving towards release, the topic should be discussed soon. I would suggest that there is at least a majority in favor of one of the variants by 07/30/2022, so that further action can then be taken. If there are any other ideas or thoughts, feel free to mention them.
>
> Thanks and best regards
>
> Tobias
>
> P. S.
> Personally, I would currently prefer variant 1, because this way, if necessary, new maintainers can be found and at the same time the Krazo repository would become leaner. Since I like to use Thymeleaf and the extension, I would also take over the maintenance.
>
> P. P. S.
>
> You can also comment into https://github.com/eclipse-ee4j/krazo/issues/319, which is the corresponding issue to this mail.
>
_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev


--
Christian Kaltepoth


_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev

_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev


_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev

Attachment: OpenPGP_0x1A46056E808BB830.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Back to the top