Hey folks! I think we need someone from the Directory PMC to chime in before committing to something official, but here are my personal thoughts:
SCIMple needs an initial release in order to be successful (grow the community), as mentioned by Eran, developers are not OK with snapshots or maintaining a fork. Here are some ideas: 1. Cut a 1.0 release of SCIMple, (following Apache release processes) 2. Create a 0.9 or 1.0-RC1 release if there is a desire to increase the committer count before cutting a 1.0 (NOTE: this would still need to follow official ASF release policies) This strategy/question is probably a question for the wider Apache Directory PMC. In either case, I can volunteer to be the release manager, but we need to ensure we have enough PMC members to vote. On Tue, Nov 15, 2022 at 4:26 PM Eran Toledano <[email protected]> wrote: > Hello, > > I am Eran, a dev at Proofpoint’s App Services team. > > > > As part of a new feature we are planning, we have been looking into > different SCIM implementations when we came across the directory-SCIMple > project. > > > > We were quite impressed with its simplicity and extensibility. I was able > to whip up a quick POC in our platform using the main modules somewhat > easily. Suffice to say it’s the preferred option for us at the moment. > > > > That being said, we were a little apprehensive about adopting SCIMple for > production purposes since it had not yet had an official release. > > > > We would love to get some insight about potential release plans/timelines > before moving forward (we are also happy to contribute if necessary). > > > > Thanks, > > Eran > > > > P.S. I have chatted with @Brian Demers <[email protected]> briefly > on the matter, who made some great points and directed me to this mailing > list as a wider audience :) Thanks again Brian! > > >
