Expected PR code review reaction times

[holgerstolzenberg]

Within my current project we decided to use OpenFGA as a core technology for authz.
Yet grateful for the open source nature of the project, we also want to contribute back.
Having done that, I waiting for my PR on the spring starter project to be reviewed, which was opened 2weeks ago.

I to not want to push too hard here - but:

• I need some information to manage my own expectations (hey I contributed - why is no one at least looking at it 🤔)
• have a better understanding of the timelines for the future (it looks like we could potentially contribute other stuff to the spring boot starter also)

Kind regards
✌️

[dyeam0]

Hi @holgerstolzenberg, thanks for your message. We have been reviewing our internal processes and are going to adjust our team activities to give better focus to community requests. We will publish guidelines soon that will give everyone better expectations of response times for reviews, requests and features so others can plan and make decisions for their own timelines. Stay tuned.

As always, we are grateful for community members willing to contribute their time and efforts to the success of OpenFGA! Thanks.

[holgerstolzenberg]

Hey @dyeam0, thanks for the quick response, now I was the one missing out 🙈.

So in general, I would tend to mark the discussion as answered, yet to be honest it is kind of an all or nothing statement :-) because ...

So for me, I can see that the OpenFGA Helm repo is quite active in terms of bringing PRs to live, whereas in my example the Spring Boot Starter repo seems to get no attention at all. Having contributed, I am for sure waiting for my PR coming to official release to the better of the starter, the community and of course myself.

Taking the starter project, there is also another PR for restructuring the repo open since October (not mine), that is essentially nearly finished, but keeping it so long is not helpful, as such kind of refactoring becomes tricky at some point in time.

So...

• I will wait for your the publication of your guidelines to mark this as answered
• Is there any chance to give PR feat!: improve error handling spring-boot-starter#90 a push!?
• What would be necessary to become maintainer on the Spring Boot Starter project?

✌️

[dyeam0]

I will wait for your the publication of your guidelines to mark this as answered

No worries. Keep this thread open until we publish and it meets your needs.

Is there any chance to give PR openfga/spring-boot-starter#90 a push!?

Yes for sure. Ahead of guidelines, I'll bring that to the team's attention now and we'll get someone to review.

What would be necessary to become maintainer on the Spring Boot Starter project?

We are definitely excited about this offer. I'll get the right team members and give you the criteria.

[holgerstolzenberg]

Hey,

so I saw the comments on the PR, will take care of it.

In regards of the maintainer-ship, maybe maintainer is a too strong word here. So this is the situation.

I am currently on a platform project where we will build a IAM solution around OpenFGA. The project using the following ecosystems: Java, .NET, Python, Typescript. As chances are high the IAM solution will be adopted by a lot of parts of the platform, we will have the one or the other idea or features we would like to share with the community. And of cours - it makes no sense and we would like to avoid maintaining internal libraries for that manner.

So here is the point - maintainer-ship has some consequences "for all of us". Taking just the perspective on our side - we would like to have shorter response times in the 1st place, I mean you know it best, there are always timelines and stakes in the background...

I will listen around in the project if there are people that would be willing to contribute/maintain stuff from the other ecosystems, because I am mainly on the Java side.

We could also have a direct private call to see how that could work out...

[dyeam0]

Good morning @holgerstolzenberg, hope you are well.

We have updated our governance document regarding roles and responsibilities for members participating in the project. Please see Governance in the Contributors section and Maintainers section for updates pertinent to your questions. The updates do not address response time (yet), as we are still trying to finalize what we are able to responsibly commit to. It is a question of prioritization of our team's resources. We are actively discussing this and still intend to publish something on that.