JPMS (JSR 376) EG video conference: Thursday 18 May, 15:00 UTC
David M. Lloyd
david.lloyd at redhat.com
Wed May 17 14:03:01 UTC 2017
On 05/16/2017 09:45 PM, mark.reinhold at oracle.com wrote:
> As you know, the JCP Executive Committee voted last week  not to
> approve this JSR for the next stage of the process. We now have until
> 7 June to submit a revised Specification .
> Time is short, so in order to move quickly I suggest that we hold a
> series of video-conference calls to discuss issues raised by the EC, the
> few remaining open issues on the list , and other issues about which
> new information has recently become available.
> I propose that we meet at 15:00 UTC this Thursday, 18 May  for one
> hour, and again at that same time each business day as needed.
> ==> Please let me know by 23:00 UTC tomorrow, 17 May , if this
> schedule is workable for you. I will send logistical information
> to attendees privately.
It is workable for me. Face-to-face meeting should help us move through
issues much more quickly.
> In order to preserve the integrity of our discussions, these meetings
> should be the sole channel for EG communication once they begin. The
> jpms-spec-experts list will therefore be closed except for the posting
> of the minutes of each meeting and for updates to the issue list and
> the draft Specification as may be agreed during these meetings. All EG
> members will be asked to refrain from posting to other public fora such
> as, e.g., the jigsaw-dev list, until this series of meetings is over.
I do not think this is necessary, helpful, or even possible. For
various reasons, not the least of which is the fundamental obligation of
EG and EC members to do so, Red Hat continuously engages with our
community and customers on this and many other issues, sometimes in
public, and must continue to do so. In addition, public communications
are essential for researching the kinds of technical issues we face,
which will no doubt be necessary as these meetings progress. EG members
must have the latitude to perform such research and solicit opinions,
ideas, and feedback from the community.
I would request that you rely on our dedication to reaching a positive
outcome in this regard. Undermining a productive technical discussion
is not something that will lead us to a "yes" vote, and public
communications are not something that will inherently undermine a
productive technical discussion.
> These meetings are open to current EG members. Each member may invite
> one additional technical representative from that member's organization.
More information about the jpms-spec-observers