|
Mikael,
Attached is a CSV with my recommended updates. I only added a
couple of other changes, just to clarify a few names that seemed
confusing, to me. I added EE4J at the start of all these lists so
one could type EE4J in the mailing list search tool, and see all
these in one view.
If anyone has objections, please voice them.
-- Ed
On 10/10/2018 11:23 AM, Ed Bratt wrote:
Right. No resource changes, just description changes.
Is there a limit to the length of these descriptions? Looking
at these, it would be nice (but increases the verbosity) to have
a common text element, maybe "EE4J," for all of these so a
simple text lookup would return all the lists.
-- Ed
On 10/10/2018 8:57 AM, Mikaël Barbero
wrote:
I was not suggesting to change the repository or project name
either.
* I was suggesting to use project names in the
mailing list names.
* Arjan was suggesting to use the repository names
in the mailing list names.
You cannot change project name anyway (at least
not by a simple bugzilla request).
Cheers,
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
_______________________________________________
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
|
