The Ideals of Cockpit [1] says that "Users of Cockpit should feel they
are interacting with the underlying Server OS, not with Cockpit." so we
took extra care to make sure Cockpit is not something that is directly
visible to the end user.
Peter Volpe is currently working on integration between ManageIQ and
Cockpit.
The idea is that you can get an overview of a cluster in ManageIQ, but
then dive in, by clicking a button, to a particular node by and
administer that with Cockpit.
Initially the button was labeled "Cockpit", so we had to come up with a
better label. Peter, me, Stef and Ben discussed this back and forth a
bit with the ManageIQ designers, and settled on "Access Web Console" in
the end.
(I am fully aware that this wording is a very tempting bike-shed to
paint, but it's also consistent with how other ways of interacting with
the server is called across several products.)
Apparently there is something similar in oVirt, so Fabian Deutch was
kind enough to quickly fix that up and have it say "Web Console" as well.
Since I think this is something that will come up more in the future, as
we integrate Cockpit with more products, I thought it would be a good
idea to set up a wiki page with general guidance on how to refer to
Cockpit from another UI.
https://github.com/cockpit-project/cockpit/wiki/Product-Integration
These are only the initial recommendations, and there is probably a ton
of wrinkles to this, so I am pretty sure the document will evolve over time.
1.http://cockpit-project.org/ideals.html
- Andreas
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
