-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regarding the long term maintenance of the project #80
Comments
Please submit any pull requests @auvipy. CoffeeKup is no longer maintained as the developer has disappeared. I have created this as a way to maintain a project I use. |
I can use all the help I can get. I've had real life demands that have caused me to neglect addressing issues with this project. |
@gradus I have invited you to join the semi official org for coffeecup/kup plz feel free to join there :D and transfer the project to coffeekup/coffeecup namespace :) |
and I need your help to update the projects npm package with the changes from other maintainers forks :) the point is as there is already a package published by you why to create new one? |
and there is https://github.com/goodeggs/teacup which seems alive. a coffeekup foundation may needed? |
Teacup IMHO is a great alternative, and works better than coffekup / coffecup cause you can still have the scope's closure etc, like any normal code. |
Can I join the "semi-official-org". I'd like to be able to help make sure this project is maintained, moved forward. Teacup's syntax sucks. Having an express-compatible templating engine in native coffee-script is ESSENTIAL to the language's survival, IMHO. |
please feel free to comment and participate to share your views :)
mauricemach/coffeekup#120
The text was updated successfully, but these errors were encountered: