Call For Discussion: New Project: Atlantis

[Andrew Dinn]

On 20/11/2018 15:14, Mario Torre wrote:
> On Tue, 2018-11-20 at 15:38 +0100, Thomas Stüfe wrote:
>> I'm worried about fragmentation though. Once we have this project,
>> what is then the role of serviceability-dev? Just smallish everyday
>> fixes? Also, the fact that VM developer feedback is hard to come by
>> is
>> mostly due to a lack of time on their part, and a new mailing list
>> will not fix that.
> 
> Generally projects have their own mailing lists for development until
> they are "finished", I would expect that for this project it would work
> the same, once it's integrated into mainline it becomes part of the
> serviceability code and the project mailing list is folded into
> serviceability-dev, until then it's somewhat an independent unit.
Well, there is a requirement that anything new of a significant size orc
complexity that gets developed under a JEP and then integrated into the
mainline repos will have someone available to maintain it.

JC, can you provide assurance that Google staff involved in pushing any
code upstream will also be available to help perform that maintenance
effort, in this case presumably as members of the serviceability team?

n.b. Modulo the above detail I'm all for this proposal. I'd be very
pleased if the project brings opportunities for Google either to
upstream their existing work to everyone's benefit or, where for
whatever reason that is not feasible, to help tailor existing upstream
capabilities (such as JFR events) so they might encompass Google's
downstream needs.

It's very welcome to see Google so willing to contribute to OpenJDK.

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander