From fabrice.bibonne at courriel.eco  Wed Feb 18 08:36:34 2026
From: fabrice.bibonne at courriel.eco (Fabrice Bibonne)
Date: Wed, 18 Feb 2026 09:36:34 +0100
Subject: Hello Open JDK community
Message-ID: <f23e806d52e1139a5e18fca060bdd30a@courriel.eco>

Hello everyone,

I am writing to introduce myself after signing my OCA.

My name is Fabrice and I am an experienced Java developer. I am very 
interested in all topics related to Java and would therefore be 
delighted to help the community improve Java. Although I am not in a 
position to contribute to the core JDK, I am happy to give my opinion on 
new features or contribute to any of the various tools.

Best regards,
Fabrice Bibonne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260218/87e1510e/attachment.htm>

From aph at redhat.com  Wed Feb 18 09:47:40 2026
From: aph at redhat.com (Andrew Haley)
Date: Wed, 18 Feb 2026 09:47:40 +0000
Subject: Hello Open JDK community
In-Reply-To: <f23e806d52e1139a5e18fca060bdd30a@courriel.eco>
References: <f23e806d52e1139a5e18fca060bdd30a@courriel.eco>
Message-ID: <2fb280df-ee19-4fc4-b4d8-0a7b9ca18152@redhat.com>

On 18/02/2026 08:36, Fabrice Bibonne wrote:
> I am writing to introduce myself after signing my OCA.
> 
> My name is Fabrice and I am an experienced Java developer. I am very
> interested in all topics related to Java and would therefore be
> delighted to help the community improve Java. Although I am not in a
> position to contribute to the core JDK, I am happy to give my opinion on
> new features or contribute to any of the various tools.

On behalf of the Governing Board, welcome to OpenJDK.

Re contributing to the core JDK: Never say Never! :-)

Andrew.


From martin.doerr at sap.com  Wed Feb 25 14:19:43 2026
From: martin.doerr at sap.com (Doerr, Martin)
Date: Wed, 25 Feb 2026 14:19:43 +0000
Subject: [External] : Re: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <AS8PR02MB8544EAE096591C0CB68C2B049A75A@AS8PR02MB8544.eurprd02.prod.outlook.com>

Vote: yes

Best regards,
Martin

Von: announce <announce-retn at openjdk.org> im Auftrag von Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com>
Datum: Mittwoch, 25. Februar 2026 um 13:35
An: announce at openjdk.org <announce at openjdk.org>
Betreff: CFV: New Project: Detroit

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev<https://v8.dev/>
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/fd36d95d/attachment-0001.htm>

From jlaskey at mac.com  Wed Feb 25 16:19:41 2026
From: jlaskey at mac.com (James Laskey)
Date: Wed, 25 Feb 2026 12:19:41 -0400
Subject: [External] : re: CFV: New Project: Detroit 
Message-ID: <2E1E616D-82E7-43E5-83C3-1D3AC3599F94@mac.com>

Vote: yes

> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
> 
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].  This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
> 
> Here in February 2026, there is still interest in using Java and
> JavaScript together.  With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
> 
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].  Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
> 
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.  We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.  Over time, the Project may consider implementing
> script engines for additional languages.
> 
> The initial Committers will be:
> 
>   Jim Laskey
>   Sundararajan Athijegannathan
>   Jorn Vernee
>   Mikael Vidstedt
>   Henry Jen
>   Maurizio Cimadamore
>   Alan Bateman
>   Hannes Walln?fer
>   Jan Lahoda
>   Jaikiran Pai
> 
> Votes are due by midnight UTC on Wednesday, 11 March.
> 
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.  Replying to this
> message is sufficient if your mail program honors the Reply-To header.
> 
> For Lazy Consensus voting instructions, see [9].
> 
> Sundar
> 
> 
> [1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
> [2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
> [3] https://jcp.org/en/jsr/detail?id=223
> [4] https://v8.dev <https://v8.dev/>
> [5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
> [6] https://github.com/python/cpython
> [7] https://openjdk.org/jeps/454
> [8] http://openjdk.java.net/census#members
> [9] http://openjdk.java.net/projects/#new-project-vote
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/b8591667/attachment.htm>

From roger.riggs at oracle.com  Wed Feb 25 16:39:50 2026
From: roger.riggs at oracle.com (Roger Riggs)
Date: Wed, 25 Feb 2026 11:39:50 -0500
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <f0f2c863-7845-4210-a1fb-595af14b85ba@oracle.com>

Vote: Yes

On 2/25/26 6:22 AM, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.


From volker.simonis at gmail.com  Wed Feb 25 17:00:10 2026
From: volker.simonis at gmail.com (Volker Simonis)
Date: Wed, 25 Feb 2026 18:00:10 +0100
Subject: [External] : Re: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <CA+3eh10PrN3ck6sPya6CpwB2bJ1tkqqxeAHcoXprHd_5p-DoxQ@mail.gmail.com>

Very interesting, if only to have something to compare GraalJS and GraalPy
against it :)

Do you still plan to import the V8/CPython sources and build them as part
of the JDK (like in the initial prototype) or will the new implementation
(also) work with existing V8/CPython implementations (like e.g. JDKs zlib)?

Vote: yes


On Wed, Feb 25, 2026 at 1:35?PM Sundararajan Athijegannathan <
sundararajan.athijegannathan at oracle.com> wrote:

> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
>
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].  This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
>
> Here in February 2026, there is still interest in using Java and
> JavaScript together.  With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
>
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].  Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
>
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.  We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.  Over time, the Project may consider implementing
> script engines for additional languages.
>
> The initial Committers will be:
>
>   Jim Laskey
>   Sundararajan Athijegannathan
>   Jorn Vernee
>   Mikael Vidstedt
>   Henry Jen
>   Maurizio Cimadamore
>   Alan Bateman
>   Hannes Walln?fer
>   Jan Lahoda
>   Jaikiran Pai
>
> Votes are due by midnight UTC on Wednesday, 11 March.
>
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.  Replying to this
> message is sufficient if your mail program honors the Reply-To header.
>
> For Lazy Consensus voting instructions, see [9].
>
> Sundar
>
>
> [1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
> [2]
> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
> [3] https://jcp.org/en/jsr/detail?id=223
> [4] https://v8.dev
> [5]
> https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
> [6] https://github.com/python/cpython
> [7] https://openjdk.org/jeps/454
> [8] http://openjdk.java.net/census#members
> [9] http://openjdk.java.net/projects/#new-project-vote
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/f2f43db1/attachment.htm>

From brian.goetz at oracle.com  Wed Feb 25 17:22:57 2026
From: brian.goetz at oracle.com (Brian Goetz)
Date: Wed, 25 Feb 2026 12:22:57 -0500
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <ff9a4add-fc2b-4743-84ab-3fbcdd79d6a8@oracle.com>

Vote: Yes

On 2/25/2026 6:22 AM, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
>
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
>
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
>
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
>
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
>
> The initial Committers will be:
>
> ? Jim Laskey
> ? Sundararajan Athijegannathan
> ? Jorn Vernee
> ? Mikael Vidstedt
> ? Henry Jen
> ? Maurizio Cimadamore
> ? Alan Bateman
> ? Hannes Walln?fer
> ? Jan Lahoda
> ? Jaikiran Pai
>
> Votes are due by midnight UTC on Wednesday, 11 March.
>
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
>
> For Lazy Consensus voting instructions, see [9].
>
> Sundar
>
>
> [1] 
> https://mail.openjdk.org/pipermail/announce/2018-February/000244.html 
> <https://mail.openjdk.org/pipermail/announce/2018-February/000244.html>
> [2] 
> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html 
> <https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 
> <https://jcp.org/en/jsr/detail?id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] 
> https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html 
> <https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members 
> <http://openjdk.java.net/census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote 
> <http://openjdk.java.net/projects/#new-project-vote>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/5db6d659/attachment-0001.htm>

From paul.sandoz at oracle.com  Wed Feb 25 17:34:58 2026
From: paul.sandoz at oracle.com (Paul Sandoz)
Date: Wed, 25 Feb 2026 17:34:58 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <A1811E28-2C71-462E-8871-22BAD8A76873@oracle.com>

Vote: yes

Paul.

From alan.bateman at oracle.com  Wed Feb 25 17:47:29 2026
From: alan.bateman at oracle.com (Alan Bateman)
Date: Wed, 25 Feb 2026 17:47:29 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <b5b69502-d063-4db4-9424-3a0baede80e3@oracle.com>

Vote: yes



From daniel.fuchs at oracle.com  Wed Feb 25 18:23:55 2026
From: daniel.fuchs at oracle.com (Daniel Fuchs)
Date: Wed, 25 Feb 2026 18:23:55 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <c0f67f32-6011-48b4-9d1c-dd2948f3372e@oracle.com>

Vote: yes

best regards,

-- daniel

On 25/02/2026 11:22, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.


From maurizio.cimadamore at oracle.com  Wed Feb 25 18:40:33 2026
From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore)
Date: Wed, 25 Feb 2026 18:40:33 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <e3712e6b-cbe1-4877-98e6-bb6600e23f2b@oracle.com>

