[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Minutes from the first EE4J PMC Meeting

Ivar,

I don't want to sound pushy, but I'm wondering if there's been any advances on the Spec Project naming.
PMC was supposed to have met two days ago, but we haven't gotten any updates.

If it won't be too much of a bother, could one of you send a copy of this week's meeting's minutes?Â

Thanks!
Mariano

Mariano Amar

Senior Consultant

email/hangouts:Âmariano.amar@xxxxxxxxxx
skype:Âmarianoamar

AVISO DE CONFIDENCIALIDAD DE CORREO ELECTRÃNICO

Esta comunicaciÃn contiene informaciÃn que es confidencial y tambiÃn puede contener informaciÃn privilegiada. Es para uso exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta que cualquier distribuciÃn, copia o uso de esta comunicaciÃn o la informaciÃn que contiene està estrictamente prohibida. Si usted ha recibido esta comunicaciÃn por error por favor notifÃquelo por correo electrÃnico(info@xxxxxxxxxx) o por telÃfono (+54 11 3249 7503)

This communication contains information that is confidential and may also be privileged. It is for the exclusive use of the recipient. If you are not the intended note that any distribution, copying or use of this communication or the information it contains is strictly prohibited. If you have received this communication in error please notify us by email(info@xxxxxxxxxx) or phone (+54 11 3249 7503)


On Thu, Dec 7, 2017 at 10:48 AM, Daniel Dias Dos Santos <daniel.dias.analistati@xxxxxxxxx> wrote:
Thanks Ivar for sharning.

@Silvio , Thank you for showing an overview, it was great.

--
Daniel Dias dos Santos
Java Developer
Diretor SouJava & JCP Member
Linkedin: http://br.linkedin.com/in/danieldiassantos

2017-12-06 18:19 GMT-02:00 Bill Shannon <bill.shannon@xxxxxxxxxx>:
Nope, sorry. :-)

Guillermo GonzÃlez de AgÃero wrote on 12/6/17 11:01 AM:
That's why I preferred to ask ;)

Could you share any insight of the options being considered?

El miÃ., 6 dic. 2017 20:00, Bill Shannon <bill.shannon@xxxxxxxxxx> escribiÃ:
I didn't say that. :-) Several options are being discussed, we've made no decision yet.

Guillermo GonzÃlez de AgÃero wrote on 12/ 6/17 09:43 AM:
You mean you are considering open sourcing them as opossed to the idea exposed to the JCP EC of new specs just referencing the old documents?

That'd be a great step forward.


El miÃ., 6 dic. 2017 17:59, Bill Shannon <bill.shannon@xxxxxxxxxx> escribiÃ:
We've converted many of our FrameMaker documents to asciidoc using pandoc. But the issue with the spec documents is a legal issue, not a technical issue.

arjan tijms wrote on 12/6/17 6:28 AM:
Hi,

Regarding the spec document sources, a technical obstacle may be that many of the older ones are authored using FrameMaker. This is a format that isn't particularly suited for community/oss contributions. Rewriting it to say AsciiDoc may be a non-trivial task.

Kind regards,
Arjan Tijms



On Wed, Dec 6, 2017 at 3:16 PM, Mike Milinkovich <mike.milinkovich@eclipse-foundation.org> wrote:
On 2017-12-06 4:05 AM, Ondrej MihÃlyi wrote:
What about specification documents (PDFs)? Are they also going to be delivered to the Eclipse foundation and when/in what form?

Ondrej,

That is still an open question that we (the EF) are working on with Oracle and others. We are meeting face-to-face with Oracle later this week to discuss this and numerous other migration-related questions. With apologies, this is one of the topics for which we must ask the community to be patient.

In the meantime, our focus is clear: stand up EE4J as a functioning open source project and community. We don't have a date or plan yet to do so, but the concrete deliverable that we are striving for is to ship a Java EE 8 compliant release from EE4J. Open sourcing the TCKs is a second related and significant milestone.

We need to do a better job of communicating these plans. That is something I personally hope to address next week.

HTH.

--
Mike Milinkovich
mike.milinkovich@eclipse-foundation.org
(m) +1.613.220.3223


_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community


_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community



_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community