Closed rguldener closed 1 year ago
Hi Robin,
It's great that you have convinced guys at Bearer to revive the repository! I have also reached out to offer my help in maintaining Pizzly but they said they had decided to archive it. There were a couple of issues/PRs before the project got archived. I think it makes sense to look over these for some feedback first. Here are my personal observations about Pizzly:
Cheers,
Sergii
Thank you for chiming in and offering to contribute!
I will go through previous issues & PRs as you advised. Also, feel free to create issues (or even PRs) if you want some of your suggestions to be implemented soon.
We are currently focusing on refreshing/fixing the repo for local development, but it would be great to have your input as we move towards improving it.
We've created a Slack room dedicated to Pizzly in our Slack community in case you want to follow Pizzly news more closely and discuss ongoing work. We will ask the community's opinion and share plans on a regular basis there.
Hi all,
As we start working on Pizzly, we wanted to consult you about a couple topics that will determine how we go about maintaining Pizzly:
Today, Pizzly executes API requests for you via a proxy. Do you like this? Would you rather have direct access to access tokens (via API/SDK) to do your own requests? We would still abstract away the token refresh, always sending you a fresh token that’s ready to be used. Eventually we could offer both options, but which one would you prioritize?
Pizzly is a larger code base than it could be, with legacy code and an unfinished migration from Bearer’s old internal use case. We could take the approach of a full rewrite to make Pizzly smaller and simpler, accelerating future development. Do you have anything against this? Do you anticipate any hurdles in the migration process?
Today, Pizzly offers a dashboard to enable and configure APIs. Would you rather have this in-code or do you want to keep the UI? Again, we could maintain both in the future, but looking to understanding your priorities.
Would you be interested in having a Cloud option for Pizzly, not having to self-host it yourself? To be clear: Pizzly will stay open source with easy free deployment options. But we want to get a sense of whether a Cloud option could make Pizzly accessible to more folks.
Thanks in advance for your much needed input :slightly_smiling_face:
Thank you for your input @mikestaub!
100% what @mikestaub says.
It should be completely configurable in code so configs can be versioned.
I do wonder though, with such a small surface area, whether it would even make sense to expose the api via api 😂
Couldn't we just throw something together in tailwind in an afternoon and call it good?
If it helps the project to remain liquid, I'm all for it.
Regarding @Simcon comment, I think you could basically do it like vscode no? Provide a skeleton of the most commonly used features via a UI and let people configure the underlying code if they see fit
Thanks a lot for voicing your opinions about Pizzly’s future (here and on the #pizzly Slack channel). There seems to be a pretty nice consensus around important features.
Last week, we started a full rewrite of Pizzly on a branch (v0.3) to make the code more maintainable and accelerate future development. It already works, and supports:
During the past week, you expressed interest in the following additional features:
The new Pizzly is also currently missing:
We would love to have you involved in building these features, or others that you have in mind. If you are interested, please let us know what you would like to take on. And if you have additional/different thoughts, please share them here or on the #pizzly Slack channel.
We want to quickly get to feature parity with the old Pizzly so that we can start making nice improvements!
We have created individual issues for the Roadmap items mentioned above (#268 to #273).
Additionally, you can follow our public roadmap: https://github.com/orgs/NangoHQ/projects/1/views/2
Lastly, please join the #pizzly Slack channel or create/comment on issues if you want to have a part in Pizzly's roadmap.
Contributors are more than welcome. We actually tagged most of the issues with 'Help Wanted' in case you want to get started.
Hey Pizzly community,
we are Bastien and Robin, the new stewards of Pizzly 🐻
Pizzly became popular because it is one of the fastest and simplest ways to get started with APIs that use OAuth. Currently Pizzly has some issues with the latest version of node and the code has been largely unmaintained for 1+ year.
We want to fix and improve Pizzly, but for this we need your help:
Your inputs will be super valuable to shape the future of this project.
If you want to get involved with contributing and designing the next version please join our Slack community: We would be happy to have you as part of the core team.
We look forward to hearing from you in the comments and building a better Pizzly together!