Vote: yes!


Maurizio


On 25/02/2026 11:22, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
>
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
>
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
>
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
>
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
>
> The initial Committers will be:
>
> ? Jim Laskey
> ? Sundararajan Athijegannathan
> ? Jorn Vernee
> ? Mikael Vidstedt
> ? Henry Jen
> ? Maurizio Cimadamore
> ? Alan Bateman
> ? Hannes Walln?fer
> ? Jan Lahoda
> ? Jaikiran Pai
>
> Votes are due by midnight UTC on Wednesday, 11 March.
>
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
>
> For Lazy Consensus voting instructions, see [9].
>
> Sundar
>
>
> [1] 
> https://mail.openjdk.org/pipermail/announce/2018-February/000244.html 
> <https://mail.openjdk.org/pipermail/announce/2018-February/000244.html>
> [2] 
> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html 
> <https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 
> <https://jcp.org/en/jsr/detail?id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] 
> https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html 
> <https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members 
> <http://openjdk.java.net/census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote 
> <http://openjdk.java.net/projects/#new-project-vote>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/e1584791/attachment.htm>

From philip.race at oracle.com  Wed Feb 25 18:52:48 2026
From: philip.race at oracle.com (Philip Race)
Date: Wed, 25 Feb 2026 10:52:48 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <50bd073f-451c-488d-bb54-d587ff4a7647@oracle.com>

Vote: yes

-phil.

From kirmaniwasif at gmail.com  Wed Feb 25 18:55:37 2026
From: kirmaniwasif at gmail.com (Wasif Kirmani)
Date: Wed, 25 Feb 2026 19:55:37 +0100
Subject: [External] : Re: CFV: New Project: Detroit
In-Reply-To: <50bd073f-451c-488d-bb54-d587ff4a7647@oracle.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
 <50bd073f-451c-488d-bb54-d587ff4a7647@oracle.com>
Message-ID: <CAPG+sN0MLJf=_GZ3wtxQoHPz1QWiPQs5phKC3Wso74O4+3iVdw@mail.gmail.com>

Vote: yes

Mit freundlichen gr??en/Kind Regards
Wasif A. Kirmani
Java Consultant


On Wed, 25 Feb 2026, 7:53 pm Philip Race, <philip.race at oracle.com> wrote:

> Vote: yes
>
> -phil.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/bb7d6c57/attachment.htm>

From vladimir.kozlov at oracle.com  Wed Feb 25 19:10:03 2026
From: vladimir.kozlov at oracle.com (Vladimir Kozlov)
Date: Wed, 25 Feb 2026 11:10:03 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <23457d90-74d9-409f-8d28-74201634de0f@oracle.com>

Vote: yes

On 2/25/26 3:22 AM, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
> 
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
> 
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
> 
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
> 
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
> 
> The initial Committers will be:
> 
>  ? Jim Laskey
>  ? Sundararajan Athijegannathan
>  ? Jorn Vernee
>  ? Mikael Vidstedt
>  ? Henry Jen
>  ? Maurizio Cimadamore
>  ? Alan Bateman
>  ? Hannes Walln?fer
>  ? Jan Lahoda
>  ? Jaikiran Pai
> 
> Votes are due by midnight UTC on Wednesday, 11 March.
> 
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
> 
> For Lazy Consensus voting instructions, see [9].
> 
> Sundar
> 
> 
> [1] https://mail.openjdk.org/pipermail/announce/2018- 
> February/000244.html <https://mail.openjdk.org/pipermail/announce/2018- 
> February/000244.html>
> [2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/ 
> javax/script/package-summary.html <https://docs.oracle.com/en/java/ 
> javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 <https://jcp.org/en/jsr/detail? 
> id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] https://mail.openjdk.org/pipermail/compiler-dev/2024- 
> September/027645.html <https://mail.openjdk.org/pipermail/compiler- 
> dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members <http://openjdk.java.net/ 
> census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote <http:// 
> openjdk.java.net/projects/#new-project-vote>
> 
> 


