Baikal: Move to a broader used Framework like symfony ...

[DeepDiver1975]

• https://github.com/jeromeschneider/Flake is unmaintained for many years
• Looking at it common practice like unit testing seems not possible ($GLOBALS are used)
• side effect: a framework like Symfony allows access to a broaded developer base

[DeepDiver1975]

oh - just saw this: https://github.com/sabre-io/Baikal/pull/568

[DeepDiver1975]

@ByteHamster shall we revive https://github.com/sabre-io/Baikal/pull/568 ???
Happy to help out any time ..

[derStephan]

I am afraid, this project is dead. https://evertpot.com/sabredav-maintenance-update/

If you still want to help out, contact Evert.

Edit: ooops. Seems like there is a new king in town. There is a very recent release and a bunch of commits to master. Sorry if I hurt anyone's feelings. Glad to see some action.

[ByteHamster]

shall we revive #568

If you want to do that, I am happy to test and review. I, myself, mostly want to keep the project working on new php versions and fix bugs that appear. I do not plan to rewrite the project or add new features which require lots of work. I wrote that to evert and he seemed to agree (at least he still made me a maintainer).

It looks like #568 is nearly finished though. I have not tested that branch yet.

[mmoll]

The problem is that Silex also got abandoned in the meanwhile, so Symfony 4 would be IMHO the way to go.

[DeepDiver1975]

The problem is that Silex also got abandoned in the meanwhile, so Symfony 4 would be IMHO the way to go.

https://symfony.com/blog/the-end-of-silex ... so symfony 4 then .... let's see ...

[evert]

Yea I put a ton of work in #568 and tried to fix all the major issues with the codebase as is. I totally accept if you want to abandon it though, but if you're doing a new version with a better framework it might be easier to start from #568 instead of the master branch.

[evert]

Duplicate of #502