Re: On the command line tools ....

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi William,

I am not expert of CLI/UI so I would just comment as novice user.

389-ds 1.4, brings a brand new CLI/UI.
To be less disruptive, the web UI reuse a lot the ideas of former java console. It allows fine tuning and shows some nasty internal details that in the future we may want to hide to make it more user friendly.  UI using CLI, the CLI need to support those nasty details and UI relies low-level CLI I agree to create  high-level CLI that will hide the complexity of 389-ds internals. But I do not feel it should be one or the other, we could have both and high-level CLI could be based on a robust set of low-level CLI.

It is both too early and too late to change the CLI. Too early because 389-ds 1.4 is just out of the door and we have not yet feedback from users to know what should be imporve. It is too late because users will adopt this new CLI/UI, create their own scripts and we will need to be backward compatible. So IMHO there is only one way to go, fix the CLI bugs and extend the CLI set following your approach.

Simon proposed an action plan (update design, review/agreement of the team, coding/deprecation) that looks quite good to me.

best regards
thierry

On 5/27/19 2:12 AM, William Brown wrote:
Of course, I am opened for the discussion on the plan and the vision.
As Mark has pointed out, we should really gather here and decide as a team. :)

Yeah, I think this is the important point. In the past I did not do well with this, so I think it's important we do it as a team. We really also should engage with people (but some mailing list feedback has already been positive though). Something to keep in mind, is that confusion about how a tool is used, is possibly a point of usability issue we could resolve.

With a weekend of reflection, I think that Mark's suggestion of leaving what we have, and maybe adding a dstask or something in parallel may be the easiest way to achieve this with the least disruption. There is plenty on my plate for now, so I think there is no rush to make changes here ...

Thank you all

Regards,
Simon
—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Directory Announce]     [Fedora Users]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [CentOS]     [Fedora SELinux]     [Big List of Linux Books]     [KDE Users]     [Fedora Art]     [Fedora Docs]

  Powered by Linux