From vicente.romero at oracle.com  Wed Feb 25 19:30:27 2026
From: vicente.romero at oracle.com (Vicente Romero)
Date: Wed, 25 Feb 2026 14:30:27 -0500
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <286a826d-eeca-4838-8de8-21e84923e702@oracle.com>

vote: yes,

Vicente

On 2/25/26 06:22, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
>
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
>
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
>
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
>
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
>
> The initial Committers will be:
>
> ? Jim Laskey
> ? Sundararajan Athijegannathan
> ? Jorn Vernee
> ? Mikael Vidstedt
> ? Henry Jen
> ? Maurizio Cimadamore
> ? Alan Bateman
> ? Hannes Walln?fer
> ? Jan Lahoda
> ? Jaikiran Pai
>
> Votes are due by midnight UTC on Wednesday, 11 March.
>
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
>
> For Lazy Consensus voting instructions, see [9].
>
> Sundar
>
>
> [1] 
> https://mail.openjdk.org/pipermail/announce/2018-February/000244.html 
> <https://mail.openjdk.org/pipermail/announce/2018-February/000244.html>
> [2] 
> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html 
> <https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 
> <https://jcp.org/en/jsr/detail?id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] 
> https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html 
> <https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members 
> <http://openjdk.java.net/census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote 
> <http://openjdk.java.net/projects/#new-project-vote>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/e440dbde/attachment.htm>

From erik.joelsson at oracle.com  Wed Feb 25 20:20:21 2026
From: erik.joelsson at oracle.com (Erik Joelsson)
Date: Wed, 25 Feb 2026 12:20:21 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <2662a2c3-c626-41fa-9cd1-7579908becbd@oracle.com>

Vote: yes

/Erik

From christian.tornqvist at oracle.com  Wed Feb 25 20:25:57 2026
From: christian.tornqvist at oracle.com (Christian Tornqvist)
Date: Wed, 25 Feb 2026 20:25:57 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <CH3PR10MB735522795ECA9DD8F5D8E8749275A@CH3PR10MB7355.namprd10.prod.outlook.com>

Vote: yes

/ Christian

From: announce <announce-retn at openjdk.org> on behalf of Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com>
Date: Wednesday, February 25, 2026 at 7:35?AM
To: announce at openjdk.org <announce at openjdk.org>
Subject: CFV: New Project: Detroit

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260225/e52c1cff/attachment.htm>

From kevin.rushforth at oracle.com  Wed Feb 25 20:27:45 2026
From: kevin.rushforth at oracle.com (Kevin Rushforth)
Date: Wed, 25 Feb 2026 12:27:45 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <e72a5021-84b3-42b4-9bd3-95ef547df18c@oracle.com>

Vote: YES

-- Kevin


From viktor.klang at oracle.com  Wed Feb 25 21:21:03 2026
From: viktor.klang at oracle.com (Viktor Klang)
Date: Wed, 25 Feb 2026 22:21:03 +0100
Subject: CFV: New Project: Detroit
In-Reply-To: <A1811E28-2C71-462E-8871-22BAD8A76873@oracle.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
 <A1811E28-2C71-462E-8871-22BAD8A76873@oracle.com>
Message-ID: <58b67c88-9f2c-43d2-9e73-4e19cca04ab8@oracle.com>

Vote: yes

-- 
Cheers,
?


Viktor Klang
Software Architect, Java Platform Group
Oracle


From john.r.rose at oracle.com  Wed Feb 25 22:30:27 2026
From: john.r.rose at oracle.com (John Rose)
Date: Wed, 25 Feb 2026 14:30:27 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <67BE74F6-9745-474D-BD7B-D4222105B4DD@oracle.com>

Vote: yes!

This should be very interesting in the context of both Panama and Babylon.

On 25 Feb 2026, at 3:22, Sundararajan Athijegannathan wrote:

> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.

