Hi Will,
I'm also in the CEST (GMT+2) timezone.
During my working hours, it is not possible for me to join any meeting
online at the client site. But the evenings (20.00h GMT+2 onwards, which I
guess will be the best time), Mondays and Fridays works the best for me.
Regards
Rudy
On 11 October 2016 at 22:22, arjan tijms <arjan.tijms_at_gmail.com> wrote:
> Hi Will,
>
> Glad to have you here, even though you basically were here already ;)
>
> As for the EDR, from the top op my head it's a month from now and
> approximately a year after the last renewal. I'm not too sure though and
> Werner likely knows this much better.
>
> As for the EDR itself, my limited understanding was that it's mainly the
> spec document that has to be handed it with the RI implementation more of
> an extra (for the EDR that is, it's of course required for the final spec
> document).
>
> As for the meeting, what would the medium be? Hangouts chat, slack, or
> something like that? I'm in the CEST timezone (Amsterdam / GMT +2 for the
> coming 2 weeks).
>
> Do we like to set an agenda for the meeting?
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
>
>
> On Tue, Oct 11, 2016 at 8:00 PM, Will Hopkins <will.hopkins_at_oracle.com>
> wrote:
>
>> Hi All,
>>
>> Firstly, I'd like to just say that I'm very happy to be taking on the
>> spec lead role for JSR-375, and looking forward to working with you all to
>> bring it to fruition.
>>
>> I do plan to submit an EDR 1 ASAP. At the moment, though, I'm still
>> getting up to speed on both the content of the JSR and the mechanics of
>> running a JSR, particularly in light of the changes occasioned by the
>> decommissioning of java.net. Question -- does anyone know off-hand what
>> the deadline is for EDR vs. Renewal Ballot? If not, I can find/figure it
>> out on my end, but it wasn't obvious to me looking at the JSR's JCP page,
>> and I haven't yet read the full JCP 2.10 process doc.
>>
>> Once I've digested the existing material, I'd like to meet with the EG to
>> discuss a plan for moving forward, either late this week or early next
>> week. I know we're scattered across a number of time zones -- is there a
>> time/day that's best for most members? If there's a clear consensus I'll
>> go with that; otherwise I'll put something up on SurveyMonkey and we can
>> vote.
>>
>> Lastly, regarding Werner's suggesting that we present at DevoXX US, I'm
>> going to submit a proposal today to present the JSR's work, which I assume
>> will be nearing completion by that time. If anyone has any suggestions as
>> to that content -- or if it conflicts with Ivar's planned presentation --
>> please let me know ASAP. I want to get something in by today's deadline.
>>
>> Thanks!
>>
>> Will
>>
>>
>>
>> On 10/11/2016 08:39 AM, Werner Keil wrote:
>>
>> Btw. not sure if it would be a great effort or e.g. the Jersey team could
>> help us (and Will or Alex), Jersey also has most of its development on
>> GitHub now, but https://github.com/jersey/jersey/ suggests, the mirror
>> works both ways.
>>
>> Something like that would make it easier for 375, too;-)
>>
>> Regards,
>> Werner
>>
>>
>> On Tue, Oct 11, 2016 at 2:20 PM, arjan tijms <arjan.tijms_at_gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Oct 11, 2016 at 1:27 PM, Werner Keil <werner.keil_at_gmail.com>
>>> wrote:
>>>
>>>> Aside from a possible replacement host, what can the EG do to help EDR
>>>> 1 of JSR 375 before a Renewal Ballot would be due?
>>>>
>>>
>>> I guess that writing the spec document would be an important thing to
>>> do. I can surely do that, but then would be great if the new spec lead
>>> could then indeed submit it (perhaps after making some edits if needed).
>>>
>>>
>>>
>>>> The RI Soteria looks in pretty good shape IMO.
>>>> Ideally the "embedded" API folder in Soteria should be moved or at
>>>> least copied into the "spec-api" repository, whether on java.net
>>>> (mirrored to Github) or directly to GitHub is a minor detail.
>>>>
>>>
>>> Indeed, something that should still be done regardless.
>>>
>>> Kind regards,
>>> Arjan Tijms
>>>
>>>
>>>
>>>
>>>>
>>>> A few JSRs (like 330, 310 or JSON-P currently in JSR 374) never
>>>> published a plain text spec in a separate document, anything they
>>>> documented is in JavaDoc so far. It may not be suitable for JSR 375, but
>>>> the spec document could be short or left out of an EDR1.
>>>>
>>>> Kind Regards,
>>>>
>>>> Werner
>>>>
>>>>
>>>> On Mon, Oct 10, 2016 at 7:57 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks for the update Bill!
>>>>>
>>>>> If there's anything I (or any of the EG) can do to help let me/us
>>>>> know.
>>>>>
>>>>> Migrating the JIRA issues manually should be doable for JSR 375,
>>>>> although if more projects are to be moved that way, specially one that have
>>>>> a very old JIRA with literally thousands of issues (like Mojarra), looking
>>>>> at something automated wouldn't hurt really.
>>>>>
>>>>> Kind regards,
>>>>> Arjan Tijms
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Oct 10, 2016 at 7:21 PM, Bill Shannon <bill.shannon_at_oracle.com
>>>>> > wrote:
>>>>>
>>>>>> This subject is under very active discussion at Oracle, but we have
>>>>>> nothing to announce at this time, nor any schedule to share.
>>>>>>
>>>>>> Werner Keil wrote on 10/10/16 4:01 AM:
>>>>>>
>>>>>> Dear All,
>>>>>>
>>>>>> JSR 380 Spec Lead Gunnar Morling just mentioned VisualVM had migrated
>>>>>> from java.net to GitHub: https://visualvm.github.io/
>>>>>>
>>>>>> A project officially run and hosted by Oracle. Is it safe to assume,
>>>>>> others will follow, or do other migration plans exist especially for Java
>>>>>> EE (Glassfish) related projects and JSRs?
>>>>>>
>>>>>> JSR 375 is actually in a rather lucky position since it's relatively
>>>>>> new and has not so much history on java.net as other JSRs.
>>>>>>
>>>>>> JIRA is used by JSR 375, but 36 tickets as of now seem like they
>>>>>> could be migrated to e.g. GitHub issue tracker without a massive effort.
>>>>>>
>>>>>> Waffle (see https://waffle.io/unitsofmeasurement/unit-ri for JSR 363
>>>>>> RI, it only recently moved from JIRA, so there are not so many tickets, as
>>>>>> the JSR is final, we may stick to the tarball or other archives for
>>>>>> historic tickets) allows to put an "agile" layer and it's probably not the
>>>>>> only solution of that kind for the GitHub tracker.
>>>>>>
>>>>>> Btw. as of Friday, the Spec Lead change was updated on jcp.org :-)
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> Werner
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>> --
>> Will Hopkins | Platform Security Architect | +1.781.442.0310
>> Oracle Cloud Application Foundation
>> 35 Network Drive, Burlington, MA 01803
>>
>>
>