On 12/05/2017 10:48 AM, Stefan Eissing wrote:
Ok, so that something good comes out of all this: Rich just promised to sing at 
the next ApacheCon, right Rich?

If I did, I must have had too much scotch ...

"Keys", by ManagedDomainFormerlyCalledYouKnowWhat:

"You don't conf certificates
  to turn me on,
  I just give encryption, baby,
  from dusk till dawn."

If you sing it with me, I'm there. :D


Am 05.12.2017 um 15:09 schrieb Daniel <dferra...@gmail.com>:



I understand it it may seem silly to discuss this or that name I think
it will be of great benefit to find a good name in the long run, to
make it easy to recognize and/or user support.

2017-12-05 15:06 GMT+01:00 Stefan Eissing <stefan.eiss...@greenbytes.de>:

Am 05.12.2017 um 15:03 schrieb Luca Toscano <toscano.l...@gmail.com>:

Maybe ManagedDomain and <ManagedDomainDefine>, as iiuc we are going to use for 


2017-12-05 14:47 GMT+01:00 Stefan Eissing <stefan.eiss...@greenbytes.de>:
Totally agree with you. If you make a better proposal that avoids existing 
overlaps, I might just pick it up.


Am 05.12.2017 um 14:40 schrieb Luca Toscano <toscano.l...@gmail.com>:

Hi Stefan,

2017-12-04 14:16 GMT+01:00 Stefan Eissing <stefan.eiss...@greenbytes.de>:
Not much input regarding this naming change. Personally, I like to keep 
'<ManagedDomain' as is.

I propose the following changes:

1. The simple, single line 'ManagedDomain' will be renamed to 'MDGroup'

I personally find the renaming a bit confusing, since visually there is no affinity 
between <ManagedDomain> and MDGroup, but I liked the previous naming so I might 
be biased. If the majority thinks this is the way to go I am fine with it, just 
wanted to express my opinion :)


Daniel Ferradal
IT Specialist

email         dferradal at gmail.com
linkedin     es.linkedin.com/in/danielferradal

Reply via email to