(replies inline) On Wed, 13 Sep 2017, Oliver Gond??a wrote:
> I suspect this question might have been asked in the room but are we ok with
> the name collisions with Java Enhancement Proposals? Which one we are
> referring to should be straightforward from the context but when this
> becomes more widespread and changes will be refereed to by their IDs, google
> searches will be quite confusing especially given the fact the areas are
> somewhat related. How about JIP? or JEEP :P
If I recall correctly, Jesse did mention the Java Enhancement Proposals acronym
collision at the Contributor Summit.
Personally, I'm not bothered at all by it at since jenkins.io and
openjdk.java.net are pretty distinguishable. If the acronym is of extremely high
importance to somebody, I don't mind changing to something similarly short and
understandable. No yak-shaving on acronyms allowed though :P
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/20170913200637.p32pkmumum54a7wg%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
