| Hey Andrey,
Thanks for bringing this up as a topic for the IDE WG. I definitely like the idea of funding work in JDT.
One of the main challenges in the past was to actually find individuals who are interested and available to do work like this. So organizing the money is one part of this challenge, finding the person to hire seems to be the huge other part of the challenge.
If you (or anybody) have any suggestions/thoughts/ideas who might be interested in this, please let us know.
Cheers Martin
Hi group, Please check the last part ("Future" topic) in the mail from Stephan below. I know we planned spent money for SWT work.JDT project is currently in no better situation, especially because of fast Java language development and very small size of JDT core team.IMHO We should consider to support JDT project with human resources to make sure Eclipse stays relevant as *Java* IDE too, not just as RCP platform. Means, ideally we would need one or more full time JDT committer working in compiler area. -------- Ursprüngliche Nachricht --------Von: Stephan Herrmann <stephan.herrmann@xxxxxxxxx>Gesendet: 13. September 2022 17:29:14 MESZAn: jdt-dev@xxxxxxxxxxxBetreff: Re: [jdt-dev] General discussion about community (Re: Telling GitHub to rebuild, rebase, ...)Thanks, I think it helps to have this spelled out explicitly.Three comments:Past:In my understanding we owe the precious assets of what is JDT today mostly to the efforts of an excellent team (with sub-teams per component). Most of my own involvement happened as a member of a team.Current changes:I have an itch in my nose that much of this cultural change is happening "accidentally", as a consequence of a switch of technology (which was not the free decision of JDT). That's why I raised questions that to some looked like purely technical in nature, but should be seen with a flavor of discussing our culture. I personally prefer explicit choices over accidental ones :)Future:If the "community" approach wants to prove its superiority, it will have to tackle some hard challenges. JDT is not only about adding some nifty usability features at your leisure, but JDT *must* keep pace with the release schedule of new Java versions. For each new language version, support in JDT starts with heavy work in the compiler. If that fails, all fail. During the last cycles, the Bangalore team (sic) has heroically shouldered that task, with lots of overtime. There have been Java releases, where the power in Bangalore did not suffice (8 & 9), but in those times the team grew until we were able to complete the job. I don't know what will happen when/if, e.g., Project Valhalla will hit the release ramp. I'm not sure JDT - in its new setup - will survive that. Who would want to use a Java IDE that doesn't support the latest versions of Java? For quite some time my offer to train a new compiler engineer has not seen much response. Generally the community doesn't seem to be very keen on compiler maintenance. If the community wants to prove my worries wrong, they better accept this challenge. There is a possibility of terminal failure.good luck,Stephan_______________________________________________jdt-dev mailing listjdt-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev--Kind regards,Andrey Loskutovhttps://www.eclipse.org/user/aloskutovСпасение утопающих - дело рук самих утопающих_______________________________________________eclipse-ide-wg mailing listeclipse-ide-wg@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
|
