Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promoting Zappa To the Next Generation of Developers #968

Closed
mslinn opened this issue Apr 24, 2021 · 3 comments
Closed

Promoting Zappa To the Next Generation of Developers #968

mslinn opened this issue Apr 24, 2021 · 3 comments

Comments

@mslinn
Copy link

mslinn commented Apr 24, 2021

I recently published a blog post on Zappa. Feedback / corrections and suggestions are invited. The main points I am attempting to make are:

  1. Zappa is a seminal project that has inspired other well-known projects.
  2. Zappa is still very useful; in fact, its best days lie ahead.
  3. Zappa needs new contributors (a "new generation") to help work through the backlog and hone the messaging.

I would like to update the blog post (and the follow-on posts that are in progress) with more information about the old-time developers and recent additions, and tell the world the skills necessary for new contributors to be most effective in addressing the backlog. Please respond publicly here or in private to me at mslinn@mslinn.com.

Has anyone communicated with @jezdez at JazzBand about discussing the possibility of having Zappa join JazzBand?

@tommie-lie
Copy link

Thanks for your research! I'm interested to know what other projects you are talking about here and in your blog post. The technology of Zappa seems to be quite unique, at least to my knowledge. While you list other frameworks in your blog post that solve different serverless computing problems, Zappa seems to be quite unique as being an easy way to run regular WSGI apps in a serverless environment.

Regarding your comment on @jazzband: I doubt anyone has done that, yet, and even if someone does it, without the maintainer of this project, nothing can be done to transfer Zappa to JazzBand. So this is a kind of chicken and egg problem: without mainteiner, there is no maintenance, and if we had an active maintainer, we wouldn't be in need of one in the first place.
Besides, judging from some issues there, they are suffering a similar problem.
And on a personal note: I don't think Zappa is currently in a state where a losely-coupled community of maintainers will do any good. It needs people with a strong vision and passion about what the project should look like in the future.

@mslinn
Copy link
Author

mslinn commented May 15, 2021

I am going to reach out to @jezdez, and then I will respond here :) after speaking with him.

@wrboyce
Copy link
Member

wrboyce commented Sep 28, 2021

Closing as, ironically enough, this issue seems to have been abandoned now.

@wrboyce wrboyce closed this as completed Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants