You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to delete the repo since we don't maintain it and don't recommend anyone to use Martini? I contributed two plugins to dogfood the framework but they keep appearing on the list of projects I have contributed on my Github profile and got highlighted occasionally as they are my best work :(
I have more responsibilities for the Go project now and I am now often being asked why I even contributed to Martini in the first place by those who don't have context. I desperately desire to free myself from this stigma and any help is appreciated.
One wonders if the more interesting plugins/middleware couldn't simply be ported to use Gin instead. Gin was inspired by Martini, after all, and that 'inspiration' actually got quite a long way — in the sense that rewriting some of the most useful contributions (such as this one!!) could be used with Gin instead...
Oh well. Sorry for necro-bumping this thread. It was just a thought...
Aye, as far as my comment is worth anything, I'd set the whole repo as read-only with a BIGGER notice that it's not being maintained any longer.
And, of course, mark everything in it as deprecated.
Is it possible to delete the repo since we don't maintain it and don't recommend anyone to use Martini? I contributed two plugins to dogfood the framework but they keep appearing on the list of projects I have contributed on my Github profile and got highlighted occasionally as they are my best work :(
I have more responsibilities for the Go project now and I am now often being asked why I even contributed to Martini in the first place by those who don't have context. I desperately desire to free myself from this stigma and any help is appreciated.
Any thoughts?
/cc @codegangsta
(Hoping no offenses are taken. Tech industry is unfortunately not a harassment-free space, hence there is this bug.)
The text was updated successfully, but these errors were encountered: