Routing-controllers: Is this project abandoned?

[sirfak]

Is this project abandoned?

[georgyfarniev]

@sirfak yes, this project is inactive. Take a look at https://github.com/iyobo/koa-ts-controllers if you using koa.

[GabeKuslansky]

Best alternative for express?

[jotamorais]

Is this project abandoned?

If it's abandoned, I would be willing to help maintain it moving forward.
There are currently 137 open issues (some as old as of July 2016).

[georgyfarniev]

@jotamorais the problem is that owner is very busy for review pull requests. @pleerock how about providing access for other maintainers to support this project if you cannot keep working on it? I think the only problem here could be the trust

[jotamorais]

@jotamorais the problem is that owner is very busy for review pull requests. @pleerock how about providing access for other maintainers to support this project if you cannot keep working on it? I think the only problem here could be the trust

I agree with the part "trust" - but that can be solved by granting permission to 2 or 3 (can collectively discuss/evaluate/approve).

[rustamwin]

the problem is that owner is very busy for review pull requests. @pleerock how about providing access for other maintainers to support this project if you cannot keep working on it? I think the only problem here could be the trust

@pleerock was left the project, now @NoNameProvided and @19majkel94 maintainers the project

[sirfak]

With new maintainers, do we have hope that this wonderful project is alive?

[cdeutsch]

Just tried this out and it looks great! But I'm stuck on #422.

There hasn't been a new commit in over a year (that's a dead project in my book)

If someone, @jotamorais is willing to maintain it, I'd say just fork it since the current owners haven't responded.

[jotamorais]

Just tried this out and it looks great! But I'm stuck on #422.

There hasn't been a new commit in over a year (that's a dead project in my book)

If someone, @jotamorais is willing to maintain it, I'd say just fork it since the current owners haven't responded.

I'm really keen to help in maintaining moving forward but would be good to get current owners agreement/acknowledgment and try to align some of their previous ideas, such as the initial backlog

[cupcakearmy]

Please don't make this die. I would be willing to help out to keep it alive!

[cupcakearmy]

Are @NoNameProvided and @MichalLytek the project maintainers? This seems like a dead end to me if it's even impossible to reply to thread about the feature of the project. Would be a pity since the code is really good and it would be stupid to just run it into the ground like this.
Worst case we could create a fork with maintainers that are willing to put the time in and continue form there.
What do you think @jotamorais ?

[jotamorais]

Are @NoNameProvided and @MichalLytek the project maintainers? This seems like a dead end to me if it's even impossible to reply to thread about the feature of the project. Would be a pity since the code is really good and it would be stupid to just run it into the ground like this.
Worst case we could create a fork with maintainers that are willing to put the time in and continue form there.
What do you think @jotamorais ?

I'm down and can certainly help to maintain this project with other interested parts on moving it forward.

[cupcakearmy]

Ok I think it's fair to give one week to @NoNameProvided and @MichalLytek to give input/feedback on this. Otherwise I'd suggest we fork. I don't have much experience with the whole reflection metadata thing in typescript. I know some base concepts but I guess it will be learning by doing.

[MichalLytek]

If you want to maintain the project, just ask @pleerock to get access to the typestack team and work on routing-controllers like @vlapo on class-validator.

[jotamorais]

If you want to maintain the project, just ask @pleerock to get access to the typestack team and work on routing-controllers like @vlapo on class-validator.

@pleerock would you grant me access to TypeStack to work with the community on open issues and review/accept PRs, etc?

Thank you!

[MichalLytek]

@jotamorais
You have to mail him at pleerock.[email protected], he has 1000+ notification on github per month.

[jotamorais]

@jotamorais
You have to mail him at pleerock.[email protected], he has 1000+ notification on github per month.

Thanks @MichalLytek. E-mail sent!

[pleerock]

@jotamorais done. Take it with responsibility please :)

[jotamorais]

@jotamorais done. Take it with responsibility please :)

Thanks, @pleerock!

Calling the community now to come up with a list of priorities for the issues and new features. Also, to contribute with PRs.

I thought of starting and prioritize all issues labeled bug, but I'm not sure how accurate and those labels are at the moment and how/when the triage was done.

[georgyfarniev]

@jotamorais yay this project will get maintained finally. Thank you. Welcome

[gstamac]

@jotamorais great news you managed to become a maintainer. I would suggest you start with open PRs.

[consense]

Unfortunately don't have the time for prolonged PR reviews currently, but could at least help by labeling current issue backlog if you need any help @jotamorais

[jotamorais]

Unfortunately don't have the time for prolonged PR reviews currently, but could at least help by labeling current issue backlog if you need any help @jotamorais

Yeah, that would be a great help, @consense
It's a bit overwhelming right now, to go through all issues, open PRs and also plan new features and new releases.

I'm about to integrate PR#315 and PR#512 in preparation for the 1st major release in a long time.
I'm integrating onto the next branch and from there will merge onto master to release the new package version (0.8.0) with breaking changes.

[jotamorais]

@NoNameProvided, can you help to review the master branch and if you're okay with, package and publish it to NPM (or grant me access to publish)?

Thank you!

[elthrasher]

@jotamorais The glitter chat referenced in the README is still active. Maybe it would make sense to set up a slack? I'm up for some more tasks to keep this project alive. I spent some time looking at alternatives, but this lib really hits the sweet spot between being great to use and being non-opinionated (like express).

I can try running some more tests against master and I think the changelog needs some additions, so I'll open a PR for that.

[jotamorais]

@elthrasher I vote to keep the Gitter channel.
I will drop a line there and will be monitoring it on a daily basis.

By the way, I accepted the PR for the changelog.

Thanks!

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.