Any reason to rename the project to ayza

[EugenMayer]

I'am on board since 7.x and kind of suprised to see a project rename with 10.0

Is there any reason to do so, esp using a name i cannot associate with anything SSL related.

Thanks for shortly elaborating on it / your reasoning and thanks for maintaining the project!

[Hakky54]

Hi @EugenMayer good to see you here again! It has been a long time since we have messaged eachother in the issues section, i think it was somewhere in 2023. Awesome to hear that you are still using the library ❤️

To be honest, a name change has always side effects so it is something which I didn't prefer to do. The community is already familar with the name. So changing it can raise confusion, developers who are not aware of the name change getting stuck on the old name/version, broken links etc.

I am bad in coming up with names. I had brainstormed long to come up with sslcontext-kickstart. The idea of that name was to simplify the creation of an sslcontext an to give a kickstart when configuring the http client or server. It made sense to me and I guess also to the community. During the early versions of the library it had a single file/class which provided some utility to easily create an sslcontext, however it grew much bigger and having more advance features over time such as hot reloading, using system certifiates, using pem files, extracting server certificates and much more. The name of the library didn't resembled the utilities which are provided within. It does not only create an sslcontext, it does much more. Next to that the pronunciation was long and not easy in my opinion and that was the biggest reason to change it. I already had the name change in my mind since version 3.x.x, but suppressed these thoughts as a name change is not good and people got used to it already.

As the community grew I had even more trouble to make the decision whether to change the name. I wanted a short name, which is easy to pronunce, easy to remember and unique. The name indeed has no relation with SSL yet, but hopefully it will be a synonym in the java world for simplifying ssl related task similar to jackson with json objectmapper or spring for dependency injection framework/http server or slf4j for logging api, mapstruct/selma for mapping etc.

The name Ayza comes from different combinations of letters from the names of my children. It is not yet used in GitHub, Maven Central or in the Java world, so it is pretty unique. I hope the community will like this name as much as I do. Sorry for the inconvenience by the way.

[EugenMayer]

Hello @Hakky54 , yes long time no seen / talk :)

We surely still use your lovely library!

Thanks for elaborating about the new name. I understand that you might have grown out of the old name and it did not reflect the actual capabilities.

I mean, surely Ayza might be easiert to spell, but for security related things i always love a descriptive name - just to be sure. This is just my taste, so surely no hard feelings - your the author, you pick and that's about it.

We are very happy that you put all the time into this project to maintain it. Very much appreciated.

[kofemann]

It will be good to add a line into the README file that mentions the rename fact, for example in the History section.

[Hakky54]

Thank you for pointing this out, I will add a reference in the changelog and readme to this discussion page