Hello!

[Martijn Verburg]

Hi Jacob,

No worries - you can try one of the following:

http://openjdk.markmail.org/
http://openjdk.5641.n7.nabble.com/

Mercurial is actually a lot like Git, except for when it isn't ;-).  Make
sure you read the docs for each command as it and git use different terms
for similar concepts.

Building OpenJDK locally on Linux is fairly trivial, other platforms not so
much.  I'd recommend working in a VM or a Docker container personally

Cheers,
Martijn

On 30 April 2018 at 19:37, Jacob Glickman <jhg023 at bucknell.edu> wrote:

> I apologize in advance, as I know I'm going to have trouble quoting
> snippets of responses.  Anyway, thank you very much for the advice!  I'll
> be sure to search thoroughly before proposing anything, and I'd love to
> discuss my proposed changes and why I believe they should be implemented.
> Also, I'd be happy to fully code, test, and write documentation for the
> change (if accepted, of course).  Unfortunately I've never used Mercurial
> before, so I can imagine that it'll be overwhelming at first like you said.
>
> > Feel free to write up your proposal here first :-)
>
> Meanwhile, I'll do some searching and possibly write up a proposal to be
> sent here first for feedback before submitting it to 'core-libs'.  Does
> there happen to be an efficient way to search through the mailing list?  If
> not, I reckon I could download the text versions and write something to
> parse through it (if that's allowed).  Thanks again!
>
> - Jacob
>
> On Mon, Apr 30, 2018 at 2:17 PM, Martijn Verburg <martijnverburg at gmail.com
> > wrote:
>
>> Hi Jacob,
>>
>> Responses inline!
>>
>> On 30 April 2018 at 18:25, Jacob Glickman <jhg023 at bucknell.edu> wrote:
>>
>>> I originally posted this in 'discuss', but was redirected to here.
>>>
>>> Hello!  My name is Jacob, and I just joined as an OpenJDK contributor the
>>> other day.  I have a plethora of ideas regarding new methods to add to
>>> existing APIs; however, I'm not entirely sure how to go about proposing
>>> them (or, at least, *where* to propose them).  Specifically, I was
>>> looking
>>> for the mailing list that covers Java's Collections API, but I'm not sure
>>> which one that would be (if I had to guess, it would be jdk-dev).
>>
>>
>> Proposals would go to core-libs first but it's *highly* recommended that
>> you:
>>
>> a.) Check that this proposal or one like it hasn't been raised before
>> both in the mailing list
>> archives http://mail.openjdk.java.net/pipermail/core-libs-dev/ and in
>> the JBUG database
>> https://bugs.openjdk.java.net/secure/Dashboard.jspa
>>
>> Feel free to write up your proposal here first :-)
>>
>> b.) Be prepared to discuss the change first
>>
>> c.) If everyone agrees be prepared to fully code, test and build the
>> changes
>> on the appropriate forest.  The Adopt Build Farm can help here.
>>
>>
>>> I've read over the "How to Contribute" page as well, but I'm still
>>> confused
>>> regarding how to build the JDK (or even where to get the files from to
>>> make
>>> changes).  If anyone could provide me with some tips that helped them
>>> when
>>> they joined, I would be very grateful!
>>>
>>
>> OpenJDK uses Mercurial Forests and the development is is done on
>> mainline:
>>
>> See http://openjdk.java.net/projects/jdk/ for details
>>
>> The Adopt Build Farm has build scripts and infra if you want to test on
>> other platforms.
>>
>> There's an awful lot to get your head around and things to do before you
>> can get patches
>> accepted, but it's worth the effort!
>>
>> Cheers,]
>> Martijn
>>
>>
>>
>>
>>>
>>> - Jacob
>>>
>>
>>
>