Move terrific to Namics/Terrific

[jantimon]

Hi @brunschgi

we are still heavily relying on terrific in CMS projects and it works quite well.

As pull requests features and terrific 3.0 seem to be out of scope for this repo we are currently considering to fork it to https://github.com/namics/terrificjs to be able to move the project forward and to fix bugs faster.

As you spent so much time for this project we would be very happy to have your support on this. Do you think it would make sense to publish upcoming updates directly to the npm terrific package or would you prefer if we rename it to @namics/terrific ?

[upstroke]

Hi Jan I only worked with terrific on projects during my times with Namix in Frankfurt, so I am not really helpful when it comes to supporting terrificjs. But I would stick with the framework name.

Greets Gregor Arz

Am 17.10.2017 um 11:54 schrieb Jan Nicklas [email protected]:

Hi @brunschgi https://github.com/brunschgi we are still heavily relying on terrific in CMS projects and it works quite well.

As pull requests features and terrific 3.0 seem to be out of scope for this repo we are currently considering to fork it to https://github.com/namics/terrificjs https://github.com/namics/terrificjs to be able to move the project forward and to fix bugs faster.

As you spent so much time for this project we would be very happy to have your support on this. Do you think it would make sense to publish upcoming updates directly to the npm terrific package or would you prefer if we rename it to ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brunschgi/terrificjs/issues/79, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjY4WiSZHEUd2hRyNM2JKbfo-fp-WIrks5stHlSgaJpZM4P74Yd.