Re: [jakarta.ee-spec.committee] GitHub repository naming conventions?

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

I have no strong opinion.

The PMC has made a recommendation that specification documents be represented in existing API repositories. At least a few project teams have expressed a desire to do this. I'm sure that some project teams will make other decisions. So, there will likely be few "wombat-spec" repositories.

As part of the restructuring review, I am assuming that projects will use existing "API" repositories. If a project team wants a separate "spec" repository, they can ask for one.

Wayne

On Tue, Jun 18, 2019 at 6:22 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Have we decided on naming conventions for the GitHub repositories
that are part of specification projects?  For example, will we have

github.com/eclipse-ee4j/wombat-spec
github.com/eclipse-ee4j/wombat-tck
github.com/eclipse-ee4j/wombat-api

(Ignoring the eventual "eclipse-ee4j" -> "jakartaee" renaming.)

Will there be a

github.com/eclipse-ee4j/wombat

repository?  And what would it contain?

Which one of the above repositories would host the GitHub Pages web site?
eclipse-ee4j.github.io/wombat-spec?

Would we expect GitHub Pages web sites for the other repos?  What would
they contain?

And when should we use a GitHub Pages web site vs. a GitHub Wiki?

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.