Organize Zappa community governance structure?
Opened this issue · 5 comments
As an open source project matures, and in order to promote the longevity of the project, it is oftentimes useful to define a community governance structure.
Currently, Zappa has a single primary maintainer/contributor, and the contributions seem to be dwindling a bit.
With gratitude, and no disrespect, to @Miserlou, may we discuss what a community governance structure for Zappa would look like?
Hi! I know @Miserlou is aware of the problems and trying to solve them. Currently there's a core team (I'm the newest member) that was created at the beginning of this year. We're still sorting out some kinks and finding a way to work things out but we've had 10 releases since this ticket was created and we have the next one in the works.
We're not perfect and I'd love to know what we're missing.
For clarification, I only see the 0.47 release being newer than this issue. Is there some other release channel?
In any case, great work! ☺
@jneves: Is this by any chance still on the radar? There are lots of folks relying on Zappa, maybe this thread can proceed by creating a Github organization Zappa, forking Zappa there and trying to engage all the folks who recently made PR to create a working group / roadmap and see if there is any chance to move on from there? your thoughts?
I (and I'm sure many others) continue to grow concerned about the lack of visible governance around this project. Can we please get some kind of comment from @Miserlou / @jneves / anyone else who can actually effect these changes ... I'm particularly concerned about the PyPI release process as in order for any kind of friendly community made fork to take over the work, it needs to be able to continue releasing new versions of the existing packages.