On 28.05.20 13:20, Aleksandar Kurtakov wrote:
> On Thu, May 28, 2020 at 1:55 PM S A <simeon.danailov.andreev@xxxxxxxxx
> <mailto:simeon.danailov.andreev@xxxxxxxxx>> wrote:
> [...]
> I can't make a comment on attracting other contributors in JDT.
>
>
> That I can comment :).
Are you speaking from your own experience of working on JDT code (as a new
contributor), or are these words you put into the mouths of others? I'd
appreciate if they speak for themselves.
I speak as the tech lead for Jeff and Roland and discussions on a weekly basis what/how/when/why to do so we can share the burden in JDT with others. Being the one that have pushed for people to work on JDT and the one that has followed up most of the late additions to the team and specifically organizing the team work so JDT team and community can grow - yes I do speak from my own experience and would dare to even say that have a broader view of the project not worse than many committers.
I haven't worked on JDT code itself a lot (releng fixes after incomplete fixes in JDT and -Werror addition) but I would dare to say that non-trivial part of the work in the last few releases has been requested by/approved by/checked by/etc. by me personally incl. freeing time for people to work on JDT and further .
I'm willing to learn from our new contributors. It's among the committers that
we have to find a mode of operation that facilitates collaboration and avoids
stepping on each others' toes. It seems this mode has not yet been found.
> P.S. Only whoever hasn't looked at unreadable JUnit3 test suites results [...]
I'm looking at such results [1] all the time and I see no problem. Do you care
to be more specific?
Stephan
[1]
https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Gerrit/lastStableBuild/testReport/
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
