On 8.3.2017 10:30, Martin Babinsky wrote:
On Tue, Feb 28, 2017 at 01:29:50PM +0100, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of user short name -> fully-qualified name resolution.[1]
In the end I have taken the liberty
On Tue, Feb 28, 2017 at 01:29:50PM +0100, Martin Babinsky wrote:
>Hello list,
>
>I have put together a draft of design page describing server-side
>implementation of user short name -> fully-qualified name resolution.[1]
>
>In the end I have taken the liberty to change a few aspects of the design w
On Wed, Mar 08, 2017 at 07:37:40AM +0100, Jan Cholasta wrote:
>On 7.3.2017 15:14, Simo Sorce wrote:
>> On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
>> > On 03/06/2017 01:48 PM, Simo Sorce wrote:
>> > > On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
>> > > > On 03/02/2017 02:
On 7.3.2017 15:14, Simo Sorce wrote:
On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
On 03/06/2017 01:48 PM, Simo Sorce wrote:
On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
On 03/02/2017 02:54 PM, Simo Sorce wrote:
On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote
On 07.03.2017 15:41, Martin Babinsky wrote:
> On Tue, Mar 07, 2017 at 04:34:42PM +0200, Alexander Bokovoy wrote:
>> On ti, 07 maalis 2017, Simo Sorce wrote:
>>> On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
On 03/06/2017 01:48 PM, Simo Sorce wrote:
> On Mon, 2017-03-06 at 07:
On Tue, Mar 07, 2017 at 04:34:42PM +0200, Alexander Bokovoy wrote:
>On ti, 07 maalis 2017, Simo Sorce wrote:
>> On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
>> > On 03/06/2017 01:48 PM, Simo Sorce wrote:
>> > > On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
>> > >> On 03/02/
On ti, 07 maalis 2017, Simo Sorce wrote:
On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
On 03/06/2017 01:48 PM, Simo Sorce wrote:
> On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
>> On 03/02/2017 02:54 PM, Simo Sorce wrote:
>>> On Thu, 2017-03-02 at 08:10 +0100, Martin Babi
On Tue, 2017-03-07 at 09:38 +0100, Martin Babinsky wrote:
> On 03/06/2017 01:48 PM, Simo Sorce wrote:
> > On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
> >> On 03/02/2017 02:54 PM, Simo Sorce wrote:
> >>> On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote:
> In this case it w
On 03/06/2017 01:48 PM, Simo Sorce wrote:
On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
On 03/02/2017 02:54 PM, Simo Sorce wrote:
On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote:
In this case it would probably be a good idea to think about "forward
compatibility" and defin
On Mon, 2017-03-06 at 07:47 +0100, Martin Babinsky wrote:
> On 03/02/2017 02:54 PM, Simo Sorce wrote:
> > On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote:
> >> In this case it would probably be a good idea to think about "forward
> >> compatibility" and define a new AUX objectclass bringin
On 03/02/2017 02:54 PM, Simo Sorce wrote:
On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote:
In this case it would probably be a good idea to think about "forward
compatibility" and define a new AUX objectclass bringing in
'ipaDomainResolutionOrder' instead of extending two separate
objec
On 03/02/2017 04:11 PM, Jakub Hrozek wrote:
On Thu, Mar 02, 2017 at 02:47:24PM +0100, Martin Babinsky wrote:
On 03/02/2017 10:25 AM, Jakub Hrozek wrote:
On Thu, Mar 02, 2017 at 08:12:04AM +0100, Martin Babinsky wrote:
On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Sim
On Thu, Mar 02, 2017 at 02:47:24PM +0100, Martin Babinsky wrote:
> On 03/02/2017 10:25 AM, Jakub Hrozek wrote:
> > On Thu, Mar 02, 2017 at 08:12:04AM +0100, Martin Babinsky wrote:
> > > On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
> > > > On ke, 01 maalis 2017, Simo Sorce wrote:
> > > > > > > M
On Thu, 2017-03-02 at 08:10 +0100, Martin Babinsky wrote:
> In this case it would probably be a good idea to think about "forward
> compatibility" and define a new AUX objectclass bringing in
> 'ipaDomainResolutionOrder' instead of extending two separate
> objectclasses. In this way we may the j
On 03/02/2017 10:25 AM, Jakub Hrozek wrote:
On Thu, Mar 02, 2017 at 08:12:04AM +0100, Martin Babinsky wrote:
On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Simo Sorce wrote:
My take is: cut API/UI work, and do the underlying infrastructure work
for the widest set of se
On Thu, Mar 02, 2017 at 08:12:04AM +0100, Martin Babinsky wrote:
> On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
> > On ke, 01 maalis 2017, Simo Sorce wrote:
> > > > > My take is: cut API/UI work, and do the underlying infrastructure work
> > > > > for the widest set of serves/clients possible i
On to, 02 maalis 2017, Jan Cholasta wrote:
"No value is set in configuration => use built-in default / some value
is set configuration => use the value" is perfectly user friendly and
pretty much common virtually everywhere I believe, much more so than
"empty value is set in configuration => igno
On 1.3.2017 14:58, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 14:05, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 13:39, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48
On 03/01/2017 05:28 PM, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Simo Sorce wrote:
> My take is: cut API/UI work, and do the underlying infrastructure work
> for the widest set of serves/clients possible instead.
>
> It is much more important to get the underlying gears done than to add
>
On 03/01/2017 05:51 PM, Simo Sorce wrote:
On Wed, 2017-03-01 at 17:29 +0100, Martin Basti wrote:
On 01.03.2017 17:04, Simo Sorce wrote:
On Wed, 2017-03-01 at 16:47 +0100, Martin Babinsky wrote:
On 03/01/2017 04:32 PM, Simo Sorce wrote:
On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote
On Wed, 2017-03-01 at 17:29 +0100, Martin Basti wrote:
>
> On 01.03.2017 17:04, Simo Sorce wrote:
> > On Wed, 2017-03-01 at 16:47 +0100, Martin Babinsky wrote:
> >> On 03/01/2017 04:32 PM, Simo Sorce wrote:
> >>> On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote:
> On 03/01/2017 03:42
On 01.03.2017 17:04, Simo Sorce wrote:
On Wed, 2017-03-01 at 16:47 +0100, Martin Babinsky wrote:
On 03/01/2017 04:32 PM, Simo Sorce wrote:
On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote:
On 03/01/2017 03:42 PM, Simo Sorce wrote:
On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky w
On ke, 01 maalis 2017, Simo Sorce wrote:
> My take is: cut API/UI work, and do the underlying infrastructure work
> for the widest set of serves/clients possible instead.
>
> It is much more important to get the underlying gears done than to add
> UI candy, that can be delayed.
>
> Simo.
>
I agr
On Wed, 2017-03-01 at 16:47 +0100, Martin Babinsky wrote:
> On 03/01/2017 04:32 PM, Simo Sorce wrote:
> > On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote:
> >> On 03/01/2017 03:42 PM, Simo Sorce wrote:
> >>> On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky wrote:
> Hello list,
> >>>
On 03/01/2017 04:32 PM, Simo Sorce wrote:
On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote:
On 03/01/2017 03:42 PM, Simo Sorce wrote:
On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation
On Wed, 2017-03-01 at 16:17 +0100, Martin Babinsky wrote:
> On 03/01/2017 03:42 PM, Simo Sorce wrote:
> > On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky wrote:
> >> Hello list,
> >>
> >> I have put together a draft of design page describing server-side
> >> implementation of user short name ->
On 03/01/2017 03:42 PM, Simo Sorce wrote:
On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of user short name -> fully-qualified name resolution.[1]
In the end I have taken the liberty to chan
On Tue, 2017-02-28 at 13:29 +0100, Martin Babinsky wrote:
> Hello list,
>
> I have put together a draft of design page describing server-side
> implementation of user short name -> fully-qualified name resolution.[1]
>
> In the end I have taken the liberty to change a few aspects of the
> desig
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 14:05, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 13:39, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helm
On 1.3.2017 14:05, Alexander Bokovoy wrote:
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 13:39, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
On ke, 01 maalis 2017, Jan Cholasta wrote:
On 1.3.2017 13:39, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page d
On ke, 01 maalis 2017, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of
On 1.3.2017 13:39, Martin Babinsky wrote:
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of user
Alexander,
thank you for your comments. Replies inline:
On 02/28/2017 01:48 PM, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of user short name -> fully-qualified name resolut
On ke, 01 maalis 2017, David Kupka wrote:
On Tue, Feb 28, 2017 at 02:48:02PM +0200, Alexander Bokovoy wrote:
On ti, 28 helmi 2017, Martin Babinsky wrote:
> Hello list,
>
> I have put together a draft of design page describing server-side
> implementation of user short name -> fully-qualified nam
On Tue, Feb 28, 2017 at 02:48:02PM +0200, Alexander Bokovoy wrote:
> On ti, 28 helmi 2017, Martin Babinsky wrote:
> > Hello list,
> >
> > I have put together a draft of design page describing server-side
> > implementation of user short name -> fully-qualified name resolution.[1]
> >
> > In the e
On ti, 28 helmi 2017, Martin Babinsky wrote:
Hello list,
I have put together a draft of design page describing server-side
implementation of user short name -> fully-qualified name
resolution.[1]
In the end I have taken the liberty to change a few aspects of the
design we have agreed on bef
Hello list,
I have put together a draft of design page describing server-side
implementation of user short name -> fully-qualified name resolution.[1]
In the end I have taken the liberty to change a few aspects of the
design we have agreed on before and I will be grad if we can discuss
them
38 matches
Mail list logo