I’ve only been following Kirby3 dev from a distance and I don’t think I’m going to use it soon. Currently focused on other open-source contributions. :)
So I was wondering if you wanted to maintain your fork separately?
This would imply:
Using a different namespace (seehat\KirbyTwig maybe)
An opportunity to drop features or options that might not be useful
You could even restart the git history from your current working version, if you don’t want to keep the noise of this project and the Twig lib’s sources being vendored in, updated and removed.
I’d be perfectly happy with passing the baton to you (keeping this repo only for Kirby 2 users), if you’re interested, and maybe contributing bug reports and PRs if I end up using Kirby 3 in a few months.
Hi @seehat. Sorry for not replying earlier.
I’ve only been following Kirby3 dev from a distance and I don’t think I’m going to use it soon. Currently focused on other open-source contributions. :)
So I was wondering if you wanted to maintain your fork separately? This would imply:
seehat\KirbyTwig
maybe)I’d be perfectly happy with passing the baton to you (keeping this repo only for Kirby 2 users), if you’re interested, and maybe contributing bug reports and PRs if I end up using Kirby 3 in a few months.
The composer.json’s authors could look like:
:)
But maybe this is much more than you’ve bargained for. :D