[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"

Even better. Will do it this afternoon.

El jue., 4 jul. 2019 12:12, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> escribiÃ:

Or an issue per chapter then the PR will correspond

Â

Â

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Guillermo GonzÃlez de AgÃero
Sent: 04 July 2019 11:11
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Platform and WebProfile specs ready to be "jakarta-ized"

Â

Thanks for the heads-up Kevin. I'll try to help there on the weekend.

Â

I can't do it right now, but I propose we create an issue with a checklist of all chapters, so people can comment and assign specific chapters themselves.

Â

Otherwise we are at risk of duplicating efforts.

Â

El jue., 4 jul. 2019 5:19, Kevin Sutter <sutter@xxxxxxxxxx> escribiÃ:

Hi,
Most of you know that the Java EE Platform and WebProfile specs have now been contributed to Eclipse and ready to go through the transformation to Jakarta Platform and WebProfile specs:
https://github.com/eclipse-ee4j/jakartaee-platform/tree/master/specification

I have broken up the individual specs into slightly more manageable pieces of asciidoc (each spec used to be one giant asciidoc file). I broke them up by chapters. Of course, some are larger than others, but at least we can now divide and conquer the effort in front of us. Many of you have been asking "how can I help?". Now's your chance. If you are interested and available, we would appreciate PRs with cleaning up the various sections of these two spec documents.

The cleanup required is mostly tedious work. Â

  • The main thing is changing "Java EE" to "Jakarta EE". Â
  • Modifying references to the JCP with corresponding Eclipse processes.
  • References to existing Java EE technologies, acronyms, and JSRs are okay as long as they are properly attributed.
  • Be careful not to modify the semantics or behavior -- we need Jakarta EE 8 to be functionally equivalent to Java EE 8.
  • Â

We are looking for the minimal work required. At this point, do not further subdivide the asciidoc files. I would suggest keeping the PRs short and simple. Don't try to do "everything" in one PR. You don't even have to complete a whole chapter in a single PR. Maybe identify the subsections covered in the title of your PR. Shorter PRs will be easier for the committers to evaluate and merge into master. Reference the list of existing PRs before starting on a chapter to avoid duplication of effort.

I am sending out this request now since many of us in the US will be out for the extended weekend. There are a few committers in other parts of the world, so hopefully we'll make some progress over the weekend. I didn't want to wait until Monday to start this effort since we need to have these spec docs ready by July 15.

Thanks for your help!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: Âsutter@xxxxxxxxxx   Twitter: Â@kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office) Â Â
LinkedIn:
https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

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