Skip to main content

General

Date: 2019-05-07

Present:

  • Dmitry

  • Kenji

  • Kevin

  • David

  • Ivar

Action Items

Reviewed, discussed and updated the GitHub Issues, https://github.com/eclipse-ee4j/ee4j/issues.

Jakarta EE 8

Scope Statements

Scope statements for the API projects must be produced in order to be able to convert them into Specification Projects.

Tracking

https://github.com/orgs/eclipse-ee4j/projects/10

Actions

  • Create a couple of examples and refer to them on the eclipse wiki (Ivar and Wayne)

  • Create an issue for each project with tasks for creating scope statements (Ivar)

  • Set up a board to follow the status of scope statements on GitHub (Ivar)

  • Reach out to projects to create their scope statements (PMC)

  • Wayne will email project leads

  • Get approval from the Spec Committee for the scope statements

  • Verify that the list is complete (Ivar)

  • Progress on names and scope statements

  • PMC will follow up

  • Request steering committee to explain why names must change

Use the traction on the platform mailing list to encourage scope statements to be proposed. Ivar will post a new thread.

Names may be influenced by package names.

Specification Names

Specifications (and the specification projects) must be renamed in order to be converted into Specification Projects.

Tracking

https://github.com/orgs/eclipse-ee4j/projects/11

Actions

  • Set up board to follow the status of renaming (Ivar)

  • Create issues for each project/specification on GitHub (Ivar)

  • Communicate why this is necessary

  • Naming standard communicated to Specification Committee with one +1

  • Publish an official naming standard on the ee4j news web page (Ivar)

  • Get approval from the Spec Committee for the names

Names may be influenced by package names.

Next Meeting

Tuesday, May 21 at 17:00 CEST (11:00 EDT)

Back to the top