@hugosenari Curious if you received a notification for the above and have any thoughts :)

I did. And have, but they aren't relevant to the subject.

Here the subjective opinionated useless thoughts:

• We have lost our most important contributor to something more important in life than code. So I'm very glad to hear that. Could be worse
• Unless you can feed your child with PR, I think that it is important that open source projects to have some financial strategy to keep them running.
• While voted against't it, TypeScript is the new "Java" for corps. I still think the laconiajs is a piece of art in its architecture and simplicity, but corps don't care, they want the enterprise solution. Means less opportunities for funding.
• If a more enlightened company wants to keep laconiaJS going while we all have the same problems as you, we all must be happy at least or workout to give project another option.
• At least you are not begging for employment, and breaking anyone else build in the way.
• Upgrade to aws-sdk v3 #508 AWS SDK 3. I was expecting SDK 3 to reduce the size of the build and the cold start, but AWS SDK is big because of API metadata that isn't modularized, if you use one AWS module or all, the size is almost the same (or was, I checked this 2 years ago).
• I planned to do the upgrade, but got demotivated once I realized that.
• Now isn't what we gain with, but what we wouldn't lose: everything.
• The motivation is different, not only for me, but for everyone.
• Even a PR for that won't fix the project lack of contribution issue.
• As I'm not working to give project another option. Whatever you decide, I'm ok with it.

Hey Hugo, I don't think these are useless thoughts!

To focus specifically on another option, another option was suggested by @Ankcorn on Twitter: Get a Foundation to host it. @brianleroux suggested https://openjsf.org/ and kindly offered to help us navigate. (The Twitter thread)

I thought it would be useful for me to document my thoughts here:

• While the ethos of the foundation (specifically OpenJSF) looks appealing, what Laconia.js needs most now is better maintenance and contributions. While a Foundation can help achieve this, they'll be doing this non-directly i.e. increase visibility -> attract more usage and contributions -> attract maintainers.
  • NearSt adoption will satisfy the needs directly.
• The upside of getting OpenJSF to host Laconia.js is its neutrality.
  • I believe NearSt will keep the project neutral, and it'll be part of the agreement in the adoption so that it won't prevent a Foundation from hosting it, if needed in the future (keeping the option open)

We have concluded for the adoption to go ahead. The list of high-level agreements in between me and NearSt can be found here:

NearSt Adoption Summary Agreement.pdf

Thanks @hugosenari for your contribution to this discussion! We'll be planning some work to make the necessary transfer of the current infrastructure.