Repository navigation
Is the project alive? #558
Description
I am going to start a new internal-tool for templating.
I see this project has more than 1 year without any new commits.
I just wanted to check-out in which situation are we:
It does not have any commits because [...]
- It's currently stable and no big-maintainance has been needed. But if twig makes major changes, this project will follow up with the proper improvements.
- It's abandoned / semi-abandoned / looking for leaders, etc.
- Other.
In case of 1. I'd consider this project or twig,js as the basis for my templating tool.
In case of 2. I wonder if there are any maintained alternatives.
In case of 3. what's the situation?
Thanks!
Xavi
Activity
ericmorand commentedon Aug 9, 2024
Hey @xmontero, yes Twing is more alive then ever. We are planning on publishing Twing 8 as soon as Twig 4 specification are set in stone.
One thing to note, the actual code repository for Twing in on GitLab: https://gitlab.com/nightlycommit/twing. There you can see that the most recent version was published a few days ago to fix performance issues.
This Github repository is kept only for legacy issue tracking, which make me think that I need to add a pinned issue about that.
xmontero commentedon Aug 9, 2024
Ah good to know!!
Maybe edit the README to show up with the new "main" location
And even... maybe a cron (even human-driven once per month) that pulls from gitlab and pushes to github so github acts as a "montly cache of gitlab" could be useful.
Thanks, going to check it out!