Project abandoned?

[OtaK]

Hi @jaredhanson,

Did you abandon the project? No PR are merged, issues are accumulating and so on.

I love this framework, and maybe you could create a GitHub org and move locomotive under it, and give repo administration to a few individuals?

IMHO that would quickly solve the main issue with locomotive as it is, being upgrading to Express 4.x

Thanks,
Mathieu

[anmonteiro]

+1

[jeanfw]

+1

[RohovDmytro]

+1

That would be truely awesome.

[crispen-smith]

+1

This framework satisfies all my needs and gets out of the way the rest of the time. I'd be very happy to contribute to it in anyway that I can.

Also, to the original concern re. Express 4.x... I do have a working version.

[OtaK]

@crispen-smith I feel the same about this framework. It's just Express MVC done right IMO.
I know that many have a working version (Oculus/Facebook have a working repo) based on Express 4, but I'm looking forward to bring that into the official repo's core.

Thus the need to delegate administration rights for Locomotive to be able to go forward.
A huge concern also, is that Express 3's support might end soon, so we might get out of luck about security updates being backported.

[slyg]

Hi, perhaps it can help you to know that Viadeo has forked @jaredhanson's Locomotive: viadeo/maglev. It is actually an Express 4 compliant version of Locomotive, maintained, still kept as simple as possible, and it has been used on high-load traffic website for months.

[jaredhanson]

Yes. I'd like to get some other contributors on this to get up-to-speed with PRs and Express 4.x support.

@slyg - Would you guys at Viadeo be willing to get your patches from Maglev submitted for merge upstream? Who would be the primary contributors, I'll add them to the repo.

@OtaK - Do you know if Oculus/Facebook has a public repo or if they'd be willing to submit there patches upstream?

I've got a GitHub organization, locomotivejs, that I'll transfer the repo to and add contributors. As always, I want to maintain the spirit of the project, primarily keeping it small and focused and not adding bloat. We can discuss the patches as they are submitted.

The one feature I have on-going (slowly) is integration with Electrolyte to support dependency injection into controllers, allowing easy mocking and stubbing of things such as database connections, etc.

[OtaK]

@jaredhanson Their repo is located here: https://github.com/OculusVR/locomotive. Although it's been a while they didn't commit into it, I guess their express4 code is stable. Didn't test it myself so if anyone else has feedback on their version, please give us a word.

👍 on the maglev backports, that would be awesome

And as always, I agree on the project's spirit, it needs to stay like that, unobtrusive, but powerful for the developers.

[tregagnon]

We would be happy at Viadeo to bring back our changes from Maglev to Locomotive. We are also looking to keep it small and focused.

Here are the changes we made:

• Upgraded Express to version 4
• Allowed custom resolver for Controllers
• Fixed broken unit tests and JSHint errors
• Replaced Makefile by NPM scripts (stay in the Node.js ecosystem and work on more OS)
• Added deprecation warnings on functions mapped to deprecated Express functions

Each changes can have its own PR to allow discussions.

I think the GitHub organization is a good idea. We are not the only active fork. I hope others are willing to contribute.

@slyg and I were the ones maintaining viadeo/maglev. But @slyg recently left Viadeo for new adventures. 😉 I don't know If he plans to keep working on it. Feel free to add me as a contributor on the organization.

@jaredhanson Do you plan to stay involved in Locomotive's development? It looks like you are busy on other projects. Maybe you don't have much time left for Locomotive?

[j3k0]

Any news on this? Too bad to see a good framework like this one being left for dead.

I was about to abandon the idea to use it until I found this thread. So if you want to keep attracting new users and not let this project die :

• Add people as contributors (from project's settings) so you they can merge pull requests and/or push directly to this repo.
  • Or forward users to one an active forks. Add a DEPRECATED please go to <whatever active repository> on top of the README.md.

[yangpu]

@jaredhanson This is a great project and you have done much of work. I choose to build our project on Locomotive.js since 3 years ago, however it's frustrating to see no one manage or maintain it now.

Please let someone contribute to this project, and quick.

[cristianchaparroa]

+1 , thanks @viadeo, and all contributors

[keithics]

+1 for 2016

[RohovDmytro]

ping 😢

[RohovDmytro]

Anybody knows about live fork of locomotive?

[crispen-smith]

I know I'm still using it but it continues to just work for me about 95% of the time.

[RohovDmytro]

It works for me for 100% of the time, but I want to move on and to perform dependecies updates to not to stuck.

[drudge]

I'm maintaining a fork at https://github.com/emvc/emvc.

[thall1961]

Is anyone still interested in moving this forward? Seems like the first org didn't set and the forks have gone stale (is Locomotive solving an issue that's already been solved?), but I'd be happy to keep working with others on it.

[alank64]

Not sure I understand, you need what?

…

On Wed, Apr 8, 2020 at 11:29 PM dellelce ***@***.***> wrote: @jaredhanson <https://github.com/jaredhanson> why don't you archive this repo? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#177 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAK6XRZ4XVPJIQY2PXWTZKLRLU6LLANCNFSM4BPJFFGA> .