<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 29/01/2024 05:45, David Alayachew wrote:<br>
<blockquote type="cite" cite="mid:CAA9v-_Mkhv=9hQzV=-wATmhP9kKZF=v_Ag0RqTxZA2UhLd=+zw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default" style="font-family:monospace">Hello
Phil,</div>
<div class="gmail_default" style="font-family:monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace">Thank
you for your response!</div>
<div class="gmail_default" style="font-family:monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace">I will
start hunting around for a sponsor.</div>
<div class="gmail_default" style="font-family:monospace"><br>
</div>
</div>
</blockquote>
Ignore the CSR and sponsorship for now. The starting point for
proposals for new APIs is to discuss and get some agreement first.
As the OpenJDK developer's guide puts it "Socialize your change"
[1]. Starting with code and PR is often counter productive as the
starting point for APIs.<br>
<br>
-Alan<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://openjdk.org/guide/#socialize-your-change">https://openjdk.org/guide/#socialize-your-change</a><br>
</body>
</html>