Vetting JEP concepts?

[Thomas Stüfe]

Hi Andy,

David wrote a very good answer, I just wanted to expand on the last point a
bit:

JEPs are a means, not an end. One typically does not set out to write a
JEP. Instead, one usually starts with a problem one wants to solve and
discusses this on the mailing lists.

If, during the discussion, we see that the problem fits certain criteria, a
JEP would be needed. But JEPs come with a lot of red tape and require a
significant amount of investment from other parties. Therefore, we try to
avoid JEPs if possible, opting instead for more low-key processes
(e.g., RFEs with CSRs).

Cheers, Thomas

On Sun, Apr 14, 2024 at 10:45 PM David Alayachew <davidalayachew at gmail.com>
wrote:

> Hello Andy. Thanks for getting involved.
>
> As for how to approach, there's a few steps involved before writing up or
> introducing JEP drafts.
>
> First thing is to find a problem that is either big enough or frequent
> enough that a change makes sense. As for what a big/frequent enough problem
> looks like, look at some of the JEP's -- in-flight, or delivered, that
> address the problems.
>
> Once you find a problem, next step is to hop onto the mailing list most
> relevant to the problem, and see if others in the community feel like it is
> as big/frequent of a problem that you say it is. Here is the list of
> mailing lists -- https://mail.openjdk.org/mailman/listinfo
>
> And if you want some traction, maybe cross post to the Java subreddit
> (with mod approval beforehand!). As long as you are respectful, read the
> documentation so you come informed, and don't jump to conclusions, you
> should find helpful responses in both places. Examples below.
>
> Good -- Why is ABC done this way (again, check ABC docs before hand)/When
> I tried doing ABC, I experienced pain point XYZ
>
> Bad -- ABC feels poorly designed/ABC is wrong/ABC shouldn't be done this
> way -- Understand, literal thousands of people have looked over even the
> darkest corners of the JDK.
>
> If your problem finds traction, next step is bringing up ideas on how to
> solve it. This is not where you start typing up a JEP format. Instead,
> introduce a solution and see if it gets anywhere. Fair warning, this is a
> higher bar to reach, and is usually as far as most ideas go.
>
> If you manage to cross that bar, post again and someone here will be happy
> to show you next steps.
>
> Let me know if you have any questions.
>
> Thank you for reaching out!
> David Alayachew
>
>
> On Sun, Apr 14, 2024 at 12:47 PM Andy Boothe <andy.boothe at gmail.com>
> wrote:
>
>> Hello,
>>
>> I have a couple of ideas for JEPs. What is the best way to vet these
>> concepts before I submit them to the official process? I'd like to confirm
>> that these ideas haven't already been entertained before (I have already
>> checked the existing draft JEPs), and I'd also like to make sure they are
>> even interesting and viable before I waste anyone's time on the official
>> committees.
>>
>> Thank you in advance for all feedback!
>>
>> Andy Boothe
>> *Email*: andy.boothe at gmail.com
>> *Mobile*: (979) 574-1089
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20240415/83a59264/attachment.htm>