From jaikiran.pai at oracle.com  Thu Feb 26 04:58:41 2026
From: jaikiran.pai at oracle.com (Jaikiran Pai)
Date: Thu, 26 Feb 2026 10:28:41 +0530
Subject: CFV: New Project: Detroit
In-Reply-To: <e3712e6b-cbe1-4877-98e6-bb6600e23f2b@oracle.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
 <e3712e6b-cbe1-4877-98e6-bb6600e23f2b@oracle.com>
Message-ID: <55e5fc17-2ae2-4a4c-accb-e9e90ba80d5f@oracle.com>

vote: yes


-Jaikiran

On 26/02/26 12:10 am, Maurizio Cimadamore wrote:
>
> Vote: yes!
>
>
> Maurizio
>
>
> On 25/02/2026 11:22, Sundararajan Athijegannathan wrote:
>> I hereby propose the (re)creation of the Detroit Project, with myself as
>> the Lead and the Compiler Group as the sponsoring Group.
>>
>> The Detroit Project was originally created in February 2018 [1], with
>> the intent to develop an implementation of the JCP-standard javax.script
>> API [2][3] based on the V8 JavaScript engine [4].? This would enable
>> JavaScript to be used as an extension language for Java applications,
>> and likewise Java libraries to be accessed from JavaScript applications.
>> The Project never got off the ground, however, so it was dissolved in
>> September 2024 [5].
>>
>> Here in February 2026, there is still interest in using Java and
>> JavaScript together.? With the rise of AI, moreover, there is also
>> interest in accessing AI functionality written in Python from Java
>> applications.
>>
>> Some colleagues and I have therefore revived the original prototype
>> JavaScript script engine based on V8, and have also prototyped a Python
>> script engine based on CPython [6]. Using widely-adopted JavaScript
>> and Python implementations, rather than re-implementing JavaScript and
>> Python from scratch, ensures both low long-term maintenance costs and
>> compatibility for existing JavaScript and Python code.
>>
>> We would like to move these prototypes into a proper OpenJDK Project
>> in order to accelerate development.? We expect to leverage and push
>> the boundaries of the FFM API [7], so this work will likely influence
>> Project Panama.? Over time, the Project may consider implementing
>> script engines for additional languages.
>>
>> The initial Committers will be:
>>
>> ? Jim Laskey
>> ? Sundararajan Athijegannathan
>> ? Jorn Vernee
>> ? Mikael Vidstedt
>> ? Henry Jen
>> ? Maurizio Cimadamore
>> ? Alan Bateman
>> ? Hannes Walln?fer
>> ? Jan Lahoda
>> ? Jaikiran Pai
>>
>> Votes are due by midnight UTC on Wednesday, 11 March.
>>
>> Only current OpenJDK Members [8] are eligible to vote on this motion.
>> Votes must be cast in the open on the discuss list.? Replying to this
>> message is sufficient if your mail program honors the Reply-To header.
>>
>> For Lazy Consensus voting instructions, see [9].
>>
>> Sundar
>>
>>
>> [1] 
>> https://mail.openjdk.org/pipermail/announce/2018-February/000244.html 
>> <https://mail.openjdk.org/pipermail/announce/2018-February/000244.html>
>> [2] 
>> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html 
>> <https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html>
>> [3] https://jcp.org/en/jsr/detail?id=223 
>> <https://jcp.org/en/jsr/detail?id=223>
>> [4] https://v8.dev <https://v8.dev>
>> [5] 
>> https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html 
>> <https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html>
>> [6] https://github.com/python/cpython <https://github.com/python/cpython>
>> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
>> [8] http://openjdk.java.net/census#members 
>> <http://openjdk.java.net/census#members>
>> [9] http://openjdk.java.net/projects/#new-project-vote 
>> <http://openjdk.java.net/projects/#new-project-vote>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260226/4a5e2fe9/attachment-0001.htm>

From kevin.walls at oracle.com  Thu Feb 26 08:05:30 2026
From: kevin.walls at oracle.com (Kevin Walls)
Date: Thu, 26 Feb 2026 08:05:30 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <DM3PPF1D4534BE44C9098FF68031EE32F5D9772A@DM3PPF1D4534BE4.namprd10.prod.outlook.com>

Vote: yes



________________________________
From: announce <announce-retn at openjdk.org> on behalf of Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com>
Sent: Wednesday, February 25, 2026 11:22 AM
To: announce at openjdk.org <announce at openjdk.org>
Subject: CFV: New Project: Detroit

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260226/159d3094/attachment.htm>

