I wasn't intending to change the repository or project names, but
we could do that as well. I'll leave that to the general community
for more input. Other relatively obscure list names are ca-dev
(common annotations), cu-dev (concurrency utilities). In the
mailing list view, they just say: ca developer discussions.
For now, I'll just send you some text to add to the mailing list
descriptions so that the proper developer discussion mailing lists
can be more easily found.
I'll send that in a bit (it's a long list).
Thanks,
-- Ed
On 10/10/2018 2:12 AM, Guillermo
González de Agüero wrote:
+1
Hi,
I'm not greatly bothered by "es", but if possible then
"ee-security" would be the better name, or possibly
"ee-security-api".
Kind regards,
Arjan
The "es" name is perhaps a bit cryptic
indeed. I think Werner made some comments
about this before as well. There's also a
disconnect with the name of the GitHub repo,
which is at https://github.com/eclipse-ee4j/security-api.
"security-api" might have been the better
name for consistency reasons.
It works for project which have a single
repository @ github, but some projects have many
repositories. How should it be named then?
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build
|