User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
I would love to see a plan for how and when all the project IDs are
going to be changed... Is that something the spec committee should
be driving? Or perhaps the PMC?
We're going to have to change project short names/ids at
some point as well (e.g., "ee4j.jaspic" becomes
"ee4j.authentication", website becomes eclipse.org/ee4j/authentication,
etc.). This sort of change has a broader impact as we use the
id as a key to connect things like LDAP, builds, websites, ...
to the project. I'd hoped that we might be able to batch some
of them to make it easier on the webmaster, but that may just
be more trouble than it's worth. I'll leave it to you to
decide whether you want to change the project id now or just
the GitHub repository now and do the rest later.
Consistency is good, so I like the idea of
updating short names, ids, and Git repo names (after the
dust has settled on Jakarta EE 8), but I defer to the
collective wisdom of the Specification Committee and
PMC.
When the time comes, we'll have to engage the
Eclipse Webmaster to make the changes.
I support renaming the
repos, but like Scott says don't let it impact
the ability to get this release done. The new
name should be just
"eclipse-ee4j/authentication". This also
involves changing all the short names and ids in
the Eclipse project structure.
Scott Stark wrote on 7/11/19 9:53 AM:
As long as it does not
impact anyone else trying to get releases out
the door I don’t see a problem with it.
I know we can continue
to use the old project
names, but should we?
Github will
automatically put a
redirect in place for the
old name, so that keeps
working.
Additionally, projects
on GitHub have a
description, but only
admins can change those.
For instance JASPIC now
says: "jaspic project:.
I'm not admin on any of
the projects, so I think
Dmitry or Wayne would have
to change these.