From hannes.wallnoefer at oracle.com  Thu Feb 26 09:18:06 2026
From: hannes.wallnoefer at oracle.com (Hannes Wallnoefer)
Date: Thu, 26 Feb 2026 09:18:06 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <FD562C4C-AC1E-4CF7-A68B-2F1DF5C676CD@oracle.com>

Vote: yes

Hannes

On 25.02.2026, at 12:22, Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com> wrote:

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev<https://v8.dev/>
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260226/73445e66/attachment-0001.htm>

From fweimer at redhat.com  Thu Feb 26 10:09:42 2026
From: fweimer at redhat.com (Florian Weimer)
Date: Thu, 26 Feb 2026 11:09:42 +0100
Subject: [External] : Re: CFV: New Project: Detroit
In-Reply-To: <CA+3eh10PrN3ck6sPya6CpwB2bJ1tkqqxeAHcoXprHd_5p-DoxQ@mail.gmail.com>
 (Volker Simonis's message of "Wed, 25 Feb 2026 18:00:10 +0100")
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
 <CA+3eh10PrN3ck6sPya6CpwB2bJ1tkqqxeAHcoXprHd_5p-DoxQ@mail.gmail.com>
Message-ID: <lhuzf4voly1.fsf@oldenburg.str.redhat.com>

An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260226/7e03741e/attachment.htm>

From andrea.peruffo1982 at gmail.com  Thu Feb 26 15:57:15 2026
From: andrea.peruffo1982 at gmail.com (Andrea Peruffo)
Date: Thu, 26 Feb 2026 15:57:15 +0000
Subject: [External] : Re: CFV: New Project: Detroit
Message-ID: <CA+D48HQb_j-PN6YFCv4--MAVTADz1gRBqRj5vi+XdKUeyNq1Qg@mail.gmail.com>

Hello,

Thank you for sharing the proposal. I?m excited to hear more about Project
Detroit. I have a few questions I hope could be clarified:

1. Interoperability
How is cross-language interaction intended to work? For example, will
objects and data be shared across boundaries, or mainly passed via
messages? The JSR 223 API does not mandate a shared-heap approach, but it
naturally favors it. I understand this can conflict with isolation and
security goals.

2. Resource model
What does running separate engines (V8, CPython) imply for performance and
resource management, particularly in containerized environments? How are
memory and CPU usage coordinated when multiple engines coexist?

3. Design principles
Could you share the guiding principles for Detroit? Is isolation
prioritized over interoperability, or is the goal to balance both?
Supporting existing ecosystems (JS/Python) seems at odds with achieving
seamless Java interoperability.

Looking forward to learning more about the approach and trade-offs.

Thanks,
Andrea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260226/42806c0d/attachment-0001.htm>

From david.holmes at oracle.com  Thu Feb 26 22:05:06 2026
From: david.holmes at oracle.com (David Holmes)
Date: Fri, 27 Feb 2026 08:05:06 +1000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <19c6009b-f33b-4b67-b986-14d5d301ff14@oracle.com>

Vote: yes

David

On 25/02/2026 9:22 pm, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
> 
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
> 
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
> 
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
> 
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
> 
> The initial Committers will be:
> 
>  ? Jim Laskey
>  ? Sundararajan Athijegannathan
>  ? Jorn Vernee
>  ? Mikael Vidstedt
>  ? Henry Jen
>  ? Maurizio Cimadamore
>  ? Alan Bateman
>  ? Hannes Walln?fer
>  ? Jan Lahoda
>  ? Jaikiran Pai
> 
> Votes are due by midnight UTC on Wednesday, 11 March.
> 
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
> 
> For Lazy Consensus voting instructions, see [9].
> 
> Sundar
> 
> 
> [1] https://mail.openjdk.org/pipermail/announce/2018- 
> February/000244.html <https://mail.openjdk.org/pipermail/announce/2018- 
> February/000244.html>
> [2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/ 
> javax/script/package-summary.html <https://docs.oracle.com/en/java/ 
> javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 <https://jcp.org/en/jsr/detail? 
> id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] https://mail.openjdk.org/pipermail/compiler-dev/2024- 
> September/027645.html <https://mail.openjdk.org/pipermail/compiler- 
> dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members <http://openjdk.java.net/ 
> census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote <http:// 
> openjdk.java.net/projects/#new-project-vote>
> 
> 


From jesper.wilhelmsson at oracle.com  Fri Feb 27 00:08:30 2026
From: jesper.wilhelmsson at oracle.com (Jesper Wilhelmsson)
Date: Fri, 27 Feb 2026 00:08:30 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <1099B9C9-66F0-4CF4-88B6-F8C358735AE2@oracle.com>

Vote: Yes
/Jesper

On 25 Feb 2026, at 12:22, Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com> wrote:

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev<https://v8.dev/>
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260227/ee06c5e0/attachment-0001.htm>

From neugens.limasoftware at gmail.com  Fri Feb 27 13:38:43 2026
From: neugens.limasoftware at gmail.com (Mario Torre)
Date: Fri, 27 Feb 2026 14:38:43 +0100
Subject: [External] : Re: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <C3EFDAD2-DA6C-4FF1-8205-6BB3636B9DAF@gmail.com>

Vote: Yes!

Cheers,
Mario

> On 25. Feb 2026, at 12:22, Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com> wrote:
> 
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
> 
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].  This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
> 
> Here in February 2026, there is still interest in using Java and
> JavaScript together.  With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
> 
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].  Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
> 
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.  We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.  Over time, the Project may consider implementing
> script engines for additional languages.
> 
> The initial Committers will be:
> 
>   Jim Laskey
>   Sundararajan Athijegannathan
>   Jorn Vernee
>   Mikael Vidstedt
>   Henry Jen
>   Maurizio Cimadamore
>   Alan Bateman
>   Hannes Walln?fer
>   Jan Lahoda
>   Jaikiran Pai
> 
> Votes are due by midnight UTC on Wednesday, 11 March.
> 
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.  Replying to this
> message is sufficient if your mail program honors the Reply-To header.
> 
> For Lazy Consensus voting instructions, see [9].
> 
> Sundar
> 
> 
> [1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
> [2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
> [3] https://jcp.org/en/jsr/detail?id=223
> [4] https://v8.dev
> [5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
> [6] https://github.com/python/cpython
> [7] https://openjdk.org/jeps/454
> [8] http://openjdk.java.net/census#members
> [9] http://openjdk.java.net/projects/#new-project-vote



From stuart.marks at oracle.com  Fri Feb 27 19:26:28 2026
From: stuart.marks at oracle.com (Stuart Marks)
Date: Fri, 27 Feb 2026 11:26:28 -0800
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <c98be463-07e9-42a3-8d1f-a6a7dfd291e8@oracle.com>

Vote: yes


On 2/25/26 3:22 AM, Sundararajan Athijegannathan wrote:
> I hereby propose the (re)creation of the Detroit Project, with myself as
> the Lead and the Compiler Group as the sponsoring Group.
>
> The Detroit Project was originally created in February 2018 [1], with
> the intent to develop an implementation of the JCP-standard javax.script
> API [2][3] based on the V8 JavaScript engine [4].? This would enable
> JavaScript to be used as an extension language for Java applications,
> and likewise Java libraries to be accessed from JavaScript applications.
> The Project never got off the ground, however, so it was dissolved in
> September 2024 [5].
>
> Here in February 2026, there is still interest in using Java and
> JavaScript together.? With the rise of AI, moreover, there is also
> interest in accessing AI functionality written in Python from Java
> applications.
>
> Some colleagues and I have therefore revived the original prototype
> JavaScript script engine based on V8, and have also prototyped a Python
> script engine based on CPython [6].? Using widely-adopted JavaScript
> and Python implementations, rather than re-implementing JavaScript and
> Python from scratch, ensures both low long-term maintenance costs and
> compatibility for existing JavaScript and Python code.
>
> We would like to move these prototypes into a proper OpenJDK Project
> in order to accelerate development.? We expect to leverage and push
> the boundaries of the FFM API [7], so this work will likely influence
> Project Panama.? Over time, the Project may consider implementing
> script engines for additional languages.
>
> The initial Committers will be:
>
> ? Jim Laskey
> ? Sundararajan Athijegannathan
> ? Jorn Vernee
> ? Mikael Vidstedt
> ? Henry Jen
> ? Maurizio Cimadamore
> ? Alan Bateman
> ? Hannes Walln?fer
> ? Jan Lahoda
> ? Jaikiran Pai
>
> Votes are due by midnight UTC on Wednesday, 11 March.
>
> Only current OpenJDK Members [8] are eligible to vote on this motion.
> Votes must be cast in the open on the discuss list.? Replying to this
> message is sufficient if your mail program honors the Reply-To header.
>
> For Lazy Consensus voting instructions, see [9].
>
> Sundar
>
>
> [1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html 
> <https://mail.openjdk.org/pipermail/announce/2018-February/000244.html>
> [2] 
> https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html 
> <https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html>
> [3] https://jcp.org/en/jsr/detail?id=223 <https://jcp.org/en/jsr/detail?id=223>
> [4] https://v8.dev <https://v8.dev>
> [5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html 
> <https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html>
> [6] https://github.com/python/cpython <https://github.com/python/cpython>
> [7] https://openjdk.org/jeps/454 <https://openjdk.org/jeps/454>
> [8] http://openjdk.java.net/census#members <http://openjdk.java.net/census#members>
> [9] http://openjdk.java.net/projects/#new-project-vote 
> <http://openjdk.java.net/projects/#new-project-vote>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260227/8fd0aad2/attachment-0001.htm>

From mikael.vidstedt at oracle.com  Fri Feb 27 20:56:04 2026
From: mikael.vidstedt at oracle.com (Mikael Vidstedt)
Date: Fri, 27 Feb 2026 20:56:04 +0000
Subject: CFV: New Project: Detroit
In-Reply-To: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
References: <CY4PR1001MB229587D8180BAF6EAD94A66FEA75A@CY4PR1001MB2295.namprd10.prod.outlook.com>
Message-ID: <CEF158BA-18C5-44C8-8FF4-743B7FC40D83@oracle.com>


Vote: yes

Cheers,
Mikael

On Feb 25, 2026, at 3:22?AM, Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com> wrote:

I hereby propose the (re)creation of the Detroit Project, with myself as
the Lead and the Compiler Group as the sponsoring Group.

The Detroit Project was originally created in February 2018 [1], with
the intent to develop an implementation of the JCP-standard javax.script
API [2][3] based on the V8 JavaScript engine [4].  This would enable
JavaScript to be used as an extension language for Java applications,
and likewise Java libraries to be accessed from JavaScript applications.
The Project never got off the ground, however, so it was dissolved in
September 2024 [5].

Here in February 2026, there is still interest in using Java and
JavaScript together.  With the rise of AI, moreover, there is also
interest in accessing AI functionality written in Python from Java
applications.

Some colleagues and I have therefore revived the original prototype
JavaScript script engine based on V8, and have also prototyped a Python
script engine based on CPython [6].  Using widely-adopted JavaScript
and Python implementations, rather than re-implementing JavaScript and
Python from scratch, ensures both low long-term maintenance costs and
compatibility for existing JavaScript and Python code.

We would like to move these prototypes into a proper OpenJDK Project
in order to accelerate development.  We expect to leverage and push
the boundaries of the FFM API [7], so this work will likely influence
Project Panama.  Over time, the Project may consider implementing
script engines for additional languages.

The initial Committers will be:

  Jim Laskey
  Sundararajan Athijegannathan
  Jorn Vernee
  Mikael Vidstedt
  Henry Jen
  Maurizio Cimadamore
  Alan Bateman
  Hannes Walln?fer
  Jan Lahoda
  Jaikiran Pai

Votes are due by midnight UTC on Wednesday, 11 March.

Only current OpenJDK Members [8] are eligible to vote on this motion.
Votes must be cast in the open on the discuss list.  Replying to this
message is sufficient if your mail program honors the Reply-To header.

For Lazy Consensus voting instructions, see [9].

Sundar


[1] https://mail.openjdk.org/pipermail/announce/2018-February/000244.html
[2] https://docs.oracle.com/en/java/javase/25/docs/api/java.scripting/javax/script/package-summary.html
[3] https://jcp.org/en/jsr/detail?id=223
[4] https://v8.dev<https://v8.dev/>
[5] https://mail.openjdk.org/pipermail/compiler-dev/2024-September/027645.html
[6] https://github.com/python/cpython
[7] https://openjdk.org/jeps/454
[8] http://openjdk.java.net/census#members
[9] http://openjdk.java.net/projects/#new-project-vote

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20260227/b4d0f449/attachment.htm>