Is this project alive?

[bitsofinfo]

just noticing not alot of activity: using 2.11.1 and this plugin, following the example I am getting Configuration warning at 'functions.myFunc.events[0].http': unrecognized property 'documentation'

[sajithneyo]

@deliveryhero is it?

@bitsofinfo looks like this project is dead

[tchock]

@bitsofinfo @sajithneyo

Sorry for not looking here for a while. We are currently not maintaining it anymore. Mainly because the use case in our company is gone. I already talked with my tech lead about searching a new maintainer, but this didn't advance.
I will ask again about it, because it would be a shame to let this project die as quite many are using it.

[sajithneyo]

@tchock Keeping this project alive will be awesome.

One more thing? Why the use case for this project gone? Documenting using some otherway? If you can shed some light on that statement, that will be awesome!

[tchock]

@sajithneyo We changed to manually writing swagger mainly and also a lot of our team's codebase is going away from serverless.

[sajithneyo]

@tchock I'm currently investing on Serverless. So my last question is, any particular reason for leaving Serverless?

[tchock]

@sajithneyo it was a team decision as the team changed quite a bit and it has more knowledge on other technologies. Also Lambda and API Gateway got quite expensive on heavy load (at least for us, we were writing into Postgres which occupled quite a bit of the runtime) with multiple million events per day.

[tchock]

Unfortunately I have to tell you that this project is no longer continued and also can't be transferred to a new maintainer due to legal reasons.
If you like to continue working on it feel free to fork it and publish under a new name.

[dls314]

Are there any known-updated forks that work with serverless > 2.30.3?

[medikoo]

@tshock Serverless Framework maintainer here. Is this possible to obtain maintenance rights for this plugin? We'd like to ensure it remains working after recent changes to the Framework.

The minimum needed for that is ability to publish new npm releases, as otherwise, if providing maintenance rights to this repo (no need for transfer) is for some reason difficult, we can simply fork the repo as you suggest.

Let us know, such move will be definitely helpful for all users which found this plugin valuable.

Thank you for all the work so far!

[tchock]

Hey @medikoo, as it's licensed under MIT I guess you can copy and redistribute it.
As I don't work for Delivery Hero anymore this is no guarantee though.

I think the only thing that didn't work was to transfer ownership.

[tchock]

Ah, sorry, you asked to publish changes to the existing npm package, right?
@aaleksandrov Can you maybe ask someone within DH if it's possible?

[aaleksandrov]

Hey @tchock man!
What exactly do you want me to do? To ask for transferring right back to you or to allow someone outside of company to publish package? The second one would be probably pretty complex