Sure, with 3 active contributors to Tamaya in the EG and 1 or 2 more who made initial contributions earlier via DeltaSpike config, etc. there are many EG members who are familiar with Tamaya.
So far the JSR page specifies, the RI should use Apache 2 License, thus most of the projects mentioned to be inspirations could in theory be declared the RI. There can only be one RI, the PMO has confirmed that. It seems there could even be some “competition” between compatible implementations. The JCP is not too strict regarding the RI, but at least once a JSR reaches Proposed Final Draft it must have a RI. Of course having it earlier would be good, Public Draft maybe. Werner From: John D. Ament Sent: Monday, November 6, 2017 20:13 To: [email protected] Subject: Re: [DISCUSS] Offering Tamaya as ConfigJSR reference Impl On Mon, Nov 6, 2017 at 2:09 PM P. Ottlinger <[email protected]> wrote: > Am 06.11.2017 um 13:27 schrieb Anatole Tresch: > > - Depending on we would agree to support also the ultimate step, I can > > discuss with the JSR EG that Tamaya might get THE official RI. > > - All our extensions and integrations would also work with other > > implementations, which would us put in a similar position that > Deltaspike > > had for CDI. Given that I expect to have a braoder target in the > developer > > community and maybe also attract additional people to join us in a > later > > step. > > +1 > > I like the idea and would love to get a more formal approval for Tamaya. > > Browsing through the code while reviewing some of the tests made me > realize how far we've already got with this young project. > > Let's give it a go! > Its ultimately up to the EG to produce the RI. I don't see any issue with proposing the idea on the ML. > > Phil >
